Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications
RFC 8532
Document Type RFC - Proposed Standard (April 2019; No errata)
Last updated 2019-04-16
Replaces draft-kumar-lime-yang-connectionless-oam
Stream IETF
Formats plain text html pdf htmlized bibtex
Yang Validation ☯ 0 errors, 0 warnings.
Reviews
GENART Telechat Review (of -13): Ready with Issues
SECDIR Telechat Review (of -11): Has Nits
YANGDOCTORS Early Review (of -05): On the Right Track
Additional Resources
- Yang catalog entry for ietf-connectionless-oam@2017-09-06.yang
- Yang catalog entry for ietf-lime-time-types@2017-09-06.yang
- Yang impact analysis for draft-ietf-lime-yang-connectionless-oam
- Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Carlos Pignataro
Shepherd write-up Show (last changed 2017-10-04)
IESG IESG state RFC 8532 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Ignas Bagdonas
Send notices to Ron Bonica <rbonica@juniper.net>, Carlos Pignataro <cpignata@cisco.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Email authors Email WG IPR References Referenced by Nits 
Internet Engineering Task Force (IETF)                          D. Kumar
Request for Comments: 8532                                         Cisco
Category: Standards Track                                        M. Wang
ISSN: 2070-1721                                               Q. Wu, Ed.
                                                                  Huawei
                                                               R. Rahman
                                                             S. Raghavan
                                                                   Cisco
                                                              April 2019

             Generic YANG Data Model for the Management of
      Operations, Administration, and Maintenance (OAM) Protocols
                 That Use Connectionless Communications

Abstract

   This document presents a base YANG Data model for the management of
   Operations, Administration, and Maintenance (OAM) protocols that use
   connectionless communications.  The data model is defined using the
   YANG data modeling language, as specified in RFC 7950.  It provides a
   technology-independent abstraction of key OAM constructs for OAM
   protocols that use connectionless communication.  The base model
   presented here can be extended to include technology-specific
   details.

   There are two key benefits of this approach: First, it leads to
   uniformity between OAM protocols.  Second, it supports both nested
   OAM workflows (i.e., performing OAM functions at the same level or
   different levels through a unified interface) as well as interactive
   OAM workflows (i.e., performing OAM functions at the same level
   through a unified interface).

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8532.

Kumar, et al.                Standards Track                    [Page 1]
RFC 8532           Connectionless OAM YANG Data Model         April 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
   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 . . . . . . . . . . . . . .   4
     2.1.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Tree Diagrams . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Overview of the Connectionless OAM Model  . . . . . . . . . .   5
     3.1.  TP Address  . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Tools . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  OAM Neighboring Test Points . . . . . . . . . . . . . . .   7
     3.4.  Test Point Location Information . . . . . . . . . . . . .   8
     3.5.  Test Point Locations  . . . . . . . . . . . . . . . . . .   8
     3.6.  Path Discovery Data . . . . . . . . . . . . . . . . . . .   8
     3.7.  Continuity Check Data . . . . . . . . . . . . . . . . . .   9
     3.8.  OAM Data Hierarchy  . . . . . . . . . . . . . . . . . . .   9
   4.  LIME Time Types YANG Module . . . . . . . . . . . . . . . . .  12
   5.  Connectionless OAM YANG Module  . . . . . . . . . . . . . . .  15
   6.  Connectionless Model Applicability  . . . . . . . . . . . . .  44
     6.1.  BFD Extension . . . . . . . . . . . . . . . . . . . . . .  45
       6.1.1.  Augment Method  . . . . . . . . . . . . . . . . . . .  45
       6.1.2.  Schema Mount  . . . . . . . . . . . . . . . . . . . .  47
     6.2.  LSP Ping Extension  . . . . . . . . . . . . . . . . . . .  49
       6.2.1.  Augment Method  . . . . . . . . . . . . . . . . . . .  49
       6.2.2.  Schema Mount  . . . . . . . . . . . . . . . . . . . .  50
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  52
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  54
Show full document text
RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement IETF Tools