A YANG Data Model for In-Situ OAM
draft-zhou-ippm-ioam-yang-08
Document Type Active Internet-Draft (individual)
Last updated 2020-07-30
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Yang Validation ☯ 0 errors, 0 warnings.
Additional Resources
- Yang catalog entry for ietf-ioam@2020-07-13.yang
- Yang impact analysis for draft-zhou-ippm-ioam-yang
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)
Email authors IPR 1 References Referenced by Nits 
IPPM                                                        T. Zhou, Ed.
Internet-Draft                                                    Huawei
Intended status: Standards Track                             J. Guichard
Expires: January 31, 2021                                      Futurewei
                                                            F. Brockners
                                                             S. Raghavan
                                                           Cisco Systems
                                                           July 30, 2020

                   A YANG Data Model for In-Situ OAM
                      draft-zhou-ippm-ioam-yang-08

Abstract

   In-situ Operations, Administration, and Maintenance (IOAM) records
   operational and telemetry information in user packets while the
   packets traverse a path between two points in the network.  This
   document defines a YANG module for the IOAM function.

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 31, 2021.

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

Zhou, Ed., et al.       Expires January 31, 2021                [Page 1]
Internet-Draft             YANG Model for IOAM                 July 2020

   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 . . . . . . . . . . . . . .   2
     2.1.  Tree Diagrams . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Design of the IOAM YANG Data Model  . . . . . . . . . . . . .   3
     3.1.  Profiles  . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Preallocated Tracing Profile  . . . . . . . . . . . . . .   5
     3.3.  Incremental Tracing Profile . . . . . . . . . . . . . . .   5
     3.4.  Direct Export Profile . . . . . . . . . . . . . . . . . .   6
     3.5.  Proof of Transit Profile  . . . . . . . . . . . . . . . .   6
     3.6.  Edge to Edge Profile  . . . . . . . . . . . . . . . . . .   7
   4.  IOAM YANG Module  . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  22
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  22
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  23
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  24
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  24

1.  Introduction

   In-situ Operations, Administration, and Maintenance (IOAM)
   [I-D.ietf-ippm-ioam-data] records OAM information within user packets
   while the packets traverse a network.  The data types and data
   formats for IOAM data records have been defined in
   [I-D.ietf-ippm-ioam-data].  The IOAM data can be embedded in many
   protocol encapsulations such as Network Services Header (NSH) and
   IPv6.

   This document defines a data model for IOAM capabilities using the
   YANG data modeling language [RFC7950].  This YANG model supports all
   the five IOAM options, which are Incremental Tracing Option, Pre-
   allocated Tracing Option, Direct Export
   Option[I-D.ietf-ippm-ioam-direct-export], Proof of Transit(PoT)
   Option, and Edge-to-Edge Option.

2.  Conventions used in this document

   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
Show full document text
RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement IETF Tools