A YANG Data Model for MPLS Base
RFC 8960

Document Type RFC - Proposed Standard (December 2020; No errata)
Authors Tarek Saad  , Kamran Raza  , Rakesh Gandhi  , Xufeng Liu  , Vishnu Beeram 
Last updated 2020-12-18
Replaces draft-saad-mpls-base-yang
Stream IETF
Formats plain text html xml pdf htmlized bibtex
Yang Validation 0 errors, 0 warnings.
Additional Resources
- Yang catalog entry for ietf-mpls@2020-10-26.yang
- Yang impact analysis for draft-ietf-mpls-base-yang
- Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Loa Andersson
Shepherd write-up Show (last changed 2020-06-30)
IESG IESG state RFC 8960 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Loa Andersson <loa@pi.nu>, mpls-chairs@ietf.org, draft-ietf-mpls-base-yang@ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack

Internet Engineering Task Force (IETF)                           T. Saad
Request for Comments: 8960                              Juniper Networks
Category: Standards Track                                        K. Raza
ISSN: 2070-1721                                                R. Gandhi
                                                     Cisco Systems, Inc.
                                                                  X. Liu
                                                          Volta Networks
                                                               V. Beeram
                                                        Juniper Networks
                                                           December 2020

                    A YANG Data Model for MPLS Base


   This document contains a specification of the MPLS base YANG data
   model.  The MPLS base YANG data model serves as a base framework for
   configuring and managing an MPLS switching subsystem on an MPLS-
   enabled router.  It is expected that other MPLS YANG data models
   (e.g., MPLS Label Switched Path (LSP) static, LDP, or RSVP-TE YANG
   data models) will augment the MPLS base YANG data model.

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

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
     1.1.  Terminology
     1.2.  Acronyms and Abbreviations
   2.  MPLS Base Model
     2.1.  Model Overview
     2.2.  Model Organization
     2.3.  Model Design
     2.4.  Model Tree Diagram
     2.5.  MPLS Base YANG Module
   3.  IANA Considerations
   4.  Security Considerations
   5.  References
     5.1.  Normative References
     5.2.  Informative References
   Appendix A.  Data Tree Instance Example
   Authors' Addresses

1.  Introduction

   A core routing YANG data model is defined in [RFC8349]; it provides a
   basis for the development of routing data models for specific Address
   Families (AFs).  Specifically, [RFC8349] defines a model for a
   generic Routing Information Base (RIB) that is AF agnostic.
   [RFC8349] also defines two instances of RIBs based on the generic RIB
   model for IPv4 and IPv6 AFs.

   The MPLS base model defined in this document augments the generic RIB
   model defined in [RFC8349] with additional data that enables MPLS
   forwarding for one or more specific destination prefixes present in
   one or more AF RIBs, as described in the MPLS architecture document

   The MPLS base model also defines a new instance of the generic RIB
   YANG data model as defined in [RFC8349] to store native MPLS routes.
   The native MPLS RIB instance stores one or more routes that are not
   associated with other AF instance RIBs (such as IPv4 or IPv6 instance
   RIBs) but are enabled for MPLS forwarding.  Examples of such native
   MPLS routes are routes programmed by RSVP on one or more transit MPLS
   routers along the path of a Label Switched Path (LSP).  Other
   examples are MPLS routes that cross-connect to specific Layer 2
   adjacencies, such as Layer 2 Attachment Circuits (ACs); or Layer 3
   adjacencies, such as Segment Routing (SR) Adjacency Segments (Adj-
   SIDs) as described in [RFC8402].

   The MPLS base YANG data model serves as a basis for future
   development of MPLS YANG data models covering MPLS features and
   subsystems that are more sophisticated.  The main purpose is to
   provide essential building blocks for other YANG data models
   involving different control-plane protocols and MPLS functions.

   To this end, it is expected that the MPLS base data model will be
   augmented by a number of other YANG modules developed by the IETF
   (e.g., by the TEAS and MPLS Working Groups).

   The YANG module defined in this document conforms to the Network
Show full document text