datatracker.ietf.org
Sign in
Version 5.12.0.p2, 2015-03-02
Report a bug

Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)
RFC 4875

Document type: RFC - Proposed Standard (May 2007; Errata)
Updated by RFC 6510
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 4875 (Proposed Standard)
Responsible AD: Ross Callon
Send notices to: mpls-chairs@ietf.org

Network Working Group                                   R. Aggarwal, Ed.
Request for Comments: 4875                              Juniper Networks
Category: Standards Track                          D. Papadimitriou, Ed.
                                                                 Alcatel
                                                        S. Yasukawa, Ed.
                                                                     NTT
                                                                May 2007

                             Extensions to
     Resource Reservation Protocol - Traffic Engineering (RSVP-TE)
         for Point-to-Multipoint TE Label Switched Paths (LSPs)

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This document describes extensions to Resource Reservation Protocol -
   Traffic Engineering (RSVP-TE) for the set up of Traffic Engineered
   (TE) point-to-multipoint (P2MP) Label Switched Paths (LSPs) in Multi-
   Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
   networks.  The solution relies on RSVP-TE without requiring a
   multicast routing protocol in the Service Provider core.  Protocol
   elements and procedures for this solution are described.

   There can be various applications for P2MP TE LSPs such as IP
   multicast.  Specification of how such applications will use a P2MP TE
   LSP is outside the scope of this document.

Aggarwal, et al.            Standards Track                     [Page 1]
RFC 4875         Extensions to RSVP-TE for P2MP TE LSPs         May 2007

Table of Contents

   1. Introduction ....................................................4
   2. Conventions Used in This Document ...............................4
   3. Terminology .....................................................4
   4. Mechanism .......................................................5
      4.1. P2MP Tunnels ...............................................5
      4.2. P2MP LSP ...................................................5
      4.3. Sub-Groups .................................................5
      4.4. S2L Sub-LSPs ...............................................6
           4.4.1. Representation of an S2L Sub-LSP ....................6
           4.4.2. S2L Sub-LSPs and Path Messages ......................7
      4.5. Explicit Routing ...........................................7
   5. Path Message ....................................................9
      5.1. Path Message Format ........................................9
      5.2. Path Message Processing ...................................11
           5.2.1. Multiple Path Messages .............................11
           5.2.2. Multiple S2L Sub-LSPs in One Path Message ..........12
           5.2.3. Transit Fragmentation of Path State Information ....14
           5.2.4. Control of Branch Fate Sharing .....................15
      5.3. Grafting ..................................................15
   6. Resv Message ...................................................16
      6.1. Resv Message Format .......................................16
      6.2. Resv Message Processing ...................................17
           6.2.1. Resv Message Throttling ............................18
      6.3. Route Recording ...........................................19
           6.3.1. RRO Processing .....................................19
      6.4. Reservation Style .........................................19
   7. PathTear Message ...............................................20
      7.1. PathTear Message Format ...................................20
      7.2. Pruning ...................................................20
           7.2.1. Implicit S2L Sub-LSP Teardown ......................20
           7.2.2. Explicit S2L Sub-LSP Teardown ......................21
   8. Notify and ResvConf Messages ...................................21
      8.1. Notify Messages ...........................................21
      8.2. ResvConf Messages .........................................23
   9. Refresh Reduction ..............................................24
   10. State Management ..............................................24
      10.1. Incremental State Update .................................25
      10.2. Combining Multiple Path Messages .........................25
   11. Error Processing ..............................................26
      11.1. PathErr Messages .........................................27

[include full document text]