draft-ietf-i2rs-yang-dc-fabric-network-topology-06.txt		draft-ietf-i2rs-yang-dc-fabric-network-topology-07.txt
	I2RS Working Group Y. Zhuang		I2RS Working Group Y. Zhuang
	Internet-Draft D. Shi		Internet-Draft D. Shi
	Intended status: Standards Track Huawei		Intended status: Standards Track Huawei
	Expires: August 15, 2018 R. Gu		Expires: September 19, 2018 R. Gu
	China Mobile		China Mobile
	H. Ananthakrishnan		H. Ananthakrishnan
	Packet Design		Packet Design
	February 11, 2018		March 18, 2018
	A YANG Data Model for Fabric Topology in Data Center Networks		A YANG Data Model for Fabric Topology in Data Center Networks
	draft-ietf-i2rs-yang-dc-fabric-network-topology-06		draft-ietf-i2rs-yang-dc-fabric-network-topology-07
	Abstract		Abstract
	This document defines a YANG data model for fabric topology in Data		This document defines a YANG data model for fabric topology in Data
	Center Network.		Center Network.
	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.
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	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 https://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 15, 2018.		This Internet-Draft will expire on September 19, 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		(https://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 2, line 25 ¶		skipping to change at page 2, line 25 ¶
	3.2.1. Fabric Topology . . . . . . . . . . . . . . . . . . . 5		3.2.1. Fabric Topology . . . . . . . . . . . . . . . . . . . 5
	3.2.2. Fabric node extension . . . . . . . . . . . . . . . . 6		3.2.2. Fabric node extension . . . . . . . . . . . . . . . . 6
	3.2.3. Fabric termination-point extension . . . . . . . . . 7		3.2.3. Fabric termination-point extension . . . . . . . . . 7
	4. Fabric YANG Module . . . . . . . . . . . . . . . . . . . . . 7		4. Fabric YANG Module . . . . . . . . . . . . . . . . . . . . . 7
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 20		6. Security Considerations . . . . . . . . . . . . . . . . . . . 20
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 21		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
	8.1. Normative References . . . . . . . . . . . . . . . . . . 21		8.1. Normative References . . . . . . . . . . . . . . . . . . 21
	8.2. Informative References . . . . . . . . . . . . . . . . . 22		8.2. Informative References . . . . . . . . . . . . . . . . . 22
	Appendix A. Non NMDA -state modules . . . . . . . . . . . . . . 22		Appendix A. Non NMDA -state modules . . . . . . . . . . . . . . 23
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
	1. Introduction		1. Introduction
	Normally, a data center (DC) network is composed of single or		Normally, a data center (DC) network is composed of single or
	multiple fabrics which are also known as PODs (Points Of Delivery).		multiple fabrics which are also known as PODs (Points Of Delivery).
	These fabrics may be heterogeneous due to implementation of different		These fabrics may be heterogeneous due to implementation of different
	technologies when a DC network is upgraded or new techniques and		technologies when a DC network is upgraded or new techniques and
	features are enrolled. For example, Fabric A may use VXLAN while		features are enrolled. For example, Fabric A may use VXLAN while
	Fabric B may use VLAN within a DC network. Likewise, an existing		Fabric B may use VLAN within a DC network. Likewise, an existing
	fabric may use VXLAN while a new fabric, for example a fabric		fabric may use VXLAN while a new fabric, for example a fabric
	skipping to change at page 7, line 45 ¶		skipping to change at page 7, line 45 ¶
	port can be mapped to a device node in the underlay network.		port can be mapped to a device node in the underlay network.
	Also, a new container for tunnel-options is introduced to present the		Also, a new container for tunnel-options is introduced to present the
	tunnel configuration on a port.		tunnel configuration on a port.
	The termination point information is learned from the underlay		The termination point information is learned from the underlay
	networks, not configured by the fabric topology layer.		networks, not configured by the fabric topology layer.
	4. Fabric YANG Module		4. Fabric YANG Module
			This module imports typedefs from [ietf-i2rs-yang-network-topo], and
			it references [RFC7348] and [draft-ietf-netmod-rfc7277bis].
			NOTE TO RFC EDITOR: (1) Please replace above reference to draft-ietf-
			i2rs-yang-network-topo-20 and [draft-ietf-netmod-rfc7277bis] with RFC
			numbers when published (i.e. RFC xxxx). (2) Please replace the date
			in the revision statement with the date of publication when
			published."
	<CODE BEGINS> file "ietf-dc-fabric-types@2017-12-21.yang"		<CODE BEGINS> file "ietf-dc-fabric-types@2017-12-21.yang"
	module ietf-dc-fabric-types {		module ietf-dc-fabric-types {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-dc-fabric-types";		namespace "urn:ietf:params:xml:ns:yang:ietf-dc-fabric-types";
	prefix fabrictypes;		prefix fabrictypes;
	organization		organization
	"IETF I2RS (Interface to the Routing System) Working Group";		"IETF I2RS (Interface to the Routing System) Working Group";
	contact		contact
	"WG Web: <http://tools.ietf.org/wg/i2rs/ >		"WG Web: <http://tools.ietf.org/wg/i2rs/ >
	WG List: <mailto:i2rs@ietf.org>		WG List: <mailto:i2rs@ietf.org>
	Editor: Yan Zhuang		Editor: Yan Zhuang
	<mailto:zhuangyan.zhuang@huawei.com>		<mailto:zhuangyan.zhuang@huawei.com>
	skipping to change at page 17, line 41 ¶		skipping to change at page 18, line 4 ¶
	type string;		type string;
	description		description
	"Name of the fabric";		"Name of the fabric";
	}		}
	leaf type {		leaf type {
	type fabrictypes:underlay-network-type;		type fabrictypes:underlay-network-type;
	description		description
	"The type of physical network that implements this		"The type of physical network that implements this
	fabric.Examples are vlan, and trill.";		fabric.Examples are vlan, and trill.";
	}		}
	container vni-capacity {		container vni-capacity {
	description "Number of vni(VXLAN Network Identifier, see [RFC7348])s that the fabric has";		description "Number of vni(VXLAN Network Identifier defined in RFC 7348)s that the fabric has.";
	leaf min {		leaf min {
	type int32;		type int32;
	description		description
	"Vni min capacity";		"Vni min capacity";
	}		}
	leaf max {		leaf max {
	type int32;		type int32;
	description		description
	"Vni max capacity";		"Vni max capacity";
	skipping to change at page 21, line 37 ¶		skipping to change at page 21, line 48 ¶
	and H. Ananthakrishnan, "A YANG Data Model for Network		and H. Ananthakrishnan, "A YANG Data Model for Network
	Topologies", I-D draft-ietf-i2rs-yang-network-topo-06,		Topologies", I-D draft-ietf-i2rs-yang-network-topo-06,
	September 2016.		September 2016.
	[I-D.draft-ietf-netmod-revised-datastores-06]		[I-D.draft-ietf-netmod-revised-datastores-06]
	Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,		Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
	and R. Wilton, "A Revised Conceptual Model for YANG		and R. Wilton, "A Revised Conceptual Model for YANG
	Datastores", I-D draft-ietf-netmod-revised-datastores-06,		Datastores", I-D draft-ietf-netmod-revised-datastores-06,
	October 2017.		October 2017.
			[I-D.draft-ietf-netmod-rfc7277bis]
			Bjorklund, M., "A YANG Data Model for IP Management", I-D
			draft-ietf-netmod-rfc7277bis-03, January 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,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
	[RFC5246] Dierks, T. and E. Rescorla, "Transport Layer Security		[RFC5246] Dierks, T. and E. Rescorla, "Transport Layer Security
	(TLS) Protocol Version 1.2", August 2008,		(TLS) Protocol Version 1.2", August 2008,
	<http://www.rfc-editor.org/info/rfc5246>.		<http://www.rfc-editor.org/info/rfc5246>.
	[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the		[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
End of changes. 10 change blocks.
	7 lines changed or deleted		22 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/