M-LDP Signaling Through BIER Core
draft-hb-bier-mldp-signaling-over-bier-01
Document | Type | Expired Internet-Draft (individual) | |
---|---|---|---|
Authors | Hooman Bidgoli , Jayant Kotalwar , Zhaohui Zhang , Eddie Leyton , Mankamana Mishra | ||
Last updated | 2020-05-07 (latest revision 2019-11-04) | ||
Stream | (None) | ||
Intended RFC status | (None) | ||
Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
Stream | Stream state | (No stream defined) | |
Consensus Boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
https://www.ietf.org/archive/id/draft-hb-bier-mldp-signaling-over-bier-01.txt
Abstract
Bit Index Explicit Replication (BIER) is an architecture that provides multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain multicast related per-flow state. Neither does BIER require an explicit tree-building protocol for its operation. A multicast data packet enters a BIER domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router adds a BIER header to the packet. Such header contains a bit-string in which each bit represents exactly one BFER to forward the packet to. The set of BFERs to which the multicast packet needs to be forwarded is expressed by the according set of bits switched on in BIER packet header. This document describes the procedure needed for mLDP tunnels to be signaled over and stitched through a BIER core, allowing LDP routers to run traditional Multipoint LDP services through a BIER core.
Authors
Hooman Bidgoli
(hooman.bidgoli@nokia.com)
Jayant Kotalwar
(jayant.kotalwar@nokia.com)
Zhaohui Zhang
(zzhang@juniper.net)
Eddie Leyton
(edward.leyton@verizonwireless.com)
Mankamana Mishra
(mankamis@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)