< draft-ietf-rtgwg-ni-model-05.txt		draft-ietf-rtgwg-ni-model-06.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: June 7, 2018 Deutsche Telekom		Expires: July 20, 2018 Deutsche Telekom
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	D. Bogdanovic		D. Bogdanovic
	X. Liu		X. Liu
	Jabil		Jabil
	December 4, 2017		January 16, 2018
	YANG Network Instances		YANG Network Instances
	draft-ietf-rtgwg-ni-model-05		draft-ietf-rtgwg-ni-model-06
	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
	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 June 7, 2018.		This Internet-Draft will expire on July 20, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 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 10, line 37 ¶		skipping to change at page 10, line 37 ¶
	| | +--rw ip:mtu? uint16		| | +--rw ip:mtu? uint16
	| | +--rw ip:address* [ip]		| | +--rw ip:address* [ip]
	| | | +--rw ip:ip inet:ipv4-address-no-zone		| | | +--rw ip:ip inet:ipv4-address-no-zone
	| | | +--rw (ip:subnet)		| | | +--rw (ip:subnet)
	| | | +--:(ip:prefix-length)		| | | +--:(ip:prefix-length)
	| | | | +--rw ip:prefix-length? uint8		| | | | +--rw ip:prefix-length? uint8
	| | | +--:(ip:netmask)		| | | +--:(ip:netmask)
	| | | +--rw ip:netmask? yang:dotted-quad		| | | +--rw ip:netmask? yang:dotted-quad
	| | +--rw ip:neighbor* [ip]		| | +--rw ip:neighbor* [ip]
	| | | +--rw ip:ip inet:ipv4-address-no-zone		| | | +--rw ip:ip inet:ipv4-address-no-zone
	| | | +--rw ip:link-layer-address yang:phys-address		| | | +--rw ip:link-layer-address yang:phys-address
	| | +--rw ni:bind-network-instance-name? string		| | +--rw ni:bind-network-instance-name? string
	| +--rw ni:bind-network-instance-name? string		| +--rw ni:bind-network-instance-name? string
	The [RFC7223] defined interface model is structured to include all		The [RFC7223] defined interface model is structured to include all
	interfaces in a flat list, without regard to virtual instances (e.g.,		interfaces in a flat list, without regard to virtual instances (e.g.,
	VRFs) supported on the device. The bind-network-instance-name leaf		VRFs) supported on the device. The bind-network-instance-name leaf
	provides the association between an interface and its associated NI		provides the association between an interface and its associated NI
	(e.g., VRF or VSI). Note that as currently defined, to assign an		(e.g., VRF or VSI). Note that as currently defined, to assign an
	interface to both an LNE and NI, the interface would first be		interface to both an LNE and NI, the interface would first be
	assigned to the LNE using the mechanisms defined in		assigned to the LNE using the mechanisms defined in
	skipping to change at page 21, line 27 ¶		skipping to change at page 21, line 27 ¶
	7.1. Normative References		7.1. Normative References
	[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-02 (work in progress),		ietf-netmod-yang-tree-diagrams-04 (work in progress),
	October 2017.		December 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>.
	[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>.
	[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>.
	7.2. Informative References		7.2. Informative References
	skipping to change at page 22, line 32 ¶		skipping to change at page 22, line 32 ¶
	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 Logical Network Elements", draft-ietf-rtgwg-
	lne-model-04 (work in progress), September 2017.		lne-model-05 (work in progress), December 2017.
	[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,		DOI 10.17487/RFC4026, March 2005, <https://www.rfc-
	<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>.
	[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,		DOI 10.17487/RFC4664, September 2006, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc4664>.		editor.org/info/rfc4664>.
	[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",		[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
	RFC 7950, DOI 10.17487/RFC7950, August 2016,		RFC 7950, DOI 10.17487/RFC7950, August 2016,
	<https://www.rfc-editor.org/info/rfc7950>.		<https://www.rfc-editor.org/info/rfc7950>.
	[RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing		[RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
	Management", RFC 8022, DOI 10.17487/RFC8022, November		Management", RFC 8022, DOI 10.17487/RFC8022, November
	2016, <https://www.rfc-editor.org/info/rfc8022>.		2016, <https://www.rfc-editor.org/info/rfc8022>.
	Appendix A. Acknowledgments		Appendix A. Acknowledgments
End of changes. 15 change blocks.
	21 lines changed or deleted		21 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/