DiffServ interconnection classes and practice
draft-ietf-tsvwg-diffserv-intercon-00

The information below is for an old version of the document
Document Type Active Internet-Draft (tsvwg WG)
Last updated 2015-01-02 (latest revision 2014-12-04)
Replaces draft-geib-tsvwg-diffserv-intercon
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TSVWG                                                       R. Geib, Ed.
Internet-Draft                                          Deutsche Telekom
Intended status: Informational                                  D. Black
Expires: June 7, 2015                                    EMC Corporation
                                                        December 4, 2014

             DiffServ interconnection classes and practice
                 draft-ietf-tsvwg-diffserv-intercon-00

Abstract

   This document proposes a limited and well defined set of DiffServ
   PHBs and codepoints to be applied at (inter)connections of two
   separately administered and operated networks.  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.

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 June 7, 2015.

Copyright Notice

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

Geib & Black              Expires June 7, 2015                  [Page 1]

Internet-Draft              Diffserv Intercon              December 2014

   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
   2.  MPLS and the Short Pipe tunnel model  . . . . . . . . . . . .   5
   3.  An Interconnection class and codepoint scheme . . . . . . . .   6
     3.1.  End-to-end QoS: PHB and DS CodePoint Transparency . . . .  11
     3.2.  Treatment of Network Control traffic at carrier
           interconnection interfaces  . . . . . . . . . . . . . . .  12
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Appendix A.  Annex A Carrier interconnection related DiffServ
                aspects  . . . . . . . . . . . . . . . . . . . . . .  15
   Appendix B.  Annex 2 The MPLS Short Pipe Model and IP traffic . .  17
   Appendix C.  Change log . . . . . . . . . . . . . . . . . . . . .  21
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   DiffServ has been deployed in many networks.  As described by section
   2.3.4.2 of RFC 2475, remarking of packets at domain boundaries is a
   DiffServ feature [RFC2475].  This draft proposes a set of standard
   QoS classes and code points at interconnection points to which and
   from which locally used classes and code points should be mapped.

   RFC2474 specifies the DiffServ Codepoint Field [RFC2474].
   Differentiated treatment is based on the specific DSCP.  Once set, it
   may change.  If traffic marked with unknown or unexpected DSCPs is
   received, RFC2474 recommends forwarding that traffic with default
   (best effort) treatment without changing the DSCP markings.  Many
   networks do not follow this recommendation, and instead remark
   unknown or unexpected DSCPs to the zero DSCP for consistency with
   default (best effort) forwarding.

   Many providers operate MPLS-based backbones that employ backbone
   traffic engineering to ensure that if a major link, switch, or router
Show full document text