| Internet-Draft | Abbreviated Title | October 2022 |
| Zhang, et al. | Expires 26 April 2023 | [Page] |
This document describes the IS-IS and OSPF protocol extensions that are required for BIER-TE with MPLS and non-MPLS encapsulation.¶
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 26 April 2023.¶
Copyright (c) 2022 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 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.¶
[RFC9262] describes per-packet stateless strict and loose path steered replication and forwarding for "Bit Index Explicit Replication" (BIER, [RFC8279]) packets. It is called BIER Tree Engineering (BIER-TE) and is intended to be used as the path steering mechanism for Traffic Engineering with BIER.¶
BIER-TE introduces a new semantic for "bit positions" (BP) of link. [I-D.ietf-bier-te-isis], [I-D.ietf-bier-te-ospf], and [I-D.ietf-bier-te-ospfv3] describe IS-IS, OSPF, OSPFv3 extensions respectively for distributing BitPositions configured on the links in "Bit Index Explicit Replication Traffic Engineering" (BIER-TE) domain.¶
As described in section 2.4 in [RFC9262], BIER-TE inherits the encapsulation supporting from BIER unchanged. The encapsulation defined in [RFC8296], which specifies a common header format for both MPLS and non-MPLS networks, though the first 20-bits (referred to as BIFT-id) of the header is an "MPLS Label" in case of MPLS networks and is a local 20-bit opaque value in case of non-MPLS networks.¶
As described in section 4.3 of [RFC9262], it is necessary to distinguish the BIER and BIER-TE packet and forwarding. like [RFC8401], [RFC8444], [I-D.ietf-bier-ospfv3-extensions], and [I-D.ietf-bier-lsr-non-mpls-extensions], the MPLS and non-MPLS encapsulation needs to be advertised for BIER-TE packet encapsulation.¶
The advertisement can follow the BIER-TE BP advertisement, like the description in [I-D.zwx-bier-te-isis-extensions], [I-D.zwx-bier-te-ospf-extensions], and [I-D.zwx-bier-te-ospfv3-extensions]. But it does not work well if there are many BIER-TE links need to be advertised. Too many octets in the advertisement will be consumed even if the same BIFT-id is used for different links.¶
This document describes the IS-IS and OSPF protocol extensions that are required for BIER-TE with MPLS and non-MPLS encapsulation associated with prefix distributing.¶
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].¶
This document does not introduce more terminologies than [RFC8279], [RFC8296], [RFC8401], [RFC9262] and [I-D.ietf-bier-te-isis], [I-D.ietf-bier-te-ospf], [I-D.ietf-bier-te-ospfv3].¶
A configured or selected prefix is used for the advertisement. When the associated prefix reachability is advertised, the BIER-TE Encapsulation sub-TLV and associated MPLS or non-MPLS Encapsulation Sub-sub-TLV is carried.¶
In case both of the two encapsulation sub-sub-TLVs are advertised by one node, the label in MPLS encapsulation sub-sub-TLV and BIFT-id in non-MPLS encapsulation sub-sub-TLV SHOULD NOT be overlapped.¶
The format is defined in Section 5. The flooding scope is the same with section 5 in [RFC8401].¶
Same with IS-IS, a configured or selected prefix is used for the advertisement. When the associated OSPFv2 Extend Prefix TLV is advertised, the BIER-TE Encapsulation sub-TLV and associated MPLS or non-MPLS Encapsulation Sub-sub-TLV is carried.¶
It is similar for OSPFv3, When the associated OSPFv3 Extend Prefix TLV for a configured or selected prefix is advertised, the BIER-TE Encapsulation sub-TLV and associated MPLS or non-MPLS Encapsulation Sub-sub-TLV is carried.¶
In case both of the two encapsulation sub-sub-TLVs are advertised by one node, the label in MPLS encapsulation sub-sub-TLV and BIFT-id in non-MPLS encapsulation sub-sub-TLV SHOULD NOT be overlapped.¶
The format defined in Section 5 works for both OSPFv2 and OSPFv3. The flooding scope for OSPFv2 is the same with section 2.3 in [RFC8444]. The flooding scope for OSPFv3 is the same with section 2.2 in [I-D.ietf-bier-ospfv3-extensions].¶
As described in section 4.3 in [RFC9262], the label for MPLS encapsulation or the BIFT-ID for non-MPLS encapsulation is allocatd per SD:BSL.¶
A BIER-TE encapsulation sub-tlv is defined for indicating the following MPLS or non-MPLS encapsulation sub-sub-tlv.¶
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS / non-MPLS encapsulation sub-tlv |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| subdomain-id | BS Len| resv |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-sub-sub-tlv |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The BIER-TE MPLS encapsulation sub-sub-TLV may be advertised many times for different subdomain-id or BS Len.¶
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| subdomain-id | BS Len| resv |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BIFT-ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-sub-tlv |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The BIER-TE non-MPLS encapsulation sub-sub-TLV may be advertised many times for different subdomain-id or BS Len.¶
As described in section 4 of [I-D.ietf-bier-bierin6], which describes how the existing BIER encapsulation specified in [RFC8296] works in a non-MPLS IPv6 network, a node that requires IPv6 encapsulation MUST advertise the BIER-TE IPv6 encapsulation sub-sub-sub-TLV, which follows the associated Non-MPLS Encapsulation, according to local configuration or policy in the BIER domain to request other BFRs to always use IPv6 encapsulation.¶
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TBD.¶
This document does not introduce more security considerations than [RFC9262] and [I-D.ietf-bier-te-isis], [I-D.ietf-bier-te-ospf], and [I-D.ietf-bier-te-ospfv3].¶