draft-ietf-tsvwg-diffserv-class-aggr-06.txt   draft-ietf-tsvwg-diffserv-class-aggr-07.txt 
TSVWG K. Chan TSVWG K. Chan
Internet-Draft J. Babiarz Internet-Draft J. Babiarz
Intended status: Informational Nortel Intended status: Informational Nortel
Expires: May 2, 2008 F. Baker Expires: May 9, 2008 F. Baker
Cisco Systems Cisco Systems
October 30, 2007 November 6, 2007
Aggregation of DiffServ Service Classes Aggregation of DiffServ Service Classes
draft-ietf-tsvwg-diffserv-class-aggr-06 draft-ietf-tsvwg-diffserv-class-aggr-07
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 2, 2008. This Internet-Draft will expire on May 9, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
In the core of a high capacity network, service differentiation may In the core of a high capacity network, service differentiation may
still be needed to support applications' utilization of the network. still be needed to support applications' utilization of the network.
Applications with similar traffic characteristics and performance Applications with similar traffic characteristics and performance
skipping to change at page 2, line 22 skipping to change at page 2, line 22
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Overview of Service Class Aggregation . . . . . . . . . . . . 5 3. Overview of Service Class Aggregation . . . . . . . . . . . . 5
4. Service Classes to Treatment Aggregate Mapping . . . . . . . . 6 4. Service Classes to Treatment Aggregate Mapping . . . . . . . . 6
4.1. Mapping Service Classes into Four Treatment Aggregates . . 7 4.1. Mapping Service Classes into Four Treatment Aggregates . . 7
4.1.1. Network Control Treatment Aggregate . . . . . . . . . 9 4.1.1. Network Control Treatment Aggregate . . . . . . . . . 9
4.1.2. Real Time Treatment Aggregate . . . . . . . . . . . . 10 4.1.2. Real Time Treatment Aggregate . . . . . . . . . . . . 10
4.1.3. Assured Elastic Treatment Aggregate . . . . . . . . . 10 4.1.3. Assured Elastic Treatment Aggregate . . . . . . . . . 10
4.1.4. Elastic Treatment Aggregate . . . . . . . . . . . . . 11 4.1.4. Elastic Treatment Aggregate . . . . . . . . . . . . . 12
5. Treatment Aggregates and Inter-Provider Relationships . . . . 12 5. Treatment Aggregates and Inter-Provider Relationships . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
Appendix A. Using MPLS for Treatment Aggregates . . . . . . . . 13 Appendix A. Using MPLS for Treatment Aggregates . . . . . . . . 13
Appendix A.1. Network Control Treatment Aggregate with E-LSP . . . 15 Appendix A.1. Network Control Treatment Aggregate with E-LSP . . . 15
Appendix A.2. Real Time Treatment Aggregate with E-LSP . . . . . . 15 Appendix A.2. Real Time Treatment Aggregate with E-LSP . . . . . . 15
Appendix A.3. Assured Elastic Treatment Aggregate with E-LSP . . . 15 Appendix A.3. Assured Elastic Treatment Aggregate with E-LSP . . . 15
Appendix A.4. Elastic Treatment Aggregate with E-LSP . . . . . . . 15 Appendix A.4. Elastic Treatment Aggregate with E-LSP . . . . . . . 15
Appendix A.5. Treatment Aggregates and L-LSP . . . . . . . . . . . 16 Appendix A.5. Treatment Aggregates and L-LSP . . . . . . . . . . . 16
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
9.1. Normative References . . . . . . . . . . . . . . . . . . . 16 9.1. Normative References . . . . . . . . . . . . . . . . . . . 16
skipping to change at page 9, line 31 skipping to change at page 9, line 31
| | ||-------------------------------------| | | ||-------------------------------------|
| | || AF33, AF23, AF13 | | | || AF33, AF23, AF13 |
|==========+==========++=====================================| |==========+==========++=====================================|
| Elastic | Default || Default, (CS0) | | Elastic | Default || Default, (CS0) |
| |(RFC 2474)||-------------------------------------| | |(RFC 2474)||-------------------------------------|
| | || CS1 | | | || CS1 |
------------------------------------------------------------ ------------------------------------------------------------
Figure 2: Treatment Aggregate Behavior Figure 2: Treatment Aggregate Behavior
Notes for Figure 2: For Assured Elastic and Elastic Treatment
Aggregates, please see sections 4.1.3 and 4.1.4, respectively, for
details on additional priority within the Treatment Aggregate.
4.1.1. Network Control Treatment Aggregate 4.1.1. Network Control Treatment Aggregate
The Network Control Treatment Aggregate aggregates all service The Network Control Treatment Aggregate aggregates all service
classes that are functionally necessary for the survival of a network classes that are functionally necessary for the survival of a network
during a DOS attack or other high traffic load interval. The theory during a DOS attack or other high traffic load interval. The theory
is that whatever else is true, the network must protect itself. This is that whatever else is true, the network must protect itself. This
includes the traffic that "Diffserv Service Classes" [3] includes the traffic that "Diffserv Service Classes" [3]
characterizes as being included in the Network Control Service Class. characterizes as being included in the Network Control Service Class.
Traffic in the Network Control treatment aggregate should be carried Traffic in the Network Control treatment aggregate should be carried
skipping to change at page 12, line 49 skipping to change at page 13, line 13
providers. providers.
6. Security Considerations 6. Security Considerations
This document discusses the policy of using Differentiated Services This document discusses the policy of using Differentiated Services
and its service classes. If implemented as described, it should and its service classes. If implemented as described, it should
require that the network do nothing that the network has not already require that the network do nothing that the network has not already
allowed. If that is the case, no new security issues should arise allowed. If that is the case, no new security issues should arise
from the use of such a policy. from the use of such a policy.
It is possible for the policy to be applied incorrectly, or for a As this document is based on Diffserv Service Classes [3], the
wrong policy to be applied in the network for the defined Security Consideration discussion of no new security issues indicated
aggregation. In that case, a policy issue exists that the network by Diffserv Service Classes [3] also applies to treatment aggregates
must detect, assess, and deal with. This is a known security issue of this document.
in any network dependent on policy-directed behavior.
A well known flaw appears when bandwidth is reserved or enabled for a
service (for example, voice transport) and another service or an
attacking traffic stream uses it. This possibility is inherent in
DiffServ technology, which depends on appropriate packet markings.
When bandwidth reservation or a priority queuing system is used in a
vulnerable network, the use of authentication and flow admission is
recommended. To the best of the authors' knowledge, there is no
known technical way to respond to or act upon a data stream that has
been admitted for service but that it is not intended for
authenticated use.
7. IANA Considerations 7. IANA Considerations
This document does not request any IANA considerations. This document does not request any IANA considerations.
8. Acknowledgements 8. Acknowledgements
This document has benefited from discussions with numerous people, This document has benefited from discussions with numerous people,
especially Shane Amante, Brian Carpenter, and Dave McDysan. It has especially Shane Amante, Brian Carpenter, and Dave McDysan. It has
also benefited from detailed reviews by David Black, Marvin Krym, also benefited from detailed reviews by David Black, Marvin Krym,
 End of changes. 8 change blocks. 
22 lines changed or deleted 14 lines changed or added

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