BIER Ping and Trace
draft-ietf-bier-ping-03
| Document | Type | Expired Internet-Draft (bier WG) | |
|---|---|---|---|
| Last updated | 2018-07-26 (latest revision 2018-01-22) | ||
| Replaces | draft-kumarzheng-bier-ping | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Consensus: Waiting for Write-Up (wg milestones: Mar 2018 - Shepherd/IESG queue:..., Jul 2018 - Publish as proposed ... ) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-bier-ping-03.txt
Abstract
Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain any multicast related per- flow state. BIER also does not require any 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. The BIER 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 setting the bits that correspond to those routers in the BIER header. This document describes the mechanism and basic BIER OAM packet format that can be used to perform failure detection and isolation on BIER data plane.
Authors
Nagendra Kumar
(naikumar@cisco.com)
Carlos Pignataro
(cpignata@cisco.com)
Nobo Akiya
(nobo.akiya.dev@gmail.com)
Lianshu Zheng
(vero.zheng@huawei.com)
Mach Chen
(mach.chen@huawei.com)
Gregory Mirsky
(gregory.mirsky@ericsson.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)