draft-ietf-ccamp-rfc4420bis-01.txt   draft-ietf-ccamp-rfc4420bis-02.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 13, 2008 Cisco Systems, Inc. Created: March 15, 2008 Cisco Systems, Inc.
Expires: September 13, 2008 Arthi Ayyangar Expires: September 15, 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-01.txt draft-ietf-ccamp-rfc4420bis-02.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 7, line 10 skipping to change at page 7, line 10
This object effectively extends the Flags field in the This object effectively extends the Flags field in the
SESSION_ATTRIBUTE object and allows for the future inclusion of more SESSION_ATTRIBUTE object and allows for the future inclusion of more
complex objects through TLVs. complex objects through TLVs.
Note that some function may require an LSR to inspect both the Note that some function may require an LSR to inspect both the
SESSION_ATTRIBUTE object and the LSP_ATTRIBUTES or SESSION_ATTRIBUTE object and the LSP_ATTRIBUTES or
LSP_REQUIRED_ATTRIBUTES object. LSP_REQUIRED_ATTRIBUTES object.
The LSP_ATTRIBUTES object may also be used to report LSP operational The LSP_ATTRIBUTES object may also be used to report LSP operational
state on a Resv even when no LSP_ATTRIBUTES or state on a Resv message even when no LSP_ATTRIBUTES or
LSP_REQUIRED_ATTRIBUTES object was carried on the corresponding Path LSP_REQUIRED_ATTRIBUTES object was carried on the corresponding Path
message. The object is added or updated by LSRs that support the message. The object is added or updated by LSRs that support the
object. LSRs that do not understand the object or have nothing to object. LSRs that do not understand the object or have nothing to
report do not add the object and forward it unchanged on Resv report do not add the object and forward it unchanged on Resv
messages that they generate. messages that they generate.
The LSP_ATTRIBUTES object class is 197 of the form 11bbbbbb. This The LSP_ATTRIBUTES object class is 197 of the form 11bbbbbb. This
C-Num value (see [RFC2205], Section 3.10) ensures that LSRs that do C-Num value (see [RFC2205], Section 3.10) ensures that LSRs that do
not recognize the object pass it on transparently. not recognize the object pass it on transparently.
skipping to change at page 19, line 22 skipping to change at page 19, line 22
Credit to the OSPF Working Group for inspiration from their solution Credit to the OSPF Working Group for inspiration from their solution
to a similar problem. Thanks to Rahul Aggarwal for his careful to a similar problem. Thanks to Rahul Aggarwal for his careful
review and support of this work. Thanks also to Raymond Zhang, review and support of this work. Thanks also to Raymond Zhang,
Kireeti Kompella, Philip Matthews, Jim Gibson, and Alan Kullberg for Kireeti Kompella, Philip Matthews, Jim Gibson, and Alan Kullberg for
their input. As so often, thanks to John Drake for useful offline their input. As so often, thanks to John Drake for useful offline
discussions. Thanks to Mike Shand for providing the Routing discussions. Thanks to Mike Shand for providing the Routing
Directorate review and to Joel Halpern for the General Area review -- Directorate review and to Joel Halpern for the General Area review --
both picked up on some unclarities. both picked up on some unclarities.
Thanks to the OIF for noticing the discrepency in RFC 4420 that is Thanks to the OIF for noticing the discrepency in RFC 4420 that is
fixed in this document. fixed in this document. Alfred Hoenes noted several typographical
errors.
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 This document obsoletes RFC 4420. The only change is in Section 3.
is the change of the text in Section 3 that describes the semantic of Section 3 describes the semantic of the Length field of the
the Length field of the Attributes TLV. Attributes TLV.
Prior to the change, the Length field indicated the length of the Prior to the change, the Length field indicated the length of the
Value field only. After the change, as described in Section 3, 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 Length field indicates the length of the whole TLV. This change means
that this document is consistent with the subobject format defined in that this document is consistent with the subobject format defined in
[RFC3209] and the TLV format defined in [RFC3471]. [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
 End of changes. 5 change blocks. 
8 lines changed or deleted 9 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/