draft-ietf-mpls-ldp-10.txt   draft-ietf-mpls-ldp-11.txt 
Network Working Group Loa Andersson Network Working Group Loa Andersson
Internet Draft Nortel Networks Inc. Internet Draft Nortel Networks Inc.
Expiration Date: February 2001 Expiration Date: February 2001
Paul Doolan Paul Doolan
Ennovate Networks Ennovate Networks
Nancy Feldman Nancy Feldman
IBM Corp IBM Corp
Andre Fredette Andre Fredette
Nortel Networks Inc. PhotonEx Corp
Bob Thomas Bob Thomas
Cisco Systems, Inc. Cisco Systems, Inc.
August 2000 August 2000
LDP Specification LDP Specification
draft-ietf-mpls-ldp-10.txt draft-ietf-mpls-ldp-11.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 5, line 36 skipping to change at page 5, line 36
5 Security Considerations ............................ 89 5 Security Considerations ............................ 89
5.1 Spoofing ........................................... 89 5.1 Spoofing ........................................... 89
5.2 Privacy ............................................ 90 5.2 Privacy ............................................ 90
5.3 Denial of Service .................................. 91 5.3 Denial of Service .................................. 91
6 Areas for Future Study ............................. 92 6 Areas for Future Study ............................. 92
7 Intellectual Property Considerations ............... 93 7 Intellectual Property Considerations ............... 93
8 Acknowledgments .................................... 93 8 Acknowledgments .................................... 93
9 References ......................................... 93 9 References ......................................... 93
10 Author Information ................................. 95 10 Author Information ................................. 95
Appendix.A LDP Label Distribution Procedures .................. 96 Appendix A LDP Label Distribution Procedures .................. 96
A.1 Handling Label Distribution Events ................. 98 A.1 Handling Label Distribution Events ................. 98
A.1.1 Receive Label Request .............................. 99 A.1.1 Receive Label Request .............................. 99
A.1.2 Receive Label Mapping .............................. 102 A.1.2 Receive Label Mapping .............................. 102
A.1.3 Receive Label Abort Request ........................ 108 A.1.3 Receive Label Abort Request ........................ 108
A.1.4 Receive Label Release .............................. 110 A.1.4 Receive Label Release .............................. 110
A.1.5 Receive Label Withdraw ............................. 112 A.1.5 Receive Label Withdraw ............................. 112
A.1.6 Recognize New FEC .................................. 113 A.1.6 Recognize New FEC .................................. 113
A.1.7 Detect Change in FEC Next Hop ...................... 116 A.1.7 Detect Change in FEC Next Hop ...................... 116
A.1.8 Receive Notification / Label Request Aborted ....... 119 A.1.8 Receive Notification / Label Request Aborted ....... 119
A.1.9 Receive Notification / No Label Resources .......... 119 A.1.9 Receive Notification / No Label Resources .......... 119
skipping to change at page 16, line 28 skipping to change at page 16, line 28
a similar manner. a similar manner.
- Compare U1 with U2. If U1 > U2, then A1 > A2; if U1 < U2, - Compare U1 with U2. If U1 > U2, then A1 > A2; if U1 < U2,
then A1 < A2. then A1 < A2.
3. If LSR1 is active, it attempts to establish the LDP TCP 3. If LSR1 is active, it attempts to establish the LDP TCP
connection by connecting to the well-known LDP port at address connection by connecting to the well-known LDP port at address
A2. If LSR1 is passive, it waits for LSR2 to establish the LDP A2. If LSR1 is passive, it waits for LSR2 to establish the LDP
TCP connection to its well-known LDP port. TCP connection to its well-known LDP port.
Note that when an LSR sends a Hello it selects the transport address
for its end of the session connection and uses the Hello to advertise
the address, either explicitly by including it in an optional
Transport Address TLV or implicitly by omitting the TLV and using it
as the Hello source address.
An LSR MUST advertise the same transport address in all Hellos that
advertise the same label space. This requirement ensures that two
LSRs linked by multiple Hello adjacencies using the same label spaces
play the same connection establishment role for each adjacency.
2.5.3. Session Initialization 2.5.3. Session Initialization
After LSR1 and LSR2 establish a transport connection they negotiate After LSR1 and LSR2 establish a transport connection they negotiate
session parameters by exchanging LDP Initialization messages. The session parameters by exchanging LDP Initialization messages. The
parameters negotiated include LDP protocol version, label parameters negotiated include LDP protocol version, label
distribution method, timer values, VPI/VCI ranges for label distribution method, timer values, VPI/VCI ranges for label
controlled ATM, DLCI ranges for label controlled Frame Relay, etc. controlled ATM, DLCI ranges for label controlled Frame Relay, etc.
Successful negotiation completes establishment of an LDP session Successful negotiation completes establishment of an LDP session
between LSR1 and LSR2 for the advertisement of label spaces LSR1:a between LSR1 and LSR2 for the advertisement of label spaces LSR1:a
skipping to change at page 95, line 8 skipping to change at page 95, line 8
[rfc2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5 [rfc2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5
Signature Option", RFC 2385, August 1998. Signature Option", RFC 2385, August 1998.
[TE] D. Awduche, J. Malcolm, J Agogbua, M. O'Dell, J. McManus, " [TE] D. Awduche, J. Malcolm, J Agogbua, M. O'Dell, J. McManus, "
Requirements for Traffic Engineering over MPLS", Work in Progress, Requirements for Traffic Engineering over MPLS", Work in Progress,
October 1998. October 1998.
10. Author Information 10. Author Information
Loa Andersson Andre Fredette Loa Andersson Andre Fredette
Nortel Networks Inc Nortel Networks Inc Nortel Networks Inc PhotonEx Corporation
St Eriksgatan 115, PO Box 6701 600 Technology Park Drive St Eriksgatan 115, PO Box 6701 8C Preston Court
113 85 Stockholm Billerica, MA 01821 113 85 Stockholm Bedford, MA 01730
Sweden Phone: 978-288-8524 Sweden Phone: 781-301-4655
Phone: +46 8 5088 36 34 email: fredette@nortelnetworks.com Phone: +46 8 5088 36 34 email: fredette@photonex.com
Mobile: +46 70 522 78 34 Mobile: +46 70 522 78 34
email: loa.andersson@nortelnetworks.com email: loa.andersson@nortelnetworks.com
Paul Doolan Bob Thomas Paul Doolan Bob Thomas
Ennovate Networks Cisco Systems, Inc. Ennovate Networks Cisco Systems, Inc.
330 Codman Hill Rd 250 Apollo Dr. 330 Codman Hill Rd 250 Apollo Dr.
Marlborough MA 01719 Chelmsford, MA 01824 Marlborough MA 01719 Chelmsford, MA 01824
Phone: 978-263-2002 Phone: 978-244-8078 Phone: 978-263-2002 Phone: 978-244-8078
email: pdoolan@ennovatenetworks.com email: rhthomas@cisco.com email: pdoolan@ennovatenetworks.com email: rhthomas@cisco.com
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/