draft-ietf-mpls-ldp-p2mp-08.txt   draft-ietf-mpls-ldp-p2mp-09.txt 
Network Working Group I. Minei (Editor) Network Working Group I. Minei (Editor)
Internet-Draft K. Kompella Internet-Draft K. Kompella
Intended status: Standards Track Juniper Networks Intended status: Standards Track Juniper Networks
Expires: April 27, 2010 I. Wijnands (Editor) Expires: November 1, 2010 I. Wijnands (Editor)
B. Thomas B. Thomas
Cisco Systems, Inc. Cisco Systems, Inc.
October 24, 2009 April 30, 2010
Label Distribution Protocol Extensions for Point-to-Multipoint and Label Distribution Protocol Extensions for Point-to-Multipoint and
Multipoint-to-Multipoint Label Switched Paths Multipoint-to-Multipoint Label Switched Paths
draft-ietf-mpls-ldp-p2mp-08 draft-ietf-mpls-ldp-p2mp-09
Abstract
This document describes extensions to the Label Distribution Protocol
(LDP) for the setup of point to multi-point (P2MP) and multipoint-to-
multipoint (MP2MP) Label Switched Paths (LSPs) in Multi-Protocol
Label Switching (MPLS) networks. These extensions are also referred
to as mLDP Multicast LDP. mLDP constructs the P2MP or MP2MP LSPs
without interacting with or relying upon any other multicast tree
construction protocol. Protocol elements and procedures for this
solution are described for building such LSPs in a receiver-initiated
manner. There can be various applications for P2MP/MP2MP LSPs, for
example IP multicast or support for multicast in BGP/MPLS L3VPNs.
Specification of how such applications can use a LDP signaled P2MP/
MP2MP LSP is outside the scope of this document.
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. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
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.
This Internet-Draft will expire on April 27, 2010. This Internet-Draft will expire on November 1, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
Copyright (c) 2010 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
This document describes extensions to the Label Distribution Protocol This document may contain material from IETF Documents or IETF
(LDP) for the setup of point to multi-point (P2MP) and multipoint-to- Contributions published or made publicly available before November
multipoint (MP2MP) Label Switched Paths (LSPs) in Multi-Protocol 10, 2008. The person(s) controlling the copyright in some of this
Label Switching (MPLS) networks. These extensions are also referred material may not have granted the IETF Trust the right to allow
to as mLDP Multicast LDP. mLDP constructs the P2MP or MP2MP LSPs modifications of such material outside the IETF Standards Process.
without interacting with or relying upon any other multicast tree Without obtaining an adequate license from the person(s) controlling
construction protocol. Protocol elements and procedures for this the copyright in such materials, this document may not be modified
solution are described for building such LSPs in a receiver-initiated outside the IETF Standards Process, and derivative works of it may
manner. There can be various applications for P2MP/MP2MP LSPs, for not be created outside the IETF Standards Process, except to format
example IP multicast or support for multicast in BGP/MPLS L3VPNs. it for publication as an RFC or to translate it into languages other
Specification of how such applications can use a LDP signaled P2MP/ than English.
MP2MP LSP is outside the scope of this document.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Conventions used in this document . . . . . . . . . . . . 5 1.1. Conventions used in this document . . . . . . . . . . . . 4
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. Setting up P2MP LSPs with LDP . . . . . . . . . . . . . . . . 6 2. Setting up P2MP LSPs with LDP . . . . . . . . . . . . . . . . 5
2.1. Support for P2MP LSP setup with LDP . . . . . . . . . . . 7 2.1. Support for P2MP LSP setup with LDP . . . . . . . . . . . 6
2.2. The P2MP FEC Element . . . . . . . . . . . . . . . . . . . 7 2.2. The P2MP FEC Element . . . . . . . . . . . . . . . . . . . 6
2.3. The LDP MP Opaque Value Element . . . . . . . . . . . . . 9 2.3. The LDP MP Opaque Value Element . . . . . . . . . . . . . 8
2.3.1. The Generic LSP Identifier . . . . . . . . . . . . . . 9 2.3.1. The Generic LSP Identifier . . . . . . . . . . . . . . 8
2.4. Using the P2MP FEC Element . . . . . . . . . . . . . . . . 10 2.4. Using the P2MP FEC Element . . . . . . . . . . . . . . . . 9
2.4.1. Label Map . . . . . . . . . . . . . . . . . . . . . . 11 2.4.1. Label Map . . . . . . . . . . . . . . . . . . . . . . 10
2.4.2. Label Withdraw . . . . . . . . . . . . . . . . . . . . 12 2.4.2. Label Withdraw . . . . . . . . . . . . . . . . . . . . 11
2.4.3. Upstream LSR change . . . . . . . . . . . . . . . . . 13 2.4.3. Upstream LSR change . . . . . . . . . . . . . . . . . 12
3. Shared Trees . . . . . . . . . . . . . . . . . . . . . . . . . 13 3. Shared Trees . . . . . . . . . . . . . . . . . . . . . . . . . 12
4. Setting up MP2MP LSPs with LDP . . . . . . . . . . . . . . . . 14 4. Setting up MP2MP LSPs with LDP . . . . . . . . . . . . . . . . 13
4.1. Support for MP2MP LSP setup with LDP . . . . . . . . . . . 15 4.1. Support for MP2MP LSP setup with LDP . . . . . . . . . . . 14
4.2. The MP2MP downstream and upstream FEC Elements. . . . . . 15 4.2. The MP2MP downstream and upstream FEC Elements. . . . . . 14
4.3. Using the MP2MP FEC Elements . . . . . . . . . . . . . . . 16 4.3. Using the MP2MP FEC Elements . . . . . . . . . . . . . . . 15
4.3.1. MP2MP Label Map . . . . . . . . . . . . . . . . . . . 17 4.3.1. MP2MP Label Map . . . . . . . . . . . . . . . . . . . 16
4.3.2. MP2MP Label Withdraw . . . . . . . . . . . . . . . . . 20 4.3.2. MP2MP Label Withdraw . . . . . . . . . . . . . . . . . 19
4.3.3. MP2MP Upstream LSR change . . . . . . . . . . . . . . 21 4.3.3. MP2MP Upstream LSR change . . . . . . . . . . . . . . 20
5. Micro-loops in MP LSPs . . . . . . . . . . . . . . . . . . . . 21 5. Micro-loops in MP LSPs . . . . . . . . . . . . . . . . . . . . 20
6. The LDP MP Status TLV . . . . . . . . . . . . . . . . . . . . 22 6. The LDP MP Status TLV . . . . . . . . . . . . . . . . . . . . 21
6.1. The LDP MP Status Value Element . . . . . . . . . . . . . 23 6.1. The LDP MP Status Value Element . . . . . . . . . . . . . 22
6.2. LDP Messages containing LDP MP Status messages . . . . . . 23 6.2. LDP Messages containing LDP MP Status messages . . . . . . 22
6.2.1. LDP MP Status sent in LDP notification messages . . . 23 6.2.1. LDP MP Status sent in LDP notification messages . . . 22
6.2.2. LDP MP Status TLV in Label Mapping Message . . . . . . 24 6.2.2. LDP MP Status TLV in Label Mapping Message . . . . . . 23
7. Upstream label allocation on a LAN . . . . . . . . . . . . . . 25 7. Upstream label allocation on a LAN . . . . . . . . . . . . . . 24
7.1. LDP Multipoint-to-Multipoint on a LAN . . . . . . . . . . 25 7.1. LDP Multipoint-to-Multipoint on a LAN . . . . . . . . . . 24
7.1.1. MP2MP downstream forwarding . . . . . . . . . . . . . 25 7.1.1. MP2MP downstream forwarding . . . . . . . . . . . . . 24
7.1.2. MP2MP upstream forwarding . . . . . . . . . . . . . . 25 7.1.2. MP2MP upstream forwarding . . . . . . . . . . . . . . 24
8. Root node redundancy . . . . . . . . . . . . . . . . . . . . . 26 8. Root node redundancy . . . . . . . . . . . . . . . . . . . . . 25
8.1. Root node redundancy - procedures for P2MP LSPs . . . . . 26 8.1. Root node redundancy - procedures for P2MP LSPs . . . . . 25
8.2. Root node redundancy - procedures for MP2MP LSPs . . . . . 27 8.2. Root node redundancy - procedures for MP2MP LSPs . . . . . 26
9. Make Before Break (MBB) . . . . . . . . . . . . . . . . . . . 27 9. Make Before Break (MBB) . . . . . . . . . . . . . . . . . . . 26
9.1. MBB overview . . . . . . . . . . . . . . . . . . . . . . . 28 9.1. MBB overview . . . . . . . . . . . . . . . . . . . . . . . 27
9.2. The MBB Status code . . . . . . . . . . . . . . . . . . . 29 9.2. The MBB Status code . . . . . . . . . . . . . . . . . . . 28
9.3. The MBB capability . . . . . . . . . . . . . . . . . . . . 29 9.3. The MBB capability . . . . . . . . . . . . . . . . . . . . 28
9.4. The MBB procedures . . . . . . . . . . . . . . . . . . . . 30 9.4. The MBB procedures . . . . . . . . . . . . . . . . . . . . 29
9.4.1. Terminology . . . . . . . . . . . . . . . . . . . . . 30 9.4.1. Terminology . . . . . . . . . . . . . . . . . . . . . 29
9.4.2. Accepting elements . . . . . . . . . . . . . . . . . . 31 9.4.2. Accepting elements . . . . . . . . . . . . . . . . . . 30
9.4.3. Procedures for upstream LSR change . . . . . . . . . . 31 9.4.3. Procedures for upstream LSR change . . . . . . . . . . 30
9.4.4. Receiving a Label Map with MBB status code . . . . . . 32 9.4.4. Receiving a Label Map with MBB status code . . . . . . 31
9.4.5. Receiving a Notification with MBB status code . . . . 32 9.4.5. Receiving a Notification with MBB status code . . . . 31
9.4.6. Node operation for MP2MP LSPs . . . . . . . . . . . . 32 9.4.6. Node operation for MP2MP LSPs . . . . . . . . . . . . 31
10. Security Considerations . . . . . . . . . . . . . . . . . . . 33 10. Security Considerations . . . . . . . . . . . . . . . . . . . 32
11. IANA considerations . . . . . . . . . . . . . . . . . . . . . 33 11. IANA considerations . . . . . . . . . . . . . . . . . . . . . 32
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 34 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 33
13. Contributing authors . . . . . . . . . . . . . . . . . . . . . 34 13. Contributing authors . . . . . . . . . . . . . . . . . . . . . 33
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 36 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35
14.1. Normative References . . . . . . . . . . . . . . . . . . . 36 14.1. Normative References . . . . . . . . . . . . . . . . . . . 35
14.2. Informative References . . . . . . . . . . . . . . . . . . 36 14.2. Informative References . . . . . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36
1. Introduction 1. Introduction
The LDP protocol is described in [RFC5036]. It defines mechanisms The LDP protocol is described in [RFC5036]. It defines mechanisms
for setting up point-to-point (P2P) and multipoint-to-point (MP2P) for setting up point-to-point (P2P) and multipoint-to-point (MP2P)
LSPs in the network. This document describes extensions to LDP for LSPs in the network. This document describes extensions to LDP for
setting up point-to-multipoint (P2MP) and multipoint-to-multipoint setting up point-to-multipoint (P2MP) and multipoint-to-multipoint
(MP2MP) LSPs. These are collectively referred to as multipoint LSPs (MP2MP) LSPs. These are collectively referred to as multipoint LSPs
(MP LSPs). A P2MP LSP allows traffic from a single root (or ingress) (MP LSPs). A P2MP LSP allows traffic from a single root (or ingress)
node to be delivered to a number of leaf (or egress) nodes. A MP2MP node to be delivered to a number of leaf (or egress) nodes. A MP2MP
 End of changes. 9 change blocks. 
86 lines changed or deleted 93 lines changed or added

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