IPv4, IPv6, and IPv4-IPv6 Coexistence: Updates for the IP Performance Metrics (IPPM) Framework
RFC 8468
| Document | Type |
RFC - Informational
(November 2018; No errata)
Updates RFC 2330
|
|
|---|---|---|---|
| Authors | Al Morton , Joachim Fabini , Nalini Elkins , mackermann@bcbsm.com , Vinayak Hegde | ||
| Last updated | 2018-11-14 | ||
| Replaces | draft-morton-ippm-2330-stdform-typep | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication (wg milestone: Jul 2018 - submit a Standards T... ) | |
| Document shepherd | Nevil Brownlee | ||
| Shepherd write-up | Show (last changed 2018-03-04) | ||
| IESG | IESG state | RFC 8468 (Informational) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Spencer Dawkins | ||
| Send notices to | Brian Trammell <ietf@trammell.ch>, Nevil Brownlee <n.brownlee@auckland.ac.nz> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) A. Morton
Request for Comments: 8468 AT&T Labs
Updates: 2330 J. Fabini
Category: Informational TU Wien
ISSN: 2070-1721 N. Elkins
Inside Products, Inc.
M. Ackermann
Blue Cross Blue Shield of Michigan
V. Hegde
Consultant
November 2018
IPv4, IPv6, and IPv4-IPv6 Coexistence:
Updates for the IP Performance Metrics (IPPM) Framework
Abstract
This memo updates the IP Performance Metrics (IPPM) framework defined
by RFC 2330 with new considerations for measurement methodology and
testing. It updates the definition of standard-formed packets to
include IPv6 packets, deprecates the definition of minimal IP packet,
and augments distinguishing aspects, referred to as Type-P, for test
packets in RFC 2330. This memo identifies that IPv4-IPv6 coexistence
can challenge measurements within the scope of the IPPM framework.
Example use cases include, but are not limited to, IPv4-IPv6
translation, NAT, and protocol encapsulation. IPv6 header
compression and use of IPv6 over Low-Power Wireless Area Networks
(6LoWPAN) are considered and excluded from the standard-formed packet
evaluation.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidates for any level of Internet
Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8468.
Morton, et al. Informational [Page 1]
RFC 8468 IPPM IPv6 Update November 2018
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Packets of Type-P . . . . . . . . . . . . . . . . . . . . . . 4
5. Standard-Formed Packets . . . . . . . . . . . . . . . . . . . 5
6. NAT, IPv4-IPv6 Transition, and Compression Techniques . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . 14
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
Morton, et al. Informational [Page 2]
Show full document text