Browse Prior Art Database

Differentiated Service Code Point and Explicit Congestion Notification Monitoring in the Two-Way Active Measurement Protocol (TWAMP) (RFC7750) Disclosure Number: IPCOM000245097D
Original Publication Date: 2016-Feb-01
Included in the Prior Art Database: 2016-Feb-08
Document File: 22 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Hedin: AUTHOR [+3]


The One-Way Active Measurement Protocol (OWAMP) [RFC4656] defines the Type-P Descriptor field and negotiation of its value in the OWAMP- Control protocol. The Two-Way Active Measurement Protocol (TWAMP) [RFC5357] states that only a Differentiated Services Code Point (DSCP) value (see [RFC2474], [RFC3168], and [RFC3260]) can be defined by Type-P Descriptor, and the negotiated value must be used by both the 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 Differentiated Services 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 a change is actually detectable.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

Internet Engineering Task Force (IETF)                          J. Hedin Request for Comments: 7750                                     G. Mirsky Updates: 5357                                            S.  Baillargeon Category: Standards Track                                       Ericsson ISSN: 2070-1721                                            February 2016

  Differentiated Service Code Point and Explicit Congestion Notification      Monitoring in the Two-Way Active Measurement Protocol (TWAMP)


   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 is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

Copyright Notice

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

 Hedin, et al.                Standards Track                    [Page 1]
 RFC 7750            DSCP and ECN Monitoring in TWAMP       February 2016

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