Network Device YANG Organizational Models
draft-rtgyangdt-rtgwg-device-model-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-02-23
Replaced by draft-ietf-rtgwg-device-model
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
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)
Network Working Group                                     A. Lindem, Ed.
Internet-Draft                                             Cisco Systems
Intended status: Informational                            L. Berger, Ed.
Expires: August 26, 2016                         LabN Consulting, L.L.C.
                                                           D. Bogdanovic

                                                                C. Hopps
                                                        Deutsche Telekom
                                                       February 23, 2016

               Network Device YANG Organizational Models
                 draft-rtgyangdt-rtgwg-device-model-03

Abstract

   This document presents an approach for organizing YANG models in a
   comprehensive structure that may be used to configure and operate
   network devices.  The structure is itself represented as a YANG
   model, with all of the related component models logically organized
   in a way that is operationally intuitive, but this model is not
   expected to be implemented.  The identified component modules are
   expected to be defined and implemented on common network devices.

   This document also defines two modules that can be used to model the
   logical and virtual resource representations that may be present on a
   network device.  Examples of common industry terms for logical
   resource representations are Logical Systems or Routers.  Examples of
   of common industry terms for virtual resource representations are
   Virtual Routing and Forwarding (VRF) instances and Virtual Switch
   Instances (VSIs).

   This document is derived from work submitted to the IETF by members
   of the informal OpenConfig working group of network operators and is
   a product of the Routing Area YANG Architecture design team.

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

Lindem, et al.           Expires August 26, 2016                [Page 1]
Internet-Draft            RTG YANG Device Model            February 2016

   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 August 26, 2016.

Copyright Notice

   Copyright (c) 2016 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.  Status of Work and Open Issues  . . . . . . . . . . . . .   4
   2.  Module Overview . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Interface Model Components  . . . . . . . . . . . . . . .   8
     2.2.  System Management . . . . . . . . . . . . . . . . . . . .  10
     2.3.  Network Services  . . . . . . . . . . . . . . . . . . . .  10
     2.4.  OAM Protocols . . . . . . . . . . . . . . . . . . . . . .  11
     2.5.  Routing . . . . . . . . . . . . . . . . . . . . . . . . .  11
     2.6.  MPLS  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   3.  Logical Network Elements  . . . . . . . . . . . . . . . . . .  13
     3.1.  LNE Management - Host Network Device View . . . . . . . .  14
     3.2.  LNE Management - LNE View . . . . . . . . . . . . . . . .  15
     3.3.  LNE Instantiation . . . . . . . . . . . . . . . . . . . .  16
   4.  Network Instances . . . . . . . . . . . . . . . . . . . . . .  16
     4.1.  Network Instance Policy . . . . . . . . . . . . . . . . .  17
     4.2.  Network Instance Management . . . . . . . . . . . . . . .  17
     4.3.  Network Instance Instantiation  . . . . . . . . . . . . .  18
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   7.  YANG Modules  . . . . . . . . . . . . . . . . . . . . . . . .  18
     7.1.  Network Device Model Structure  . . . . . . . . . . . . .  18
     7.2.  Logical Network Element Model . . . . . . . . . . . . . .  25
Show full document text