--- 1/draft-ietf-mpls-ldp-end-of-lib-02.txt 2009-01-14 17:12:02.000000000 +0100 +++ 2/draft-ietf-mpls-ldp-end-of-lib-03.txt 2009-01-14 17:12:02.000000000 +0100 @@ -1,87 +1,90 @@ MPLS Working Group Rajiv Asati Internet Draft Cisco Systems Intended status: Standards Track -Expires: June 2009 Pradosh Mohapatra +Expires: July 2009 Pradosh Mohapatra Cisco Systems Bob Thomas Emily Chen Huawei Technologies - December 29, 2008 + January 14, 2009 LDP End-of-LIB - draft-ietf-mpls-ldp-end-of-lib-02.txt + draft-ietf-mpls-ldp-end-of-lib-03.txt Status of this Memo - By submitting this Internet-Draft, each author represents that - 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 - becomes aware will be disclosed, in accordance with Section 6 of - BCP 79. + This Internet-Draft is submitted to IETF in full conformance with the + provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html - This Internet-Draft will expire on June 29, 2009. + This Internet-Draft will expire on May 14, 2009. Copyright Notice - Copyright (C) The IETF Trust (2008). + Copyright (c) 2009 IETF Trust and the persons identified as the + document authors. All rights reserved. + + This document is subject to BCP 78 and the IETF Trust's Legal + Provisions Relating to IETF Documents + (http://trustee.ietf.org/license-info) in effect on the date of + publication of this document. Please review these documents + carefully, as they describe your rights and restrictions with respect + to this document. Abstract There are situations following Label Distribution Protocol (LDP) session establishment where it would be useful for an LDP speaker to know when its peer has advertised all of its labels. The LDP specification provides no mechanism for an LDP speaker to notify a peer when it has completed its initial label advertisements to that peer. This document specifies means for an LDP speaker to signal completion of its initial label advertisements following session establishment. Table of Contents - 1. Introduction...................................................2 + 1. Introduction...................................................3 2. Specification Language.........................................3 3. Unrecognized Notification Capability...........................3 4. Signaling Completion of Label Advertisement....................4 5. Usage Guidelines...............................................5 - 5.1. LDP-IGP Sync..............................................5 + 5.1. LDP-IGP Sync..............................................6 5.2. LDP Graceful Restart......................................6 5.3. Wildcard Label Request....................................7 5.4. Missing Expected End-of-LIB Notifications.................7 6. Security Considerations........................................7 - 7. IANA Considerations............................................7 + 7. IANA Considerations............................................8 8. Acknowledgments................................................8 9. References.....................................................9 9.1. Normative References......................................9 9.2. Informative References....................................9 Author's Addresses...............................................10 - Intellectual Property Statement..................................10 - Disclaimer of Validity...........................................11 1. Introduction There are situations following LDP session establishment where it would be useful for an LDP speaker to know when its peer has advertised all of its labels. For example, when an LDP speaker is using LDP-IGP synchronization procedures [LDPSync], it would be useful for the speaker to know when its peer has completed advertisement of its IP label bindings. Similarly, after an LDP session is re-established when LDP Graceful Restart [RFC3478] is in @@ -330,22 +334,22 @@ Capabilities", draft-ietf-mpls-ldp-capabilities-02, Work in Progress, May 2007. [TypedWC] Thomas, B., Minei, I., "LDP Typed Wildcard FEC", draft- ietf-mpls-ldp-typed-wildcard-03, Work in Progress, March 2008. 9.2. Informative References [LDPSync] Jork, M., Atlas, A., Fang, L., "LDP IGP Synchronization", - draft-ietf-mpls-ldp-igp-sync-02, Work in Progress, June - 2008. + draft-ietf-mpls-ldp-igp-sync-04, Work in Progress, Dec + 2007. [RFC3478] Leelanivas, M., Rekhter, Y., Aggarwal, R., "Graceful Restart Mechanism for Label Distribution Protocol", February 2003. [MPLSsec] Fang, L., "Security Framework for MPLS and GMPLS Networks", draft-ietf-mpls-mpls-and-gmpls-security-framework-04, Work in Progress, Nov 2008. Author's Addresses @@ -360,57 +364,10 @@ 3750 Cisco Way, San Jose, CA, 95134 Email: pmohapat@cisco.com Bob Thomas Email: bobthomas@alum.mit.edu Emily Chen Huawei Technologies No.5 Street, Shangdi Information, Haidian, Beijing, China Email: chenying220@huawei.com - -Intellectual Property Statement - - The IETF takes no position regarding the validity or scope of any - Intellectual Property Rights or other rights that might be claimed to - pertain to the implementation or use of the technology described in - this document or the extent to which any license under such rights - might or might not be available; nor does it represent that it has - made any independent effort to identify any such rights. Information - on the procedures with respect to rights in RFC documents can be - found in BCP 78 and BCP 79. - - Copies of IPR disclosures made to the IETF Secretariat and any - assurances of licenses to be made available, or the result of an - attempt made to obtain a general license or permission for the use of - such proprietary rights by implementers or users of this - specification can be obtained from the IETF on-line IPR repository at - http://www.ietf.org/ipr. - - The IETF invites any interested party to bring to its attention any - copyrights, patents or patent applications, or other proprietary - rights that may cover technology that may be required to implement - this standard. Please address the information to the IETF at - ietf-ipr@ietf.org. - -Disclaimer of Validity - - This document and the information contained herein are provided on an - "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS - OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND - THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS - OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF - THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED - WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. - -Copyright Statement - - Copyright (C) The IETF Trust (2008). - - This document is subject to the rights, licenses and restrictions - contained in BCP 78, and except as set forth therein, the authors - retain all their rights. - -Acknowledgment - - Funding for the RFC Editor function is currently provided by the - Internet Society.