draft-ietf-tsvwg-diffserv-intercon-10.txt   draft-ietf-tsvwg-diffserv-intercon-11.txt 
TSVWG R. Geib, Ed. TSVWG R. Geib, Ed.
Internet-Draft Deutsche Telekom Internet-Draft Deutsche Telekom
Intended status: Informational D. Black Intended status: Informational D. Black
Expires: April 13, 2017 Dell EMC Expires: April 14, 2017 Dell EMC
October 10, 2016 October 11, 2016
Diffserv-Interconnection classes and practice Diffserv-Interconnection classes and practice
draft-ietf-tsvwg-diffserv-intercon-10 draft-ietf-tsvwg-diffserv-intercon-11
Abstract Abstract
This document defines a limited common set of Diffserv PHBs and This document defines a limited common set of Diffserv PHBs and
codepoints (DSCPs) to be applied at (inter)connections of two codepoints (DSCPs) to be applied at (inter)connections of two
separately administered and operated networks, and explains how this separately administered and operated networks, and explains how this
approach can simplify network configuration and operation. Many approach can simplify network configuration and operation. Many
network providers operate MPLS using Treatment Aggregates for traffic network providers operate MPLS using Treatment Aggregates for traffic
marked with different Diffserv Per Hop Behaviors, and use MPLS for marked with different Diffserv Per Hop Behaviors, and use MPLS for
interconnection with other networks. This document offers a simple interconnection with other networks. This document offers a simple
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 13, 2017. This Internet-Draft will expire on April 14, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 14, line 44 skipping to change at page 14, line 44
Boucadair and Thomas Knoll helped adding awareness of related work. Boucadair and Thomas Knoll helped adding awareness of related work.
James Polk's discussion during IETF 89 helped to improve the text on James Polk's discussion during IETF 89 helped to improve the text on
the relation of this draft to RFC4594 and RFC5127. the relation of this draft to RFC4594 and RFC5127.
6. IANA Considerations 6. IANA Considerations
This memo includes no request to IANA. This memo includes no request to IANA.
7. Security Considerations 7. Security Considerations
DSCP marks expose additional traffic classification information is at DSCP marks expose additional traffic classification information at
network interconnections by comparison to DSCP remarking to zero - if network interconnections by comparison to use of zero DSCPs for all
that traffic classification info is sensitive, remarking DSCPs to interconnect traffic - if that traffic classification info is
zero to hide the classification is the countermeasure, at the cost of sensitive, remarking DSCPs to zero to hide the classification is the
loss of Diffserv info and differentiated traffic handling on the countermeasure, at the cost of loss of Diffserv info and
interconnect. differentiated traffic handling on the interconnect.
This document does not introduce new features; it describes how to This document does not introduce new features; it describes how to
use existing ones. The Diffserv security considerations in RFC2475 use existing ones. The Diffserv security considerations in RFC2475
[RFC2475] and RFC4594 [RFC4594] apply. [RFC2475] and RFC4594 [RFC4594] apply.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
 End of changes. 4 change blocks. 
10 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/