< draft-ietf-rtgwg-ni-model-07.txt		draft-ietf-rtgwg-ni-model-08.txt >
	skipping to change at page 1, line 16 ¶		skipping to change at page 1, line 16 ¶
	Expires: August 7, 2018 Deutsche Telekom		Expires: August 7, 2018 Deutsche Telekom
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	D. Bogdanovic		D. Bogdanovic
	X. Liu		X. Liu
	Jabil		Jabil
	February 3, 2018		February 3, 2018
	YANG Network Instances		YANG Network Instances
	draft-ietf-rtgwg-ni-model-07		draft-ietf-rtgwg-ni-model-08
	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).
	Status of This Memo		Status of This Memo
	skipping to change at page 2, line 30 ¶		skipping to change at page 2, line 30 ¶
	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 . . . . . . . . . . . . . 12		3.4. Network Instance Instantiation . . . . . . . . . . . . . 12
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 13		4. Security Considerations . . . . . . . . . . . . . . . . . . . 13
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
	6. Network Instance Model . . . . . . . . . . . . . . . . . . . 14		6. Network Instance Model . . . . . . . . . . . . . . . . . . . 14
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 20		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
	7.1. Normative References . . . . . . . . . . . . . . . . . . 20		7.1. Normative References . . . . . . . . . . . . . . . . . . 20
	7.2. Informative References . . . . . . . . . . . . . . . . . 21		7.2. Informative References . . . . . . . . . . . . . . . . . 22
	Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 23		Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 23
	Appendix B. Example NI usage . . . . . . . . . . . . . . . . . . 23		Appendix B. Example NI usage . . . . . . . . . . . . . . . . . . 23
	B.1. Configuration Data . . . . . . . . . . . . . . . . . . . 23		B.1. Configuration Data . . . . . . . . . . . . . . . . . . . 23
	B.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 26		B.2. State Data . . . . . . . . . . . . . . . . . . . . . . . 26
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
	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
	skipping to change at page 3, line 33 ¶		skipping to change at page 3, line 33 ¶
	One notable difference between the LNE model and the NI model is that		One notable difference between the LNE model and the NI model is that
	the NI model provides a framework for VRF and VSI management. This		the NI model provides a framework for VRF and VSI management. This
	document envisions the separate definition of VRF and VSI, i.e., L3		document envisions the separate definition of VRF and VSI, i.e., L3
	and L2 VPN, technology specific models. An example of such can be		and L2 VPN, technology specific models. An example of such can be
	found in the emerging L3VPN model defined in		found in the emerging L3VPN model defined in
	[I-D.ietf-bess-l3vpn-yang] and the examples discussed below.		[I-D.ietf-bess-l3vpn-yang] and the examples discussed below.
	1.1. Terminology		1.1. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	document are to be interpreted as described in [RFC2119].		"OPTIONAL" in this document are to be interpreted as described in BCP
			14 [RFC2119] [RFC8174] when, and only when, they appear in all
			capitals, as shown here.
	Readers are expected to be familiar with terms and concepts of YANG		Readers are expected to be familiar with terms and concepts of YANG
	[RFC7950] and YANG Schema Mount [I-D.ietf-netmod-schema-mount].		[RFC7950] and YANG Schema Mount [I-D.ietf-netmod-schema-mount].
	This document uses the graphical representation of data models		This document uses the graphical representation of data models
	defined in [I-D.ietf-netmod-yang-tree-diagrams].		defined in [I-D.ietf-netmod-yang-tree-diagrams].
	1.2. Status of Work and Open Issues		1.2. Status of Work and Open Issues
	The top open issues are:		The top open issues are:
	skipping to change at page 21, line 47 ¶		skipping to change at page 21, line 47 ¶
	[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, <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
			2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/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-07 (work in progress),
	October 2017.		October 2017.
	[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.,
End of changes. 4 change blocks.
	4 lines changed or deleted		10 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/