Control and Monitoring Differentiated Service Code Point in Two-Way Active Measurement Protocol (TWAMP)
draft-bailmir-ippm-twamp-dscp-ctrl-mon-02

Document Type Active Internet-Draft (individual)
Last updated 2017-02-21
Stream (None)
Intended RFC status (None)
Formats plain text xml 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. Mirsky
Internet-Draft                                                 ZTE Corp.
Updates: 5357, 7750 (if approved)                        S.  Baillargeon
Intended status: Standards Track                                Ericsson
Expires: August 25, 2017                               February 21, 2017

  Control and Monitoring Differentiated Service Code Point in Two-Way
                  Active Measurement Protocol (TWAMP)
               draft-bailmir-ippm-twamp-dscp-ctrl-mon-02

Abstract

   This document describes an optional extension for Two-Way Active
   Measurement Protocol (TWAMP) allowing control and monitoring of the
   Differentiated Service Code Point (DSCP) field in forward and reverse
   directions within single test session with the TWAMP-Test protocol.
   This document, if accepted, will be an update to the TWAMP core
   protocol specified in RFC 5357 and DSCP Monitoring mode defined in
   RFC 7750 .

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."

   This Internet-Draft will expire on August 25, 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

Mirsky &  Baillargeon    Expires August 25, 2017                [Page 1]
Internet-Draft      Control and Monitor DSCP in TWAMP      February 2017

   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
     1.1.  Conventions used in this document . . . . . . . . . . . .   3
       1.1.1.  Terminology . . . . . . . . . . . . . . . . . . . . .   3
       1.1.2.  Requirements Language . . . . . . . . . . . . . . . .   3
   2.  TWAMP Extensions  . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Setting Up Connection to Test DSCP and ECN  . . . . . . .   4
     2.2.  TWAMP-Test Extension  . . . . . . . . . . . . . . . . . .   4
       2.2.1.  Session-Sender Packet Format for DSCP and ECN Testing   4
       2.2.2.  Combining DSCP and ECN Testing and Monitoring
               extensions  . . . . . . . . . . . . . . . . . . . . .   6
       2.2.3.  DSCP and ECN Testing with RFC 6038 extensions . . . .   6
       2.2.4.  Consideration for TWAMP Light mode  . . . . . . . . .   7
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The One-Way Active Measurement Protocol (OWAMP) [RFC4656] defines the
   Type-P Descriptor field and negotiation of its value in OWAMP-Control
   protocol.  The Two-Way Active Measurement Protocol (TWAMP) [RFC5357]
   states that only a Differentiated Services Code Point (DSCP)
   [RFC2474], [RFC3168], [RFC3260] value can be defined by Type-P
   Descriptor and the negotiated value must be used by both Session-
   Sender and Session-Reflector.  The TWAMP specification also states
   that the same DSCP value (found in the Session-Sender packet) MUST be
   used in the test packet reflected by the Session-Reflector.  The
   [RFC7750] introduced optional DSCP Monitoring mode that can be
   negotiated using TWAMP Control protocol and supported by TWAMP-Test
   protocol or by TWAMP Light mode.  Still the TWAMP-Test protocol does
Show full document text