Tree Engineering for Bit Index Explicit Replication (BIER-TE)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 43
- Abstract
- This memo describes per-packet stateless strict and loose path steered replication and forwarding for "Bit Index Explicit Replication" (BIER) packets (RFC 8279); it is called "Tree Engineering for Bit Index Explicit Replication" (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" (BPs). These BPs indicate adjacencies of the network topology, as opposed to (non-TE) BIER in which BPs indicate "Bit-Forwarding Egress Routers" (BFERs). A BIER-TE "packets BitString" therefore indicates the edges of the (loop-free) tree across which the packets are forwarded by BIER-TE. BIER-TE can leverage BIER forwarding engines with little changes. Co-existence of BIER and BIER-TE forwarding in the same domain is possible -- for example, by using separate BIER "subdomains" (SDs). Except for the optional routed adjacencies, BIER-TE does not require a BIER routing underlay and can therefore operate without depending on a routing protocol such as the "Interior Gateway Protocol" (IGP).
- Publication Date
- 2022-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC9262- Link
- https://doi.org/10.17487/RFC9262
- Author(s)
- Toerless EckertMichael MenthGregory Cauchie
- Keyword(s)
- BIER, Controller, ECMP, Forwarding, Traffic Engineering, Multicast, Traffic Steering
Latest version of IETF RFC 9262
Document Versions — IETF RFC 9262
-
▶ IETF RFC 9262 (2022-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8279 [Active*]
- IETF RFC 8296 [Active*]
Bibliographic Reference(s)
- 10.1109-ICC.2016.7511036 — ICC EXTERNAL
- 10.1145-362686.362692 — Bloom70 EXTERNAL
- 10.3233-JHS-1994-3405 — RCSD94 EXTERNAL
- IETF.draft-eckert-bier-te-frr-03 — BIER-TE-PROTECTION EXTERNAL
- IETF.draft-ietf-bier-multicast-http-response-06 — BIER-MCAST-OVERLAY EXTERNAL
- IETF.draft-ietf-bier-non-mpls-bift-encoding-04 — NON-MPLS-BIER-ENCODING EXTERNAL
- IETF.draft-ietf-bier-te-yang-05 — BIER-TE-YANG EXTERNAL
- IETF.draft-ietf-roll-ccast-01 — I-D.ietf-roll-ccast EXTERNAL
- IETF.draft-ietf-teas-rfc3272bis-21 — TE-OVERVIEW EXTERNAL
- IETF RFC 4253 [Active*]
- IETF RFC 4456 [Active*]
- IETF RFC 4655 [Active*]
- IETF RFC 5440 [Active*]
- IETF RFC 6241 [Active*]
- IETF RFC 6242 [Active*]
- IETF RFC 7589 [Active*]
- IETF RFC 7752 [Superseded*]
- IETF RFC 7950 [Active, Amended*]
- IETF RFC 7988 [Active*]
- IETF RFC 8040 [Active*]
- IETF RFC 8253 [Active*]
- IETF RFC 8345 [Active*]
- RFC8401 — RFC8401 EXTERNAL
- IETF RFC 8402 [Active*]
- RFC8444 — RFC8444 EXTERNAL
- IETF RFC 8556 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC9262.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 9262, Tree Engineering for Bit Index Explicit Replication (BIER-TE). Available at https://doi.org/10.17487/RFC9262
Snippet:
IETF RFC 9262, Tree Engineering for Bit Index Explicit Replication (BIER-TE). Available at https://doi.org/10.17487/RFC9262
HTML (ISO 690 compliant)
Preview:
IETF RFC 9262, Tree Engineering for Bit Index Explicit Replication (BIER-TE). Available at https://doi.org/10.17487/RFC9262
Snippet:
<span class="citation"><cite>IETF RFC 9262</cite>, Tree Engineering for Bit Index Explicit Replication (BIER-TE). Available at <a href="https://doi.org/10.17487/RFC9262" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9262</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 9262, Tree Engineering for Bit Index Explicit Replication (BIER-TE)
doi: 10.17487/RFC9262
url: https://doi.org/10.17487/RFC9262
doi: 10.17487/RFC9262
url: https://doi.org/10.17487/RFC9262
Snippet:
<li> <cite id="bib-rfc9262">IETF RFC 9262</cite>, Tree Engineering for Bit Index Explicit Replication (BIER-TE) <span class="doi">10.17487/RFC9262</span> </li>
Referenced By
- IETF RFC 9522 [Active*]