Browse Prior Art Database

Diffserv-Interconnection Classes and Practice (RFC8100)

IP.com Disclosure Number: IPCOM000249635D
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-10
Document File: 42 page(s) / 50K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Geib: AUTHOR [+3]

Abstract

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

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

Internet Engineering Task Force (IETF)                      R. Geib, Ed. Request for Comments: 8100                              Deutsche Telekom Category: Informational                                         D. Black ISSN: 2070-1721                                                 Dell EMC                                                               March 2017

              Diffserv-Interconnection Classes and Practice

Abstract

   This document defines a limited common set of Diffserv Per-Hop    Behaviors (PHBs) and Diffserv Codepoints (DSCPs) to be applied at    (inter)connections of two separately administered and operated    networks, and it explains how this approach can simplify network    configuration and operation.  Many network providers operate    Multiprotocol Label Switching (MPLS) using Treatment Aggregates for    traffic marked with different Diffserv Per-Hop Behaviors 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 Model.  While motivated by the requirements    of MPLS network operators that use Short Pipe Model tunnels, this    document is applicable to other networks, both MPLS and non-MPLS.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   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).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8100.

Geib & Black                  Informational                     [Page 1]
 RFC 8100                    Diffserv-Intercon                 March 2017

 Copyright Notice

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