BIER Ping and Trace
draft-ietf-bier-ping-03
|
| Document |
Type |
|
Active Internet-Draft (bier WG)
|
|
Last updated |
|
2018-02-21
(latest revision 2018-01-22)
|
|
Replaces |
|
draft-kumarzheng-bier-ping
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Consensus: Waiting for Write-Up
(wg milestones:
Mar 2018 - Shepherd/IESG queue:...,
Jul 2018 - Publish as proposed ...
)
Other - see Comment Log
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Work group N. Kumar
Internet-Draft C. Pignataro
Intended status: Standards Track Cisco Systems, Inc.
Expires: July 26, 2018 N. Akiya
Big Switch Networks
L. Zheng
M. Chen
Huawei Technologies
G. Mirsky
Ericsson
January 22, 2018
BIER Ping and Trace
draft-ietf-bier-ping-03
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
Kumar, et al. Expires July 26, 2018 [Page 1]
Internet-Draft BIER Ping January 2018
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 26, 2018.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions used in this document . . . . . . . . . . . . . . 3
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Requirements notation . . . . . . . . . . . . . . . . . . 3
3. BIER OAM . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. BIER OAM message format . . . . . . . . . . . . . . . . . 4
3.2. Return Code . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. BIER OAM TLV . . . . . . . . . . . . . . . . . . . . . . 8
3.3.1. Original SI-BitString TLV . . . . . . . . . . . . . . 8
3.3.2. Target SI-BitString TLV . . . . . . . . . . . . . . . 9
3.3.3. Incoming SI-BitString TLV . . . . . . . . . . . . . . 10
3.3.4. Downstream Mapping TLV . . . . . . . . . . . . . . . 10
3.3.5. Responder BFER TLV . . . . . . . . . . . . . . . . . 13
3.3.6. Responder BFR TLV . . . . . . . . . . . . . . . . . . 14
3.3.7. Upstream Interface TLV . . . . . . . . . . . . . . . 14
3.3.8. Reply-To TLV . . . . . . . . . . . . . . . . . . . . 15
4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1. BIER OAM Processing . . . . . . . . . . . . . . . . . . . 16
4.2. Per BFER ECMP Discovery . . . . . . . . . . . . . . . . . 16
4.3. Sending BIER Echo Request . . . . . . . . . . . . . . . . 17
4.4. Receiving BIER Echo Request . . . . . . . . . . . . . . . 18
Show full document text