draft-ietf-mpls-mldp-recurs-fec-00.txt   draft-ietf-mpls-mldp-recurs-fec-01.txt 
Network Working Group IJsbrand Wijnands Network Working Group IJsbrand Wijnands
Internet Draft Eric C. Rosen Internet Draft Eric C. Rosen
Intended Status: Proposed Standard Cisco Systems, Inc. Intended Status: Proposed Standard Cisco Systems, Inc.
Expires: April 11, 2011 Expires: October 4, 2011
Maria Napierala Maria Napierala
AT&T AT&T
Nicolai Leymann Nicolai Leymann
Deutsche Telekom Deutsche Telekom
October 11, 2010 April 4, 2011
Using mLDP through a Backbone where there is no Route to the Root Using mLDP through a Backbone where there is no Route to the Root
draft-ietf-mpls-mldp-recurs-fec-00.txt draft-ietf-mpls-mldp-recurs-fec-01.txt
Abstract
The control protocol used for constructing Point-to-Multipoint and
Multipoint-to-Multipoint Label Switched Paths ("MP LSPs") contains a
field that identifies the address of a "root node". Intermediate
nodes are expected to be able to look up that address in their
routing tables. However, if the route to the root node is a BGP
route, and the intermediate nodes are part of a BGP-free core, this
is not possible. This document specifies procedures which enable a
MP LSP to be constructed through a BGP-free core. In these
procedures, the root node address is temporarily replaced by an
address which is known to the intermediate nodes.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
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 1, line 33 skipping to change at page 2, line 4
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.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Abstract
The control protocol used for constructing Point-to-Multipoint and
Multipoint-to-Multipoint Label Switched Paths ("MP LSPs") contains a
field that identifies the address of a "root node". Intermediate
nodes are expected to be able to look up that address in their
routing tables. However, if the route to the root node is a BGP
route, and the intermediate nodes are part of a BGP-free core, this
is not possible. This document specifies procedures which enable a
MP LSP to be constructed through a BGP-free core. In these
procedures, the root node address is temporarily replaced by an
address which is known to the intermediate nodes.
Table of Contents Table of Contents
1 Introduction .......................................... 3 1 Introduction .......................................... 3
2 The Recursive Opaque Value Type ....................... 5 2 The Recursive Opaque Value Type ....................... 5
2.1 Encoding .............................................. 5 2.1 Encoding .............................................. 5
2.2 Procedures ............................................ 5 2.2 Procedures ............................................ 5
3 The VPN-Recursive MP FEC Element ...................... 6 3 The VPN-Recursive MP FEC Element ...................... 6
3.1 Encoding .............................................. 6 3.1 Encoding .............................................. 6
3.2 Procedures ............................................ 7 3.2 Procedures ............................................ 7
3.2.1 Unsegmented Inter-AS P-tunnels ........................ 7 3.2.1 Unsegmented Inter-AS P-tunnels ........................ 7
skipping to change at page 12, line 9 skipping to change at page 12, line 9
Deutsche Telekom Deutsche Telekom
Winterfeldtstrasse 21 Winterfeldtstrasse 21
Berlin 10781 Berlin 10781
Germany Germany
E-mail: n.leymann@telekom.de E-mail: n.leymann@telekom.de
8. Normative References 8. Normative References
[MLDP] "Label Distribution Protocol Extensions for Point-to- [MLDP] "Label Distribution Protocol Extensions for Point-to-
Multipoint and Multipoint-to-Multipoint Label Switched Paths", Minei, Multipoint and Multipoint-to-Multipoint Label Switched Paths", Minei,
Kompella, Wijnands, Thomas, draft-ietf-mpls-ldp-p2mp-11.txt, October Kompella, Wijnands, Thomas, draft-ietf-mpls-ldp-p2mp-12.txt, February
2010 2011
[MVPN] "Multicast in MPLS/BGP IP VPNs", Rosen, Aggarwal, et. al., [MVPN] "Multicast in MPLS/BGP IP VPNs", Rosen, Aggarwal, et. al.,
draft-ietf-l3vpn-2547bis-mcast-10.txt, January 2009 draft-ietf-l3vpn-2547bis-mcast-10.txt, January 2009
[RFC2119] "Key words for use in RFCs to Indicate Requirement [RFC2119] "Key words for use in RFCs to Indicate Requirement
Levels.", Bradner, March 1997 Levels.", Bradner, March 1997
[VPN] "BGP/MPLS IP Virtual Private Networks (VPNs)", Rosen, Rekhter, [VPN] "BGP/MPLS IP Virtual Private Networks (VPNs)", Rosen, Rekhter,
RFC 4364, February 2006 RFC 4364, February 2006
 End of changes. 7 change blocks. 
20 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/