Skip to main content

BIER Ping and Trace
draft-kumarzheng-bier-ping-02

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Authors Nagendra Kumar Nainar , Carlos Pignataro , Nobo Akiya , Lianshu Zheng , Mach Chen , Greg Mirsky
Last updated 2016-07-03 (Latest revision 2015-12-31)
Replaced by draft-ietf-bier-ping
RFC stream Internet Engineering Task Force (IETF)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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 Nainar
Carlos Pignataro
Nobo Akiya
Lianshu Zheng
Mach Chen
Greg Mirsky

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)