Differentiated Service Code Point and Explicit Congestion Notification Monitoring in Two-Way Active Measurement Protocol (TWAMP)
draft-ietf-ippm-type-p-monitor-02

The information below is for an old version of the document
Document Type Active Internet-Draft (ippm WG)
Last updated 2015-10-22 (latest revision 2015-05-20)
Replaces draft-hedin-ippm-type-p-monitor
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication (wg milestone: Jul 2015 - Submit draft on DSCP... )
Document shepherd Brian Trammell
Shepherd write-up Show (last changed 2015-10-07)
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Spencer Dawkins
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                           J. Hedin
Internet-Draft                                                 G. Mirsky
Intended status: Standards Track                         S.  Baillargeon
Expires: November 21, 2015                                      Ericsson
                                                            May 20, 2015

 Differentiated Service Code Point and Explicit Congestion Notification
       Monitoring in Two-Way Active Measurement Protocol (TWAMP)
                   draft-ietf-ippm-type-p-monitor-02

Abstract

   This document describes an OPTIONAL extension for Two-Way Active
   Measurement Protocol (TWAMP) allowing the monitoring of the
   Differentiated Service Code Point and Explicit Congestion
   Notification fields with the TWAMP-Test protocol.

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 November 22, 2015.

Copyright Notice

   Copyright (c) 2015 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

Hedin, et al.           Expires November 22, 2015               [Page 1]

Internet-Draft      DSCP and ECN Monitoring in TWAMP            May 2015

   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 Monitor DSCP and ECN . . . . . .   3
     2.2.  TWAMP-Test Extension  . . . . . . . . . . . . . . . . . .   4
       2.2.1.  Session-Reflector Packet Format for DSCP and ECN
               Monitoring  . . . . . . . . . . . . . . . . . . . . .   4
       2.2.2.  DSCP and ECN Monitoring with RFC 6038 extensions  . .   7
       2.2.3.  Consideration for TWAMP Light mode  . . . . . . . . .   8
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   One-Way Active Measurement Protocol (OWAMP) [RFC4656] defines Type-P
   descriptor and negotiation of its value in OWAMP-Control protocol.
   Two-Way Active Measurement Protocol (TWAMP) [RFC5357] states that
   only Differentiated Service Code Point (DSCP) values 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.
   However the TWAMP-Test protocol does not specify any methods to
   determine or report when the DSCP value has changed or is different
   than expected in the forward or reverse direction.  Re-marking the
   DSCP (changing its original value) in IP networks is possible and
   often accomplished by a Diffserv policy configured on a single node
   along the IP path.  In many cases, a change of the DSCP value
   indicates an unintentional or erroneous behavior.  At best, the
   Session-Sender can detect a change of the DSCP reverse direction
   assuming such change is actually detectable.

   This document describes an OPTIONAL feature for TWAMP.  It is called
   the DSCP and ECN monitoring feature.  This feature allows the
   Session-Sender to know the actual DSCP value received at the Session-
Show full document text