< draft-ietf-rtgwg-lne-model-07.txt   draft-ietf-rtgwg-lne-model-08.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 18, 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 14, 2018 March 1, 2018
YANG Model for Logical Network Elements YANG Model for Logical Network Elements
draft-ietf-rtgwg-lne-model-07 draft-ietf-rtgwg-lne-model-08
Abstract Abstract
This document defines a logical network element YANG module. This This document defines a logical network element YANG module. This
module can be used to manage the logical resource partitioning that module can be used to manage the logical resource partitioning that
may be present on a network device. Examples of common industry may be present on a network device. Examples of common industry
terms for logical resource partitioning are Logical Systems or terms for logical resource partitioning are Logical Systems or
Logical Routers. Logical Routers.
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 https://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 18, 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
(https://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
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
skipping to change at page 2, line 30 skipping to change at page 2, line 30
3.3. LNE Management - Host Network Device View . . . . . . . . 7 3.3. LNE Management - Host Network Device View . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Logical Network Element Model . . . . . . . . . . . . . . . . 10 6. Logical Network Element Model . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.1. Normative References . . . . . . . . . . . . . . . . . . 14 7.1. Normative References . . . . . . . . . . . . . . . . . . 14
7.2. Informative References . . . . . . . . . . . . . . . . . 15 7.2. Informative References . . . . . . . . . . . . . . . . . 15
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 15 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 15
Appendix B. Examples . . . . . . . . . . . . . . . . . . . . . . 17 Appendix B. Examples . . . . . . . . . . . . . . . . . . . . . . 17
B.1. Example: Host Device Managed LNE . . . . . . . . . . . . 17 B.1. Example: Host Device Managed LNE . . . . . . . . . . . . 17
B.1.1. Configuration Data . . . . . . . . . . . . . . . . . 22 B.1.1. Configuration Data . . . . . . . . . . . . . . . . . 21
B.1.2. State Data . . . . . . . . . . . . . . . . . . . . . 26 B.1.2. State Data . . . . . . . . . . . . . . . . . . . . . 25
B.2. Example: Self Managed LNE . . . . . . . . . . . . . . . . 36 B.2. Example: Self Managed LNE . . . . . . . . . . . . . . . . 35
B.2.1. Configuration Data . . . . . . . . . . . . . . . . . 40 B.2.1. Configuration Data . . . . . . . . . . . . . . . . . 39
B.2.2. State Data . . . . . . . . . . . . . . . . . . . . . 43 B.2.2. State Data . . . . . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 51
1. Introduction 1. Introduction
This document defines a YANG [RFC6020] module to support the creation This document defines a YANG [RFC6020] module to support the creation
of logical network elements on a network device. A logical network of logical network elements on a network device. A logical network
element (LNE) is an independently managed virtual device made up of element (LNE) is an independently managed virtual device made up of
resources allocated to it from the host or parent network device. An resources allocated to it from the host or parent network device. An
LNE running on a host network device conceptually parallels a virtual LNE running on a host network device conceptually parallels a virtual
machine running on a host system. Using host-virtualization machine running on a host system. Using host-virtualization
terminology one could refer to an LNE as a "Guest", and the terminology one could refer to an LNE as a "Guest", and the
skipping to change at page 14, line 21 skipping to change at page 14, line 21
Management", draft-ietf-netmod-rfc7223bis-03 (work in Management", draft-ietf-netmod-rfc7223bis-03 (work in
progress), January 2018. progress), 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.
[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, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
<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, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc3688>. 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, DOI 10.17487/RFC5246, August 2008, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc5246>. 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, DOI 10.17487/RFC6020, October 2010, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc6020>. 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, DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc6536>. 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 15, line 27 skipping to change at page 15, line 27
YANG Data Model for Hardware Management", draft-ietf- YANG Data Model for Hardware Management", draft-ietf-
netmod-entity-08 (work in progress), January 2018. netmod-entity-08 (work in progress), January 2018.
[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-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.
[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-ni-model] [I-D.ietf-rtgwg-ni-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 Network Instances", draft-ietf-rtgwg- Liu, "YANG Model for Network Instances", draft-ietf-rtgwg-
ni-model-10 (work in progress), February 2018. ni-model-10 (work in progress), February 2018.
skipping to change at page 17, line 52 skipping to change at page 17, line 52
| +--rw name string | +--rw name string
| +--rw algorithm string | +--rw algorithm string
| +--rw key-data binary | +--rw key-data binary
+--ro sys:system-state/ +--ro sys:system-state/
| ... | ...
+--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 areas
| +--rw areas | +--rw area* [area-id]
| +--rw area* [area-id] | +--rw interfaces
| +--rw interfaces | +--rw interface* [name]
| +--rw interface* [name] | +--rw name if:interface-ref
| +--rw name if:interface-ref | +--rw cost? uint16
| +--rw cost? uint16
+--rw if:interfaces/ +--rw if:interfaces/
+--rw interface* [name] +--rw interface* [name]
+--rw name string +--rw name string
+--rw ip:ipv4!/ +--rw ip:ipv4!/
| +--rw address* [ip] | +--rw address* [ip]
| ... | ...
module: ietf-interfaces module: ietf-interfaces
+--rw interfaces +--rw interfaces
+--rw interface* [name] +--rw interface* [name]
skipping to change at page 21, line 35 skipping to change at page 21, line 35
+--ro platform +--ro platform
+--ro os-name? string +--ro os-name? string
+--ro os-release? string +--ro os-release? string
module: ietf-routing module: ietf-routing
rw-- routing rw-- 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 areas
+--rw areas +--rw area* [area-id]
+--rw area* [area-id] +--rw interfaces
+--rw interfaces +--rw interface* [name]
+--rw interface* [name] +--rw name if:interface-ref
+--rw name if:interface-ref +--rw cost? uint16
+--rw cost? uint16
module: ietf-interfaces module: ietf-interfaces
+--rw interfaces +--rw interfaces
+--rw interface* [name] +--rw interface* [name]
+--rw name string +--rw name string
+--ro oper-status enumeration +--ro oper-status enumeration
B.1.1. Configuration Data B.1.1. Configuration Data
The following shows an example where two customer specific LNEs are The following shows an example where two customer specific LNEs are
skipping to change at page 22, line 34 skipping to change at page 22, line 29
} }
}, },
"ietf-routing:routing": { "ietf-routing:routing": {
"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": {
"instance": [ "af": "ipv4",
{ "areas": {
"af": "ipv4", "area": [
"areas": { {
"area": [ "area-id": "203.0.113.1",
{ "interfaces": {
"area-id": "203.0.113.1", "interface": [
"interfaces": { {
"interface": [ "name": "eth1",
{ "cost": 10
"name": "eth1",
"cost": 10
}
]
} }
} ]
] }
} }
} ]
}
]
} }
} }
] ]
} }
}, },
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interfaces": { "interfaces": {
"interface": [ "interface": [
{ {
"name": "eth1", "name": "eth1",
skipping to change at page 24, line 10 skipping to change at page 23, line 49
} }
} }
"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": {
"instance": [ "af": "ipv4",
{ "areas": {
"af": "ipv4", "area": [
"areas": { {
"area": [ "area-id": "203.0.113.1",
{ "interfaces": {
"area-id": "203.0.113.1", "interface": [
"interfaces": { {
"interface": [ "name": "eth1",
{ "cost": 10
"name": "eth1",
"cost": 10
}
]
} }
} ]
] }
} }
} ]
] }
} }
} }
] ]
} }
} },
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interfaces": { "interfaces": {
{ {
"name": "eth1", "name": "eth1",
"ip:ipv4": { "ip:ipv4": {
"address": [ "address": [
{ {
"ip": "192.0.2.11", "ip": "192.0.2.11",
"prefix-length": 24, "prefix-length": 24,
} }
skipping to change at page 28, line 6 skipping to change at page 27, line 42
} }
}, },
"ietf-routing:routing": { "ietf-routing:routing": {
"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": {
"instance": [ "af": "ipv4",
{ "areas": {
"af": "ipv4", "area": [
"areas": { {
"area": [ "area-id": "203.0.113.1",
{ "interfaces": {
"area-id": "203.0.113.1", "interface": [
"interfaces": { {
"interface": [ "name": "eth1",
{ "cost": 10
"name": "eth1",
"cost": 10
}
]
} }
} ]
] }
} }
} ]
] }
} }
} }
] ]
} }
}, },
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interfaces": { "interfaces": {
"interface": [ "interface": [
{ {
"name": "eth1", "name": "eth1",
skipping to change at page 30, line 51 skipping to change at page 30, line 34
} }
}, },
"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": {
"instance": [ "af": "ipv4",
{ "areas": {
"af": "ipv4", "area": [
"areas": { {
"area": [ "area-id": "203.0.113.1",
{ "interfaces": {
"area-id": "203.0.113.1", "interface": [
"interfaces": { {
"interface": [ "name": "eth1",
{ "cost": 10
"name": "eth1",
"cost": 10
}
]
} }
} ]
] }
} }
} ]
] }
} }
} }
] ]
} }
} }
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interfaces": { "interfaces": {
{ {
"name": "eth1", "name": "eth1",
"type": "iana-if-type:ethernetCsmacd", "type": "iana-if-type:ethernetCsmacd",
"oper-status": "up", "oper-status": "up",
"phys-address": "00:01:02:A1:B1:C2", "phys-address": "00:01:02:A1:B1:C2",
skipping to change at page 40, line 34 skipping to change at page 39, line 34
} }
}, },
"ietf-routing:routing": { "ietf-routing:routing": {
"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": {
"instance": [ "af": "ipv4",
{ "areas": {
"af": "ipv4", "area": [
"areas": { {
"area": [ "area-id": "203.0.113.1",
{ "interfaces": {
"area-id": "203.0.113.1", "interface": [
"interfaces": { {
"interface": [ "name": "eth1",
{ "cost": 10
"name": "eth1",
"cost": 10
}
]
} }
} ]
] }
} }
} ]
}
]
} }
} }
] ]
} }
}, },
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interfaces": { "interfaces": {
"interface": [ "interface": [
{ {
"name": "eth1", "name": "eth1",
"ip:ipv4": { "ip:ipv4": {
"address": [ "address": [
{ {
skipping to change at page 42, line 5 skipping to change at page 40, line 50
} }
}, },
"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": {
"instance": [ "af": "ipv4",
{ "areas": {
"af": "ipv4", "area": [
"areas": { {
"area": [ "area-id": "203.0.113.1",
{ "interfaces": {
"area-id": "203.0.113.1", "interface": [
"interfaces": { {
"interface": [ "name": "eth1",
{ "cost": 10
"name": "eth1",
"cost": 10
}
]
} }
} ]
] }
} }
} ]
] }
} }
} }
] ]
} }
}, },
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interfaces": { "interfaces": {
"interface": [ "interface": [
{ {
"name": "eth1", "name": "eth1",
skipping to change at page 48, line 4 skipping to change at page 46, line 40
}, },
{ {
"name": "ietf-yang-types", "name": "ietf-yang-types",
"revision": "2013-07-15", "revision": "2013-07-15",
"namespace": "namespace":
"urn:ietf:params:xml:ns:yang:ietf-yang-types", "urn:ietf:params:xml:ns:yang:ietf-yang-types",
"conformance-type": "import" "conformance-type": "import"
} }
] ]
}, },
"ietf-system:system-state": { "ietf-system:system-state": {
"platform": { "platform": {
"os-name": "NetworkOS" "os-name": "NetworkOS"
} }
}, },
"ietf-routing:routing": { "ietf-routing:routing": {
"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": {
"instance": [ "af": "ipv4",
{ "areas": {
"af": "ipv4", "area": [
"areas": { {
"area": [ "area-id": "203.0.113.1",
{ "interfaces": {
"area-id": "203.0.113.1", "interface": [
"interfaces": { {
"interface": [ "name": "eth1",
{ "cost": 10
"name": "eth1",
"cost": 10
}
]
} }
} ]
] }
} }
} ]
] }
} }
} }
] ]
} }
}, },
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interfaces": { "interfaces": {
"interface": [ "interface": [
{ {
skipping to change at page 51, line 17 skipping to change at page 49, line 51
}, },
"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": {
"instance": [ "af": "ipv4",
{ "areas": {
"af": "ipv4", "area": [
"areas": { {
"area": [ "area-id": "203.0.113.1",
{ "interfaces": {
"area-id": "203.0.113.1", "interface": [
"interfaces": { {
"interface": [ "name": "eth1",
{ "cost": 10
"name": "eth1",
"cost": 10
}
]
} }
} ]
] }
} }
} ]
] }
} }
} }
] ]
} }
}, },
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interfaces": { "interfaces": {
"interface": [ "interface": [
{ {
 End of changes. 43 change blocks. 
185 lines changed or deleted 153 lines changed or added

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