< draft-ietf-rtgwg-lne-model-08.txt		draft-ietf-rtgwg-lne-model-09.txt >
	skipping to change at page 1, line 16 ¶		skipping to change at page 1, line 16 ¶
	Expires: September 2, 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
	March 1, 2018		March 1, 2018
	YANG Model for Logical Network Elements		YANG Model for Logical Network Elements
	draft-ietf-rtgwg-lne-model-08		draft-ietf-rtgwg-lne-model-09
	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
	skipping to change at page 2, line 33 ¶		skipping to change at page 2, line 33 ¶
	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 . . . . . . . . . . . . . . . . . 21		B.1.1. Configuration Data . . . . . . . . . . . . . . . . . 21
	B.1.2. State Data . . . . . . . . . . . . . . . . . . . . . 25		B.1.2. State Data . . . . . . . . . . . . . . . . . . . . . 25
	B.2. Example: Self Managed LNE . . . . . . . . . . . . . . . . 35		B.2. Example: Self Managed LNE . . . . . . . . . . . . . . . . 35
	B.2.1. Configuration Data . . . . . . . . . . . . . . . . . 39		B.2.1. Configuration Data . . . . . . . . . . . . . . . . . 38
	B.2.2. State Data . . . . . . . . . . . . . . . . . . . . . 41		B.2.2. State Data . . . . . . . . . . . . . . . . . . . . . 41
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 51		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50
	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 38, line 35 ¶		skipping to change at page 38, 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.2.1. Configuration Data		B.2.1. Configuration Data
	Each of the child virtual routers is managed through its own sessions		Each of the child virtual routers is managed through its own sessions
End of changes. 4 change blocks.
	10 lines changed or deleted		9 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/