Diffserv-Interconnection classes and practice
draft-ietf-tsvwg-diffserv-intercon-06

The information below is for an old version of the document
Document Type Active Internet-Draft (tsvwg WG)
Last updated 2016-08-23 (latest revision 2016-06-20)
Replaces draft-geib-tsvwg-diffserv-intercon
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication (wg milestone: Jan 2016 - Submit 'DiffServ int... )
Document shepherd Gorry Fairhurst
Shepherd write-up Show (last changed 2016-08-23)
IESG IESG state AD Evaluation::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Responsible AD Spencer Dawkins
Send notices to "Gorry Fairhurst" <gorry@erg.abdn.ac.uk>
TSVWG                                                       R. Geib, Ed.
Internet-Draft                                          Deutsche Telekom
Intended status: Informational                                  D. Black
Expires: December 22, 2016                               EMC Corporation
                                                           June 20, 2016

             Diffserv-Interconnection classes and practice
                 draft-ietf-tsvwg-diffserv-intercon-06

Abstract

   This document defines a limited common set of Diffserv PHBs and
   codepoints (DSCPs) to be applied at (inter)connections of two
   separately administered and operated networks, and explains how this
   approach can simplify network configuration and operation.  Many
   network providers operate MPLS using Treatment Aggregates for traffic
   marked with different Diffserv PHBs, and use MPLS for interconnection
   with other networks.  This document offers a simple interconnection
   approach that may simplify operation of Diffserv for network
   interconnection among providers that use MPLS and apply the Short-
   Pipe tunnel mode.

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 December 22, 2016.

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

Geib & Black            Expires December 22, 2016               [Page 1]

Internet-Draft              Diffserv-Intercon                  June 2016

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Related work  . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Applicability Statement . . . . . . . . . . . . . . . . .   4
     1.3.  Document Organization . . . . . . . . . . . . . . . . . .   5
   2.  MPLS and the Short Pipe tunnel model  . . . . . . . . . . . .   5
   3.  Relationship to RFC 5127  . . . . . . . . . . . . . . . . . .   6
     3.1.  RFC 5127 Background . . . . . . . . . . . . . . . . . . .   6
     3.2.  Differences from RFC 5127 . . . . . . . . . . . . . . . .   7
   4.  The Diffserv-Intercon Interconnection Classes . . . . . . . .   8
     4.1.  Diffserv-Intercon Example . . . . . . . . . . . . . . . .   9
     4.2.  End-to-end QoS: PHB and DS CodePoint Transparency . . . .  12
     4.3.  Treatment of Network Control traffic at carrier
           interconnection interfaces  . . . . . . . . . . . . . . .  13
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Appendix A.  Appendix A The MPLS Short Pipe Model and IP traffic   16
   Appendix B.  Change log (to be removed by the RFC editor) . . . .  20
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   Diffserv has been deployed in many networks; it provides
   differentiated traffic forwarding based on the Diffserv Codepoint
   (DSCP) field [RFC2474].  This document defines a set of common
   Diffserv QoS classes (Per Hop Behaviors, PHBs)and code points at
   interconnection points to which and from which locally used classes
   and code points should be mapped.

   As described by section 2.3.4.2 of RFC 2475, remarking of packets at
   domain boundaries is a Diffserv feature [RFC2475].  If traffic marked
   with unknown or unexpected DSCPs is received, RFC2474 recommends
Show full document text