Common YANG Data Types for Traffic Engineering
RFC 8776

Document Type RFC - Proposed Standard (June 2020; No errata)
Last updated 2020-06-10
Stream IETF
Formats plain text html xml pdf htmlized bibtex
Yang Validation 0 errors, 1 warnings.
Reviews
Additional Resources
- Yang catalog entry for ietf-te-packet-types@2019-11-18.yang
- Yang catalog entry for ietf-te-types@2019-11-18.yang
- Yang impact analysis for draft-ietf-teas-yang-te-types
- Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Lou Berger
Shepherd write-up Show (last changed 2019-03-05)
IESG IESG state RFC 8776 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Lou Berger <lberger@labn.net>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack


Internet Engineering Task Force (IETF)                           T. Saad
Request for Comments: 8776                              Juniper Networks
Category: Standards Track                                      R. Gandhi
ISSN: 2070-1721                                      Cisco Systems, Inc.
                                                                  X. Liu
                                                          Volta Networks
                                                               V. Beeram
                                                        Juniper Networks
                                                              I. Bryskin
                                            Futurewei Technologies, Inc.
                                                               June 2020

             Common YANG Data Types for Traffic Engineering

Abstract

   This document defines a collection of common data types and groupings
   in YANG data modeling language.  These derived common types and
   groupings are intended to be imported by modules that model Traffic
   Engineering (TE) configuration and state capabilities.

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/rfc8776.

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.  Prefixes in Data Node Names
   2.  Acronyms and Abbreviations
   3.  Overview
     3.1.  TE Types Module Contents
     3.2.  Packet TE Types Module Contents
   4.  TE Types YANG Module
   5.  Packet TE Types YANG Module
   6.  IANA Considerations
   7.  Security Considerations
   8.  References
     8.1.  Normative References
     8.2.  Informative References
   Acknowledgments
   Contributors
   Authors' Addresses

1.  Introduction

   YANG [RFC6020] [RFC7950] is a data modeling language used to model
   configuration data, state data, Remote Procedure Calls, and
   notifications for network management protocols such as the Network
   Configuration Protocol (NETCONF) [RFC6241].  The YANG language
   supports a small set of built-in data types and provides mechanisms
   to derive other types from the built-in types.

   This document introduces a collection of common data types derived
   from the built-in YANG data types.  The derived types and groupings
   are designed to be the common types applicable for modeling Traffic
   Engineering (TE) features in model(s) defined outside of this
   document.

1.1.  Terminology

   The key words "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
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   The terminology for describing YANG data models is found in
   [RFC7950].

1.2.  Prefixes in Data Node Names

   In this document, names of data nodes and other data model objects
   are prefixed using the standard prefix associated with the
   corresponding YANG imported modules, as shown in Table 1.

        +-----------------+----------------------+---------------+
        | Prefix          | YANG Module          | Reference     |
        +=================+======================+===============+
        | yang            | ietf-yang-types      | [RFC6991]     |
        +-----------------+----------------------+---------------+
        | inet            | ietf-inet-types      | [RFC6991]     |
        +-----------------+----------------------+---------------+
        | rt-types        | ietf-routing-types   | [RFC8294]     |
        +-----------------+----------------------+---------------+
        | te-types        | ietf-te-types        | This document |
        +-----------------+----------------------+---------------+
        | te-packet-types | ietf-te-packet-types | This document |
Show full document text