--- 1/draft-ietf-mpls-mldp-in-band-signaling-01.txt 2010-07-07 17:12:49.000000000 +0200 +++ 2/draft-ietf-mpls-mldp-in-band-signaling-02.txt 2010-07-07 17:12:49.000000000 +0200 @@ -1,23 +1,23 @@ Network Working Group I. Wijnands (Editor) Internet-Draft T. Eckert Intended status: Standards Track Cisco Systems, Inc. -Expires: August 30, 2010 N. Leymann +Expires: January 8, 2011 N. Leymann Deutsche Telekom M. Napierala AT&T Labs - February 26, 2010 + July 7, 2010 mLDP based in-band signaling for Point-to-Multipoint and Multipoint-to- Multipoint Label Switched Paths - draft-ietf-mpls-mldp-in-band-signaling-01 + draft-ietf-mpls-mldp-in-band-signaling-02 Abstract Suppose an IP multicast tree, constructed by Protocol Independent Multicast (PIM), needs to pass through an MPLS domain in which Multipoint LDP (mLDP) Point-to-Multipoint and/or Multipoint-to- Multipoint Labels Switched Paths (LSPs) can be created. The part of the IP multicast tree that traverses the MPLS domain can be instantiated as a multipoint LSP. When a PIM Join message is received at the border of the MPLS domain, information from that @@ -41,21 +41,21 @@ 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 August 30, 2010. + This Internet-Draft will expire on January 8, 2011. Copyright Notice Copyright (c) 2010 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 @@ -292,61 +292,61 @@ 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Source +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Group +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Type: 2 (to be assigned by IANA). + Type: 3 (to be assigned by IANA). Length: 8 Source: IPv4 multicast source address, 4 octets. Group: IPv4 multicast group address, 4 octets. 3.2. Transit IPv6 Source TLV 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Source ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ | Group ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Type: 3 (to be assigned by IANA). + Type: 4 (to be assigned by IANA). Length: 32 Source: IPv6 multicast source address, 16 octets. Group: IPv6 multicast group address, 16 octets. 3.3. Transit IPv4 bidir TLV 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Mask Len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RP | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Group | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Type: 4 (to be assigned by IANA). + Type: 5 (to be assigned by IANA). Length: 9 Mask Len: The number of contiguous one bits that are left justified and used as a mask, 1 octet. RP: Rendezvous Point (RP) IPv4 address used for encoded Group, 4 octets. Group: IPv4 multicast group address, 4 octets. @@ -359,21 +359,21 @@ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RP ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Group ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Type: 4 (to be assigned by IANA). + Type: 6 (to be assigned by IANA). Length: 33 Mask Len: The number of contiguous one bits that are left justified and used as a mask, 1 octet. RP: Rendezvous Point (RP) IPv6 address used for encoded group, 16 octets. Group: IPv6 multicast group address, 16 octets. @@ -381,26 +381,26 @@ 4. Security Considerations The same security considerations apply as for the base LDP specification, as described in [RFC5036]. 5. IANA considerations This document requires allocation from the LDP MP Opaque Value Element type name space managed by IANA. The values requested are: - Transit IPv4 Source TLV type - requested 2 + Transit IPv4 Source TLV type - requested 3 - Transit IPv6 Source TLV type - requested 3 - Transit IPv4 Bidir TLV type - requested 4 + Transit IPv6 Source TLV type - requested 4 + Transit IPv4 Bidir TLV type - requested 5 - Transit IPv6 Bidir TLV type - requested 5 + Transit IPv6 Bidir TLV type - requested 6 6. Acknowledgments Thanks to Eric Rosen for his valuable comments on this draft. Also thanks to Yakov Rekhter, Adrial Farrel and Uwe Joorde for providing comments on this draft. 7. Contributing authors Below is a list of the contributing authors in alphabetical order: