IS-IS Extensions for BIER-TE

Internet-Draft	ISIS for BIER-TE	August 2022
Chen, et al.	Expires 3 February 2023	[Page]

Abstract

This document describes IS-IS extensions for distributing BitPositions configured on the links in "Bit Index Explicit Replication Traffic Engineering" (BIER-TE) domain.¶

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 3 February 2023.¶

Copyright Notice

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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

1. Introduction

[I-D.ietf-bier-te-arch] introduces Bit Index Explicit Replication (BIER) Traffic/Tree Engineering (BIER-TE). It is an architecture for per-packet stateless explicit point to multipoint (P2MP) multicast path/tree. A link in a BIER-TE domain has its BitPositions. For a link between two nodes X and Y, there are two BitPositions for two forward connected adjacencies. These two adjacency BitPositions could be configured on nodes X and Y respectively. The BitPosition configured on X is the forward connected adjacency of Y. The BitPosition configured on Y is the forward connected adjacency of X.¶

This document proposes IS-IS extensions for distributing BitPositions configured on the links in "Bit Index Explicit Replication Traffic Engineering" (BIER-TE) domain.¶

1.1. Terminology

BIER:: Bit Index Explicit Replication.¶
BIER-TE:: BIER Traffic Engineering.¶
BFR:: Bit-Forwarding Router.¶
BFIR:: Bit-Forwarding Ingress Router.¶
BFER:: Bit-Forwarding Egress Router.¶
BFR-id:: BFR Identifier. It is a number in the range [1,65535].¶
BFR-NBR:: BFR Neighbor.¶
IS-IS:: Intermediate System to Intermediate System.¶

2. Extensions to IS-IS

This section describes protocol extensions to IS-IS for distributing BIER-TE information such as the BitPositions configured on the links in a BIER-TE domain.¶

An Extended IS Reachability TLV (Type 22) defined in [RFC5305] may contain Sub-TLVs (such as those for TE) that apply to a link/interface to a neighbor. To encode multiple links or interfaces to neighbors, the structure inside TLV is repeated.¶

MT Intermediate Systems TLV (Type 222) defined in [RFC5120] may contain Sub-TLVs (such as those for TE) that apply to a link/interface. It is aligned with Extended IS Reachability TLV (Type 22) beside an additional two bytes in front at the beginning of the TLV for MT-ID.¶

BIER-TE Info Sub-TLV of the following format is defined and used in Extended IS Reachability TLV (Type 22) and/or MT Intermediate Systems TLV (Type 222) to advertise the BIER-TE information about a link or interface.¶

    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 (TBD1)  |    Length     | sub-domain-id |      BAR      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      IPA      |         BitPosition           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     DisEndBitPosition         |    Sub-Sub-TLVs (variable)    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               +
   |                                                               ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Figure 1: BIER-TE Info Sub-TLV

Type:: TBD1 is to be assigned by IANA.¶
Length:: Variable, dependent on Sub-Sub-TLVs.¶
sub-domain-id:: Unique value identifying a BIER-TE sub-domain.¶
BAR:: Single-octet BIER Algorithm used to calculate underlay paths to reach other BFRs. Values are allocated from the "BIER Algorithm" registry defined in [RFC8401].¶
IPA:: Single-octet IGP Algorithm used to either modify, enhance, or replace the calculation of underlay paths to reach other BFRs as defined by the BAR value. Values are defined in the "IGP Algorithm Types" registry.¶
BitPosition:: A 2-octet field encoding the BitPosition locally configured on the link/interface to an Intermediate System neighbor.¶
DisEndBitPosition:: A 2-octet field encoding the BitPosition of the connection on the designated Intermediate Systems (Dis) end. This field is valid when the neighbor is a pseudonode. If the neighbor is not a pseudonode, this field MUST be ignored. The DisEndBitPosition may be configured on the link/interface to a transit network (i.e., broadcast link or say LAN).¶

No Sub-Sub-TLV is defined so far.¶

4. IANA Considerations

Under "IS-IS Sub-TLVs for TLVs Advertising Neighbor Information" registry, IANA is requested to assign a new Sub-TLV Type for BIER-TE Info as follows:¶

  +=======+=============+==+==+==+===+===+===+=============+
  | Type  |Description  |22|23|25|141|222|223|reference    |
  +=======+=============+==+==+==+===+===+===+=============+
  | TBD1  |BIER-TE Info |y |y |n | n | y | y |This document|
  +-------+-------------+--+--+--+---+---+---+-------------+

6. References

6.1. Normative References

[I-D.ietf-bier-te-arch]: Eckert, T., Menth, M., and G. Cauchie, "Tree Engineering for Bit Index Explicit Replication (BIER-TE)", Work in Progress, Internet-Draft, draft-ietf-bier-te-arch-13, 25 April 2022, <https://www.ietf.org/archive/id/draft-ietf-bier-te-arch-13.txt>.
[RFC2119]: Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", DOI 10.17487/RFC2119, BCP 14, RFC 2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC5120]: Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)", RFC 5120, DOI 10.17487/RFC5120, February 2008, <https://www.rfc-editor.org/info/rfc5120>.
[RFC5226]: Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", RFC 5226, DOI 10.17487/RFC5226, May 2008, <https://www.rfc-editor.org/info/rfc5226>.
[RFC5305]: Li, T. and H. Smit, "IS-IS Extensions for Traffic Engineering", DOI 10.17487/RFC5305, RFC 5305, October 2008, <https://www.rfc-editor.org/info/rfc5305>.
[RFC8174]: Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", DOI 10.17487/RFC8174, RFC 8174, BCP 14, May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8279]: Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., Przygienda, T., and S. Aldrin, "Multicast Using Bit Index Explicit Replication (BIER)", RFC 8279, DOI 10.17487/RFC8279, November 2017, <https://www.rfc-editor.org/info/rfc8279>.

6.2. Informative References

[RFC8296]: Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 2018, <https://www.rfc-editor.org/info/rfc8296>.
[RFC8401]: Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z. Zhang, "Bit Index Explicit Replication (BIER) Support via IS-IS", DOI 10.17487/RFC8401, RFC 8401, June 2018, <https://www.rfc-editor.org/info/rfc8401>.
[RFC8556]: Rosen, E., Ed., Sivakumar, M., Przygienda, T., Aldrin, S., and A. Dolganow, "Multicast VPN Using Bit Index Explicit Replication (BIER)", RFC 8556, DOI 10.17487/RFC8556, April 2019, <https://www.rfc-editor.org/info/rfc8556>.