draft-ietf-pce-dste-01.txt   draft-ietf-pce-dste-02.txt 
Network Working Group S. Sivabalan, Ed. Network Working Group S. Sivabalan, Ed.
Internet Draft J. Parker Internet Draft J. Parker
Intended status: Standards Track S. Boutros Intended status: Standards Track S. Boutros
Expires: November 23, 2008 Cisco Systems, Inc. Expires: May 2, 2009 Cisco Systems, Inc.
K. Kumaki K. Kumaki
KDDI Corporation KDDI Corporation
May 23, 2008 November 3, 2008
Diff-Serv Aware Class Type Object for Diff-Serv Aware Class Type Object for
Path Computation Element Communication Protocol Path Computation Element Communication Protocol
draft-ietf-pce-dste-01.txt draft-ietf-pce-dste-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is any 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 aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 November 23, 2008. This Internet-Draft will expire on May 2, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document specifies a CLASSTYPE object to support Diff-Serve This document specifies a CLASSTYPE object to support Diff-Serve
Aware Traffic Engineering (DS-TE) where path computation is performed Aware Traffic Engineering (DS-TE) where path computation is performed
with an aid of Path Computation Element (PCE). with an aid of Path Computation Element (PCE).
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 Error! document are to be interpreted as described in RFC-2119 Error!
Reference source not found.. Reference source not found..
skipping to change at page 2, line 26 skipping to change at page 2, line 29
1. Introduction...................................................2 1. Introduction...................................................2
2. Terminology....................................................3 2. Terminology....................................................3
3. CLASSTYPE Object...............................................4 3. CLASSTYPE Object...............................................4
3.1. Object Definition.........................................4 3.1. Object Definition.........................................4
3.2. Path Computation Request message with CLASSTYPE Object....4 3.2. Path Computation Request message with CLASSTYPE Object....4
3.3. Processing CLASSTYPE Object...............................5 3.3. Processing CLASSTYPE Object...............................5
3.4. Determination of Traffic Engineering Class (TE-Class).....6 3.4. Determination of Traffic Engineering Class (TE-Class).....6
3.5. Significance of Class-Type and TE-Class...................6 3.5. Significance of Class-Type and TE-Class...................6
3.6. Error Codes for CLASSTYPE Object..........................6 3.6. Error Codes for CLASSTYPE Object..........................6
4. Security Considerations........................................6 4. Security Considerations........................................7
5. IANA Considerations............................................7 5. IANA Considerations............................................7
6. Acknowledgments................................................7 6. Acknowledgments................................................7
6.1. Normative References......................................7 6.1. Normative References......................................8
6.2. Informative References....................................8 6.2. Informative References....................................8
Author's Addresses................................................8 Author's Addresses................................................8
Intellectual Property Statement...................................9 Intellectual Property Statement...................................9
Disclaimer of Validity............................................9 Disclaimer of Validity............................................9
1. Introduction 1. Introduction
The Internet Draft [PCEP-ID] specifies the Path Computation Element The Internet Draft [PCEP-ID] specifies the Path Computation Element
communication Protocol (PCEP) for communications between a Path communication Protocol (PCEP) for communications between a Path
Computation Client (PCC) and a Path Computation Element (PCE), or Computation Client (PCC) and a Path Computation Element (PCE), or
skipping to change at page 5, line 23 skipping to change at page 5, line 23
[<CLASSTYPE>] [<CLASSTYPE>]
[<LSPA>] [<LSPA>]
[<BANDWIDTH>] [<BANDWIDTH>]
[<metric-list>] [<metric-list>]
[<RRO>] [<RRO>]
[<IRO>] [<IRO>]
[<LOAD-BALANCING>] [<LOAD-BALANCING>]
where: where:
<metric-list>::=<METRIC>[<metric-list>] <metric-list>::=<METRIC>[<metric-list>]
Note that an implementation MUST form the PCEP messages using the
object ordering rules specified using Backus-Naur Form. Please refer
[OBJ-ORD] for more details.
3.3. Processing CLASSTYPE Object 3.3. Processing CLASSTYPE Object
If the LSP is associated with Class-Type N (1 <= N <= 7), the PCC If the LSP is associated with Class-Type N (1 <= N <= 7), the PCC
originating the path computation request MUST include the CLASSTYPE originating the path computation request MUST include the CLASSTYPE
object in the Path computation request message with the Class-Type object in the Path computation request message with the Class-Type
(CT) field set to N. (CT) field set to N.
If a path computation request contains multiple CLASSTYPE objects, If a path computation request contains multiple CLASSTYPE objects,
only the first one is meaningful; subsequent CLASSTYPE object(s) MUST only the first one is meaningful; subsequent CLASSTYPE object(s) MUST
be ignored and MUST NOT be forwarded. be ignored and MUST NOT be forwarded.
skipping to change at page 7, line 13 skipping to change at page 7, line 18
considerations pertaining to PCEP [PCEP-ID] remain relevant. considerations pertaining to PCEP [PCEP-ID] remain relevant.
5. IANA Considerations 5. IANA Considerations
IANA maintains a registry of parameters for PCEP. This contains a IANA maintains a registry of parameters for PCEP. This contains a
sub-registry for PCEP objects. IANA is requested to make new sub-registry for PCEP objects. IANA is requested to make new
allocation from this registry as follows: allocation from this registry as follows:
Object-Class Name Reference Object-Class Name Reference
22 CLASSTYPE draft-ietf-pce-dste-01.txt 22 CLASSTYPE draft-ietf-pce-dste-02.txt
Object-Type Object-Type
1: Class Type draft-ietf-pce-dste-01.txt 1: Class Type draft-ietf-pce-dste-02.txt
IANA is requested to make new allocation for error types and values IANA is requested to make new allocation for error types and values
as follows: as follows:
Error-Type Meaning Reference Error-Type Meaning Reference
12 Diff-Serv aware TE error draft-ietf-pce-dste-01.txt 12 Diff-Serv aware TE error draft-ietf-pce-dste-02.txt
Error-value = 1: draft-ietf-pce-dste-01.txt Error-value = 1: draft-ietf-pce-dste-02.txt
Unsupported class-type Unsupported class-type
Error-value = 2: draft-ietf-pce-dste-01.txt Error-value = 2: draft-ietf-pce-dste-02.txt
Invalid class-type Invalid class-type
Error-value = 3: draft-ietf-pce-dste-01.txt Error-value = 3: draft-ietf-pce-dste-02.txt
Class type and setup priority Class type and setup priority
does not form a configured TE class does not form a configured TE class
6. Acknowledgments 6. Acknowledgments
The authors would like to thank Jean Philippe Vasseur, Adrian The authors would like to thank Jean Philippe Vasseur, Adrian
Farrel and Zafar Ali for their valuable comments. Farrel and Zafar Ali for their valuable comments.
References References
6.1. Normative References 6.1. Normative References
[RFC4124] Le Faucheur, F. and W. Lai, "Protocol Extensions for [RFC4124] Le Faucheur, F. and W. Lai, "Protocol Extensions for
Support of Diffserv-aware MPLS Traffic Engineering", RFC Support of Diffserv-aware MPLS Traffic Engineering", RFC
4124, June 2005. 4124, June 2005.
[PCEP-ID] Path Computation Element (PCE) communication Protocol [PCEP-ID] Path Computation Element (PCE) communication Protocol
(PCEP)", draft-ietf-pce-pcep-12.txt (work in progress), (PCEP)", draft-ietf-pce-pcep-18.txt (work in progress),
September 2008. November 2008.
6.2. Informative References 6.2. Informative References
[RFC4657] Ash, J. and J. Le Roux, "Path Computation Element (PCE) [RFC4657] Ash, J. and J. Le Roux, "Path Computation Element (PCE)
Communication Protocol Generic Requirements", RFC 4657, Communication Protocol Generic Requirements", RFC 4657,
September 2006. September 2006.
[RFC3564] Le Faucheur, F. and W. Lai, "Requirements for Support of [RFC3564] Le Faucheur, F. and W. Lai, "Requirements for Support of
Differentiated Services-aware MPLS Traffic Engineering", Differentiated Services-aware MPLS Traffic Engineering",
RFC 3564, July 2003. RFC 3564, July 2003.
[OBJ-ORD] Farrel, A., "Reduced Backus-Naur Form (RBNF) A Syntax Used
in Various Protocol Specifications", draft-farrel-rtg-
common-bnf-07.txt, November 2008.
Author's Addresses Author's Addresses
Siva Sivabalan Siva Sivabalan
Cisco Systems, Inc. Cisco Systems, Inc.
2000 Innovation Drive 2000 Innovation Drive
Kanata, Ontario, K2K 3E8 Kanata, Ontario, K2K 3E8
Canada Canada
Email: msiva@cisco.com Email: msiva@cisco.com
 End of changes. 16 change blocks. 
14 lines changed or deleted 23 lines changed or added

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