< draft-ietf-spring-sr-yang-07.txt		draft-ietf-spring-sr-yang-08.txt >
	SPRING Working Group S. Litkowski		SPRING Working Group S. Litkowski
	Internet-Draft Orange Business Service		Internet-Draft Orange Business Service
	Intended status: Standards Track Y. Qu		Intended status: Standards Track Y. Qu
	Expires: January 2, 2018 Huawei		Expires: July 1, 2018 Huawei
	P. Sarkar		P. Sarkar
	J. Tantsura		J. Tantsura
	Individual		Individual
	July 01, 2017		December 28, 2017
	YANG Data Model for Segment Routing		YANG Data Model for Segment Routing
	draft-ietf-spring-sr-yang-07		draft-ietf-spring-sr-yang-08
	Abstract		Abstract
	This document defines a YANG data model ([RFC6020], [RFC7950]) for		This document defines a YANG data model ([RFC6020], [RFC7950]) for
	segment routing ([I-D.ietf-spring-segment-routing]) configuration and		segment routing ([I-D.ietf-spring-segment-routing]) configuration and
	operation. This YANG model is intended to be used on network		operation. This YANG model is intended to be used on network
	elements to configure or operate segment routing. This document		elements to configure or operate segment routing. This document
	defines also generic containers that SHOULD be reused by IGP protocol		defines also generic containers that SHOULD be reused by IGP protocol
	modules to support segment routing.		modules to support segment routing.
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	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 http://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 January 2, 2018.		This Internet-Draft will expire on July 1, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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
	(http://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
	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
	1.1. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 3		1.1. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 3
	2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3		2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3
	3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . 6		3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . 5
	4. IGP Control plane configuration . . . . . . . . . . . . . . . 7		4. IGP Control plane configuration . . . . . . . . . . . . . . . 6
	4.1. IGP interface configuration . . . . . . . . . . . . . . . 7		4.1. IGP interface configuration . . . . . . . . . . . . . . . 6
	4.1.1. Adjacency SID properties . . . . . . . . . . . . . . 7		4.1.1. Adjacency SID properties . . . . . . . . . . . . . . 7
	4.1.1.1. Bundling . . . . . . . . . . . . . . . . . . . . 7		4.1.1.1. Bundling . . . . . . . . . . . . . . . . . . . . 7
	4.1.1.2. Protection . . . . . . . . . . . . . . . . . . . 8		4.1.1.2. Protection . . . . . . . . . . . . . . . . . . . 7
	5. States . . . . . . . . . . . . . . . . . . . . . . . . . . . 8		5. States . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	6. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 8		6. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 8
	7. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 9		7. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 8
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 28		8. Security Considerations . . . . . . . . . . . . . . . . . . . 28
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28		9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
	11. Normative References . . . . . . . . . . . . . . . . . . . . 29		11. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
			11.1. Normative References . . . . . . . . . . . . . . . . . . 28
			11.2. Informative References . . . . . . . . . . . . . . . . . 29
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
	1. Introduction		1. Introduction
	This document defines a YANG data model for segment routing		This document defines a YANG data model for segment routing
	configuration and operation. This document does not define the IGP		configuration and operation. This document does not define the IGP
	extensions to support segment routing but defines generic groupings		extensions to support segment routing but defines generic groupings
	that SHOULD be reused by IGP extension modules. The reason of this		that SHOULD be reused by IGP extension modules. The reason of this
	design choice is to not require implementations to support all IGP		design choice is to not require implementations to support all IGP
	extensions. For example, an implementation may support IS-IS		extensions. For example, an implementation may support IS-IS
	extension but not OSPF.		extension but not OSPF.
	1.1. Tree diagram		1.1. Tree diagram
	A simplified graphical representation of the data model is presented		Tree diagrams used in this document follow the notation defined in
	in Section 2.		[I-D.ietf-netmod-yang-tree-diagrams].
	The meaning of the symbols in these diagrams is as follows:
	o Brackets "[" and "]" enclose list keys.
	o Curly braces "{" and "}" contain names of optional features that
	make the corresponding node conditional.
	o Abbreviations before data node names: "rw" means configuration
	(read-write), and "ro" state data (read-only).
	o Symbols after data node names: "?" means an optional node and "*"
	denotes a "list" or "leaf-list".
	o Parentheses enclose choice and case nodes, and case nodes are also
	marked with a colon (":").
	o Ellipsis ("...") stands for contents of subtrees that are not
	shown.
	2. Design of the Data Model		2. Design of the Data Model
	As the module definition is just starting, it is expected that there		As the module definition is just starting, it is expected that there
	will be changes as the module matures.		will be changes as the module matures.
	module: ietf-segment-routing		module: ietf-segment-routing
	augment /rt:routing:		augment /rt:routing:
	+--rw segment-routing		+--rw segment-routing
	+--rw transport-type? identityref		+--rw transport-type? identityref
	skipping to change at page 9, line 19 ¶		skipping to change at page 8, line 35 ¶
	advertised index is already associated with another target (in		advertised index is already associated with another target (in
	this version, the only defined targets are IPv4 and IPv6		this version, the only defined targets are IPv4 and IPv6
	prefixes).		prefixes).
	o segment-routing-index-out-of-range: Raised when a control plane		o segment-routing-index-out-of-range: Raised when a control plane
	advertised index fall outside the range of SRGBs configured for		advertised index fall outside the range of SRGBs configured for
	the network device.		the network device.
	7. YANG Module		7. YANG Module
	<CODE BEGINS> file "ietf-segment-routing-common@2017-07-01.yang"		<CODE BEGINS> file "ietf-segment-routing-common@2017-12-28.yang"
	module ietf-segment-routing-common {		module ietf-segment-routing-common {
	namespace "urn:ietf:params:xml:ns:yang:ietf-segment-routing-common";		namespace "urn:ietf:params:xml:ns:yang:ietf-segment-routing-common";
	prefix sr-cmn;		prefix sr-cmn;
	import ietf-inet-types {		import ietf-inet-types {
	prefix inet;		prefix inet;
	}		}
	organization		organization
	"IETF SPRING - SPRING Working Group";		"IETF SPRING - SPRING Working Group";
	skipping to change at page 10, line 18 ¶		skipping to change at page 9, line 35 ¶
	to the license terms contained in, the Simplified BSD License		to the license terms contained in, the Simplified BSD License
	set forth in Section 4.c of the IETF Trust's Legal Provisions		set forth in Section 4.c of the IETF Trust's Legal Provisions
	Relating to IETF Documents		Relating to IETF Documents
	(http://trustee.ietf.org/license-info).		(http://trustee.ietf.org/license-info).
	This version of this YANG module is part of RFC XXXX;		This version of this YANG module is part of RFC XXXX;
	see the RFC itself for full legal notices.";		see the RFC itself for full legal notices.";
	reference "RFC XXXX";		reference "RFC XXXX";
			revision 2017-12-28 {
			description
			"
			";
			reference "RFC XXXX: YANG Data Model for Segment Routing.";
			}
	revision 2017-07-01 {		revision 2017-07-01 {
	description		description
	"		"
	*Conform to RFC6087BIS Appendix C		*Conform to RFC6087BIS Appendix C
	";		";
	reference "RFC XXXX: YANG Data Model for Segment Routing.";		reference "RFC XXXX: YANG Data Model for Segment Routing.";
	}		}
	revision 2017-03-10 {		revision 2017-03-10 {
	description		description
	"		"
	skipping to change at page 15, line 13 ¶		skipping to change at page 14, line 38 ¶
	leaf algorithm {		leaf algorithm {
	type identityref {		type identityref {
	base prefix-sid-algorithm;		base prefix-sid-algorithm;
	}		}
	description		description
	"Prefix-sid algorithm.";		"Prefix-sid algorithm.";
	}		}
	}		}
	}		}
	<CODE ENDS>		<CODE ENDS>
	<CODE BEGINS> file "ietf-segment-routing@2017-07-01.yang"		<CODE BEGINS> file "ietf-segment-routing@2017-12-28.yang"
	module ietf-segment-routing {		module ietf-segment-routing {
	namespace "urn:ietf:params:xml:ns:yang:ietf-segment-routing";		namespace "urn:ietf:params:xml:ns:yang:ietf-segment-routing";
	prefix sr;		prefix sr;
	import ietf-inet-types {		import ietf-inet-types {
	prefix inet;		prefix inet;
	}		}
	import ietf-yang-types {		import ietf-yang-types {
	prefix yang;		prefix yang;
	}		}
	skipping to change at page 16, line 26 ¶		skipping to change at page 15, line 49 ¶
	to the license terms contained in, the Simplified BSD License		to the license terms contained in, the Simplified BSD License
	set forth in Section 4.c of the IETF Trust's Legal Provisions		set forth in Section 4.c of the IETF Trust's Legal Provisions
	Relating to IETF Documents		Relating to IETF Documents
	(http://trustee.ietf.org/license-info).		(http://trustee.ietf.org/license-info).
	This version of this YANG module is part of RFC XXXX;		This version of this YANG module is part of RFC XXXX;
	see the RFC itself for full legal notices.";		see the RFC itself for full legal notices.";
	reference "RFC XXXX";		reference "RFC XXXX";
			revision 2017-12-28 {
			description
			"";
			reference "RFC XXXX: YANG Data Model for Segment Routing.";
			}
	revision 2017-07-01 {		revision 2017-07-01 {
	description		description
	"		"
	* Implement NMDA model		* Implement NMDA model
	*Conform to RFC6087BIS Appendix C		*Conform to RFC6087BIS Appendix C
	";		";
	reference "RFC XXXX: YANG Data Model for Segment Routing.";		reference "RFC XXXX: YANG Data Model for Segment Routing.";
	}		}
	revision 2017-03-10 {		revision 2017-03-10 {
	skipping to change at page 29, line 9 ¶		skipping to change at page 28, line 37 ¶
	9. Acknowledgements		9. Acknowledgements
	Authors would like to thank Derek Yeung, Acee Lindem, Greg Hankins,		Authors would like to thank Derek Yeung, Acee Lindem, Greg Hankins,
	Hannes Gredler, Uma Chunduri, Jeffrey Zhang, Shradda Hedge, Les		Hannes Gredler, Uma Chunduri, Jeffrey Zhang, Shradda Hedge, Les
	Ginsberg for their contributions.		Ginsberg for their contributions.
	10. IANA Considerations		10. IANA Considerations
	TBD.		TBD.
	11. Normative References		11. References
			11.1. Normative References
	[I-D.ietf-isis-segment-routing-msd]		[I-D.ietf-isis-segment-routing-msd]
	Tantsura, J., Chunduri, U., Aldrin, S., and L. Ginsberg,		Tantsura, J., Chunduri, U., Aldrin, S., and L. Ginsberg,
	"Signaling MSD (Maximum SID Depth) using IS-IS", draft-		"Signaling MSD (Maximum SID Depth) using IS-IS", draft-
	ietf-isis-segment-routing-msd-04 (work in progress), June		ietf-isis-segment-routing-msd-04 (work in progress), June
	2017.		2017.
	[I-D.ietf-ospf-segment-routing-msd]		[I-D.ietf-ospf-segment-routing-msd]
	Tantsura, J., Chunduri, U., Aldrin, S., and P. Psenak,		Tantsura, J., Chunduri, U., Aldrin, S., and P. Psenak,
	"Signaling MSD (Maximum SID Depth) using OSPF", draft-		"Signaling MSD (Maximum SID Depth) using OSPF", draft-
	skipping to change at page 29, line 38 ¶		skipping to change at page 29, line 20 ¶
	[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, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the		[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
	Network Configuration Protocol (NETCONF)", RFC 6020,		Network Configuration Protocol (NETCONF)", RFC 6020,
	October 2010.		October 2010.
	[RFC7950] Bjorklund, M., "The YANG 1.1 Data Modeling Language",		[RFC7950] Bjorklund, M., "The YANG 1.1 Data Modeling Language",
	RFC 7950, August 2016.		RFC 7950, August 2016.
			11.2. Informative References
			[I-D.ietf-netmod-yang-tree-diagrams]
			Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
			ietf-netmod-yang-tree-diagrams-04 (work in progress),
			December 2017.
	Authors' Addresses		Authors' Addresses
	Stephane Litkowski		Stephane Litkowski
	Orange Business Service		Orange Business Service
	Email: stephane.litkowski@orange.com		Email: stephane.litkowski@orange.com
	Yingzhen Qu		Yingzhen Qu
	Huawei		Huawei
End of changes. 17 change blocks.
	37 lines changed or deleted		41 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/