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

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2013-04-19
Replaces draft-jjwl-mpls-mldp-hsmp
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd Loa Andersson
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             L. Jin
Internet-Draft
Intended status: Standards Track                               F. Jounay
Expires: October 20, 2013                                 France Telecom
                                                             I. Wijnands
                                                      Cisco Systems, Inc
                                                              N. Leymann
                                                     Deutsche Telekom AG
                                                          April 18, 2013

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

Abstract

   This draft introduces a hub & spoke multipoint LSP (short for HSMP
   LSP), 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, exactly as if it was traveling downstream
   along a P2MP LSP to each leaf node, and 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, except that it follows the path of the tree
   rather than ordinary unicast 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."

   This Internet-Draft will expire on October 20, 2013.

Jin, et al.             Expires October 20, 2013                [Page 1]
Internet-Draft          draft-ietf-mpls-mldp-hsmp             April 2013

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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Applications . . . . . . . . . . . . . . . . . . . . . . . . .  3
     3.1.  Time synchronization scenario  . . . . . . . . . . . . . .  4
     3.2.  VPMS scenario  . . . . . . . . . . . . . . . . . . . . . .  4
     3.3.  IPTV scenario  . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Setting up HSMP LSP with LDP . . . . . . . . . . . . . . . . .  5
     4.1.  Support for HSMP LSP setup with LDP  . . . . . . . . . . .  5
     4.2.  HSMP FEC Elements  . . . . . . . . . . . . . . . . . . . .  6
     4.3.  Using the HSMP FEC Elements  . . . . . . . . . . . . . . .  6
       4.3.1.  HSMP LSP Label Map . . . . . . . . . . . . . . . . . .  6
       4.3.2.  HSMP LSP Label Withdraw  . . . . . . . . . . . . . . .  8
       4.3.3.  HSMP LSP upstream LSR change . . . . . . . . . . . . .  9
   5.  HSMP LSP on a LAN  . . . . . . . . . . . . . . . . . . . . . .  9
   6.  Redundancy considerations  . . . . . . . . . . . . . . . . . .  9
   7.  Co-routed path exceptions  . . . . . . . . . . . . . . . . . .  9
   8.  Failure Detection of HSMP LSP  . . . . . . . . . . . . . . . . 10
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   11. Acknowledgement  . . . . . . . . . . . . . . . . . . . . . . . 11
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     12.1. Normative references . . . . . . . . . . . . . . . . . . . 11
Show full document text