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

Document Type Active Internet-Draft (teas WG)
Last updated 2017-03-11
Replaces draft-saad-teas-yang-te
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TEAS Working Group                                          T. Saad, Ed.
Internet-Draft                                                 R. Gandhi
Intended status: Standards Track                       Cisco Systems Inc
Expires: September 11, 2017                                       X. Liu
                                                                   Jabil
                                                               V. Beeram
                                                        Juniper Networks
                                                                 H. Shah
                                                                   Ciena
                                                              I. Bryskin
                                                     Huawei Technologies
                                                          March 10, 2017

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

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.  The model also includes module(s) that
   contain reusable TE data types and data groupings.

   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 http://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 September 11, 2017.

Saad, et al.           Expires September 11, 2017               [Page 1]
Internet-Draft             TE YANG Data Model                 March 2017

Copyright Notice

   Copyright (c) 2017 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
   (http://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.  Tree Diagram  . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Prefixes in Data Node Names . . . . . . . . . . . . . . .   4
     1.4.  Open Issues and Next Steps  . . . . . . . . . . . . . . .   5
       1.4.1.  TE Technology Models  . . . . . . . . . . . . . . . .   5
       1.4.2.  State Data Organization . . . . . . . . . . . . . . .   6
   2.  Model Overview  . . . . . . . . . . . . . . . . . . . . . . .   7
     2.1.  Module(s) Relationship  . . . . . . . . . . . . . . . . .   7
     2.2.  Design Considerations . . . . . . . . . . . . . . . . . .   9
     2.3.  Optional Features . . . . . . . . . . . . . . . . . . . .  10
     2.4.  Configuration Inheritance . . . . . . . . . . . . . . . .  10
   3.  TE Generic Model Organization . . . . . . . . . . . . . . . .  10
     3.1.  Global Configuration and State Data . . . . . . . . . . .  11
     3.2.  Interfaces Configuration and State Data . . . . . . . . .  12
     3.3.  Tunnels Configuration and State Data  . . . . . . . . . .  13
       3.3.1.  Tunnel Compute-Only Mode  . . . . . . . . . . . . . .  14
       3.3.2.  Tunnel Hierarchical Link Endpoint . . . . . . . . . .  15
     3.4.  TE LSPs State Data  . . . . . . . . . . . . . . . . . . .  15
     3.5.  Global RPC Data . . . . . . . . . . . . . . . . . . . . .  15
     3.6.  Interface RPC Data  . . . . . . . . . . . . . . . . . . .  15
     3.7.  Tunnel RPC Data . . . . . . . . . . . . . . . . . . . . .  15
     3.8.  Global Notifications Data . . . . . . . . . . . . . . . .  16
     3.9.  Interfaces Notifications Data . . . . . . . . . . . . . .  16
Show full document text