idnits 2.17.1 draft-pdutta-mpls-ldp-v2-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC5036]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 05, 2012) is 4397 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '6074' on line 119 == Unused Reference: 'RFC2328' is defined on line 226, but no explicit reference was found in the text == Unused Reference: 'RFC4447' is defined on line 234, but no explicit reference was found in the text == Unused Reference: 'RFC6074' is defined on line 238, but no explicit reference was found in the text == Outdated reference: A later version (-22) exists of draft-ietf-pwe3-dynamic-ms-pw-14 -- Obsolete informational reference (is this intentional?): RFC 2373 (Obsoleted by RFC 3513) -- Obsolete informational reference (is this intentional?): RFC 4447 (Obsoleted by RFC 8077) Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MPLS Working Group P. Dutta 3 Internet-Draft M. Aissaoui 4 Intended status: Standards Track Alcatel-Lucent 5 Expires: October 7, 2012 April 05, 2012 7 LDP Version 2 8 draft-pdutta-mpls-ldp-v2-00 10 Abstract 12 The Label Distribution Protocol (LDP) is a protocol defined for 13 distributing labels for Multi-Protocol Label Switching (MPLS) and its 14 procedures are defined in [RFC5036] . LDP has been one of the most 15 deployed MPLS signaling protocols. [RFC5036] defines LDP version 1 16 and this document introduces LDP version 2 to full-fill various 17 operational needs when LDP is deployed for IPV6 networks. LDP 18 version 1 procedures can support IPV6 Label Switch Path (LSP) setup 19 and this document enhances those procedures in Version 2. 21 Requirements Language 23 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 24 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 25 document are to be interpreted as described in RFC 2119 [RFC2119]. 27 Status of this Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on October 7, 2012. 44 Copyright Notice 46 Copyright (c) 2012 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. LDP Version 2 Identifier . . . . . . . . . . . . . . . . . . . 4 63 3. Procedures for Version 2 . . . . . . . . . . . . . . . . . . . 5 64 4. Applicability . . . . . . . . . . . . . . . . . . . . . . . . . 5 65 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 66 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 67 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 68 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 69 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5 70 8.2. Informative References . . . . . . . . . . . . . . . . . . 6 71 Appendix A. An Appendix . . . . . . . . . . . . . . . . . . . . . 6 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 74 1. Introduction 76 The Multi-Protocol Label Switching (MPLS) architecture is described 77 in [RFC3031]. Label Distribution Protocol (LDP) is a signaling 78 protocol for setup and maintenance of MPLS LSPs (Label Switched 79 Paths) and the protocol specification is defined in [RFC5036]. 81 [RFC5036] defines the LDP Version 1 and all its related procedures. 82 Two Label Switched Routers (LSR) that use LDP to exchange label/FEC 83 mapping information are known as "LDP Peers" with respect to that 84 information, and we speak of there being an "LDP Session" between 85 them. A single LDP session allows each peer to learn the other's 86 label mappings. Each LSR is indentified by an LDP identifier. In 87 LDP Version 1, an LDP Identifier is a six octet quantity used to 88 identify an LSR label space. The 4 octets identify the LSR and is a 89 globally unique value which acts like as a 32-bit router Id assigned 90 to the LSR. The last two octets identify a specific label space 91 within the LSR. The last two octets of LDP Indentifers for platform- 92 wide label spaces are always both zero. This document uses the 93 following representation for LDP Indentifiers: 95 :