Skip to main content

IPv4, IPv6, and IPv4-IPv6 Coexistence: Updates for the IP Performance Metrics (IPPM) Framework
RFC 8468

Revision differences

Document history

Date By Action
2021-06-09
Amy Vezza Downref to RFC 8468 approved by Last Call for draft-ietf-ippm-capacity-metric-method-12
2019-08-19
Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2019-08-19
Gunter Van de Velde Assignment of request for Last Call review by OPSDIR to Tim Wicinski was marked no-response
2018-11-14
(System)
Received changes through RFC Editor sync (created alias RFC 8468, changed title to 'IPv4, IPv6, and IPv4-IPv6 Coexistence: Updates for the IP Performance Metrics …
Received changes through RFC Editor sync (created alias RFC 8468, changed title to 'IPv4, IPv6, and IPv4-IPv6 Coexistence: Updates for the IP Performance Metrics (IPPM) Framework', changed abstract to '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.', changed standardization level to Informational, changed state to RFC, added RFC published event at 2018-11-14, changed IESG state to RFC Published, created updates relation between draft-ietf-ippm-2330-ipv6 and RFC 2330)
2018-11-14
(System) RFC published