Bit Index Explicit Replication (BIER) Encapsulation for In-situ OAM (IOAM) Data
draft-xzlnp-bier-ioam-00

Document Type Active Internet-Draft (individual)
Last updated 2020-07-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
BIER Working Group                                                X. Min
Internet-Draft                                                  Z. Zhang
Intended status: Standards Track                               ZTE Corp.
Expires: January 14, 2021                                         Y. Liu
                                                            China Mobile
                                                               N. Nainar
                                                            C. Pignataro
                                                     Cisco Systems, Inc.
                                                           July 13, 2020

  Bit Index Explicit Replication (BIER) Encapsulation for In-situ OAM
                              (IOAM) Data
                        draft-xzlnp-bier-ioam-00

Abstract

   In-situ Operations, Administration, and Maintenance (IOAM) collects
   operational and telemetry information while the packet traverses a
   particular network domain.  Bit Index Explicit Replication (BIER) is
   an architecture that provides optimal multicast forwarding through a
   "multicast domain", without requiring intermediate routers to
   maintain any per-flow state or to engage in an explicit tree-building
   protocol.  The BIER header contains a bit-string in which each bit
   represents exactly one egress router to forward the packet to.  This
   document outlines the requirements to carry IOAM data in BIER header
   and specifies how IOAM data fields are encapsulated in BIER header.

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 January 14, 2021.

Min, et al.             Expires January 14, 2021                [Page 1]
Internet-Draft          BIER Encap for IOAM Data               July 2020

Copyright Notice

   Copyright (c) 2020 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   3
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     2.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Requirements to carry IOAM data in BIER header  . . . . . . .   3
   4.  IOAM data fields encapsulation in BIER header . . . . . . . .   4
   5.  Considerations  . . . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Discussion of the encapsulation approach  . . . . . . . .   6
     5.2.  IOAM and the use of the BIER OAM bits . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   In-situ Operations, Administration, and Maintenance (IOAM) collects
   operational and telemetry information while the packet traverses a
   particular network domain.  [I-D.ietf-ippm-ioam-data] defines
   different IOAM data fields used to record various telemetry data from
   the transit nodes.  The term "in-situ" refers to the fact that the
   IOAM data fields are added to the data packets rather than being sent
   within packets specifically dedicated to OAM.

   Bit Index Explicit Replication (BIER), as defined in [RFC8279], is an
   architecture that provides optimal multicast forwarding through a
   "multicast domain", without requiring intermediate routers to
Show full document text