IPv6 Updates for IPPM's Active Metric Framework
draft-ietf-ippm-2330-ipv6-01

Document Type Active Internet-Draft (ippm WG)
Last updated 2017-03-06
Replaces draft-morton-ippm-2330-stdform-typep
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          A. Morton
Internet-Draft                                                 AT&T Labs
Updates: 2330 (if approved)                                    J. Fabini
Intended status: Informational                                   TU Wien
Expires: September 7, 2017                                     N. Elkins
                                                   Inside Products, Inc.
                                                            M. Ackermann
                                      Blue Cross Blue Shield of Michigan
                                                                V. Hegde
                                                              Consultant
                                                           March 6, 2017

            IPv6 Updates for IPPM's Active Metric Framework
                      draft-ietf-ippm-2330-ipv6-01

Abstract

   This memo updates the IP Performance Metrics (IPPM) Framework RFC
   2330 with new considerations for measurement methodology and testing.
   It updates the definition of standard-formed packets in RFC 2330 to
   include IPv6 packets and augments distinguishing aspects of packets,
   referred to as Type-P for test packets in RFC 2330.  This memo
   identifies that IPv4-IPv6 co-existence can challenge measurements
   within the scope of the IPPM Framework.  Exemplary use cases include,
   but are not limited to IPv4-IPv6 translation, NAT, protocol
   encapsulation, or IPv6 header compression.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Morton, et al.          Expires September 7, 2017               [Page 1]
Internet-Draft              IPPM IPv6 Update                  March 2017

   This Internet-Draft will expire on September 7, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Packets of Type-P . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Standard-Formed Packets . . . . . . . . . . . . . . . . . . .   5
   5.  NAT, IPv4-IPv6 Transition and Compression Techniques  . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   The IETF IP Performance Metrics (IPPM) working group first created a
   framework for metric development in [RFC2330].  This framework has
   stood the test of time and enabled development of many fundamental
   metrics.  It has been updated in the area of metric composition
   [RFC5835], and in several areas related to active stream measurement
   of modern networks with reactive properties [RFC7312].

   The IPPM framework [RFC2330] recognized (in section 13) that many
Show full document text