< draft-ietf-ospf-sr-yang-12.txt		draft-ietf-ospf-sr-yang-13.txt >
	Internet D. Yeung		Internet D. Yeung
	Internet-Draft Arrcus		Internet-Draft Arrcus
	Intended status: Standards Track Y. Qu		Intended status: Standards Track Y. Qu
	Expires: January 13, 2021 Futurewei		Expires: July 15, 2021 Futurewei
	J. Zhang		J. Zhang
	Juniper Networks		Juniper Networks
	I. Chen		I. Chen
	The MITRE Corporation		The MITRE Corporation
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	July 12, 2020		January 11, 2021
	YANG Data Model for OSPF SR (Segment Routing) Protocol		YANG Data Model for OSPF SR (Segment Routing) Protocol
	draft-ietf-ospf-sr-yang-12		draft-ietf-ospf-sr-yang-13
	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. The model is based on YANG 1.1 as		and manage OSPF Segment Routing. The model is based on YANG 1.1 as
	defined in RFC 7950 and conforms to the Network Management Datastore		defined in RFC 7950 and conforms to the Network Management Datastore
	Architecture (NDMA) as described in RFC 8342.		Architecture (NDMA) as described in RFC 8342.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	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 January 13, 2021.		This Internet-Draft will expire on July 15, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2021 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
	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
	skipping to change at page 2, line 38 ¶		skipping to change at page 2, line 38 ¶
	YANG [RFC6020] [RFC7950] is a data definition language used to define		YANG [RFC6020] [RFC7950] is a data definition language used to define
	the contents of a conceptual data store that allows networked devices		the contents of a conceptual data store that allows networked devices
	to be managed using NETCONF [RFC6241]. YANG is proving relevant		to be managed using NETCONF [RFC6241]. YANG is proving relevant
	beyond its initial confines, as bindings to other interfaces (e.g.,		beyond its initial confines, as bindings to other interfaces (e.g.,
	ReST) and encodings other than XML (e.g., JSON) are being defined.		ReST) and encodings other than XML (e.g., JSON) are being defined.
	Furthermore, YANG data models can be used as the basis for		Furthermore, YANG data models can be used as the basis for
	implementation of other interfaces, such as CLI and programmatic		implementation of other interfaces, such as CLI and programmatic
	APIs.		APIs.
	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 it is an augmentation to the OSPF		and manage OSPF Segment Routing [RFC8665] and it is an augmentation
	YANG data model.		to the OSPF YANG data model.
	The YANG modules in this document conform to the Network Management		The YANG module in this document conforms to the Network Management
	Datastore Architecture (NMDA) [RFC8342].		Datastore Architecture (NMDA) [RFC8342].
	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. Tree Diagrams		2. Tree Diagrams
	skipping to change at page 7, line 38 ¶		skipping to change at page 7, line 38 ¶
	+--ro local-block-tlvs		+--ro local-block-tlvs
	| +--ro local-block-tlv*		| +--ro local-block-tlv*
	| +--ro range-size? uint24		| +--ro range-size? 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
	4. OSPF Segment Routing YANG Module		4. OSPF Segment Routing YANG Module
	<CODE BEGINS> file "ietf-ospf-sr@2020-02-05.yang"		<CODE BEGINS> file "ietf-ospf-sr@2021-01-10.yang"
	module ietf-ospf-sr {		module ietf-ospf-sr {
	yang-version 1.1;		yang-version 1.1;
	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";
	reference "RFC 6991 - Common YANG Data Types";		reference "RFC 6991 - Common YANG Data Types";
	}		}
	skipping to change at page 9, line 5 ¶		skipping to change at page 9, line 5 ¶
	<mailto:greg.hankins@alcatel-lucent.com>";		<mailto:greg.hankins@alcatel-lucent.com>";
	description		description
	"This YANG module defines the generic configuration		"This YANG module defines the generic configuration
	and operational state for OSPF Segment Routing, which is		and operational state for OSPF Segment Routing, which is
	common across all of the vendor implementations. It is		common across all of the vendor implementations. It is
	intended that the module will be extended by vendors to		intended that the module will be extended by vendors to
	define vendor-specific OSPF Segment Routing configuration		define vendor-specific OSPF Segment Routing configuration
	and operational parameters and policies.		and operational parameters and policies.
	This YANG model conforms to the Network Management		This YANG model conforms to the Network Management
	Datastore Architecture (NMDA) as described in RFC 8242.		Datastore Architecture (NMDA) as described in RFC 8242.
	Copyright (c) 2020 IETF Trust and the persons identified as		Copyright (c) 2021 IETF Trust and the persons identified as
	authors of the code. All rights reserved.		authors of the code. All rights reserved.
	Redistribution and use in source and binary forms, with or		Redistribution and use in source and binary forms, with or
	without modification, is permitted pursuant to, and subject to		without modification, is permitted pursuant to, and subject to
	the license terms contained in, the Simplified BSD License set		the license terms contained in, the Simplified BSD License set
	forth in Section 4.c of the IETF Trust's Legal Provisions		forth in Section 4.c of the IETF Trust's Legal Provisions
	Relating to IETF Documents		Relating to IETF Documents
	(https://trustee.ietf.org/license-info).		(https://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
	(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself		(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
	for full legal notices.		for full legal notices.
	The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL		The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
	NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',		NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
	'MAY', and 'OPTIONAL' in this document are to be interpreted as		'MAY', and 'OPTIONAL' in this document are to be interpreted as
	described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,		described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
	they appear in all capitals, as shown here.		they appear in all capitals, as shown here.
	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 2020-07-12 {		revision 2021-01-10 {
	description		description
	"Initial revision.";		"Initial revision.";
	reference		reference
	"RFC XXXX: A YANG Data Model for OSPF Segment Routing.";		"RFC XXXX: A YANG Data Model for OSPF Segment Routing.";
	}		}
	feature ti-lfa {		feature ti-lfa {
	description		description
	"Topology-Independent Loop-Free Alternate (TI-LFA)		"Topology-Independent Loop-Free Alternate (TI-LFA)
	computation using segment routing.";		computation using segment routing.";
	skipping to change at page 15, line 5 ¶		skipping to change at page 15, line 5 ¶
	+ "/rt:control-plane-protocol/ospf:ospf" {		+ "/rt:control-plane-protocol/ospf:ospf" {
	when "../rt:type = 'ospf:ospfv2' or "		when "../rt:type = 'ospf:ospfv2' or "
	+ "../rt:type = 'ospf:ospfv3'" {		+ "../rt:type = 'ospf:ospfv3'" {
	description		description
	"This augments the OSPF routing protocol when used.";		"This augments the OSPF routing protocol when used.";
	}		}
	description		description
	"This augments the OSPF protocol configuration		"This augments the OSPF protocol configuration
	with segment routing.";		with segment routing.";
	uses sr-mpls:sr-controlplane;		uses sr-mpls:sr-control-plane;
	container protocol-srgb {		container protocol-srgb {
	if-feature sr-mpls:protocol-srgb;		if-feature sr-mpls:protocol-srgb;
	uses sr-cmn:srgb;		uses sr-cmn:srgb;
	description		description
	"Per-protocol SRGB.";		"Per-protocol SRGB.";
	}		}
	}		}
	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 21, line 24 ¶		skipping to change at page 21, line 24 ¶
	7.1. Normative References		7.1. Normative References
	[I-D.ietf-ospf-yang]		[I-D.ietf-ospf-yang]
	Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,		Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,
	"YANG Data Model for OSPF Protocol", draft-ietf-ospf-		"YANG Data Model for OSPF Protocol", draft-ietf-ospf-
	yang-29 (work in progress), October 2019.		yang-29 (work in progress), October 2019.
	[I-D.ietf-spring-sr-yang]		[I-D.ietf-spring-sr-yang]
	Litkowski, S., Qu, Y., Lindem, A., Sarkar, P., and J.		Litkowski, S., Qu, Y., Lindem, A., Sarkar, P., and J.
	Tantsura, "YANG Data Model for Segment Routing", draft-		Tantsura, "YANG Data Model for Segment Routing", draft-
	ietf-spring-sr-yang-17 (work in progress), July 2020.		ietf-spring-sr-yang-29 (work in progress), December 2020.
	[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>.
End of changes. 17 change blocks.
	32 lines changed or deleted		32 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/