draft-ietf-ccamp-rfc4420bis-00.txt   draft-ietf-ccamp-rfc4420bis-01.txt 
INTERNET-DRAFT Adrian Farrel (Editor) INTERNET-DRAFT Adrian Farrel (Editor)
Network Working Group Old Dog Consulting Network Working Group Old Dog Consulting
Obsoletes: RFC4420 Dimitri Papadimitriou Obsoletes: RFC4420 Dimitri Papadimitriou
Updates: RFC3209, RFC3473 Alcatel Updates: RFC3209, RFC3473 Alcatel
Category: Standards Track Jean-Philippe Vasseur Category: Standards Track Jean-Philippe Vasseur
Created: March 11, 2008 Cisco Systems, Inc. Created: March 13, 2008 Cisco Systems, Inc.
Expires: September 11, 2008 Arthi Ayyangar Expires: September 13, 2008 Arthi Ayyangar
Juniper Networks Juniper Networks
Encoding of Attributes for Multiprotocol Label Switching (MPLS) Encoding of Attributes for Multiprotocol Label Switching (MPLS)
Label Switched Path (LSP) Establishment Using RSVP-TE Label Switched Path (LSP) Establishment Using RSVP-TE
draft-ietf-ccamp-rfc4420bis-00.txt draft-ietf-ccamp-rfc4420bis-01.txt
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 other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 2, line ? skipping to change at page 2, line ?
10.3. Communicating to All LSRs ................................16 10.3. Communicating to All LSRs ................................16
11. IANA Considerations ...........................................16 11. IANA Considerations ...........................................16
11.1. New RSVP C-Nums and C-Types ..............................16 11.1. New RSVP C-Nums and C-Types ..............................16
11.2. New TLV Space ............................................17 11.2. New TLV Space ............................................17
11.3. Attributes Flags .........................................17 11.3. Attributes Flags .........................................17
11.4. New Error Codes ..........................................18 11.4. New Error Codes ..........................................18
11.5. New Record Route Subobject Identifier ....................18 11.5. New Record Route Subobject Identifier ....................18
12. Security Considerations .......................................18 12. Security Considerations .......................................18
13. Acknowledgements ..............................................19 13. Acknowledgements ..............................................19
14. Changes from RFC 4420 to RFC XXXX .............................19 14. Changes from RFC 4420 to RFC XXXX .............................19
14. Normative References ..........................................19 15. Normative References ..........................................19
15. Informative References ........................................19 16. Informative References ........................................20
17. Authors' Addresses ............................................20 17. Authors' Addresses ............................................20
1. Introduction and Problem Statement 1. Introduction and Problem Statement
This document replaces and obsoletes the previous version of this This document replaces and obsoletes the previous version of this
work published as RFC 4420. The only change is in the encoding of the work published as RFC 4420. The only change is in the encoding of the
Type-Length-Variable (TLV) data structures presented in Section 3. Type-Length-Variable (TLV) data structures presented in Section 3.
See Section 14 for a summary of changes.
Traffic-Engineered Multiprotocol Label Switching (MPLS) Label Traffic-Engineered Multiprotocol Label Switching (MPLS) Label
Switched Paths (LSPs) [RFC3031] may be set up using the Path message Switched Paths (LSPs) [RFC3031] may be set up using the Path message
of the RSVP-TE signaling protocol [RFC3209]. The Path message of the RSVP-TE signaling protocol [RFC3209]. The Path message
includes the SESSION_ATTRIBUTE object, which carries a Flags field includes the SESSION_ATTRIBUTE object, which carries a Flags field
used to indicate desired options and attributes of the LSP. used to indicate desired options and attributes of the LSP.
The Flags field in the SESSION_ATTRIBUTE object has eight bits. Just The Flags field in the SESSION_ATTRIBUTE object has eight bits. Just
three of those bits are assigned in [RFC3209]. A further two bits three of those bits are assigned in [RFC3209]. A further two bits
are assigned in [RFC4090] for fast re-reroute functionality leaving are assigned in [RFC4090] for fast re-reroute functionality leaving
skipping to change at page 19, line 33 skipping to change at page 19, line 33
14. Changes from RFC 4420 to RFC XXXX 14. Changes from RFC 4420 to RFC XXXX
[RFC Editor - Please replace "XXXX" with the RFC number assigned for [RFC Editor - Please replace "XXXX" with the RFC number assigned for
this work and remove this note.] this work and remove this note.]
The only changes between this document and RFC 4420 that it obsoletes The only changes between this document and RFC 4420 that it obsoletes
is the change of the text in Section 3 that describes the semantic of is the change of the text in Section 3 that describes the semantic of
the Length field of the Attributes TLV. the Length field of the Attributes TLV.
Prior to the change, the Length field indicated the length of the
Value field only. After the change, as described in Section 3, the
Length field indicates the length of the whole TLV. This change means
that this document is consistent with the subobject format defined in
[RFC3209] and the TLV format defined in [RFC3471].
15. Normative References 15. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2205] Braden, R. (Ed.), Zhang, L., Berson, S., Herzog, S., and [RFC2205] Braden, R. (Ed.), Zhang, L., Berson, S., Herzog, S., and
S. Jamin, "Resource ReSerVation Protocol (RSVP) -- S. Jamin, "Resource ReSerVation Protocol (RSVP) --
Version 1 Functional Specification", RFC 2205, September Version 1 Functional Specification", RFC 2205, September
1997. 1997.
 End of changes. 5 change blocks. 
5 lines changed or deleted 12 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/