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

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2013-11-17 (latest revision 2013-10-16)
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
Document shepherd Loa Andersson
Shepherd write-up Show (last changed 2013-11-16)
IESG IESG state AD Evaluation::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
Network Working Group                                             L. Jin
Internet-Draft
Intended status: Standards Track                               F. Jounay
Expires: April 19, 2014                                   France Telecom
                                                             I. Wijnands
                                                           Cisco Systems
                                                              N. Leymann
                                                        Deutsche Telekom
                                                        October 16, 2013

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

Abstract

   This draft introduces a hub & spoke multipoint LSP (or HSMP LSP for
   short), which allows traffic both from root to leaf through P2MP LSP
   and also leaf to root along the co-routed 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, and strictly
   follows the downstream path of the tree rather than routing protocol
   based unicast path to the root.

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 April 19, 2014                 [Page 1]
Internet-Draft          draft-ietf-mpls-mldp-hsmp           October 2013

   This Internet-Draft will expire on April 19, 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 April 19, 2014                 [Page 2]
Internet-Draft          draft-ietf-mpls-mldp-hsmp           October 2013

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Applications . . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.1.  Time Synchronization Scenario  . . . . . . . . . . . . . .  5
     3.2.  Virtual Private Multicast Service Scenario . . . . . . . .  5
     3.3.  IPTV Scenario  . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Setting up HSMP LSP with LDP . . . . . . . . . . . . . . . . .  6
     4.1.  Support for HSMP LSP Setup with LDP  . . . . . . . . . . .  6
     4.2.  HSMP FEC Elements  . . . . . . . . . . . . . . . . . . . .  7
     4.3.  Using the HSMP FEC Elements  . . . . . . . . . . . . . . .  7
       4.3.1.  HSMP LSP Label Map . . . . . . . . . . . . . . . . . .  8
       4.3.2.  HSMP LSP Label Withdraw  . . . . . . . . . . . . . . . 10
       4.3.3.  HSMP LSP Upstream LSR Change . . . . . . . . . . . . . 10
   5.  HSMP LSP on a LAN  . . . . . . . . . . . . . . . . . . . . . . 10
   6.  Redundancy Considerations  . . . . . . . . . . . . . . . . . . 11
   7.  Co-routed Path Exceptions  . . . . . . . . . . . . . . . . . . 11
   8.  Failure Detection of HSMP LSP  . . . . . . . . . . . . . . . . 11
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
Show full document text