< draft-acee-lsr-ospf-yang-augmentation-v1-00.txt		draft-acee-lsr-ospf-yang-augmentation-v1-01.txt >
	Internet A. Lindem		Internet A. Lindem
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Informational Y. Qu		Intended status: Informational Y. Qu
	Expires: January 8, 2020 Futurewei		Expires: February 14, 2020 Futurewei
	July 7, 2019		August 13, 2019
	OSPF YANG Model Augmentations for Additional Features - Version 1		OSPF YANG Model Augmentations for Additional Features - Version 1
	draft-acee-lsr-ospf-yang-augmentation-v1-00		draft-acee-lsr-ospf-yang-augmentation-v1-01
	Abstract		Abstract
	This document defines YANG data modules augmenting the IETF OSPF YANG		This document defines YANG data modules augmenting the IETF OSPF YANG
	model to provide support for OSPF Two-Part Metric as defined in RFC		model to provide support for Traffic Engineering Extensions to OSPF
	8042, OSPF Graceful Link Shutdown as defined in RFC 8379 and OSPF		Version 3 as defined in RF 5329, OSPF Two-Part Metric as defined in
			RFC 8042, OSPF Graceful Link Shutdown as defined in RFC 8379 and OSPF
	Link-Local Signaling (LLS) Extensions for Local Interface ID		Link-Local Signaling (LLS) Extensions for Local Interface ID
	Advertisement as defined in RFC 8510.		Advertisement as defined in RFC 8510.
	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 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 8, 2020.		This Internet-Draft will expire on February 14, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3		1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
	2. YANG Module for OSPF Two-Part Metric . . . . . . . . . . . . 3		2. YANG Module for Traffic Engineering Extesions to OSPF Version
	3. YANG Module for OSPF Graceful Link Shutdown . . . . . . . . . 6		3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	4. YANG Module for OSPF LLS Extenstion for Local Interface ID		3. YANG Module for OSPF Two-Part Metric . . . . . . . . . . . . 8
	Advertisement . . . . . . . . . . . . . . . . . . . . . . . . 11		4. YANG Module for OSPF Graceful Link Shutdown . . . . . . . . . 12
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 13		5. YANG Module for OSPF LLS Extenstion for Local Interface ID
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14		Advertisement . . . . . . . . . . . . . . . . . . . . . . . . 17
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15		6. Security Considerations . . . . . . . . . . . . . . . . . . . 19
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
	8.1. Normative References . . . . . . . . . . . . . . . . . . 15		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
	8.2. Informative References . . . . . . . . . . . . . . . . . 16		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16		9.1. Normative References . . . . . . . . . . . . . . . . . . 21
			9.2. Informative References . . . . . . . . . . . . . . . . . 22
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
	1. Overview		1. Overview
	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 YANG data modules augmenting the IETF OSPF YANG		This document defines YANG data modules augmenting the IETF OSPF YANG
	model [I-D.ietf-ospf-yang], which itself augments [RFC8349], to		model [I-D.ietf-ospf-yang], which itself augments [RFC8349], to
	provide support for configuration and operational state for the		provide support for configuration and operational state for the
	following OSPF features:		following OSPF features:
			RFC5329: Traffic Engineering Extensions to OSPF Version 3 [RFC5329].
	RFC8042: OSPF Two-Part Metric [RFC8042].		RFC8042: OSPF Two-Part Metric [RFC8042].
	RFC8379: OSPF Graceful Link Shutdown [RFC8379].		RFC8379: OSPF Graceful Link Shutdown [RFC8379].
	RFC8510: OSPF Link-Local Signaling (LLS) Extensions for Local		RFC8510: OSPF Link-Local Signaling (LLS) Extensions for Local
	Interface ID Advertisement[RFC8510].		Interface ID Advertisement[RFC8510].
	The augmentations defined in this document requires support for the		The augmentations defined in this document requires support for the
	OSPF base model[I-D.ietf-ospf-yang] which defines basic OSPF		OSPF base model[I-D.ietf-ospf-yang] which defines basic OSPF
	configuration and state. The OSPF YANG model augments the ietf-		configuration and state. The OSPF YANG model augments the ietf-
	routing YANG model defined in [RFC8022].		routing YANG model defined in [RFC8022].
	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. YANG Module for OSPF Two-Part Metric		2. YANG Module for Traffic Engineering Extesions to OSPF Version 3
			This document defines a YANG module for Traffic Engineering
			Extersions to OSPF Version 3 as defined in [RFC5329]. It is an
			augmentation of the OSPF base model.
			module: ietf-ospfv3-te
			augment /rt:routing/rt:control-plane-protocols
			/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
			/ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas
			/ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3
			/ospf:body:
			+--ro ospfv3-intra-area-te
			+--ro router-address-tlv
			| +--ro router-address? inet:ipv6-address
			+--ro link-tlv
			+--ro link-type ospf:router-link-type
			+--ro local-if-ipv6-addrs
			| +--ro local-if-ipv6-addr* inet:ipv6-address
			+--ro remote-if-ipv6-addrs
			| +--ro remote-if-ipv6-addr* inet:ipv6-address
			+--ro te-metric? uint32
			+--ro max-bandwidth? rt-types:bandwidth-ieee-float32
			+--ro max-reservable-bandwidth? rt-types:bandwidth-ieee-float32
			+--ro unreserved-bandwidths
			| +--ro unreserved-bandwidth*
			| +--ro priority? uint8
			| +--ro unreserved-bandwidth? rt-types:bandwidth-ieee-float32
			+--ro admin-group? uint32
			+--ro neighbor-id
			| +--ro nbr-interface-id inet:ipv4-address
			| +--ro nbr-router-id yang:dotted-quad
			+--ro unknown-tlvs
			+--ro unknown-tlv*
			+--ro type? uint16
			+--ro length? uint16
			+--ro value? yang:hex-string
			<CODE BEGINS> file "ietf-ospfv3-te@2019-08-13.yang"
			module ietf-ospfv3-te {
			yang-version 1.1;
			namespace "urn:ietf:params:xml:ns:yang:ietf-ospfv3-te";
			prefix ospfv3-te;
			import ietf-inet-types {
			prefix "inet";
			reference "RFC 6991: Common YANG Data Types";
			}
			import ietf-yang-types {
			prefix "yang";
			reference "RFC 6991: Common YANG Data Types";
			}
			import ietf-routing-types {
			prefix "rt-types";
			reference "RFC 8294: Common YANG Data Types for the
			Routing Area";
			}
			import ietf-routing {
			prefix "rt";
			}
			import ietf-ospf {
			prefix "ospf";
			}
			organization
			"IETF LSR - Link State Routing Working Group";
			contact
			"WG Web: <http://tools.ietf.org/wg/lsr>
			WG List: <mailto:lsr@ietf.org>
			Author: Yingzhen Qu
			<mailto:yqu@futurewei.com>
			Author: Acee Lindem
			<mailto:acee@cisco.com>";
			description
			"This YANG module defines the configuration and operational
			state for OSPFv3 extensions to support intra-area Traffic
			Engineering (TE) as defined in RFC 5329.
			Copyright (c) 2019 IETF Trust and the persons identified as
			authors of the code. All rights reserved.
			Redistribution and use in source and binary forms, with or
			without modification, is permitted pursuant to, and subject
			to the license terms contained in, the Simplified BSD License
			set forth in Section 4.c of the IETF Trust's Legal Provisions
			Relating to IETF Documents
			(http://trustee.ietf.org/license-info).
			This version of this YANG module is part of RFC XXXX;
			see the RFC itself for full legal notices.";
			reference "RFC XXXX";
			revision 2019-08-13 {
			description
			"Initial version";
			reference
			"RFC XXXX: A YANG Data Model for OSPFv3 TE.";
			}
			identity ospfv3-intra-area-te-lsa {
			base ospf:ospfv3-lsa-type;
			description
			"OSPFv3 Intrea-area TE LSA.";
			}
			grouping ospfv3-intra-area-te {
			description "Grouping for OSPFv3 intra-area-te-lsa.";
			container ospfv3-intra-area-te {
			container router-address-tlv {
			description "The router IPv6 address tlv advertises a reachable
			IPv6 address.";
			leaf router-address {
			type inet:ipv6-address;
			description
			"Router IPv6 address.";
			}
			}
			container link-tlv {
			description "Describes a singel link, and it is constructed
			of a set of Sub-TLVs.";
			leaf link-type {
			type ospf:router-link-type;
			mandatory true;
			description "Link type.";
			}
			container local-if-ipv6-addrs {
			description "All local interface IPv6 addresses.";
			leaf-list local-if-ipv6-addr {
			type inet:ipv6-address;
			description
			"List of local interface IPv6 addresses.";
			}
			}
			container remote-if-ipv6-addrs {
			description "All remote interface IPv6 addresses.";
			leaf-list remote-if-ipv6-addr {
			type inet:ipv6-address;
			description
			"List of remote interface IPv6 addresses.";
			}
			}
			leaf te-metric {
			type uint32;
			description "TE metric.";
			}
			leaf max-bandwidth {
			type rt-types:bandwidth-ieee-float32;
			description "Maximum bandwidth.";
			}
			leaf max-reservable-bandwidth {
			type rt-types:bandwidth-ieee-float32;
			description "Maximum reservable bandwidth.";
			}
			container unreserved-bandwidths {
			description "All unreserved bandwidths.";
			list unreserved-bandwidth {
			leaf priority {
			type uint8 {
			range "0 .. 7";
			}
			description "Priority from 0 to 7.";
			}
			leaf unreserved-bandwidth {
			type rt-types:bandwidth-ieee-float32;
			description "Unreserved bandwidth.";
			}
			description
			"List of unreserved bandwidths for different
			priorities.";
			}
			}
			leaf admin-group {
			type uint32;
			description
			"Administrative group/Resource Class/Color.";
			}
			container neighbor-id {
			description "Neighbor link identitification.";
			leaf nbr-interface-id {
			type inet:ipv4-address;
			mandatory true;
			description "The neighbor's interface ID.";
			}
			leaf nbr-router-id {
			type yang:dotted-quad;
			mandatory true;
			description "The neighbor's router ID.";
			}
			}
			uses ospf:unknown-tlvs;
			}
			description "OSPFv3 Intra-Area-TE-LSA.";
			reference "RFC 5329: Traffic Engineering Extensions to OSPF
			: Version 3.";
			}
			}
			augment "/rt:routing/"
			+ "rt:control-plane-protocols/rt:control-plane-protocol/"
			+ "ospf:ospf/ospf:areas/"
			+ "ospf:area/ospf:database/"
			+ "ospf:area-scope-lsa-type/ospf:area-scope-lsas/"
			+ "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/"
			+ "ospf:ospfv3/ospf:body" {
			when "../../../../../../../../../"
			+ "rt:type = 'ospf:ospfv3'" {
			description
			"This augmentation is only valid for OSPFv3.";
			}
			description
			"OSPFv3 Intrea-Area-TE-LSA.";
			uses ospfv3-intra-area-te;
			}
			}
			<CODE ENDS>
			3. YANG Module for OSPF Two-Part Metric
	This document defines a YANG module for OSPF Two-Part Metric feature		This document defines a YANG module for OSPF Two-Part Metric feature
	as defined in [RFC8042]. It is an augmentation of the OSPF base		as defined in [RFC8042]. It is an augmentation of the OSPF base
	model.		model.
	module: ietf-ospf-two-part-metric		module: ietf-ospf-two-part-metric
	augment /rt:routing/rt:control-plane-protocols		augment /rt:routing/rt:control-plane-protocols
	/rt:control-plane-protocol/ospf:ospf/ospf:areas		/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
	/ospf:area/ospf:interfaces/ospf:interface:		/ospf:interfaces/ospf:interface:
	+--rw two-part-metric		+--rw two-part-metric
	+--rw enable? boolean		+--rw enable? boolean
	+--rw int-input-cost? uint16		+--rw int-input-cost? ospf:ospf-link-metric
	augment /rt:routing/rt:control-plane-protocols		augment /rt:routing/rt:control-plane-protocols
	/rt:control-plane-protocol/ospf:ospf/ospf:areas		/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
	/ospf:area/ospf:database/ospf:area-scope-lsa-type		/ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas
	/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version		/ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2
	/ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque		/ospf:body/ospf:opaque/ospf:extended-link-opaque
	/ospf:extended-link-tlvs/ospf:extended-link-tlv:		/ospf:extended-link-tlv:
	+--ro network-to-router-metric-sub-tlvs		+--ro network-to-router-metric-sub-tlvs
	+--ro net-to-rtr-sub-tlv*		+--ro net-to-rtr-sub-tlv*
	+--ro mt-id? uint8		+--ro mt-id? uint8
	+--ro mt-metric? uint16		+--ro mt-metric? uint16
			augment /rt:routing/rt:control-plane-protocols
			/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
			/ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas
			/ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2
			/ospf:body/ospf:opaque/ospf:te-opaque/ospf:link-tlv:
			+--ro network-to-router-te-metric? uint32
			augment /rt:routing/rt:control-plane-protocols
			/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
			/ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas
			/ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3
			/ospf:body/ospfv3-te:ospfv3-intra-area-te/ospfv3-te:link-tlv:
			+--ro network-to-router-te-metric? uint32
	<CODE BEGINS> file "ietf-ospf-two-part-metric@2019-07-05.yang"		<CODE BEGINS> file "ietf-ospf-two-part-metric@2019-08-13.yang"
	module ietf-ospf-two-part-metric {		module ietf-ospf-two-part-metric {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-two-part-metric";		namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-two-part-metric";
	prefix ospf-two-metric;		prefix ospf-two-metric;
	import ietf-routing {		import ietf-routing {
	prefix "rt";		prefix "rt";
	}		}
	import ietf-ospf {		import ietf-ospf {
	prefix "ospf";		prefix "ospf";
	}		}
			import ietf-ospfv3-te {
			prefix "ospfv3-te";
			}
	organization		organization
	"IETF LSR - Link State Routing Working Group";		"IETF LSR - Link State Routing Working Group";
	contact		contact
	"WG Web: <http://tools.ietf.org/wg/lsr>		"WG Web: <http://tools.ietf.org/wg/lsr>
	WG List: <mailto:lsr@ietf.org>		WG List: <mailto:lsr@ietf.org>
	Author: Yingzhen Qu		Author: Yingzhen Qu
	<mailto:yqu@futurewei.com>		<mailto:yqu@futurewei.com>
	Author: Acee Lindem		Author: Acee Lindem
	skipping to change at page 4, line 33 ¶		skipping to change at page 9, line 47 ¶
	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 2019-07-05 {		revision 2019-08-13 {
	description		description
	"Initial version";		"Initial version";
	reference		reference
	"RFC XXXX: A YANG Data Model for OSPF.";		"RFC XXXX: A YANG Data Model for OSPF.";
			}
			identity two-part-metric {
			base ospf:informational-capability;
			description
			"When set, the router is capable of supporting OSPF
			two-part metrics.";
			reference
			"RFC 8042: OSPF Two-Part Metric";
	}		}
	/* RFC 8042 */		/* RFC 8042 */
	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/"
	+ "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" {		+ "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" {
	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 interface configuration		"This augments the OSPF interface configuration
	skipping to change at page 5, line 17 ¶		skipping to change at page 10, line 42 ¶
	description		description
	"Two-part metric when link type is multi-access.";		"Two-part metric when link type is multi-access.";
	}		}
	leaf enable {		leaf enable {
	type boolean;		type boolean;
	default false;		default false;
	description		description
	"Enable two-part metric.";		"Enable two-part metric.";
	}		}
	leaf int-input-cost {		leaf int-input-cost {
	type uint16;		type ospf:ospf-link-metric;
	description		description
	"Link state metric from the two-part-metric network		"Link state metric from the two-part-metric network
	to this router.";		to this router.";
	}		}
	description		description
	"Interface two part metric configuration.";		"Interface two part metric configuration.";
	}		}
	}		}
	augment "/rt:routing/"		augment "/rt:routing/"
	+ "rt:control-plane-protocols/rt:control-plane-protocol/"		+ "rt:control-plane-protocols/rt:control-plane-protocol/"
	+ "ospf:ospf/ospf:areas/"		+ "ospf:ospf/ospf:areas/"
	+ "ospf:area/ospf:database/"		+ "ospf:area/ospf:database/"
	+ "ospf:area-scope-lsa-type/ospf:area-scope-lsas/"		+ "ospf:area-scope-lsa-type/ospf:area-scope-lsas/"
	+ "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/"		+ "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/"
	+ "ospf:ospfv2/ospf:body/ospf:opaque/"		+ "ospf:ospfv2/ospf:body/ospf:opaque/"
	+ "ospf:extended-link-tlvs/ospf:extended-link-tlv" {		+ "ospf:extended-link-opaque/ospf:extended-link-tlv" {
	when "../../../../../../../../../../../../"		when "../../../../../../../../../../../../"
	+ "rt:type = 'ospf:ospfv2'" {		+ "rt:type = 'ospf:ospfv2'" {
	description		description
	"This augmentation is only valid for OSPFv2.";		"This augmentation is only valid for OSPFv2.";
	}		}
	description		description
	"Network-to-Router metric sub tlv for OSPFv2 extended link TLV		"Network-to-Router metric sub tlv for OSPFv2 extended link TLV
	in type 10 opaque LSA.";		in type 10 opaque LSA.";
	container network-to-router-metric-sub-tlvs {		container network-to-router-metric-sub-tlvs {
	skipping to change at page 6, line 11 ¶		skipping to change at page 11, line 36 ¶
	}		}
	leaf mt-metric {		leaf mt-metric {
	type uint16;		type uint16;
	description "Network-to-router metric.";		description "Network-to-router metric.";
	}		}
	description		description
	"Network-to-Router metric sub-TLV.";		"Network-to-Router metric sub-TLV.";
	}		}
	}		}
	}		}
			augment "/rt:routing/"
			+ "rt:control-plane-protocols/rt:control-plane-protocol/"
			+ "ospf:ospf/ospf:areas/"
			+ "ospf:area/ospf:database/"
			+ "ospf:area-scope-lsa-type/ospf:area-scope-lsas/"
			+ "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/"
			+ "ospf:ospfv2/ospf:body/ospf:opaque/ospf:te-opaque/"
			+ "ospf:link-tlv" {
			when "../../../../../../../../../../../../"
			+ "rt:type = 'ospf:ospfv2'" {
			description
			"This augmentation is only valid for OSPFv2.";
			}
			description
			"Traffic Engineering Network-to-Router Sub-TLV.";
			leaf network-to-router-te-metric {
			type uint32;
			description "Network to Router TE metric.";
			reference
			"RFC 8042 - OSPF Two-Part Metric";
			}
			}
			augment "/rt:routing/"
			+ "rt:control-plane-protocols/rt:control-plane-protocol/"
			+ "ospf:ospf/ospf:areas/"
			+ "ospf:area/ospf:database/"
			+ "ospf:area-scope-lsa-type/ospf:area-scope-lsas/"
			+ "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/"
			+ "ospf:ospfv3/ospf:body/ospfv3-te:ospfv3-intra-area-te/"
			+ "ospfv3-te:link-tlv" {
			when "../../../../../../../../../../../"
			+ "rt:type = 'ospf:ospfv3'" {
			description
			"This augmentation is only valid for OSPFv3.";
			}
			description
			"Traffic Engineering Network-to-Router Sub-TLV.";
			leaf network-to-router-te-metric {
			type uint32;
			description "Network to Router TE metric.";
			reference
			"RFC 8042 - OSPF Two-Part Metric";
			}
			}
	}		}
	<CODE ENDS>		<CODE ENDS>
	3. YANG Module for OSPF Graceful Link Shutdown		4. YANG Module for OSPF Graceful Link Shutdown
	This document defines a YANG module for OSPF Graceful Link Shutdown		This document defines a YANG module for OSPF Graceful Link Shutdown
	feature as defined in [RFC8379]. It is an augmentation of the OSPF		feature as defined in [RFC8379]. It is an augmentation of the OSPF
	base model.		base model.
	module: ietf-ospf-graceful-link-shutdown		module: ietf-ospf-graceful-link-shutdown
	augment /rt:routing/rt:control-plane-protocols		augment /rt:routing/rt:control-plane-protocols
	/rt:control-plane-protocol/ospf:ospf/ospf:areas		/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
	/ospf:area/ospf:interfaces/ospf:interface:		/ospf:interfaces/ospf:interface:
	+--rw graceful-link-shutdown		+--rw graceful-link-shutdown
	+--rw enable? boolean		+--rw enable? boolean
	augment /rt:routing/rt:control-plane-protocols		augment /rt:routing/rt:control-plane-protocols
	/rt:control-plane-protocol/ospf:ospf/ospf:areas		/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
	/ospf:area/ospf:database/ospf:area-scope-lsa-type		/ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas
	/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version		/ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2
	/ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque		/ospf:body/ospf:opaque/ospf:extended-link-opaque
	/ospf:extended-link-tlvs/ospf:extended-link-tlv:		/ospf:extended-link-tlv:
	+--ro grace-link-shut-sub-tlv!		+--ro graceful-link-shutdown-sub-tlv!
	+--ro remote-address-sub-tlv		+--ro remote-address-sub-tlv
	| +--ro remote-address? inet:ipv4-address		| +--ro remote-address? inet:ipv4-address
	+--ro local-remote-int-id-sub-tlv		+--ro local-remote-int-id-sub-tlv
	+--ro local-int-id? uint32		+--ro local-int-id? uint32
	+--ro remote-int-id? uint32		+--ro remote-int-id? uint32
	augment /rt:routing/rt:control-plane-protocols		augment /rt:routing/rt:control-plane-protocols
	/rt:control-plane-protocol/ospf:ospf/ospf:areas		/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
	/ospf:area/ospf:database/ospf:area-scope-lsa-type		/ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas
	/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version		/ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3
	/ospf:ospfv3/ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router		/ospf:body/ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs
	/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv:		/ospfv3-e-lsa:link-tlv:
	+--ro grace-link-shut-sub-tlv!		+--ro graceful-link-shutdown-sub-tlv!
	augment /rt:routing/rt:control-plane-protocols		augment /rt:routing/rt:control-plane-protocols
	/rt:control-plane-protocol/ospf:ospf/ospf:database		/rt:control-plane-protocol/ospf:ospf/ospf:database
	/ospf:as-scope-lsa-type/ospf:as-scope-lsas		/ospf:as-scope-lsa-type/ospf:as-scope-lsas/ospf:as-scope-lsa
	/ospf:as-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3		/ospf:version/ospf:ospfv3/ospf:ospfv3/ospf:body
	/ospf:body/ospfv3-e-lsa:e-router		/ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs
	/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv:		/ospfv3-e-lsa:link-tlv:
	+--ro grace-link-shut-sub-tlv!		+--ro graceful-link-shutdown-sub-tlv!
	<CODE BEGINS> file "ietf-ospf-graceful-link-shutdown@2019-07-05.yang"		<CODE BEGINS> file "ietf-ospf-graceful-link-shutdown@2019-08-13.yang"
	module ietf-ospf-graceful-link-shutdown {		module ietf-ospf-graceful-link-shutdown {
	yang-version 1.1;		yang-version 1.1;
	namespace		namespace
	"urn:ietf:params:xml:ns:yang:ietf-ospf-graceful-link-shutdown";		"urn:ietf:params:xml:ns:yang:ietf-ospf-graceful-link-shutdown";
	prefix ospf-grace-linkdown;		prefix ospf-grace-linkdown;
	import ietf-inet-types {		import ietf-inet-types {
	prefix "inet";		prefix "inet";
	}		}
	skipping to change at page 8, line 47 ¶		skipping to change at page 14, line 47 ¶
	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 2019-07-05 {		revision 2019-08-13 {
	description		description
	"Initial version";		"Initial version";
	reference		reference
	"RFC XXXX: A YANG Data Model for OSPF.";		"RFC XXXX: A YANG Data Model for OSPF.";
	}		}
	/* RFC 8379 */		/* RFC 8379 */
	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 9, line 41 ¶		skipping to change at page 15, line 41 ¶
	}		}
	/* Database */		/* Database */
	augment "/rt:routing/"		augment "/rt:routing/"
	+ "rt:control-plane-protocols/rt:control-plane-protocol/"		+ "rt:control-plane-protocols/rt:control-plane-protocol/"
	+ "ospf:ospf/ospf:areas/"		+ "ospf:ospf/ospf:areas/"
	+ "ospf:area/ospf:database/"		+ "ospf:area/ospf:database/"
	+ "ospf:area-scope-lsa-type/ospf:area-scope-lsas/"		+ "ospf:area-scope-lsa-type/ospf:area-scope-lsas/"
	+ "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/"		+ "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/"
	+ "ospf:ospfv2/ospf:body/ospf:opaque/"		+ "ospf:ospfv2/ospf:body/ospf:opaque/"
	+ "ospf:extended-link-tlvs/ospf:extended-link-tlv" {		+ "ospf:extended-link-opaque/ospf:extended-link-tlv" {
	when "../../../../../../../../../../../../"		when "../../../../../../../../../../../../"
	+ "rt:type = 'ospf:ospfv2'" {		+ "rt:type = 'ospf:ospfv2'" {
	description		description
	"This augmentation is only valid for OSPFv2.";		"This augmentation is only valid for OSPFv2.";
	}		}
	description		description
	"OSPF graceful link shutdown for OSPFv2 extended link TLV		"OSPF graceful link shutdown for OSPFv2 extended link TLV
	in type 10 opaque LSA.";		in type 10 opaque LSA.";
	container graceful-link-shutdown-sub-tlv {		container graceful-link-shutdown-sub-tlv {
	skipping to change at page 11, line 37 ¶		skipping to change at page 17, line 37 ¶
	description		description
	"Graceful-Link-Shutdown sub-TLV identifies the link as being		"Graceful-Link-Shutdown sub-TLV identifies the link as being
	gracefully shutdown.";		gracefully shutdown.";
	}		}
	description		description
	"Augemnt OSPFv3 AS scope router-link TLV.";		"Augemnt OSPFv3 AS scope router-link TLV.";
	}		}
	}		}
	<CODE ENDS>		<CODE ENDS>
	4. YANG Module for OSPF LLS Extenstion for Local Interface ID		5. YANG Module for OSPF LLS Extenstion for Local Interface ID
	Advertisement		Advertisement
	This document defines a YANG module for OSPF Link-Local Signaling		This document defines a YANG module for OSPF Link-Local Signaling
	(LLS) Extensions for Local Interface ID Advertisement feature as		(LLS) Extensions for Local Interface ID Advertisement feature as
	defined in [RFC8510]. It is an augmentation of the OSPF base model.		defined in [RFC8510]. It is an augmentation of the OSPF base model.
	module: ietf-ospf-lls-local-id		module: ietf-ospf-lls-local-id
	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:
	+--rw lls-int-id		+--rw lls-int-id
	+--rw enable? boolean		+--rw enable? boolean
	<CODE BEGINS> file "ietf-ospf-lls-local-id@2019-07-05.yang"		<CODE BEGINS> file "ietf-ospf-lls-local-id@2019-08-13.yang"
	module ietf-ospf-lls-local-id {		module ietf-ospf-lls-local-id {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-lls-local-id";		namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-lls-local-id";
	prefix ospf-lls-localid;		prefix ospf-lls-localid;
	import ietf-routing {		import ietf-routing {
	prefix "rt";		prefix "rt";
	}		}
	skipping to change at page 12, line 50 ¶		skipping to change at page 18, line 50 ¶
	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 2019-07-05 {		revision 2019-08-13 {
	description		description
	"Initial version";		"Initial version";
	reference		reference
	"RFC XXXX: A YANG Data Model for OSPF.";		"RFC XXXX: A YANG Data Model for OSPF.";
	}		}
	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" {
	when "../rt:type = 'ospf:ospfv2' or "		when "../rt:type = 'ospf:ospfv2' or "
	+ "../rt:type = 'ospf:ospfv3'" {		+ "../rt:type = 'ospf:ospfv3'" {
	skipping to change at page 13, line 34 ¶		skipping to change at page 19, line 34 ¶
	description		description
	"Enable LLS to advertise local interface ID.";		"Enable LLS to advertise local interface ID.";
	}		}
	description		description
	"OSPF LLS Extensions for interface ID.";		"OSPF LLS Extensions for interface ID.";
	}		}
	}		}
	}		}
	<CODE ENDS>		<CODE ENDS>
	5. Security Considerations		6. Security Considerations
	The YANG modules specified in this document define a schema for data		The YANG modules specified in this document define a schema for data
	that is designed to be accessed via network management protocols such		that is designed to be accessed via network management protocols such
	as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer		as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
	is the secure transport layer, and the mandatory-to-implement secure		is the secure transport layer, and the mandatory-to-implement secure
	transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer		transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
	is HTTPS, and the mandatory-to-implement secure transport is TLS		is HTTPS, and the mandatory-to-implement secure transport is TLS
	[RFC5246].		[RFC5246].
	The NETCONF access control model [RFC6536] provides the means to		The NETCONF access control model [RFC6536] provides the means to
	skipping to change at page 14, line 17 ¶		skipping to change at page 20, line 17 ¶
	Some of the readable data nodes in the modules may be considered		Some of the readable data nodes in the modules may be considered
	sensitive or vulnerable in some network environments. It is thus		sensitive or vulnerable in some network environments. It is thus
	important to control read access (e.g., via get, get-config, or		important to control read access (e.g., via get, get-config, or
	notification) to these data nodes. The exposure of the Link State		notification) to these data nodes. The exposure of the Link State
	Database (LSDB) will expose the detailed topology of the network.		Database (LSDB) will expose the detailed topology of the network.
	This may be undesirable since both due to the fact that exposure may		This may be undesirable since both due to the fact that exposure may
	facilitate other attacks. Additionally, network operators may		facilitate other attacks. Additionally, network operators may
	consider their topologies to be sensitive confidential data.		consider their topologies to be sensitive confidential data.
	6. IANA Considerations		7. IANA Considerations
	This document registers URIs in the IETF XML registry [RFC3688].		This document registers URIs in the IETF XML registry [RFC3688].
	Following the format in [RFC3688], the following registrations is		Following the format in [RFC3688], the following registrations is
	requested to be made:		requested to be made:
	URI: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric		URI: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric
	Registrant Contact: The IESG.		Registrant Contact: The IESG.
	XML: N/A, the requested URI is an XML namespace.		XML: N/A, the requested URI is an XML namespace.
	URI: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown		URI: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown
	skipping to change at page 15, line 5 ¶		skipping to change at page 21, line 5 ¶
	name: ietf-ospf-grace-linkdown		name: ietf-ospf-grace-linkdown
	namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown		namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown
	prefix: ospf-grace-linkdown		prefix: ospf-grace-linkdown
	reference: RFC XXXX		reference: RFC XXXX
	name: ietf-ospf-lls-localid		name: ietf-ospf-lls-localid
	namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid		namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid
	prefix: ospf-lls-localid		prefix: ospf-lls-localid
	reference: RFC XXXX		reference: RFC XXXX
	7. Acknowledgements		8. Acknowledgements
	This document was produced using Marshall Rose's xml2rfc tool.		This document was produced using Marshall Rose's xml2rfc tool.
	The YANG model was developed using the suite of YANG tools written		The YANG model was developed using the suite of YANG tools written
	and maintained by numerous authors.		and maintained by numerous authors.
	8. References		9. References
	8.1. Normative References		9.1. Normative References
	[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>.
	[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-editor.org/info/rfc3688>.		<https://www.rfc-editor.org/info/rfc3688>.
	[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security		[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
	(TLS) Protocol Version 1.2", RFC 5246,		(TLS) Protocol Version 1.2", RFC 5246,
	DOI 10.17487/RFC5246, August 2008,		DOI 10.17487/RFC5246, August 2008,
	<https://www.rfc-editor.org/info/rfc5246>.		<https://www.rfc-editor.org/info/rfc5246>.
			[RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed.,
			"Traffic Engineering Extensions to OSPF Version 3",
			RFC 5329, DOI 10.17487/RFC5329, September 2008,
			<https://www.rfc-editor.org/info/rfc5329>.
	[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>.
	skipping to change at page 16, line 33 ¶		skipping to change at page 22, line 37 ¶
	Jalil, "OSPF Graceful Link Shutdown", RFC 8379,		Jalil, "OSPF Graceful Link Shutdown", RFC 8379,
	DOI 10.17487/RFC8379, May 2018,		DOI 10.17487/RFC8379, May 2018,
	<https://www.rfc-editor.org/info/rfc8379>.		<https://www.rfc-editor.org/info/rfc8379>.
	[RFC8510] Psenak, P., Ed., Talaulikar, K., Henderickx, W., and P.		[RFC8510] Psenak, P., Ed., Talaulikar, K., Henderickx, W., and P.
	Pillay-Esnault, "OSPF Link-Local Signaling (LLS)		Pillay-Esnault, "OSPF Link-Local Signaling (LLS)
	Extensions for Local Interface ID Advertisement",		Extensions for Local Interface ID Advertisement",
	RFC 8510, DOI 10.17487/RFC8510, January 2019,		RFC 8510, DOI 10.17487/RFC8510, January 2019,
	<https://www.rfc-editor.org/info/rfc8510>.		<https://www.rfc-editor.org/info/rfc8510>.
	8.2. Informative References		9.2. Informative 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-23 (work in progress), July 2019.		yang-26 (work in progress), August 2019.
	Authors' Addresses		Authors' Addresses
	Acee Lindem		Acee Lindem
	Cisco Systems		Cisco Systems
	301 Midenhall Way		301 Midenhall Way
	Cary, NC 27513		Cary, NC 27513
	EMail: acee@cisco.com		EMail: acee@cisco.com
	Yingzhen Qu		Yingzhen Qu
End of changes. 33 change blocks.
	87 lines changed or deleted		404 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/