Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Hub and Spoke Multipoint Label Switched Paths (LSPs)
draft-jjb-mpls-rsvp-te-hsmp-lsp-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-02-24
Replaced by draft-ietf-mpls-rsvp-te-hsmp-lsp
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MPLS Working Group                                                L. Jin
Internet-Draft                                                                                          
Intended status: Standards Track                               F. Jounay
Expires: August 26, 2013                                  France Telecom
                                                               M. Bhatia
                                                          Alcatel-Lucent
                                                       February 22, 2013

   Extensions to Resource Reservation Protocol - Traffic Engineering
   (RSVP-TE) for Hub and Spoke Multipoint Label Switched Paths (LSPs)
                   draft-jjb-mpls-rsvp-te-hsmp-lsp-03

Abstract

   In Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
   environment, the RSVP-TE based Point-to-Multipoint (P2MP) LSP allows
   traffic to transmit from root to leaf node, but there is no co-routed
   reverse path for traffic from leaf to root node.  There are
   applications that require bi-directional, co-routed and guaranteed
   communication from a root node to several leaf nodes in a hub-and-
   spoke fashion.  This draft defines such a Hub and Spoke Multipoint
   LSP (HSMP LSP) and defines protocol extensions to P2MP RSVP-TE to
   setup such LSPs.

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 August 26, 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

Jin, et al.              Expires August 26, 2013                [Page 1]
Internet-Draft      RSVP-TE Hub-Spoke Multipoint LSP       February 2013

   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.  Application  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Time Synchronization . . . . . . . . . . . . . . . . . . .  3
     1.2.  Virtual Private Multicast Service  . . . . . . . . . . . .  3
   2.  Comparing Hub-Spoke MP LSP with P2MP and Unidirectional
       Reverse LSP  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1.  Number of Path and Resv State Blocks . . . . . . . . . . .  4
     2.2.  Hardware Programming and Label Utilization . . . . . . . .  5
     2.3.  RSVP Control Traffic . . . . . . . . . . . . . . . . . . .  6
   3.  Setting up a Hub and Spoke Multipoint LSP with RSVP-TE . . . .  6
     3.1.  Hub and Spoke Multipoint LSP and Path Messages . . . . . .  6
     3.2.  Procedures for Hub and Spoke Multipoint LSP  . . . . . . .  6
     3.3.  Symmetric Bandwidth Allocation . . . . . . . . . . . . . .  7
     3.4.  Asymmetric bandwidth allocation  . . . . . . . . . . . . .  7
       3.4.1.  Packet Format  . . . . . . . . . . . . . . . . . . . .  8
       3.4.2.  UPSTREAM_FLOWSPEC processing . . . . . . . . . . . . .  9
       3.4.3.  UPSTREAM_TSPEC and UPSTREAM_ADSPEC processing  . . . .  9
   4.  Setting up the Hub Spoke Multipoint  LSP . . . . . . . . . . .  9
   5.  Grafting . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
   6.  Pruning  . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
   7.  Refresh Reduction  . . . . . . . . . . . . . . . . . . . . . . 12
   8.  Fast Reroute . . . . . . . . . . . . . . . . . . . . . . . . . 12
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
   10. Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   11. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 13
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 13
     12.2. Informative References . . . . . . . . . . . . . . . . . . 13
   Appendix 1.  Appendix: Alternate Mechanism to set up a reverse
                LSP . . . . . . . . . . . . . . . . . . . . . . . . . 14
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
Show full document text