A YANG Data Model for Traffic Engineering Tunnels and Interfaces
draft-saad-teas-yang-te-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-03-23
Replaced by draft-ietf-teas-yang-te
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
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 23, 2015                                       X. Liu
                                                                Ericsson
                                                               V. Beeram
                                                        Juniper Networks
                                                                 H. Shah
                                                                   Ciena
                                                                 X. Chen
                                                     Huawei Technologies
                                                                R. Jones
                                                                 Brocade
                                                          March 22, 2015

    A YANG Data Model for Traffic Engineering Tunnels and Interfaces
                       draft-saad-teas-yang-te-01

Abstract

   This document defines a YANG data model for the configuration and
   management of Traffic Engineering (TE) interfaces and tunnels.  The
   model defines generic data that is reusable across multiple data and
   control plane protocols.

   The data model covers the configuration, operational state, remote
   procedural calls, and event notifications data for TE data.

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 23, 2015.

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

Copyright Notice

   Copyright (c) 2015 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
   2.  Data Model Overview . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Design Objectives . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Optional Features . . . . . . . . . . . . . . . . . . . .   7
     2.3.  Configuration Inheritance . . . . . . . . . . . . . . . .   7
     2.4.  Vendor Configuration Models . . . . . . . . . . . . . . .   8
   3.  Model Organization  . . . . . . . . . . . . . . . . . . . . .   8
     3.1.  TE Configuration Data . . . . . . . . . . . . . . . . . .   9
       3.1.1.  Global Configuration Data . . . . . . . . . . . . . .   9
       3.1.2.  Interface Configuration Data  . . . . . . . . . . . .  12
       3.1.3.  Tunnel Configuration Data . . . . . . . . . . . . . .  14
     3.2.  TE State Data . . . . . . . . . . . . . . . . . . . . . .  19
       3.2.1.  Global State Data . . . . . . . . . . . . . . . . . .  19
       3.2.2.  Interface State Data  . . . . . . . . . . . . . . . .  19
       3.2.3.  Tunnel State Data . . . . . . . . . . . . . . . . . .  19
     3.3.  TE RPC data . . . . . . . . . . . . . . . . . . . . . . .  20
       3.3.1.  Global RPC Data . . . . . . . . . . . . . . . . . . .  20
       3.3.2.  Interface RPC Data  . . . . . . . . . . . . . . . . .  20
       3.3.3.  Tunnel RPC Data . . . . . . . . . . . . . . . . . . .  20
     3.4.  TE Notification Data  . . . . . . . . . . . . . . . . . .  20
       3.4.1.  Global Notifications Data . . . . . . . . . . . . . .  20
       3.4.2.  Interfaces Notifications Data . . . . . . . . . . . .  21
Show full document text