A YANG Data Model for Traffic Engineering Tunnels and Interfaces
draft-ietf-teas-yang-te-22
Document Type Active Internet-Draft (teas WG)
Last updated 2019-11-02
Replaces draft-saad-teas-yang-te
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Yang Validation ☯ 0 errors, 0 warnings.
Reviews
YANGDOCTORS Early Review (of -21): On the Right Track
Additional URLs
- Yang catalog entry for ietf-te-device@2019-11-02.yang
- Yang catalog entry for ietf-te@2019-11-02.yang
- Yang impact analysis for draft-ietf-teas-yang-te
- Mailing list discussion
Stream WG state WG Document
Other - see Comment Log
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Email authors Email WG IPR References Referenced by Nits 
TEAS Working Group                                               T. Saad
Internet-Draft                                          Juniper Networks
Intended status: Standards Track                               R. Gandhi
Expires: May 5, 2020                                   Cisco Systems Inc
                                                                  X. Liu
                                                          Volta Networks
                                                               V. Beeram
                                                        Juniper Networks
                                                              I. Bryskin
                                                              Individual
                                                       November 02, 2019

    A YANG Data Model for Traffic Engineering Tunnels and Interfaces
                       draft-ietf-teas-yang-te-22

Abstract

   This document defines a YANG data model for the configuration and
   management of Traffic Engineering (TE) interfaces, tunnels and Label
   Switched Paths (LSPs).  The model is divided into YANG modules that
   classify data into generic, device-specific, technology agnostic, and
   technology-specific elements.

   This model covers data for configuration, operational state, remote
   procedural calls, and event notifications.

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 May 5, 2020.

Saad, et al.               Expires May 5, 2020                  [Page 1]
Internet-Draft             TE YANG Data Model              November 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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Prefixes in Data Node Names . . . . . . . . . . . . . . .   3
     1.3.  TE Technology Models  . . . . . . . . . . . . . . . . . .   4
     1.4.  State Data Organization . . . . . . . . . . . . . . . . .   4
   2.  Model Overview  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Module(s) Relationship  . . . . . . . . . . . . . . . . .   5
     2.2.  Design Considerations . . . . . . . . . . . . . . . . . .   7
     2.3.  Model Tree Diagram  . . . . . . . . . . . . . . . . . . .   7
   3.  Model Organization  . . . . . . . . . . . . . . . . . . . . .  48
     3.1.  Global Configuration and State Data . . . . . . . . . . .  49
     3.2.  Interfaces Configuration and State Data . . . . . . . . .  50
     3.3.  Tunnels Configuration and State Data  . . . . . . . . . .  51
       3.3.1.  Tunnel Compute-Only Mode  . . . . . . . . . . . . . .  51
       3.3.2.  Tunnel Hierarchical Link Endpoint . . . . . . . . . .  52
     3.4.  TE LSPs State Data  . . . . . . . . . . . . . . . . . . .  52
     3.5.  Global RPC Data . . . . . . . . . . . . . . . . . . . . .  52
     3.6.  Interface RPC Data  . . . . . . . . . . . . . . . . . . .  52
     3.7.  Tunnel RPC Data . . . . . . . . . . . . . . . . . . . . .  52
   4.  TE Generic and Helper YANG Modules  . . . . . . . . . . . . .  53
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  99
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . 100
   7.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 101
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . . 101
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . . 102
     9.1.  Normative References  . . . . . . . . . . . . . . . . . . 102
     9.2.  Informative References  . . . . . . . . . . . . . . . . . 104
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . 105
Show full document text
RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement IETF Tools