draft-ietf-rtgwg-ni-model-11.txt   draft-ietf-rtgwg-ni-model-12.txt 
Network Working Group L. Berger Network Working Group L. Berger
Internet-Draft LabN Consulting, L.L.C. Internet-Draft LabN Consulting, L.L.C.
Intended status: Standards Track C. Hopps Intended status: Standards Track C. Hopps
Expires: September 2, 2018 Deutsche Telekom Expires: September 20, 2018 Deutsche Telekom
A. Lindem A. Lindem
Cisco Systems Cisco Systems
D. Bogdanovic D. Bogdanovic
X. Liu X. Liu
Jabil Jabil
March 1, 2018 March 19, 2018
YANG Model for Network Instances YANG Model for Network Instances
draft-ietf-rtgwg-ni-model-11 draft-ietf-rtgwg-ni-model-12
Abstract Abstract
This document defines a network instance module. This module can be This document defines a network instance module. This module can be
used to manage the virtual resource partitioning that may be present used to manage the virtual resource partitioning that may be present
on a network device. Examples of common industry terms for virtual on a network device. Examples of common industry terms for virtual
resource partitioning are Virtual Routing and Forwarding (VRF) resource partitioning are Virtual Routing and Forwarding (VRF)
instances and Virtual Switch Instances (VSIs). instances and Virtual Switch Instances (VSIs).
The YANG model in this document conforms to the Network Management The YANG model in this document conforms to the Network Management
Datastore Architecture defined in I-D.ietf-netmod-revised-datastores. Datastore Architecture defined in I-D.ietf-netmod-revised-datastores.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 2, 2018. This Internet-Draft will expire on September 20, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Network Instances . . . . . . . . . . . . . . . . . . . . . . 5 3. Network Instances . . . . . . . . . . . . . . . . . . . . . . 5
3.1. NI Types and Mount Points . . . . . . . . . . . . . . . . 6 3.1. NI Types and Mount Points . . . . . . . . . . . . . . . . 6
3.1.1. Well Known Mount Points . . . . . . . . . . . . . . . 7 3.1.1. Well Known Mount Points . . . . . . . . . . . . . . . 7
3.1.2. NI Type Example . . . . . . . . . . . . . . . . . . . 8 3.1.2. NI Type Example . . . . . . . . . . . . . . . . . . . 8
3.2. NIs and Interfaces . . . . . . . . . . . . . . . . . . . 9 3.2. NIs and Interfaces . . . . . . . . . . . . . . . . . . . 9
3.3. Network Instance Management . . . . . . . . . . . . . . . 10 3.3. Network Instance Management . . . . . . . . . . . . . . . 10
3.4. Network Instance Instantiation . . . . . . . . . . . . . 13 3.4. Network Instance Instantiation . . . . . . . . . . . . . 12
4. Security Considerations . . . . . . . . . . . . . . . . . . . 14 4. Security Considerations . . . . . . . . . . . . . . . . . . . 13
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
6. Network Instance Model . . . . . . . . . . . . . . . . . . . 15 6. Network Instance Model . . . . . . . . . . . . . . . . . . . 14
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
7.1. Normative References . . . . . . . . . . . . . . . . . . 21 7.1. Normative References . . . . . . . . . . . . . . . . . . 20
7.2. Informative References . . . . . . . . . . . . . . . . . 23 7.2. Informative References . . . . . . . . . . . . . . . . . 22
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 24 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 23
Appendix B. Example NI usage . . . . . . . . . . . . . . . . . . 24 Appendix B. Example NI usage . . . . . . . . . . . . . . . . . . 23
B.1. Configuration Data . . . . . . . . . . . . . . . . . . . 24 B.1. Configuration Data . . . . . . . . . . . . . . . . . . . 23
B.2. State Data - Non-NDMA Version . . . . . . . . . . . . . . 28 B.2. State Data - Non-NMDA Version . . . . . . . . . . . . . . 27
B.3. State Data - NDMA Version . . . . . . . . . . . . . . . . 34 B.3. State Data - NMDA Version . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42
1. Introduction 1. Introduction
This document defines the second of two new modules that are defined This document defines the second of two new modules that are defined
to support the configuration and operation of network-devices that to support the configuration and operation of network-devices that
allow for the partitioning of resources from both, or either, allow for the partitioning of resources from both, or either,
management and networking perspectives. Both leverage the YANG management and networking perspectives. Both leverage the YANG
functionality enabled by YANG Schema Mount functionality enabled by YANG Schema Mount
[I-D.ietf-netmod-schema-mount]. [I-D.ietf-netmod-schema-mount].
skipping to change at page 10, line 16 skipping to change at page 10, line 16
currently defined, to assign an interface to both an LNE and NI, the currently defined, to assign an interface to both an LNE and NI, the
interface would first be assigned to the LNE using the mechanisms interface would first be assigned to the LNE using the mechanisms
defined in [I-D.ietf-rtgwg-lne-model] and then within that LNE's defined in [I-D.ietf-rtgwg-lne-model] and then within that LNE's
interface module, the LNE's representation of that interface would be interface module, the LNE's representation of that interface would be
assigned to an NI. assigned to an NI.
3.3. Network Instance Management 3.3. Network Instance Management
Modules that may be used to represent network instance information Modules that may be used to represent network instance information
will be available under the ni-type specific 'root' mount point. The will be available under the ni-type specific 'root' mount point. The
use-schema mechanism defined as part of the Schema Mount module "shared-schema" method defined in the "ietf-yang-schema-mount" module
[I-D.ietf-netmod-schema-mount] MUST be used with the module defined [I-D.ietf-netmod-schema-mount] MUST be used to identify accessible
in this document to identify accessible modules. A future version of modules. A future version of this document could relax this
this document could relax this requirement. Mounted modules in the requirement. Mounted modules SHOULD be defined with access, via the
non-inline case SHOULD be defined with access, via the appropriate appropriate schema mount parent-references
schema mount parent-references [I-D.ietf-netmod-schema-mount], to [I-D.ietf-netmod-schema-mount], to device resources such as
device resources such as interfaces. An implementation MAY choose to interfaces. An implementation MAY choose to restrict parent
restrict parent referenced information to information related to a referenced information to information related to a specific instance,
specific instance, e.g., only allowing references to interfaces that e.g., only allowing references to interfaces that have a "bind-
have a "bind-network-instance-name" which is identical to the network-instance-name" which is identical to the instance's "name".
instance's "name".
All modules that represent control-plane and data-plane information All modules that represent control-plane and data-plane information
may be present at the 'root' mount point, and be accessible via paths may be present at the 'root' mount point, and be accessible via paths
modified per [I-D.ietf-netmod-schema-mount]. The list of available modified per [I-D.ietf-netmod-schema-mount]. The list of available
modules is expected to be implementation dependent, as is the method modules is expected to be implementation dependent, as is the method
used by an implementation to support NIs. used by an implementation to support NIs.
For example, the following could be used to define the data For example, the following could be used to define the data
organization of the example NI shown in Section 3.1.2: organization of the example NI shown in Section 3.1.2:
"ietf-yang-schema-mount:schema-mounts": { "ietf-yang-schema-mount:schema-mounts": {
"mount-point": [ "mount-point": [
{ {
"module": "ietf-network-instance", "module": "ietf-network-instance",
"label": "vrf-root", "label": "vrf-root",
"use-schema": [ "shared-schema": {
{ "parent-reference": [
"name": "ni-schema", "/*[namespace-uri() = 'urn:ietf:...:ietf-interfaces']"
"parent-reference": [ ]
"/*[namespace-uri() = 'urn:ietf:...:ietf-interfaces']" }
]
}
]
}
],
"schema": [
{
"name": "ni-schema",
"module": [
{
"name": "ietf-routing",
"revision": "2018-01-25",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-routing",
"conformance-type": "implement"
},
{
"name": "ietf-ospf",
"revision": "2017-10-30",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-ospf",
"conformance-type": "implement"
}
]
} }
] ]
} }
Module data identified under "schema" will be instantiated under the Module data identified according to the ietf-yang-schema-mount module
mount point identified under "mount-point". These modules will be will be instantiated under the mount point identified under "mount-
able to reference information for nodes belonging to top-level point". These modules will be able to reference information for
modules that are identified under "parent-reference". Parent nodes belonging to top-level modules that are identified under
referenced information is available to clients via their top level "parent-reference". Parent referenced information is available to
paths only, and not under the associated mount point. clients via their top level paths only, and not under the associated
mount point.
To allow a client to understand the previously mentioned instance To allow a client to understand the previously mentioned instance
restrictions on parent referenced information, an implementation MAY restrictions on parent referenced information, an implementation MAY
represent such restrictions in the "parent-reference" leaf-list. For represent such restrictions in the "parent-reference" leaf-list. For
example: example:
"namespace": [ "namespace": [
{ {
"prefix": "if", "prefix": "if",
"uri": "urn:ietf:params:xml:ns:yang:ietf-interfaces" "uri": "urn:ietf:params:xml:ns:yang:ietf-interfaces"
}, },
{ {
"prefix": "ni", "prefix": "ni",
"uri": "urn:ietf:params:xml:ns:yang:ietf-network-instance" "uri": "urn:ietf:params:xml:ns:yang:ietf-network-instance"
} }
], ],
"mount-point": [ "mount-point": [
{ {
"module": "ietf-network-instance",
"label": "vrf-root",
"shared-schema": {
"parent-reference": [ "parent-reference": [
"/if:interfaces/if:interface "/if:interfaces/if:interface
[ni:bind-network-instance-name = current()/../ni:name]", [ni:bind-network-instance-name = current()/../ni:name]",
"/if:interfaces/if:interface/ip:ipv4 "/if:interfaces/if:interface/ip:ipv4
[ni:bind-network-instance-name = current()/../ni:name]", [ni:bind-network-instance-name = current()/../ni:name]",
"/if:interfaces/if:interface/ip:ipv6 "/if:interfaces/if:interface/ip:ipv6
[ni:bind-network-instance-name = current()/../ni:name]", [ni:bind-network-instance-name = current()/../ni:name]"
]
} }
], }
],
The same such "parent-reference" restrictions for non-NDMA The same such "parent-reference" restrictions for non-NMDA
implementations can be represented based on the [RFC7223] and implementations can be represented based on the [RFC7223] and
[RFC7277] as: [RFC7277] as:
"namespace": [ "namespace": [
{ {
"prefix": "if", "prefix": "if",
"uri": "urn:ietf:params:xml:ns:yang:ietf-interfaces" "uri": "urn:ietf:params:xml:ns:yang:ietf-interfaces"
}, },
{ {
"prefix": "ni", "prefix": "ni",
"uri": "urn:ietf:params:xml:ns:yang:ietf-network-instance" "uri": "urn:ietf:params:xml:ns:yang:ietf-network-instance"
} }
], ],
"mount-point": [ "mount-point": [
{ {
"module": "ietf-network-instance",
"label": "vrf-root",
"shared-schema": {
"parent-reference": [ "parent-reference": [
"/if:interfaces/if:interface "/if:interfaces/if:interface
[ni:bind-network-instance-name = current()/../ni:name]", [ni:bind-network-instance-name = current()/../ni:name]",
"/if:interfaces-state/if:interface "/if:interfaces-state/if:interface
[if:name = /if:interfaces/if:interface [if:name = /if:interfaces/if:interface
[ni:bind-ni-name = current()/../ni:name]/if:name]", [ni:bind-ni-name = current()/../ni:name]/if:name]",
"/if:interfaces/if:interface/ip:ipv4 "/if:interfaces/if:interface/ip:ipv4
[ni:bind-network-instance-name = current()/../ni:name]", [ni:bind-network-instance-name = current()/../ni:name]",
"/if:interfaces-state/if:interface/ip:ipv4 "/if:interfaces-state/if:interface/ip:ipv4
[if:name = /if:interfaces/if:interface/ip:ipv4 [if:name = /if:interfaces/if:interface/ip:ipv4
[ni:bind-ni-name = current()/../ni:name]/if:name]", [ni:bind-ni-name = current()/../ni:name]/if:name]",
"/if:interfaces/if:interface/ip:ipv6 "/if:interfaces/if:interface/ip:ipv6
[ni:bind-network-instance-name = current()/../ni:name]", [ni:bind-network-instance-name = current()/../ni:name]",
"/if:interfaces-state/if:interface/ip:ipv6 "/if:interfaces-state/if:interface/ip:ipv6
[if:name = /if:interfaces/if:interface/ip:ipv4 [if:name = /if:interfaces/if:interface/ip:ipv4
[ni:bind-ni-name = current()/../ni:name]/if:name]", [ni:bind-ni-name = current()/../ni:name]/if:name]"
] ]
} }
], }
],
3.4. Network Instance Instantiation 3.4. Network Instance Instantiation
Network instances may be controlled by clients using existing list Network instances may be controlled by clients using existing list
operations. When a list entry is created, a new instance is operations. When a list entry is created, a new instance is
instantiated. The models mounted under an NI root are expected to be instantiated. The models mounted under an NI root are expected to be
dependent on the server implementation. When a list entry is dependent on the server implementation. When a list entry is
deleted, an existing network instance is destroyed. For more deleted, an existing network instance is destroyed. For more
information, see [RFC7950] Section 7.8.6. information, see [RFC7950] Section 7.8.6.
skipping to change at page 15, line 35 skipping to change at page 14, line 38
name: ietf-network-instance name: ietf-network-instance
namespace: urn:ietf:params:xml:ns:yang:ietf-network-instance namespace: urn:ietf:params:xml:ns:yang:ietf-network-instance
prefix: ni prefix: ni
reference: RFC XXXX reference: RFC XXXX
6. Network Instance Model 6. Network Instance Model
The structure of the model defined in this document is described by The structure of the model defined in this document is described by
the YANG module below. the YANG module below.
<CODE BEGINS> file "ietf-network-instance@2018-02-03.yang" <CODE BEGINS> file "ietf-network-instance@2018-03-20.yang"
module ietf-network-instance { module ietf-network-instance {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-network-instance"; namespace "urn:ietf:params:xml:ns:yang:ietf-network-instance";
prefix ni; prefix ni;
// import some basic types // import some basic types
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference "draft-ietf-netmod-rfc7223bis: A YANG Data Model reference "draft-ietf-netmod-rfc7223bis: A YANG Data Model
skipping to change at page 16, line 48 skipping to change at page 15, line 51
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove // RFC Ed.: replace XXXX with actual RFC number and remove
// this note // this note
// RFC Ed.: please update TBD // RFC Ed.: please update TBD
revision 2018-02-03 { revision 2018-03-20 {
description description
"Initial revision."; "Initial revision.";
reference "RFC TBD"; reference "RFC TBD";
} }
// top level device definition statements // top level device definition statements
container network-instances { container network-instances {
description description
"Network instances each of which consists of a "Network instances each of which consists of a
VRFs (virtual routing and forwarding) and/or VRFs (virtual routing and forwarding) and/or
VSIs (virtual switching instances)."; VSIs (virtual switching instances).";
reference "draft-ietf-rtgwg-rfc8022bis - A YANG Data Model reference "draft-ietf-rtgwg-rfc8022bis - A YANG Data Model
skipping to change at page 22, line 17 skipping to change at page 21, line 17
ietf-netmod-schema-mount-08 (work in progress), October ietf-netmod-schema-mount-08 (work in progress), October
2017. 2017.
[I-D.ietf-netmod-yang-tree-diagrams] [I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-06 (work in progress), ietf-netmod-yang-tree-diagrams-06 (work in progress),
February 2018. February 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- DOI 10.17487/RFC2119, March 1997,
editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, <https://www.rfc- DOI 10.17487/RFC3688, January 2004,
editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, <https://www.rfc- DOI 10.17487/RFC5246, August 2008,
editor.org/info/rfc5246>. <https://www.rfc-editor.org/info/rfc5246>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, <https://www.rfc- DOI 10.17487/RFC6020, October 2010,
editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, <https://www.rfc- DOI 10.17487/RFC6536, March 2012,
editor.org/info/rfc6536>. <https://www.rfc-editor.org/info/rfc6536>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
7.2. Informative References 7.2. Informative References
skipping to change at page 23, line 31 skipping to change at page 22, line 31
in progress), October 2017. in progress), October 2017.
[I-D.ietf-netmod-rfc8022bis] [I-D.ietf-netmod-rfc8022bis]
Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", draft-ietf-netmod- Routing Management (NMDA Version)", draft-ietf-netmod-
rfc8022bis-11 (work in progress), January 2018. rfc8022bis-11 (work in progress), January 2018.
[I-D.ietf-ospf-yang] [I-D.ietf-ospf-yang]
Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,
"Yang Data Model for OSPF Protocol", draft-ietf-ospf- "Yang Data Model for OSPF Protocol", draft-ietf-ospf-
yang-09 (work in progress), October 2017. yang-10 (work in progress), March 2018.
[I-D.ietf-rtgwg-device-model] [I-D.ietf-rtgwg-device-model]
Lindem, A., Berger, L., Bogdanovic, D., and C. Hopps, Lindem, A., Berger, L., Bogdanovic, D., and C. Hopps,
"Network Device YANG Logical Organization", draft-ietf- "Network Device YANG Logical Organization", draft-ietf-
rtgwg-device-model-02 (work in progress), March 2017. rtgwg-device-model-02 (work in progress), March 2017.
[I-D.ietf-rtgwg-lne-model] [I-D.ietf-rtgwg-lne-model]
Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X. Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X.
Liu, "YANG Model for Logical Network Elements", draft- Liu, "YANG Model for Logical Network Elements", draft-
ietf-rtgwg-lne-model-07 (work in progress), February 2018. ietf-rtgwg-lne-model-09 (work in progress), March 2018.
[RFC4026] Andersson, L. and T. Madsen, "Provider Provisioned Virtual [RFC4026] Andersson, L. and T. Madsen, "Provider Provisioned Virtual
Private Network (VPN) Terminology", RFC 4026, Private Network (VPN) Terminology", RFC 4026,
DOI 10.17487/RFC4026, March 2005, <https://www.rfc- DOI 10.17487/RFC4026, March 2005,
editor.org/info/rfc4026>. <https://www.rfc-editor.org/info/rfc4026>.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <https://www.rfc-editor.org/info/rfc4364>. 2006, <https://www.rfc-editor.org/info/rfc4364>.
[RFC4664] Andersson, L., Ed. and E. Rosen, Ed., "Framework for Layer [RFC4664] Andersson, L., Ed. and E. Rosen, Ed., "Framework for Layer
2 Virtual Private Networks (L2VPNs)", RFC 4664, 2 Virtual Private Networks (L2VPNs)", RFC 4664,
DOI 10.17487/RFC4664, September 2006, <https://www.rfc- DOI 10.17487/RFC4664, September 2006,
editor.org/info/rfc4664>. <https://www.rfc-editor.org/info/rfc4664>.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface [RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
<https://www.rfc-editor.org/info/rfc7223>. <https://www.rfc-editor.org/info/rfc7223>.
[RFC7277] Bjorklund, M., "A YANG Data Model for IP Management", [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management",
RFC 7277, DOI 10.17487/RFC7277, June 2014, RFC 7277, DOI 10.17487/RFC7277, June 2014,
<https://www.rfc-editor.org/info/rfc7277>. <https://www.rfc-editor.org/info/rfc7277>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
skipping to change at page 28, line 10 skipping to change at page 27, line 10
{ {
"name": "john", "name": "john",
"password": "$0$password" "password": "$0$password"
} }
] ]
} }
} }
} }
B.2. State Data - Non-NDMA Version B.2. State Data - Non-NMDA Version
The following shows state data for the configuration example above The following shows state data for the configuration example above
based on [RFC7223], [RFC7277], and [RFC8022]. based on [RFC7223], [RFC7277], and [RFC8022].
{ {
"ietf-network-instance:network-instances": { "ietf-network-instance:network-instances": {
"network-instance": [ "network-instance": [
{ {
"name": "vrf-red", "name": "vrf-red",
"vrf-root": { "vrf-root": {
"ietf-yang-library:modules-state": {
"module-set-id": "123e4567-e89b-12d3-a456-426655440000",
"module": [
{
"name": "ietf-yang-library",
"revision": "2016-06-21",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-yang-library",
"conformance-type": "implement"
},
{
"name": "ietf-ospf",
"revision": "2018-03-03",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-ospf",
"conformance-type": "implement"
},
{
"name": "ietf-routing",
"revision": "2018-03-13",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-routing",
"conformance-type": "implement"
}
]
},
"ietf-routing:routing-state": { "ietf-routing:routing-state": {
"router-id": "192.0.2.1", "router-id": "192.0.2.1",
"control-plane-protocols": { "control-plane-protocols": {
"control-plane-protocol": [ "control-plane-protocol": [
{ {
"type": "ietf-routing:ospf", "type": "ietf-routing:ospf",
"name": "1", "name": "1",
"ietf-ospf:ospf": { "ietf-ospf:ospf": {
"af": "ipv4", "af": "ipv4",
"areas": { "areas": {
skipping to change at page 29, line 6 skipping to change at page 28, line 32
} }
} }
] ]
} }
} }
} }
}, },
{ {
"name": "vrf-blue", "name": "vrf-blue",
"vrf-root": { "vrf-root": {
"ietf-yang-library:modules-state": {
"module-set-id": "123e4567-e89b-12d3-a456-426655440000",
"module": [
{
"name": "ietf-yang-library",
"revision": "2016-06-21",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-yang-library",
"conformance-type": "implement"
},
{
"name": "ietf-ospf",
"revision": "2018-03-03",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-ospf",
"conformance-type": "implement"
},
{
"name": "ietf-routing",
"revision": "2018-03-13",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-routing",
"conformance-type": "implement"
}
]
},
"ietf-routing:routing-state": { "ietf-routing:routing-state": {
"router-id": "192.0.2.2", "router-id": "192.0.2.2",
"control-plane-protocols": { "control-plane-protocols": {
"control-plane-protocol": [ "control-plane-protocol": [
{ {
"type": "ietf-routing:ospf", "type": "ietf-routing:ospf",
"name": "1", "name": "1",
"ietf-ospf:ospf": { "ietf-ospf:ospf": {
"af": "ipv4", "af": "ipv4",
"areas": { "areas": {
skipping to change at page 32, line 31 skipping to change at page 32, line 36
"revision": "2018-02-03", "revision": "2018-02-03",
"feature": [ "feature": [
"bind-network-instance-name" "bind-network-instance-name"
], ],
"namespace": "namespace":
"urn:ietf:params:xml:ns:yang:ietf-network-instance", "urn:ietf:params:xml:ns:yang:ietf-network-instance",
"conformance-type": "implement" "conformance-type": "implement"
}, },
{ {
"name": "ietf-ospf", "name": "ietf-ospf",
"revision": "2017-03-12", "revision": "2018-03-03",
"namespace": "urn:ietf:params:xml:ns:yang:ietf-ospf", "namespace": "urn:ietf:params:xml:ns:yang:ietf-ospf",
"conformance-type": "implement" "conformance-type": "implement"
}, },
{ {
"name": "ietf-routing", "name": "ietf-routing",
"revision": "2016-11-04", "revision": "2018-03-13",
"namespace": "namespace":
"urn:ietf:params:xml:ns:yang:ietf-routing", "urn:ietf:params:xml:ns:yang:ietf-routing",
"conformance-type": "implement" "conformance-type": "implement"
}, },
{ {
"name": "ietf-system", "name": "ietf-system",
"revision": "2014-08-06", "revision": "2014-08-06",
"namespace": "namespace":
"urn:ietf:params:xml:ns:yang:ietf-system", "urn:ietf:params:xml:ns:yang:ietf-system",
"conformance-type": "implement" "conformance-type": "implement"
skipping to change at page 33, line 30 skipping to change at page 33, line 35
"conformance-type": "import" "conformance-type": "import"
} }
] ]
}, },
"ietf-yang-schema-mount:schema-mounts": { "ietf-yang-schema-mount:schema-mounts": {
"mount-point": [ "mount-point": [
{ {
"module": "ietf-network-instance", "module": "ietf-network-instance",
"label": "vrf-root", "label": "vrf-root",
"use-schema": [ "shared-schema": {
{ "parent-reference": [
"name": "ni-schema", "/*[namespace-uri() = 'urn:ietf:...:ietf-interfaces']"
"parent-reference": [ ]
"/*[namespace-uri() = 'urn:ietf:...:ietf-interfaces']" }
]
}
]
}
],
"schema": [
{
"name": "ni-schema",
"module": [
{
"name": "ietf-routing",
"revision": "2016-11-04",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-routing",
"conformance-type": "implement"
},
{
"name": "ietf-ospf",
"revision": "2017-03-12",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-ospf",
"conformance-type": "implement"
}
]
} }
] ]
} }
} }
B.3. State Data - NDMA Version B.3. State Data - NMDA Version
The following shows state data for the configuration example above The following shows state data for the configuration example above
based on [I-D.ietf-netmod-rfc7223bis], [I-D.ietf-netmod-rfc7277bis], based on [I-D.ietf-netmod-rfc7223bis], [I-D.ietf-netmod-rfc7277bis],
and [I-D.ietf-netmod-rfc8022bis]. and [I-D.ietf-netmod-rfc8022bis].
{ {
"ietf-network-instance:network-instances": { "ietf-network-instance:network-instances": {
"network-instance": [ "network-instance": [
{ {
"name": "vrf-red", "name": "vrf-red",
"vrf-root": { "vrf-root": {
"ietf-routing:routing": { "ietf-yang-library:yang-library": {
"router-id": "192.0.2.1", "checksum": "41e2ab5dc325f6d86f743e8da3de323f1a61a801",
"control-plane-protocols": { "module-set": [
"control-plane-protocol": [ {
{ "name": "ni-modules",
"type": "ietf-routing:ospf", "module": [
"name": "1", {
"ietf-ospf:ospf": { "name": "ietf-yang-library",
"af": "ipv4", "revision": "2016-06-21",
"areas": { "namespace":
"area": [ "urn:ietf:params:xml:ns:yang:ietf-yang-library",
{ "conformance-type": "implement"
"area-id": "203.0.113.1", },
"interfaces": { {
"interface": [ "name": "ietf-ospf",
{ "revision": "2018-03-03",
"name": "eth1", "namespace":
"cost": 10 "urn:ietf:params:xml:ns:yang:ietf-ospf",
} "conformance-type": "implement"
] },
} {
} "name": "ietf-routing",
] "revision": "2018-03-13",
} "namespace":
"urn:ietf:params:xml:ns:yang:ietf-routing",
"conformance-type": "implement"
}
],
"import-only-module": [
{
"name": "ietf-inet-types",
"revision": "2013-07-15",
"namespace": "urn:ietf:params:xml:ns:yang:ietf-inet-types"
},
{
"name": "ietf-yang-types",
"revision": "2013-07-15",
"namespace": "urn:ietf:params:xml:ns:yang:ietf-yang-types"
},
{
"name": "ietf-datastores",
"revision": "2018-02-14",
"namespace": "urn:ietf:params:xml:ns:yang:ietf-datastores"
}
} ]
} }
] ],
} "schema": [
} {
} "name": "ni-schema",
}, "module-set": [ "ni-modules" ]
{ }
"name": "vrf-blue", ],
"vrf-root": { "datastore": [
"ietf-routing:routing": { {
"router-id": "192.0.2.2", "name": "ietf-datastores:running",
"control-plane-protocols": { "schema": "ni-schema"
"control-plane-protocol": [ },
{ {
"type": "ietf-routing:ospf", "name": "ietf-datastores:operational",
"name": "1", "schema": "ni-schema"
"ietf-ospf:ospf": { }
"af": "ipv4", ]
"areas": { },
"area": [ "ietf-routing:routing": {
{ "router-id": "192.0.2.1",
"area-id": "203.0.113.1", "control-plane-protocols": {
"interfaces": { "control-plane-protocol": [
"interface": [ {
{ "type": "ietf-routing:ospf",
"name": "eth2", "name": "1",
"cost": 10 "ietf-ospf:ospf": {
} "af": "ipv4",
] "areas": {
} "area": [
} {
] "area-id": "203.0.113.1",
} "interfaces": {
} "interface": [
} {
] "name": "eth1",
} "cost": 10
} }
} ]
} }
] }
}, ]
}
}
}
]
}
"ietf-interfaces:interfaces": { }
"interfaces": { }
"interface": [ },
{ {
"name": "eth0", "name": "vrf-blue",
"type": "iana-if-type:ethernetCsmacd", "vrf-root": {
"oper-status": "up", "ietf-yang-library:yang-library": {
"phys-address": "00:01:02:A1:B1:C0", "checksum": "41e2ab5dc325f6d86f743e8da3de323f1a61a801",
"statistics": { "module-set": [
"discontinuity-time": "2017-06-26T12:34:56-05:00" {
}, "name": "ni-modules",
"ip:ipv4": { "module": [
"address": [ {
{ "name": "ietf-yang-library",
"ip": "192.0.2.10", "revision": "2016-06-21",
"prefix-length": 24, "namespace":
} "urn:ietf:params:xml:ns:yang:ietf-yang-library",
] "conformance-type": "implement"
} },
"ip:ipv6": { {
"address": [ "name": "ietf-ospf",
{ "revision": "2018-03-03",
"ip": "2001:db8:0:2::10", "namespace":
"prefix-length": 64, "urn:ietf:params:xml:ns:yang:ietf-ospf",
} "conformance-type": "implement"
] },
} {
}, "name": "ietf-routing",
{ "revision": "2018-03-13",
"name": "eth1", "namespace":
"type": "iana-if-type:ethernetCsmacd", "urn:ietf:params:xml:ns:yang:ietf-routing",
"oper-status": "up", "conformance-type": "implement"
"phys-address": "00:01:02:A1:B1:C1", }
"statistics": { ],
"discontinuity-time": "2017-06-26T12:34:56-05:00" "import-only-module": [
}, {
"ip:ipv4": { "name": "ietf-inet-types",
"address": [ "revision": "2013-07-15",
{ "namespace": "urn:ietf:params:xml:ns:yang:ietf-inet-types"
"ip": "192.0.2.11", },
"prefix-length": 24, {
} "name": "ietf-yang-types",
] "revision": "2013-07-15",
} "namespace": "urn:ietf:params:xml:ns:yang:ietf-yang-types"
"ip:ipv6": { },
"address": [ {
{ "name": "ietf-datastores",
"ip": "2001:db8:0:2::11", "revision": "2018-02-14",
"prefix-length": 64, "namespace": "urn:ietf:params:xml:ns:yang:ietf-datastores"
} }
] ]
} }
],
"schema": [
{
"name": "ni-schema",
"module-set": [ "ni-modules" ]
}
],
"datastore": [
{
"name": "ietf-datastores:running",
"schema": "ni-schema"
},
{
"name": "ietf-datastores:operational",
"schema": "ni-schema"
}
]
},
"ietf-routing:routing": {
"router-id": "192.0.2.2",
"control-plane-protocols": {
"control-plane-protocol": [
{
"type": "ietf-routing:ospf",
"name": "1",
"ietf-ospf:ospf": {
"af": "ipv4",
"areas": {
"area": [
{
"area-id": "203.0.113.1",
"interfaces": {
"interface": [
{
"name": "eth2",
"cost": 10
}
]
}
}
]
}
}
}
}, ]
{ }
"name": "eth2", }
"type": "iana-if-type:ethernetCsmacd", }
"oper-status": "up", }
"phys-address": "00:01:02:A1:B1:C2", ]
"statistics": { },
"discontinuity-time": "2017-06-26T12:34:56-05:00"
},
"ip:ipv4": {
"address": [
{
"ip": "192.0.2.11",
"prefix-length": 24,
}
]
}
"ip:ipv6": {
"address": [
{
"ip": "2001:db8:0:2::11",
"prefix-length": 64,
}
]
}
}
]
}
},
"ietf-system:system-state": { "ietf-interfaces:interfaces": {
"platform": { "interfaces": {
"os-name": "NetworkOS" "interface": [
} {
} "name": "eth0",
"type": "iana-if-type:ethernetCsmacd",
"oper-status": "up",
"phys-address": "00:01:02:A1:B1:C0",
"statistics": {
"discontinuity-time": "2017-06-26T12:34:56-05:00"
},
"ip:ipv4": {
"address": [
{
"ip": "192.0.2.10",
"prefix-length": 24,
}
]
}
"ip:ipv6": {
"address": [
{
"ip": "2001:db8:0:2::10",
"prefix-length": 64,
}
]
}
},
{
"name": "eth1",
"type": "iana-if-type:ethernetCsmacd",
"oper-status": "up",
"phys-address": "00:01:02:A1:B1:C1",
"statistics": {
"discontinuity-time": "2017-06-26T12:34:56-05:00"
},
"ip:ipv4": {
"address": [
{
"ip": "192.0.2.11",
"prefix-length": 24,
}
]
}
"ip:ipv6": {
"address": [
{
"ip": "2001:db8:0:2::11",
"prefix-length": 64,
}
]
}
},
{
"name": "eth2",
"type": "iana-if-type:ethernetCsmacd",
"oper-status": "up",
"phys-address": "00:01:02:A1:B1:C2",
"statistics": {
"discontinuity-time": "2017-06-26T12:34:56-05:00"
},
"ip:ipv4": {
"address": [
{
"ip": "192.0.2.11",
"prefix-length": 24,
}
]
}
"ip:ipv6": {
"address": [
{
"ip": "2001:db8:0:2::11",
"prefix-length": 64,
}
]
}
}
]
}
},
"ietf-yang-library:modules-state": { "ietf-system:system-state": {
"module-set-id": "123e4567-e89b-12d3-a456-426655440000", "platform": {
"module": [ "os-name": "NetworkOS"
{ }
"name": "iana-if-type", }
"revision": "2014-05-08", "ietf-yang-library:modules-state": {
"namespace": "module-set-id": "123e4567-e89b-12d3-a456-426655440000",
"urn:ietf:params:xml:ns:yang:iana-if-type", "module": [
"conformance-type": "import" {
}, "name": "iana-if-type",
{ "revision": "2014-05-08",
"name": "ietf-inet-types", "namespace":
"revision": "2013-07-15", "urn:ietf:params:xml:ns:yang:iana-if-type",
"namespace": "conformance-type": "import"
"urn:ietf:params:xml:ns:yang:ietf-inet-types", },
"conformance-type": "import" {
}, "name": "ietf-inet-types",
{ "revision": "2013-07-15",
"name": "ietf-interfaces", "namespace":
"revision": "2018-01-09", "urn:ietf:params:xml:ns:yang:ietf-inet-types",
"feature": [ "conformance-type": "import"
"arbitrary-names", },
"pre-provisioning" {
], "name": "ietf-interfaces",
"namespace": "revision": "2018-01-09",
"urn:ietf:params:xml:ns:yang:ietf-interfaces", "feature": [
"conformance-type": "implement" "arbitrary-names",
}, "pre-provisioning"
{ ],
"name": "ietf-ip", "namespace":
"revision": "2018-01-09", "urn:ietf:params:xml:ns:yang:ietf-interfaces",
"namespace": "conformance-type": "implement"
"urn:ietf:params:xml:ns:yang:ietf-ip", },
"conformance-type": "implement" {
}, "name": "ietf-ip",
{ "revision": "2018-01-09",
"name": "ietf-network-instance", "namespace":
"revision": "2018-02-03", "urn:ietf:params:xml:ns:yang:ietf-ip",
"feature": [ "conformance-type": "implement"
"bind-network-instance-name" },
], {
"namespace": "name": "ietf-network-instance",
"urn:ietf:params:xml:ns:yang:ietf-network-instance", "revision": "2018-02-03",
"conformance-type": "implement" "feature": [
}, "bind-network-instance-name"
{ ],
"name": "ietf-ospf", "namespace":
"revision": "2017-10-30", "urn:ietf:params:xml:ns:yang:ietf-network-instance",
"namespace": "urn:ietf:params:xml:ns:yang:ietf-ospf", "conformance-type": "implement"
"conformance-type": "implement" },
}, {
{ "name": "ietf-ospf",
"name": "ietf-routing", "revision": "2017-10-30",
"revision": "2018-01-25", "namespace": "urn:ietf:params:xml:ns:yang:ietf-ospf",
"namespace": "conformance-type": "implement"
"urn:ietf:params:xml:ns:yang:ietf-routing", },
"conformance-type": "implement" {
}, "name": "ietf-routing",
{ "revision": "2018-01-25",
"name": "ietf-system", "namespace":
"revision": "2014-08-06", "urn:ietf:params:xml:ns:yang:ietf-routing",
"namespace": "conformance-type": "implement"
"urn:ietf:params:xml:ns:yang:ietf-system", },
"conformance-type": "implement" {
}, "name": "ietf-system",
{ "revision": "2014-08-06",
"name": "ietf-yang-library", "namespace":
"revision": "2016-06-21", "urn:ietf:params:xml:ns:yang:ietf-system",
"namespace": "conformance-type": "implement"
"urn:ietf:params:xml:ns:yang:ietf-yang-library", },
"conformance-type": "implement" {
}, "name": "ietf-yang-library",
{ "revision": "2016-06-21",
"name": "ietf-yang-schema-mount", "namespace":
"revision": "2017-05-16", "urn:ietf:params:xml:ns:yang:ietf-yang-library",
"namespace": "conformance-type": "implement"
"urn:ietf:params:xml:ns:yang:ietf-yang-schema-mount", },
"conformance-type": "implement" {
}, "name": "ietf-yang-schema-mount",
{ "revision": "2017-05-16",
"name": "ietf-yang-types", "namespace":
"revision": "2013-07-15", "urn:ietf:params:xml:ns:yang:ietf-yang-schema-mount",
"namespace": "conformance-type": "implement"
"urn:ietf:params:xml:ns:yang:ietf-yang-types", },
"conformance-type": "import" {
} "name": "ietf-yang-types",
] "revision": "2013-07-15",
}, "namespace":
"urn:ietf:params:xml:ns:yang:ietf-yang-types",
"conformance-type": "import"
}
]
},
"ietf-yang-schema-mount:schema-mounts": { "ietf-yang-schema-mount:schema-mounts": {
"mount-point": [ "mount-point": [
{ {
"module": "ietf-network-instance", "module": "ietf-network-instance",
"label": "vrf-root", "label": "vrf-root",
"use-schema": [ "shared-schema": {
{ "parent-reference": [
"name": "ni-schema", "/*[namespace-uri() = 'urn:ietf:...:ietf-interfaces']"
"parent-reference": [ ]
"/*[namespace-uri() = 'urn:ietf:...:ietf-interfaces']" }
] }
} ]
] }
} }
],
"schema": [
{
"name": "ni-schema",
"module": [
{
"name": "ietf-routing",
"revision": "2018-01-25",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-routing",
"conformance-type": "implement"
},
{
"name": "ietf-ospf",
"revision": "2017-10-30",
"namespace":
"urn:ietf:params:xml:ns:yang:ietf-ospf",
"conformance-type": "implement"
}
]
}
]
}
}
Authors' Addresses Authors' Addresses
Lou Berger Lou Berger
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
Email: lberger@labn.net Email: lberger@labn.net
Christan Hopps Christan Hopps
Deutsche Telekom Deutsche Telekom
 End of changes. 43 change blocks. 
431 lines changed or deleted 547 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/