draft-ietf-mpls-ldp-capabilities-01.txt   draft-ietf-mpls-ldp-capabilities-02.txt 
Network Working Group Bob Thomas Network Working Group Bob Thomas
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Expiration Date: August 2008 Expiration Date: October 2008
Intended Status: Proposed Standard S. Aggarwal Intended Status: Proposed Standard S. Aggarwal
Juniper Networks Juniper Networks
R. Aggarwal R. Aggarwal
Juniper Networks Juniper Networks
J.L. Le Roux J.L. Le Roux
France Telecom France Telecom
February 2008
LDP Capabilities LDP Capabilities
draft-ietf-mpls-ldp-capabilities-01.txt draft-ietf-mpls-ldp-capabilities-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 Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 32 skipping to change at page 2, line 32
Table of Contents Table of Contents
1 Introduction .................................................. 3 1 Introduction .................................................. 3
2 Specification Language ........................................ 3 2 Specification Language ........................................ 3
3 The LDP Capability Mechanism .................................. 3 3 The LDP Capability Mechanism .................................. 3
4 Specifying Capabilities in LDP Messages ....................... 5 4 Specifying Capabilities in LDP Messages ....................... 5
5 Capability Message ............................................ 6 5 Capability Message ............................................ 6
6 Note on Terminology ........................................... 7 6 Note on Terminology ........................................... 7
7 Procedures for Capability Parameters in Initialization Messages 7 7 Procedures for Capability Parameters in Initialization Messages 7
8 Procedures for Capability Parameters in Capability Messages ... 8 8 Procedures for Capability Parameters in Capability Messages ... 8
9 Extensions to Error Handling .................................. 8 9 Extensions to Error Handling ................................. 9
10 Dynamic Capability Announcement TLV ........................... 9 10 Dynamic Capability Announcement TLV ......................... 9
11 Backward Compatibility ........................................ 10 11 Backward Compatibility ...................................... 10
12 Security Considerations ....................................... 10 12 Security Considerations ..................................... 10
13 IANA Considerations ........................................... 10 13 IANA Considerations ......................................... 10
14 Acknowledgements .............................................. 11 14 Acknowledgements ............................................ 11
15 References .................................................... 11 15 References .................................................. 11
16 Author Information ............................................ 12 16 Author Information .......................................... 12
17 Intellectual Property Statement ............................... 12 17 Intellectual Property Statement ............................. 12
18 Full Copyright Statement ...................................... 13 18 Full Copyright Statement .................................... 13
1. Introduction 1. Introduction
A number of enhancements to LDP as specified in [RFC5036] have been A number of enhancements to LDP as specified in [RFC5036] have been
proposed. These include LDP Graceful Restart [RFC3478], Fault proposed. These include LDP Graceful Restart [RFC3478], Fault
Tolerant LDP [RFC3479], multicast extensions [MLDP], signaling for Tolerant LDP [RFC3479], multicast extensions [MLDP], signaling for
layer 2 circuits [RFC4447], a method for learning labels advertised layer 2 circuits [RFC4447], a method for learning labels advertised
by next next hop routers in support of fast reroute node protection by next next hop routers in support of fast reroute node protection
[NNHOP], upstream label allocation [UPSTREAM_LDP], and extensions for [NNHOP], upstream label allocation [UPSTREAM_LDP], and extensions for
signaling inter-area LSPs [IALDP]. Some have been implemented, and signaling inter-area LSPs [IALDP]. Some have been implemented, and
skipping to change at page 5, line 32 skipping to change at page 5, line 32
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F| TLV Code Point | Length | |U|F| TLV Code Point | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S| Reserved | | |S| Reserved | |
+-+-+-+-+-+-+-+-+ Capability Data | +-+-+-+-+-+-+-+-+ Capability Data |
| +-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
U and F bits: U-bit
As specified in [RFC5036]. SHOULD be 1 (ignore if not understood).
F-bit:
SHOULD be 0 (don't forward if not understood).
TLV Code Point: TLV Code Point:
The TLV type, which identifies a specific capability. The "IANA The TLV type, which identifies a specific capability. The "IANA
Considerations" section of [RFC5036] specifies the assignment of Considerations" section of [RFC5036] specifies the assignment of
code points for LDP TLVs. code points for LDP TLVs.
S-bit: S-bit:
The State Bit indicates whether the sender is advertising or The State Bit indicates whether the sender is advertising or
withdrawing the capability corresponding to the TLV Code Point. withdrawing the capability corresponding to the TLV Code Point.
The State bit is used as follows: The State bit is used as follows:
skipping to change at page 9, line 24 skipping to change at page 9, line 38
include the unknown TLV in a Returned TLVs TLV. include the unknown TLV in a Returned TLVs TLV.
10. Dynamic Capability Announcement TLV 10. Dynamic Capability Announcement TLV
The Dynamic Capability Announcement TLV is a Capability Parameter. The Dynamic Capability Announcement TLV is a Capability Parameter.
Its format is: Its format is:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| DynCap Announcement (IANA)| Length | |1|0| DynCap Announcement (IANA)| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S| Reserved | |S| Reserved |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
The Dynamic Capability Announcement Parameter MAY be included by an The Dynamic Capability Announcement Parameter MAY be included by an
LDP speaker in an Initialization message to signal its peer that the LDP speaker in an Initialization message to signal its peer that the
speaker is capable of processing Capability messages. speaker is capable of processing Capability messages.
An LDP speaker MUST NOT include the Dynamic Capability Announcement An LDP speaker MUST NOT include the Dynamic Capability Announcement
Parameter in Capability messages sent to its peers. Once enabled Parameter in Capability messages sent to its peers. Once enabled
 End of changes. 7 change blocks. 
18 lines changed or deleted 19 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/