LDP Extensions for Hub & Spoke Multipoint Label Switched Path
draft-ietf-mpls-mldp-hsmp-05

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2013-12-28 (latest revision 2013-12-11)
Replaces draft-jjwl-mpls-mldp-hsmp
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Loa Andersson
Shepherd write-up Show (last changed 2013-11-26)
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Telechat date
Responsible AD Adrian Farrel
Send notices to mpls-chairs@tools.ietf.org, draft-ietf-mpls-mldp-hsmp@tools.ietf.org
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                             L. Jin
Internet-Draft
Intended status: Standards Track                               F. Jounay
Expires: June 14, 2014                                    France Telecom
                                                             I. Wijnands
                                                      Cisco Systems, Inc
                                                              N. Leymann
                                                     Deutsche Telekom AG
                                                       December 11, 2013

     LDP Extensions for Hub & Spoke Multipoint Label Switched Path
                    draft-ietf-mpls-mldp-hsmp-05.txt

Abstract

   This draft introduces a hub & spoke multipoint (HSMP) Label Switched
   Path (LSP), which allows traffic both from root to leaf through
   point-to-multipoint (P2MP) LSP and also leaf to root along the
   reverse path.  That means traffic entering the HSMP LSP from
   application/customer at the root node travels downstream to each leaf
   node, exactly as if it is travelling downstream along a P2MP LSP to
   each leaf node.  Upstream traffic entering the HSMP LSP at any leaf
   node travels upstream along the tree to the root, as if it is unicast
   to the root.  Direct communication among the leaf nodes is not
   allowed.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC2119 [RFC2119].

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

Jin, et al.               Expires June 14, 2014                 [Page 1]
Internet-Draft          draft-ietf-mpls-mldp-hsmp          December 2013

   This Internet-Draft will expire on June 14, 2014.

Copyright Notice

   Copyright (c) 2013 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.  Code Components extracted from this document must
   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 Simplified BSD License.

Jin, et al.               Expires June 14, 2014                 [Page 2]
Internet-Draft          draft-ietf-mpls-mldp-hsmp          December 2013

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Setting up HSMP LSP with LDP . . . . . . . . . . . . . . . . .  4
     3.1.  Support for HSMP LSP Setup with LDP  . . . . . . . . . . .  5
     3.2.  HSMP FEC Elements  . . . . . . . . . . . . . . . . . . . .  6
     3.3.  Using the HSMP FEC Elements  . . . . . . . . . . . . . . .  6
     3.4.  HSMP LSP Label Map . . . . . . . . . . . . . . . . . . . .  7
       3.4.1.  HSMP LSP Leaf Node Operation . . . . . . . . . . . . .  8
       3.4.2.  HSMP LSP Transit Node Operation  . . . . . . . . . . .  8
       3.4.3.  HSMP LSP Root Node Operation . . . . . . . . . . . . .  9
     3.5.  HSMP LSP Label Withdraw  . . . . . . . . . . . . . . . . . 10
       3.5.1.  HSMP Leaf Operation  . . . . . . . . . . . . . . . . . 10
       3.5.2.  HSMP Transit Node Operation  . . . . . . . . . . . . . 10
       3.5.3.  HSMP Root Node Operation . . . . . . . . . . . . . . . 10
     3.6.  HSMP LSP Upstream LSR Change . . . . . . . . . . . . . . . 11
     3.7.  Determining Forwarding Interface . . . . . . . . . . . . . 11
   4.  HSMP LSP on a LAN  . . . . . . . . . . . . . . . . . . . . . . 11
   5.  Redundancy Considerations  . . . . . . . . . . . . . . . . . . 12
   6.  Failure Detection of HSMP LSP  . . . . . . . . . . . . . . . . 12
Show full document text