YANG Model for Logical Network Elements
RFC 8530

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10

draft-ietf-rtgwg-lne-model-10.txt:
xym 0.4:
Extracting 'ietf-logical-network-element@2018-03-20.yang'
   Removed 0 empty lines


ietf-logical-network-element@2018-03-20.yang:
pyang 1.7.8: pyang --verbose --ietf -p {libs} {model}:
# read ietf-logical-network-element@2018-03-20.yang (CL)
# read /a/www/ietf-datatracker/6.93.0/env/share/yang/modules/ietf/ietf-interfaces.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-interfaces@2018-02-20.yang
# read /a/www/ietf-datatracker/6.93.0/env/share/yang/modules/ietf/ietf-yang-types.yang
# read /a/www/ietf-ftp/yang/draftmod/ietf-yang-types@2019-02-27.yang
# read /a/www/ietf-ftp/yang/draftmod/ietf-yang-schema-mount@2018-10-16.yang
# read /a/www/ietf-datatracker/6.93.0/env/share/yang/modules/ietf/ietf-inet-types.yang
# read /a/www/ietf-ftp/yang/draftmod/ietf-inet-types@2019-02-27.yang

yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors

Internet Engineering Task Force (IETF)                         L. Berger
Request for Comments: 8530                                      C. Hopps
Category: Standards Track                        LabN Consulting, L.L.C.
ISSN: 2070-1721                                                A. Lindem
                                                           Cisco Systems
                                                           D. Bogdanovic
                                                                  X. Liu
                                                          Volta Networks
                                                              March 2019

                YANG Model for Logical Network Elements

Abstract

   This document defines a logical network element (LNE) YANG module
   that is compliant with the Network Management Datastore Architecture
   (NMDA).  This module can be used to manage the logical resource
   partitioning that may be present on a network device.  Examples of
   common industry terms for logical resource partitioning are logical
   systems or logical routers.  The YANG model in this document conforms
   with NMDA as defined in RFC 8342.

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

Berger, et al.               Standards Track                    [Page 1]
RFC 8530                        YANG LNEs                     March 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 . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Logical Network Elements  . . . . . . . . . . . . . . . . . .   5
     3.1.  LNE Instantiation and Resource Assignment . . . . . . . .   6
     3.2.  LNE Management -- LNE View  . . . . . . . . . . . . . . .   7
     3.3.  LNE Management -- Host Network Device View  . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  Logical Network Element Model . . . . . . . . . . . . . . . .  10
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Appendix A.  Examples . . . . . . . . . . . . . . . . . . . . . .  17
     A.1.  Example: Host-Device-Managed LNE  . . . . . . . . . . . .  17
       A.1.1.  Configuration Data  . . . . . . . . . . . . . . . . .  21
       A.1.2.  State Data  . . . . . . . . . . . . . . . . . . . . .  25
     A.2.  Example: Self-Managed LNE . . . . . . . . . . . . . . . .  33
       A.2.1.  Configuration Data  . . . . . . . . . . . . . . . . .  36
       A.2.2.  State Data  . . . . . . . . . . . . . . . . . . . . .  39
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  49
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  49

Berger, et al.               Standards Track                    [Page 2]
RFC 8530                        YANG LNEs                     March 2019

1.  Introduction

   This document defines an NMDA-compliant YANG module [RFC6020] to
   support the creation of logical network elements (LNEs) on a network
   device.  An LNE is an independently managed virtual device made up of
   resources allocated to it from the host or parent network device.  An
   LNE running on a host network device conceptually parallels a virtual
   machine running on a host system.  Using host-virtualization
   terminology, one could refer to an LNE as a "Guest" and the
   containing network device as the "Host".  While LNEs may be
   implemented via host-virtualization technologies, this is not a