Network Working Group J. Xie Internet-Draft Huawei Technologies Intended status: Standards Track M. Chen Expires: September 6, 2018 R. Li Huawei March 5, 2018 RSVP-TE Extensions for P2MP-based BIER draft-xie-mpls-rsvp-bier-extension-00 Abstract Bit Index Explicit Replication (BIER) is a new architecture that provides optimal multicast forwarding without requiring intermediate routers to maintain any per-flow state by using a multicast-specific BIER header. 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) with BIER infomation, which is called P2MP based BIER in [I-D.xie-bier-mvpn-mpls-p2mp]. 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]. 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 https://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 September 6, 2018. Xie, et al. Expires September 6, 2018 [Page 1] Internet-Draft RSVP-TE Extensions for P2MP-based BIER March 2018 Copyright Notice Copyright (c) 2018 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 (https://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. RSVP Extensions . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. Example of signaling the P2MP-BIER . . . . . . . . . . . 3 3.2. PATH Message . . . . . . . . . . . . . . . . . . . . . . 4 3.3. RESV Message . . . . . . . . . . . . . . . . . . . . . . 5 3.4. SESSION Object . . . . . . . . . . . . . . . . . . . . . 7 3.4.1. P2MP BIER Tunnel IPv4 SESSION Object . . . . . . . . 7 3.4.2. P2MP BIER Tunnel IPv6 SESSION Object . . . . . . . . 8 3.5. SENDER_TEMPLATE Object . . . . . . . . . . . . . . . . . 8 3.5.1. P2MP BIER Tunnel IPv4 SENDER_TEMPLATE Object . . . . 9 3.5.2. P2MP BIER Tunnel IPv6 SENDER_TEMPLATE Object . . . . 9 3.6. S2L_BIER_SUB_LSP Object . . . . . . . . . . . . . . . . . 10 3.6.1. S2L_BIER_SUB_LSP IPv4 Object . . . . . . . . . . . . 10 3.6.2. S2L_BIER_SUB_LSP IPv6 Object . . . . . . . . . . . . 11 3.7. FILTER_SPEC Object . . . . . . . . . . . . . . . . . . . 11 3.7.1. P2MP BIER_IPv4 FILTER_SPEC Object . . . . . . . . . . 11 3.7.2. P2MP BIER_IPv6 FILTER_SPEC Object . . . . . . . . . . 11 4. Capability and Error Handling . . . . . . . . . . . . . . . . 11 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . 12 8.2. Informative References . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Xie, et al. Expires September 6, 2018 [Page 2] Internet-Draft RSVP-TE Extensions for P2MP-based BIER March 2018 1. Introduction Bit Index Explicit Replication (BIER) is a new architecture that provides optimal multicast forwarding without requiring intermediate routers to maintain any per-flow state by using a multicast-specific BIER header. [RFC4875] defines extensions to the RSVP-TE protocol ([RFC3209] and [RFC3473] ) to support P2MP TE LSPs satisfying the set of requirements described in [RFC4461] . This document extends RSVP-TE to establish P2MP TE LSPs with BIER information, which is called P2MP based BIER in [I-D.xie-bier-mvpn-mpls-p2mp]. 2. Terminology Readers of this document are assumed to be familiar with the terminology and concepts of the documents listed as Normative References. For convenience, some of the more frequently used terms and new terms list below. o LSP: Label Switch Path o LSR: Label Switching Router o BFR: BIER Forwarding Router o BFR-ID: BIER Forwarding Router IDentify. o P2MP: Point to Multi-point o P2MP based BIER: BIER using P2MP as topology 3. RSVP Extensions RSVP Extensions to setup a P2MP-based BIER is very similar to the setup of a P2MP LSP described in [RFC4875]. Most of the structure and description are borrowed from RFC4875, and a precursive example is put in the beginning to give a whole picture of building the forwarding state of P2MP based BIER. 3.1. Example of signaling the P2MP-BIER Consider LSRs A - F, interconnected as follows: Xie, et al. Expires September 6, 2018 [Page 3] Internet-Draft RSVP-TE Extensions for P2MP-based BIER March 2018 ( A ) ------------ ( B ) ------------ ( C ) ------------ ( D ) (Root) \ \ 1 (0:0001) \ \ ( E ) ( F ) 3 (0:0100) 2 (0:0010) Figure 1: P2MP-based BIER Topology Say that the node D has a BFR-id 1, F has a BFR-id 2, and E has a BFR-id 3, and we use a Bit String Length 4. Consider an P2MP SESSION, for which A is the Root, and say that D,E,F are all the Leafs of this P2MP SESSION. There are 3 Sub-LSPs: A-->B-->E, A-->B-->C-->D, A-->B-->C-->F. PATH message: When PATH message walk through A-->B-->E, it include an session attribute that identify ths session is to establish a P2MP- based BIER LSP. The same to A-->B-->C-->D and A-->B-->C-->F. RESV message: When RESV message work throuth A<--B<--E, it include an Object that identify BFR-ID of E. The same to A<--B<--C<--D and A<--B<--C<--F. Procedure: B learns that it's downstream endpoint has a BFR-ID<3> after a RSVP message passes through A<--B<--E. B also learns a BFR- ID<1> after a RSVP message passes throuth A<--B<--C<--D, and a BFR- ID<2> after a RSVP message passes through A<--B<--C<--D. 3.2. PATH Message This section describes modifications made to the Path message format as specified in [RFC4875]. The Path message is enhanced to signal one or more S2L sub-LSPs with BIER information. This is done by including the S2L BIER sub-LSP descriptor list in the Path message as shown below. Xie, et al. Expires September 6, 2018 [Page 4] Internet-Draft RSVP-TE Extensions for P2MP-based BIER March 2018 ::= [ ] [ [ | ] ...] [ ] [ ] [ ] [ ... ] [ ] [ ] [ ] [ ... ] [] ::= [ ] ::= [ ] Figure 2: PATH Message 3.3. RESV Message The Resv message follows the [RFC4875] format: Xie, et al. Expires September 6, 2018 [Page 5] Internet-Draft RSVP-TE Extensions for P2MP-based BIER March 2018 ::= [ ] [ [ | ] ... ] [ ] [ ] [ ] [ ] [ ] [ ... ]