Alternate Marking Extension to Active Measurement Protocol
draft-fioccola-ippm-alt-mark-active-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        G. Fioccola
Internet-Draft                                            Telecom Italia
Intended status: Informational                                  A. Clemm
Expires: September 14, 2017                                    S. Bryant
                                                                  Huawei
                                                             M. Cociglio
                                                          Telecom Italia
                                                         M. Chandramouli
                                                           Cisco Systems
                                                              A. Capello
                                                          Telecom Italia
                                                          March 13, 2017

       Alternate Marking Extension to Active Measurement Protocol
                 draft-fioccola-ippm-alt-mark-active-01

Abstract

   This document describes how to extend the existing Active Measurement
   Protocol, in order to implement alternate marking methodology
   detailed in [I-D.ietf-ippm-alt-mark].  The extension for Two-Way
   Active Measurement Protocol (TWAMP) RFC 5357 [RFC5357] and One-way
   Active Measurement Protocol (OWAMP) RFC 4656 [RFC4656] will be
   considered.  RFC6374 [RFC6374] Use Case is also reported.  This
   proposal defines a simplified mechanism with benefits to the metric
   precision and computational load.  Hybrid measurements are also
   enabled.

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

Fioccola, et al.       Expires September 14, 2017               [Page 1]
Internet-Draft          Active Alternate Marking              March 2017

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 14, 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Description of the method . . . . . . . . . . . . . . . . . .   3
     2.1.  Packet loss measurement . . . . . . . . . . . . . . . . .   4
     2.2.  Delay measurement . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Delay variation measurement . . . . . . . . . . . . . . .   6
   3.  Hybrid measurement  . . . . . . . . . . . . . . . . . . . . .   6
   4.  Protocol Extension overview . . . . . . . . . . . . . . . . .   7
     4.1.  Control Phase . . . . . . . . . . . . . . . . . . . . . .   8
     4.2.  Test Phase  . . . . . . . . . . . . . . . . . . . . . . .   8
     4.3.  Calculation Phase . . . . . . . . . . . . . . . . . . . .   9
   5.  Open Issues . . . . . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  Extension of TWAMP/OWAMP Control Protocol . . . . . . . .  10
     5.2.  Extension of TWAMP/OWAMP Test Protocol  . . . . . . . . .  10
   6.  RFC6374 Use Case  . . . . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
Show full document text