BIER-TE Ping and Trace
draft-chen-bier-te-ping-04

Document Type Active Internet-Draft (individual)
Last updated 2019-02-26
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Networking Working Group                                       Ran. Chen
Internet-Draft                                              Greg. Mirsky
Intended status: Standards Track                            Shaofu. Peng
Expires: August 30, 2019                                 ZTE Corporation
                                                       February 26, 2019

                         BIER-TE Ping and Trace
                       draft-chen-bier-te-ping-04

Abstract

   Bit Index Explicit Replication (BIER)-TE shares architecture and
   packet formats with BIER-TE forwards and replicates packets based on
   a BitString in the packet header, but every BitPosition of the
   BitString of a BIER-TE packet indicates one or more adjacencies.

   This document describes the mechanism and basic BIER-TE OAM packet
   format that can be used to perform Ping and Traceroute on the BIER-TE
   network.

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
   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 August 30, 2019.

Copyright Notice

   Copyright (c) 2019 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

Chen, et al.             Expires August 30, 2019                [Page 1]
Internet-Draft           BIER-TE Ping and Trace            February 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  BIER-TE OAM Packet format . . . . . . . . . . . . . . . . . .   3
     3.1.  Target FEC Stack  . . . . . . . . . . . . . . . . . . . .   3
       3.1.1.  BIER-TE forward-connected TLV . . . . . . . . . . . .   4
       3.1.2.  BIER-TE local-decap sub-TLV . . . . . . . . . . . . .   5
       3.1.3.  BIER-TE forward-routed TLV  . . . . . . . . . . . . .   6
     3.2.  Downstream Mapping TLV  . . . . . . . . . . . . . . . . .   6
       3.2.1.  FEC Stack Change Sub-TLV  . . . . . . . . . . . . . .   6
     3.3.  Reply-To TLV  . . . . . . . . . . . . . . . . . . . . . .   7
   4.  BIER-TE OAM Processing  . . . . . . . . . . . . . . . . . . .   8
     4.1.  Sending BIER Echo Request . . . . . . . . . . . . . . . .   8
     4.2.  Receiving BIER Echo Request . . . . . . . . . . . . . . .   9
     4.3.  Sending Echo Reply  . . . . . . . . . . . . . . . . . . .  10
     4.4.  Receiving Echo Reply  . . . . . . . . . . . . . . . . . .  11
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     6.1.  TLVs  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     6.2.  Target FEC Stack  . . . . . . . . . . . . . . . . . . . .  12
     6.3.  Downstream Detailed Mapping Sub-TLVs  . . . . . . . . . .  12
   7.  Normative references  . . . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   [I-D.ietf-bier-te-arch] introduces and explains BIER-TE architecture
   that provides policy-based multicast forwarding through a "BIER-TE
   domain" without requiring intermediate routers to maintain any
   multicast related per-flow state.  BIER-TE forwards and replicates
   packets based on a BitString in the packet header, but every
   BitPosition of the BitString of a BIER-TE packet indicates one or
   more adjacencies.

   This document describes the mechanism and the basic BIER-TE OAM
   packet format that can be used to perform Ping and Traceroute on the
   BIER-TE network.

   This document enhances the BIER Ping and Traceroute, as defined in
   [I-D.ietf-bier-ping].  [RFC8296] defines a 4-bit field as "Proto" to
   identify the payload following BIER header.  When the payload is

Chen, et al.             Expires August 30, 2019                [Page 2]
Show full document text