Tree Engineering for Bit Index Explicit Replication (BIER-TE)
RFC 9262
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['BIER', 'BIER-TE', 'controller', 'ECMP', 'forwarding', 'traffic-engineering', 'multicast', 'pseudocode', 'routing', 'traffic-steering', 'tree-steering']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "G. Cauchie": changed name from "Gregory Cauchie" to "G. Cauchie" |
|
2026-05-20
|
(System) | Changed author "M. Menth": changed name from "Michael Menth" to "M. Menth" |
|
2026-05-20
|
(System) | Changed author "T. Eckert": changed name from "Toerless Eckert" to "T. Eckert", changed is_editor from "False" to "True", cleared country (was "USA") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2022-12-03
|
Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events' |
|
2022-10-14
|
(System) | Received changes through RFC Editor sync (created alias RFC 9262, changed abstract to 'This memo describes per-packet stateless strict and loose path steered replication … Received changes through RFC Editor sync (created alias RFC 9262, changed abstract to '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).', changed pages to 43, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2022-10-14, changed IESG state to RFC Published) |
|
2022-10-14
|
(System) | RFC published |