| Internet Engineering Task Force | A. Przygienda |
| Internet-Draft | Ericsson |
| Intended status: Standards Track | September 27, 2014 |
| Expires: March 31, 2015 |
BIER support via ISIS
draft-przygienda-bier-isis-ranges-00
Specification of an ISIS extension to support BIER domains.
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 RFC 2119 [RFC2119].
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 March 31, 2015.
Copyright (c) 2014 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.
Bit Index Explicit Replication (BIER) [I-D.draft-wijnands-bier-architecture-00] defines an architecture where all intended multicast receivers are encoded as bitmask in the Multicast packet header within different encapsulations such as [I-D.draft-wijnands-mpls-bier-encapsulation-00]. A router that receives such a packet will forward the packet based on the Bit Position in the packet header towards the receiver(s), following a precomputed tree for each of the bits in the packet. Each receiver is represented by a unique bit in the bitmask.
This document presents necessary extensions to the currently deployed ISIS for IP [RFC7142] protocol to support distribution of information necessary for operation of BIER domains. This document defines a new TLV to be distributed by every router participating in such BIER domains.
Some of the terminology specified in [I-D.draft-wijnands-bier-architecture-00] is replicated here and extended by necessary definitions:
This document requests IANA to assign sub-TLV type values from the ISIS router capability TLV [RFC4971] registry.
This draft introduces a sub-TLV in the router capabilites TLV [RFC4971] to distribute the information. Any of the router's loopback addresses that it originates are considered BFR prefixes as required by [I-D.draft-wijnands-bier-architecture-00]. The question whether a particular loopback address is routable in a specific topology [RFC5120] can be resolved by [I-D.draft-xu-isis-routable-ip-address-01].
ISIS can carry BIER information not only for a single BIER domain but for multiple, distinct domains. This allows to run many disjoint BIER layers within the same Multi-Topology [RFC5120] easily instead of always forcing different multicast overlays to share the exactly same set of BFRs and resources. Moreover, multi topology [RFC5120] can be used for the purpose of restricting links that certain set of BIER domains can use or change metrics of such links. A BIER set is therefore always uniquely identified by the tuple of topology T, domain D it belongs to and its number S, denoted as <T,D,S>. The domain itself has as its unique attributes the encapsulation, bitmask length and the type of tree it is using to forward BIER frames (currently always SPF).
A given domain D in a multi-topology T [RFC5120] (denoted as <T,D> from now on) is normally not advertised to preserve the scaling of the protocol (i.e. ISIS carries no TLVs containing any of the elements related to <T,D>) and is enabled by a first BIER sub-TLV (Section 6.1) containing <T,D> being advertised into the area. The trigger itself is outside the scope of this draft but can be .e.g. a VPN desiring to initiate a domain as MP2MP or P2MP tree or a BMP being administratively assigned to a BFER and advertised via BIER TLV into the area or any other means within Multicast BIER Overlay(s) using BIER domains.
All routers in the flooding scope of the BIER TLVs SHOULD advertise the same bit mask length for a given <T,D>. A router discovering bitmask lengths advertised that are shorter than its own MUST report a misconfiguration of a specific <T,D>. Each router MUST compute BFTs for <T,D> using only routers having the same mask length as its own advertised Bit Mask Length in BIER sub-TLV for <T,D>.
The same router MAY advertise for different <T,D> combinations two different mask lengths. This allows to cleanly delineate domains crossing the same router but using different mask lengths in the encoding, even within the same topology.
Since encapsulation is an attribute of a domain <T,D> just like bitmask length, all rules that apply to Bitmask Length per Section 5.2 apply to it well.
Each router MAY advertise within the sub-TLV of an according <T,D> (denoted further as TLV<T,D>) a valid starting label value and a non-zero range length. It MUST advertise a valid label value and a non-zero range length IF it has computed itself as being on the BFT rooted at any of the BFRs with valid BFR-ids (except itself) participating in <T,D>.
A router CAN withdraw its TLV<T,D> if it does not want to participate in the domain due to resource constraints, label space optimization, administrative configuration or any other reasons. In case a router advertises a label range size of 0 for <T,D> it MUST be excluded from the BIER BFTs for <T,D>.
A router MUST advertise a for <T,D> label range size that guarantees to cover the maximum BFR-id injected into <T,D> (which implies a certain set id as described in [I-D.draft-wijnands-bier-architecture-00]). Any router that violates this condition MUST be excluded from BIER BFTs for <T,D>.
Each BFER MAY advertise with its TLV<T,D> the according BFR-id that it has administratively chosen.
If two BFRs advertise in their TLV<T,D> the same value for BFR-id, all routers MUST report it as misconfiguration and disregard those routers for all BIER calculations and procedures to align with [I-D.draft-wijnands-bier-architecture-00]. Such routers with colliding assignments MAY still act as BFIRs but will be never able to receive traffic.
All ISIS BIER information is carried within the router capability TLV [RFC4971] with S bit clear.
This sub-TLV carries the information for the BIER domains that the router participates in as BFR. It can repeat multiple times. If the same <T,D> is advertised more than once, the first one in the first sub-TLV in the fragment with the lowest ID MUST be used.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MT-ID | Bier Domain ID | Bit Msk Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lbl Range Size| Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFR-id |A|R|T| Reserv | Encaps |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The extension does not introduce any known new protocol vulnerabilities.
The draft is aligned with the [I-D.draft-kumar-ospf-bier-extension-00] draft as far as the protocol mechanisms overlap.