draft-ietf-rtgwg-ni-model-10.txt   draft-ietf-rtgwg-ni-model-11.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: August 17, 2018 Deutsche Telekom Expires: September 2, 2018 Deutsche Telekom
A. Lindem A. Lindem
Cisco Systems Cisco Systems
D. Bogdanovic D. Bogdanovic
X. Liu X. Liu
Jabil Jabil
February 13, 2018 March 1, 2018
YANG Model for Network Instances YANG Model for Network Instances
draft-ietf-rtgwg-ni-model-10 draft-ietf-rtgwg-ni-model-11
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
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 http://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 August 17, 2018. This Internet-Draft will expire on September 2, 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 (http://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
skipping to change at page 8, line 43 skipping to change at page 8, line 43
| +--ro l3vpn:l3vpn-state | +--ro l3vpn:l3vpn-state
| | ... // state data | | ... // state data
+--rw (root-type) +--rw (root-type)
+--:(vrf-root) +--:(vrf-root)
+--mp vrf-root +--mp vrf-root
+--rw rt:routing/ +--rw rt:routing/
| +--rw router-id? yang:dotted-quad | +--rw router-id? yang:dotted-quad
| +--rw control-plane-protocols | +--rw control-plane-protocols
| +--rw control-plane-protocol* [type name] | +--rw control-plane-protocol* [type name]
| +--rw ospf:ospf/ | +--rw ospf:ospf/
| +--rw instance* [af] | +--rw area* [area-id]
| +--rw areas | +--rw interfaces
| +--rw area* [area-id] | +--rw interface* [name]
| +--rw interfaces | +--rw name if:interface-ref
| +--rw interface* [name] | +--rw cost? uint16
| +--rw name if:interface-ref
| +--rw cost? uint16
+--ro if:interfaces@ +--ro if:interfaces@
| ... | ...
This shows YANG Routing Management [I-D.ietf-netmod-rfc8022bis] and This shows YANG Routing Management [I-D.ietf-netmod-rfc8022bis] and
YANG OSPF [I-D.ietf-ospf-yang] as mounted modules. The mounted YANG OSPF [I-D.ietf-ospf-yang] as mounted modules. The mounted
modules can reference interface information via a parent-reference to modules can reference interface information via a parent-reference to
the containers defined in [I-D.ietf-netmod-rfc7223bis]. the containers defined in [I-D.ietf-netmod-rfc7223bis].
3.2. NIs and Interfaces 3.2. NIs and Interfaces
skipping to change at page 22, line 12 skipping to change at page 22, line 12
draft-ietf-netmod-rfc7277bis-03 (work in progress), draft-ietf-netmod-rfc7277bis-03 (work in progress),
January 2018. January 2018.
[I-D.ietf-netmod-schema-mount] [I-D.ietf-netmod-schema-mount]
Bjorklund, M. and L. Lhotka, "YANG Schema Mount", draft- Bjorklund, M. and L. Lhotka, "YANG Schema Mount", draft-
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-05 (work in progress), ietf-netmod-yang-tree-diagrams-06 (work in progress),
January 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, <https://www.rfc-
editor.org/info/rfc2119>. 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, <https://www.rfc-
editor.org/info/rfc3688>. editor.org/info/rfc3688>.
skipping to change at page 23, line 14 skipping to change at page 23, line 14
[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
[I-D.ietf-bess-l2vpn-yang] [I-D.ietf-bess-l2vpn-yang]
Shah, H., Brissette, P., Chen, I., Hussain, I., Wen, B., Shah, H., Brissette, P., Chen, I., Hussain, I., Wen, B.,
and K. Tiruveedhula, "YANG Data Model for MPLS-based and K. Tiruveedhula, "YANG Data Model for MPLS-based
L2VPN", draft-ietf-bess-l2vpn-yang-07 (work in progress), L2VPN", draft-ietf-bess-l2vpn-yang-08 (work in progress),
October 2017. February 2018.
[I-D.ietf-bess-l3vpn-yang] [I-D.ietf-bess-l3vpn-yang]
Jain, D., Patel, K., Brissette, P., Li, Z., Zhuang, S., Jain, D., Patel, K., Brissette, P., Li, Z., Zhuang, S.,
Liu, X., Haas, J., Esale, S., and B. Wen, "Yang Data Model Liu, X., Haas, J., Esale, S., and B. Wen, "Yang Data Model
for BGP/MPLS L3 VPNs", draft-ietf-bess-l3vpn-yang-02 (work for BGP/MPLS L3 VPNs", draft-ietf-bess-l3vpn-yang-02 (work
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-
skipping to change at page 23, line 40 skipping to change at page 23, line 40
"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-09 (work in progress), October 2017.
[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 Logical Network Elements", draft-ietf-rtgwg- Liu, "YANG Model for Logical Network Elements", draft-
lne-model-05 (work in progress), December 2017. ietf-rtgwg-lne-model-07 (work in progress), February 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, <https://www.rfc-
editor.org/info/rfc4026>. 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>.
skipping to change at page 26, line 39 skipping to change at page 26, line 39
"interface": [ "interface": [
{ {
"name": "eth0", "name": "eth0",
"ip:ipv4": { "ip:ipv4": {
"address": [ "address": [
{ {
"ip": "192.0.2.10", "ip": "192.0.2.10",
"prefix-length": 24, "prefix-length": 24,
} }
] ]
} },
"ip:ipv6": { "ip:ipv6": {
"address": [ "address": [
{ {
"ip": "2001:db8:0:2::10", "ip": "2001:db8:0:2::10",
"prefix-length": 64, "prefix-length": 64,
} }
] ]
} }
}, },
{ {
skipping to change at page 35, line 23 skipping to change at page 35, line 23
"name": "vrf-blue", "name": "vrf-blue",
"vrf-root": { "vrf-root": {
"ietf-routing:routing": { "ietf-routing:routing": {
"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",
"areas": { "areas": {
"area": [ "area": [
{ {
"area-id": "203.0.113.1", "area-id": "203.0.113.1",
"interfaces": { "interfaces": {
"interface": [ "interface": [
{ {
"name": "eth2", "name": "eth2",
"cost": 10 "cost": 10
} }
 End of changes. 10 change blocks. 
18 lines changed or deleted 17 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/