< draft-ietf-ospf-sr-yang-04.txt		draft-ietf-ospf-sr-yang-05.txt >
	Internet D. Yeung		Internet D. Yeung
	Internet-Draft Arrcus		Internet-Draft Arrcus
	Intended status: Informational Y. Qu		Intended status: Informational Y. Qu
	Expires: September 4, 2018 Huawei		Expires: January 2, 2019 Huawei
	J. Zhang		J. Zhang
	Juniper Networks		Juniper Networks
	I. Chen		I. Chen
	Jabil Circuit		Jabil Circuit
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	March 3, 2018		July 1, 2018
	Yang Data Model for OSPF SR (Segment Routing) Protocol		Yang Data Model for OSPF SR (Segment Routing) Protocol
	draft-ietf-ospf-sr-yang-04		draft-ietf-ospf-sr-yang-05
	Abstract		Abstract
	This document defines a YANG data model that can be used to configure		This document defines a YANG data model that can be used to configure
	and manage OSPF Segment Routing.		and manage OSPF Segment Routing.
	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 38 ¶		skipping to change at page 1, line 38 ¶
	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 September 4, 2018.		This Internet-Draft will expire on January 2, 2019.
	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 46 ¶		skipping to change at page 2, line 46 ¶
	YANG data model.		YANG data model.
	1.1. Requirements Language		1.1. Requirements Language
	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", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	2. OSPF Segment Routing		2. OSPF Segment Routing
	This document defines a model for OSPF Segment Routing feature. It		This document defines a model for OSPF Segment Routing feature [I-D.i
	is an augmentation of the OSPF base model.		etf-ospf-segment-routing-extensions][I-D.ietf-ospf-ospfv3-segment-rou
			ting-extensions]. It is an augmentation of the OSPF base model.
	The OSPF SR YANG module requires support for the base segment routing		The OSPF SR YANG module requires support for the base segment routing
	module [I-D.ietf-spring-sr-yang], which defines the global segment		module [I-D.ietf-spring-sr-yang], which defines the global segment
	routing configuration independent of any specific routing protocol		routing configuration independent of any specific routing protocol
	configuration, and support of OSPF base model[I-D.ietf-ospf-yang]		configuration, and support of OSPF base model[I-D.ietf-ospf-yang]
	which defines basic OSPF configuration and state.		which defines basic OSPF configuration and state.
	module: ietf-ospf-sr		module: ietf-ospf-sr
	augment /rt:routing/rt:control-plane-protocols		augment /rt:routing/rt:control-plane-protocols
	/rt:control-plane-protocol/ospf:ospf:		/rt:control-plane-protocol/ospf:ospf:
	skipping to change at page 7, line 7 ¶		skipping to change at page 7, line 8 ¶
	+--ro local-block-tlvs		+--ro local-block-tlvs
	| +--ro local-block-tlv*		| +--ro local-block-tlv*
	| +--ro range-size? ospf:uint24		| +--ro range-size? ospf:uint24
	| +--ro sid-sub-tlv		| +--ro sid-sub-tlv
	| +--ro sid? uint32		| +--ro sid? uint32
	+--ro srms-preference-tlv		+--ro srms-preference-tlv
	+--ro preference? uint8		+--ro preference? uint8
	3. OSPF Segment Routing Yang Module		3. OSPF Segment Routing Yang Module
	<CODE BEGINS> file "ietf-ospf-sr@2018-03-03.yang"		<CODE BEGINS> file "ietf-ospf-sr@2018-06-25.yang"
	module ietf-ospf-sr {		module ietf-ospf-sr {
	namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-sr";		namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-sr";
	prefix ospf-sr;		prefix ospf-sr;
	import ietf-inet-types {		import ietf-inet-types {
	prefix "inet";		prefix "inet";
	}		}
	import ietf-yang-types {		import ietf-yang-types {
	skipping to change at page 8, line 31 ¶		skipping to change at page 8, line 33 ¶
	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 2018-06-25 {
			description
			"";
			reference
			"RFC XXXX: A YANG Data Model for OSPF Segment Routing.";
			}
	revision 2018-03-03 {		revision 2018-03-03 {
	description		description
	"* Remove OSPF instance.";		"* Remove OSPF instance.";
	reference		reference
	"RFC XXXX: A YANG Data Model for OSPF Segment Routing.";		"RFC XXXX: A YANG Data Model for OSPF Segment Routing.";
	}		}
	revision 2017-12-28 {		revision 2017-12-28 {
	description		description
	"";		"";
	skipping to change at page 20, line 24 ¶		skipping to change at page 20, line 28 ¶
	The authors wish to thank Yi Yang, Alexander Clemm, Gaurav Gupta,		The authors wish to thank Yi Yang, Alexander Clemm, Gaurav Gupta,
	Ladislav Lhotka, Stephane Litkowski, Greg Hankins, Manish Gupta and		Ladislav Lhotka, Stephane Litkowski, Greg Hankins, Manish Gupta and
	Alan Davey for their thorough reviews and helpful comments.		Alan Davey for their thorough reviews and helpful comments.
	This document was produced using Marshall Rose's xml2rfc tool.		This document was produced using Marshall Rose's xml2rfc tool.
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	[RFC1793] Moy, J., "Extending OSPF to Support Demand Circuits",		[I-D.ietf-ospf-ospfv3-segment-routing-extensions]
	RFC 1793, DOI 10.17487/RFC1793, April 1995,		Psenak, P., Filsfils, C., Previdi, S., Gredler, H.,
	<https://www.rfc-editor.org/info/rfc1793>.		Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3
			Extensions for Segment Routing", draft-ietf-ospf-ospfv3-
			segment-routing-extensions-13 (work in progress), May
			2018.
			[I-D.ietf-ospf-segment-routing-extensions]
			Psenak, P., Previdi, S., Filsfils, C., Gredler, H.,
			Shakir, R., Henderickx, W., and J. Tantsura, "OSPF
			Extensions for Segment Routing", draft-ietf-ospf-segment-
			routing-extensions-25 (work in progress), April 2018.
			[I-D.ietf-ospf-yang]
			Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,
			"Yang Data Model for OSPF Protocol", draft-ietf-ospf-
			yang-11 (work in progress), April 2018.
			[I-D.ietf-spring-sr-yang]
			Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG
			Data Model for Segment Routing", draft-ietf-spring-sr-
			yang-09 (work in progress), June 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,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,		[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
	DOI 10.17487/RFC2328, April 1998,		DOI 10.17487/RFC2328, April 1998,
	<https://www.rfc-editor.org/info/rfc2328>.		<https://www.rfc-editor.org/info/rfc2328>.
	[RFC3101] Murphy, P., "The OSPF Not-So-Stubby Area (NSSA) Option",
	RFC 3101, DOI 10.17487/RFC3101, January 2003,
	<https://www.rfc-editor.org/info/rfc3101>.
	[RFC3623] Moy, J., Pillay-Esnault, P., and A. Lindem, "Graceful OSPF
	Restart", RFC 3623, DOI 10.17487/RFC3623, November 2003,
	<https://www.rfc-editor.org/info/rfc3623>.
	[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
	(TE) Extensions to OSPF Version 2", RFC 3630,
	DOI 10.17487/RFC3630, September 2003,
	<https://www.rfc-editor.org/info/rfc3630>.
	[RFC4577] Rosen, E., Psenak, P., and P. Pillay-Esnault, "OSPF as the
	Provider/Customer Edge Protocol for BGP/MPLS IP Virtual
	Private Networks (VPNs)", RFC 4577, DOI 10.17487/RFC4577,
	June 2006, <https://www.rfc-editor.org/info/rfc4577>.
	[RFC4750] Joyal, D., Ed., Galecki, P., Ed., Giacalone, S., Ed.,		[RFC4750] Joyal, D., Ed., Galecki, P., Ed., Giacalone, S., Ed.,
	Coltun, R., and F. Baker, "OSPF Version 2 Management		Coltun, R., and F. Baker, "OSPF Version 2 Management
	Information Base", RFC 4750, DOI 10.17487/RFC4750,		Information Base", RFC 4750, DOI 10.17487/RFC4750,
	December 2006, <https://www.rfc-editor.org/info/rfc4750>.		December 2006, <https://www.rfc-editor.org/info/rfc4750>.
	[RFC5187] Pillay-Esnault, P. and A. Lindem, "OSPFv3 Graceful
	Restart", RFC 5187, DOI 10.17487/RFC5187, June 2008,
	<https://www.rfc-editor.org/info/rfc5187>.
	[RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF		[RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
	for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008,		for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008,
	<https://www.rfc-editor.org/info/rfc5340>.		<https://www.rfc-editor.org/info/rfc5340>.
	[RFC5643] Joyal, D., Ed. and V. Manral, Ed., "Management Information		[RFC5643] Joyal, D., Ed. and V. Manral, Ed., "Management Information
	Base for OSPFv3", RFC 5643, DOI 10.17487/RFC5643, August		Base for OSPFv3", RFC 5643, DOI 10.17487/RFC5643, August
	2009, <https://www.rfc-editor.org/info/rfc5643>.		2009, <https://www.rfc-editor.org/info/rfc5643>.
	[RFC5838] Lindem, A., Ed., Mirtorabi, S., Roy, A., Barnes, M., and		[RFC5838] Lindem, A., Ed., Mirtorabi, S., Roy, A., Barnes, M., and
	R. Aggarwal, "Support of Address Families in OSPFv3",		R. Aggarwal, "Support of Address Families in OSPFv3",
	RFC 5838, DOI 10.17487/RFC5838, April 2010,		RFC 5838, DOI 10.17487/RFC5838, April 2010,
	<https://www.rfc-editor.org/info/rfc5838>.		<https://www.rfc-editor.org/info/rfc5838>.
	[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
	(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
	<https://www.rfc-editor.org/info/rfc5880>.
	[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-editor.org/info/rfc6020>.		<https://www.rfc-editor.org/info/rfc6020>.
	[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,		[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
	and A. Bierman, Ed., "Network Configuration Protocol		and A. Bierman, Ed., "Network Configuration Protocol
	(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,		(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
	<https://www.rfc-editor.org/info/rfc6241>.		<https://www.rfc-editor.org/info/rfc6241>.
	[RFC6565] Pillay-Esnault, P., Moyer, P., Doyle, J., Ertekin, E., and
	M. Lundberg, "OSPFv3 as a Provider Edge to Customer Edge
	(PE-CE) Routing Protocol", RFC 6565, DOI 10.17487/RFC6565,
	June 2012, <https://www.rfc-editor.org/info/rfc6565>.
	[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>.
	[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>.
			6.2. Informative References
	[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>.
	6.2. Informative References
	[I-D.ietf-ospf-yang]
	Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,
	"Yang Data Model for OSPF Protocol", draft-ietf-ospf-
	yang-09 (work in progress), October 2017.
	[I-D.ietf-spring-sr-yang]
	Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG
	Data Model for Segment Routing", draft-ietf-spring-sr-
	yang-08 (work in progress), December 2017.
	Appendix A. Contributors' Addreses		Appendix A. Contributors' Addreses
	Dean Bogdanovic		Dean Bogdanovic
	Volta Networks, Inc.		Volta Networks, Inc.
	EMail: dean@voltanet.io		EMail: dean@voltanet.io
	Kiran Koushik Agrahara Sreenivasa		Kiran Koushik Agrahara Sreenivasa
	Cisco Systems		Cisco Systems
	12515 Research Blvd, Bldg 4		12515 Research Blvd, Bldg 4
End of changes. 14 change blocks.
	53 lines changed or deleted		39 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/