DSCP mangle detection
draft-martinsen-tram-dscp-mangle-detection-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-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)
TRAM                                                        P. Martinsen
Internet-Draft                                             S. Nandakumar
Intended status: Experimental                                      Cisco
Expires: April 24, 2017                                 October 21, 2016

                         DSCP mangle detection
             draft-martinsen-tram-dscp-mangle-detection-00

Abstract

   This document describes a mechanism for an endpoint to detect DSCP
   "mangling" by the network path.

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 April 24, 2017.

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

Martinsen & Nandakumar   Expires April 24, 2017                 [Page 1]
Internet-Draft            DSCP mangle detection             October 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   2
   3.  Detecting DSCP mangling . . . . . . . . . . . . . . . . . . .   3
     3.1.  DSCP VALUE attribute  . . . . . . . . . . . . . . . . . .   3
     3.2.  Usage in Requests . . . . . . . . . . . . . . . . . . . .   3
     3.3.  Usage in Responses  . . . . . . . . . . . . . . . . . . .   3
     3.4.  Example Operation . . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   In some use-cases is useful to know if the network path changes the
   DSCP/TOS values in the IP header.

   This document introduces a new STUN attribute that can carry the
   original DSCP/TOS values.  This enables the remote receiver to
   compare the values in the IP header and the STUN attribute to detect
   mangling.

   The information in the STUN attribute is probably of little interest
   for the remote receiver.  The main use case is to collect metrics
   regarding how often DSCP values are mangled.

   ICE could potentially also use this information to prefer paths with
   intact DSCP markings.

   (Just assigning an attribute from IANA is possible, but we thought it
   was better to have a draft describing the attribute so everyone knows
   what it is)

2.  Notational Conventions

   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 [RFC2119].

   This specification uses terminology defined in ICE [RFC5245] And STUN
   [RFC5389].

Martinsen & Nandakumar   Expires April 24, 2017                 [Page 2]
Internet-Draft            DSCP mangle detection             October 2016

3.  Detecting DSCP mangling

   Both ICE ICE [RFC5245] connectivity checks and TURN ICE [RFC5766]
   allocations can benefit from detecting if the DSCP bits survives the
   rough journey across the Internet ocean.
Show full document text