%% You should probably cite draft-ietf-bier-ping-14 instead of this revision. @techreport{ietf-bier-ping-01, number = {draft-ietf-bier-ping-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-bier-ping/01/}, author = {Nagendra Kumar Nainar and Carlos Pignataro and Nobo Akiya and Lianshu Zheng and Mach Chen and Greg Mirsky}, title = {{BIER Ping and Trace}}, pagetotal = 26, year = 2017, month = jan, day = 17, 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.}, }