draft-ietf-ospf-yang-12.txt		draft-ietf-ospf-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 3, 2019 Huawei		Expires: January 27, 2019 Huawei
	J. Zhang		J. Zhang
	Juniper Networks		Juniper Networks
	I. Chen		I. Chen
	Jabil		Jabil
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	July 2, 2018		July 26, 2018
	Yang Data Model for OSPF Protocol		Yang Data Model for OSPF Protocol
	draft-ietf-ospf-yang-12		draft-ietf-ospf-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.		and manage OSPF.
	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 http://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 3, 2019.		This Internet-Draft will expire on January 27, 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		(http://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. Design of Data Model . . . . . . . . . . . . . . . . . . . . 3		2. Design of Data Model . . . . . . . . . . . . . . . . . . . . 3
	2.1. OSPF Operational State . . . . . . . . . . . . . . . . . 3		2.1. OSPF Operational State . . . . . . . . . . . . . . . . . 3
	2.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3		2.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3
	2.3. OSPFv2 and OSPFv3 . . . . . . . . . . . . . . . . . . . . 5		2.3. OSPFv2 and OSPFv3 . . . . . . . . . . . . . . . . . . . . 5
	2.4. Optional Features . . . . . . . . . . . . . . . . . . . . 5		2.4. Optional Features . . . . . . . . . . . . . . . . . . . . 5
	2.5. OSPF Router Configuration/Operational State . . . . . . . 5		2.5. OSPF Router Configuration/Operational State . . . . . . . 5
	2.6. OSPF Area Configuration/Operational State . . . . . . . . 8		2.6. OSPF Area Configuration/Operational State . . . . . . . . 8
	2.7. OSPF Interface Configuration/Operational State . . . . . 13		2.7. OSPF Interface Configuration/Operational State . . . . . 13
	2.8. OSPF notification . . . . . . . . . . . . . . . . . . . . 15		2.8. OSPF notification . . . . . . . . . . . . . . . . . . . . 16
	2.9. OSPF RPC Operations . . . . . . . . . . . . . . . . . . . 19		2.9. OSPF RPC Operations . . . . . . . . . . . . . . . . . . . 19
	3. OSPF Yang Module . . . . . . . . . . . . . . . . . . . . . . 19		3. OSPF Yang Module . . . . . . . . . . . . . . . . . . . . . . 20
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 100		4. Security Considerations . . . . . . . . . . . . . . . . . . . 104
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 101		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 105
	6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 102		6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 106
	7. Normative References . . . . . . . . . . . . . . . . . . . . 102		7. Normative References . . . . . . . . . . . . . . . . . . . . 106
	Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 108		Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 112
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 108		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 112
	1. Overview		1. Overview
	YANG [RFC6020] is a data definition language used to define the		YANG [RFC6020] is a data definition language used to define the
	contents of a conceptual data store that allows networked devices to		contents of a conceptual data store that allows networked devices to
	be managed using NETCONF [RFC6241]. YANG is proving relevant beyond		be managed using NETCONF [RFC6241]. YANG is proving relevant beyond
	its initial confines, as bindings to other interfaces (e.g., ReST)		its initial confines, as bindings to other interfaces (e.g., ReST)
	and encodings other than XML (e.g., JSON) are being defined.		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
	skipping to change at page 6, line 22 ¶		skipping to change at page 6, line 22 ¶
	| +--rw enable? boolean		| +--rw enable? boolean
	| +--rw reference-bandwidth? uint32		| +--rw reference-bandwidth? uint32
	+--rw spf-control		+--rw spf-control
	| +--rw paths? uint16 {max-ecmp}?		| +--rw paths? uint16 {max-ecmp}?
	| +--rw ietf-spf-delay {ietf-spf-delay}?		| +--rw ietf-spf-delay {ietf-spf-delay}?
	| +--rw initial-delay? uint16		| +--rw initial-delay? uint16
	| +--rw short-delay? uint16		| +--rw short-delay? uint16
	| +--rw long-delay? uint16		| +--rw long-delay? uint16
	| +--rw hold-down? uint16		| +--rw hold-down? uint16
	| +--rw time-to-learn? uint16		| +--rw time-to-learn? uint16
			| +--ro current-state? enumeration
			| +--ro remaining-time-to-learn? uint16
			| +--ro remaining-hold-down? uint16
			| +--ro last-event-received? yang:timestamp
			| +--ro next-spf-time? yang:timestamp
			| +--ro last-spf-time? yang:timestamp
	+--rw database-control		+--rw database-control
	| +--rw max-lsa? uint32 {max-lsa}?		| +--rw max-lsa? uint32 {max-lsa}?
	+--rw stub-router {stub-router}?		+--rw stub-router {stub-router}?
	| +--rw (trigger)?		| +--rw (trigger)?
	| +--:(always)		| +--:(always)
	| +--rw always!		| +--rw always!
	+--rw mpls		+--rw mpls
	| +--rw te-rid {te-rid}?		| +--rw te-rid {te-rid}?
	| | +--rw ipv4-router-id? inet:ipv4-address		| | +--rw ipv4-router-id? inet:ipv4-address
	| | +--rw ipv6-router-id? inet:ipv6-address		| | +--rw ipv6-router-id? inet:ipv6-address
	| +--rw ldp		| +--rw ldp
	| +--rw igp-sync? boolean {ldp-igp-sync}?		| +--rw igp-sync? boolean {ldp-igp-sync}?
	+--rw fast-reroute {fast-reroute}?		+--rw fast-reroute {fast-reroute}?
	| +--rw lfa {lfa}?		| +--rw lfa {lfa}?
			+--ro protected-routes
			| +--ro af-stats* [af prefix alternate]
			| +--ro af iana-rt-types:address-family
			| +--ro prefix string
			| +--ro alternate string
			| +--ro alternate-type? enumeration
			| +--ro best? boolean
			| +--ro non-best-reason? string
			| +--ro protection-available? bits
			| +--ro alternate-metric1? uint32
			| +--ro alternate-metric2? uint32
			| +--ro alternate-metric3? uint32
			+--ro unprotected-routes
			| +--ro af-stats* [af prefix]
			| +--ro af iana-rt-types:address-family
			| +--ro prefix string
			+--ro protection-statistics* [frr-protection-method]
			| +--ro frr-protection-method string
			| +--ro af-stats* [af]
			| +--ro af iana-rt-types:address-family
			| +--ro total-routes? uint32
			| +--ro unprotected-routes? uint32
			| +--ro protected-routes? uint32
			| +--ro linkprotected-routes? uint32
			| +--ro nodeprotected-routes? uint32
	+--rw node-tags {node-tag}?		+--rw node-tags {node-tag}?
	| +--rw node-tag* [tag]		| +--rw node-tag* [tag]
	| +--rw tag uint32		| +--rw tag uint32
	+--ro router-id?		+--ro router-id?
	+--ro local-rib		+--ro local-rib
	| +--ro route* [prefix]		| +--ro route* [prefix]
	| +--ro prefix inet:ip-prefix		| +--ro prefix inet:ip-prefix
	| +--ro next-hops		| +--ro next-hops
	| | +--ro next-hop* [next-hop]		| | +--ro next-hop* [next-hop]
	| | +--ro outgoing-interface? if:interface-ref		| | +--ro outgoing-interface? if:interface-ref
	skipping to change at page 7, line 12 ¶		skipping to change at page 7, line 43 ¶
	+--ro statistics		+--ro statistics
	| +--ro originate-new-lsa-count? yang:counter32		| +--ro originate-new-lsa-count? yang:counter32
	| +--ro rx-new-lsas-count? yang:counter32		| +--ro rx-new-lsas-count? yang:counter32
	| +--ro as-scope-lsa-count? yang:gauge32		| +--ro as-scope-lsa-count? yang:gauge32
	| +--ro as-scope-lsa-chksum-sum? uint32		| +--ro as-scope-lsa-chksum-sum? uint32
	| +--ro database		| +--ro database
	| +--ro as-scope-lsa-type*		| +--ro as-scope-lsa-type*
	| +--ro lsa-type? uint16		| +--ro lsa-type? uint16
	| +--ro lsa-count? yang:gauge32		| +--ro lsa-count? yang:gauge32
	| +--ro lsa-cksum-sum? int32		| +--ro lsa-cksum-sum? int32
	+--ro ietf-spf-delay
	| +--ro initial-delay? uint16
	| +--ro short-delay? uint16
	| +--ro long-delay? uint16
	| +--ro hold-down? uint16
	| +--ro time-to-learn? uint16
	| +--ro current-state? enumeration
	| +--ro remaining-time-to-learn? uint16
	| +--ro remaining-hold-down? uint16
	| +--ro last-event-received? yang:timestamp
	| +--ro next-spf-time? yang:timestamp
	| +--ro last-spf-time? yang:timestamp
	+--ro database		+--ro database
	| +--ro as-scope-lsa-type* [lsa-type]		| +--ro as-scope-lsa-type* [lsa-type]
	| +--ro as-scope-lsas		| +--ro as-scope-lsas
	| +--ro as-scope-lsa* [lsa-id adv-router]		| +--ro as-scope-lsa* [lsa-id adv-router]
	| +--ro lsa-id union		| +--ro lsa-id union
	| +--ro adv-router inet:ipv4-address		| +--ro adv-router inet:ipv4-address
	| +--ro decoded-completed? boolean		| +--ro decoded-completed? boolean
	| +--ro raw-data? yang:hex-string		| +--ro raw-data? yang:hex-string
	| +--ro (version)?		| +--ro (version)?
	| +--:(ospfv2)		| +--:(ospfv2)
	skipping to change at page 20, line 4 ¶		skipping to change at page 20, line 24 ¶
	+---w routing-protocol-name		+---w routing-protocol-name
	-> /rt:routing/control-plane-protocols/		-> /rt:routing/control-plane-protocols/
	control-plane-protocol/name		control-plane-protocol/name
	3. OSPF Yang Module		3. OSPF Yang Module
	The following RFCs and drafts are not referenced in the document text		The following RFCs and drafts are not referenced in the document text
	but are referenced in the ietf-ospf.yang module: [RFC0905],		but are referenced in the ietf-ospf.yang module: [RFC0905],
	[RFC1765], [RFC4552], [RFC4576], [RFC4915], [RFC5082], [RFC5185],		[RFC1765], [RFC4552], [RFC4576], [RFC4915], [RFC5082], [RFC5185],
	[RFC5250], [RFC5286], [RFC5329], [RFC5443], [RFC5613], [RFC5714],		[RFC5250], [RFC5286], [RFC5329], [RFC5443], [RFC5613], [RFC5714],
	[RFC5880], [RFC5881], [RFC6021], [RFC6860], [RFC6987], [RFC7490],		[RFC5880], [RFC5881], [RFC6021], [RFC6860], [RFC6987], [RFC7490],
	[RFC7684], [RFC7770], [RFC7777], [RFC8291], [RFC8343], [RFC8349],		[RFC7684], [RFC7770], [RFC7777], [RFC8294], [RFC8343], [RFC8349],
	[I-D.ietf-bfd-yang], and [I-D.ietf-rtgwg-backoff-algo].		[I-D.ietf-bfd-yang], and [RFC8405].
	<CODE BEGINS> file "ietf-ospf@2018-07-02.yang"		<CODE BEGINS> file "ietf-ospf@2018-07-27.yang"
	module ietf-ospf {		module ietf-ospf {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-ospf";		namespace "urn:ietf:params:xml:ns:yang:ietf-ospf";
	prefix ospf;		prefix ospf;
	import ietf-inet-types {		import ietf-inet-types {
	prefix "inet";		prefix "inet";
	reference "RFC 6021 - Common YANG Data Types";		reference "RFC 6021 - Common YANG Data Types";
	}		}
	skipping to change at page 20, line 34 ¶		skipping to change at page 21, line 4 ¶
	}		}
	import ietf-interfaces {		import ietf-interfaces {
	prefix "if";		prefix "if";
	reference "RFC 8343 - A YANG Data Model for Interface		reference "RFC 8343 - A YANG Data Model for Interface
	Management (NDMA Version)";		Management (NDMA Version)";
	}		}
	import ietf-routing-types {		import ietf-routing-types {
	prefix "rt-types";		prefix "rt-types";
	reference "RFC 8291 - Common YANG Data Types for the		reference "RFC 8294 - Common YANG Data Types for the
	Routing Area";		Routing Area";
	}		}
	import iana-routing-types {		import iana-routing-types {
	prefix "iana-rt-types";		prefix "iana-rt-types";
	reference "RFC 8291 - Common YANG Data Types for the		reference "RFC 8294 - Common YANG Data Types for the
	Routing Area";		Routing Area";
	}		}
	import ietf-routing {		import ietf-routing {
	prefix "rt";		prefix "rt";
	reference "RFC 8349 - A YANG Data Model for Routing		reference "RFC 8349 - A YANG Data Model for Routing
	Management (NMDA Version)";		Management (NMDA Version)";
	}		}
	import ietf-key-chain {		import ietf-key-chain {
	skipping to change at page 22, line 10 ¶		skipping to change at page 22, line 29 ¶
	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		without modification, is permitted pursuant to, and subject
	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.";
	revision 2018-07-02 {		revision 2018-07-27 {
	description		description
	"Initial revision.";		"Initial revision.";
	reference		reference
	"RFC XXXX: A YANG Data Model for OSPF.";		"RFC XXXX: A YANG Data Model for OSPF.";
	}		}
	feature multi-topology {		feature multi-topology {
	description		description
	"Support Multiple-Topolgy Routing (MTR).";		"Support Multiple-Topolgy Routing (MTR).";
	reference "RFC 4915 - Multi-Topology Routing";		reference "RFC 4915 - Multi-Topology Routing";
	skipping to change at page 59, line 23 ¶		skipping to change at page 59, line 41 ¶
	container lfa {		container lfa {
	if-feature lfa;		if-feature lfa;
	description		description
	"This container may be augmented with		"This container may be augmented with
	global parameters for Loop-Free Alternatives (LFA).		global parameters for Loop-Free Alternatives (LFA).
	Container creation has no effect on LFA activation.";		Container creation has no effect on LFA activation.";
	}		}
	}		}
	}		}
			grouping instance-fast-reroute-state {
			description "IPFRR state data grouping";
			container protected-routes {
			config false;
			description "Instance protection statistics";
			list af-stats {
			key "af prefix alternate";
			description "Per AF protected prefix information";
			leaf af {
			type iana-rt-types:address-family;
			description
			"Address-family";
			}
			leaf prefix {
			type string;
			description
			"Protected prefix.";
			}
			leaf alternate {
			type string;
			description
			"Alternate nexthop for the prefix.";
			}
			leaf alternate-type {
			type enumeration {
			enum equal-cost {
			description
			"ECMP alternate.";
			}
			enum lfa {
			description
			"LFA alternate.";
			}
			enum remote-lfa {
			description
			"Remote LFA alternate.";
			}
			enum tunnel {
			description
			"Tunnel based alternate
			(like RSVP-TE or GRE).";
			}
			enum ti-lfa {
			description
			"TI-LFA alternate.";
			}
			enum mrt {
			description
			"MRT alternate.";
			}
			enum other {
			description
			"Unknown alternate type.";
			}
			}
			description
			"Type of alternate.";
			}
			leaf best {
			type boolean;
			description
			"Indicates if the alternate is the preferred.";
			}
			leaf non-best-reason {
			type string;
			description
			"Information field to describe why the alternate
			is not best.";
			}
			leaf protection-available {
			type bits {
			bit node-protect {
			position 0;
			description
			"Node protection available.";
			}
			bit link-protect {
			position 1;
			description
			"Link protection available.";
			}
			bit srlg-protect {
			position 2;
			description
			"SRLG protection available.";
			}
			bit downstream-protect {
			position 3;
			description
			"Downstream protection available.";
			}
			bit other {
			position 4;
			description
			"Other protection available.";
			}
			}
			description "Protection provided by the alternate.";
			}
			leaf alternate-metric1 {
			type uint32;
			description
			"Metric from Point of Local Repair (PLR) to
			destination through the alternate path.";
			}
			leaf alternate-metric2 {
			type uint32;
			description
			"Metric from PLR to the alternate node";
			}
			leaf alternate-metric3 {
			type uint32;
			description
			"Metric from alternate node to the destination";
			}
			}
			}
			container unprotected-routes {
			config false;
			description "List of prefixes that are not protected";
			list af-stats {
			key "af prefix";
			description "Per AF unprotected prefix statistics.";
			leaf af {
			type iana-rt-types:address-family;
			description "Address-family";
			}
			leaf prefix {
			type string;
			description "Unprotected prefix.";
			}
			}
			}
			list protection-statistics {
			key frr-protection-method;
			config false;
			description "List protection method statistics";
			leaf frr-protection-method {
			type string;
			description "Protection method used.";
			}
			list af-stats {
			key af;
			description "Per AF protection statistics.";
			leaf af {
			type iana-rt-types:address-family;
			description "Address-family";
			}
			leaf total-routes {
			type uint32;
			description "Total prefixes.";
			}
			leaf unprotected-routes {
			type uint32;
			description
			"Total prefixes that are not protected.";
			}
			leaf protected-routes {
			type uint32;
			description
			"Total prefixes that are protected.";
			}
			leaf linkprotected-routes {
			type uint32;
			description
			"Total prefixes that are link protected.";
			}
			leaf nodeprotected-routes {
			type uint32;
			description
			"Total prefixes that are node protected.";
			}
			}
			}
			}
	grouping interface-fast-reroute-config {		grouping interface-fast-reroute-config {
	description		description
	"This group defines interface configuration of IP-FRR.";		"This group defines interface configuration of IP-FRR.";
	container fast-reroute {		container fast-reroute {
	if-feature fast-reroute;		if-feature fast-reroute;
	container lfa {		container lfa {
	if-feature lfa;		if-feature lfa;
	leaf candidate-enable {		leaf candidate-enable {
	type boolean;		type boolean;
	default true;		default true;
	skipping to change at page 74, line 10 ¶		skipping to change at page 78, line 18 ¶
	description "Route type for this route.";		description "Route type for this route.";
	}		}
	leaf route-tag {		leaf route-tag {
	type uint32;		type uint32;
	description "Route tag for this route.";		description "Route tag for this route.";
	}		}
	}		}
	}		}
	}		}
	grouping ietf-spf-delay-config {		grouping ietf-spf-delay {
	leaf initial-delay {		leaf initial-delay {
	type uint16;		type uint16;
	units msec;		units msec;
	description		description
	"Delay used while in QUIET state (milliseconds).";		"Delay used while in QUIET state (milliseconds).";
	}		}
	leaf short-delay {		leaf short-delay {
	type uint16;		type uint16;
	units msec;		units msec;
	description		description
	skipping to change at page 74, line 43 ¶		skipping to change at page 78, line 51 ¶
	"Timer used to consider an IGP stability period		"Timer used to consider an IGP stability period
	(milliseconds).";		(milliseconds).";
	}		}
	leaf time-to-learn {		leaf time-to-learn {
	type uint16;		type uint16;
	units msec;		units msec;
	description		description
	"Duration used to learn all the IGP events		"Duration used to learn all the IGP events
	related to a single component failure (milliseconds).";		related to a single component failure (milliseconds).";
	}		}
	description
	"Grouping for IETF SPF delay configuration.";
	}
	grouping ietf-spf-delay-state {
	leaf current-state {		leaf current-state {
	type enumeration {		type enumeration {
	enum "quiet" {		enum "quiet" {
	description "QUIET state";		description "QUIET state";
	}		}
	enum "short-wait" {		enum "short-wait" {
	description "SHORT_WAIT state";		description "SHORT_WAIT state";
	}		}
	enum "long-wait" {		enum "long-wait" {
	description "LONG_WAIT state";		description "LONG_WAIT state";
	}		}
	}		}
	config false;		config false;
	description		description
	skipping to change at page 75, line 50 ¶		skipping to change at page 80, line 4 ¶
	description		description
	"Time when next SPF has been scheduled.";		"Time when next SPF has been scheduled.";
	}		}
	leaf last-spf-time {		leaf last-spf-time {
	type yang:timestamp;		type yang:timestamp;
	config false;		config false;
	description		description
	"Time of last SPF computation.";		"Time of last SPF computation.";
	}		}
	description		description
	"Grouping for IETF SPF backoff operational states.";		"Grouping for IETF SPF delay configuration and state";
	}		}
	grouping node-tag-config {		grouping node-tag-config {
	description		description
	"OSPF node tag config state.";		"OSPF node tag config state.";
	container node-tags {		container node-tags {
	if-feature node-tag;		if-feature node-tag;
	list node-tag {		list node-tag {
	key tag;		key tag;
	leaf tag {		leaf tag {
	type uint32;		type uint32;
	description		description
	skipping to change at page 79, line 33 ¶		skipping to change at page 83, line 35 ¶
	leaf paths {		leaf paths {
	if-feature max-ecmp;		if-feature max-ecmp;
	type uint16 {		type uint16 {
	range "1..32";		range "1..32";
	}		}
	description		description
	"Maximum number of Equal-Cost Multi-Path (ECMP) paths.";		"Maximum number of Equal-Cost Multi-Path (ECMP) paths.";
	}		}
	container ietf-spf-delay {		container ietf-spf-delay {
	if-feature ietf-spf-delay;		if-feature ietf-spf-delay;
	uses ietf-spf-delay-config;		uses ietf-spf-delay;
	description		description
	"IETF SPF delay algorithm configuration.";		"IETF SPF delay algorithm configuration.";
	}		}
	description "SPF calculation control.";		description "SPF calculation control.";
	}		}
	container database-control {		container database-control {
	leaf max-lsa {		leaf max-lsa {
	if-feature max-lsa;		if-feature max-lsa;
	type uint32 {		type uint32 {
	skipping to change at page 80, line 49 ¶		skipping to change at page 85, line 4 ¶
	}		}
	container ldp {		container ldp {
	description		description
	"OSPF MPLS LDP config state.";		"OSPF MPLS LDP config state.";
	leaf igp-sync {		leaf igp-sync {
	if-feature ldp-igp-sync;		if-feature ldp-igp-sync;
	type boolean;		type boolean;
	description		description
	"Enable LDP IGP synchronization.";		"Enable LDP IGP synchronization.";
	}		}
	}		}
	}		}
	uses instance-fast-reroute-config;		uses instance-fast-reroute-config;
			uses instance-fast-reroute-state;
	uses node-tag-config;		uses node-tag-config;
	}		}
	grouping instance-state {		grouping instance-state {
	description		description
	"OSPF instance operational state.";		"OSPF instance operational state.";
	leaf router-id {		leaf router-id {
	type rt-types:router-id;		type rt-types:router-id;
	config false;		config false;
	skipping to change at page 81, line 27 ¶		skipping to change at page 85, line 32 ¶
	}		}
	uses local-rib;		uses local-rib;
	container statistics {		container statistics {
	config false;		config false;
	description "Per-instance statistics";		description "Per-instance statistics";
	uses instance-stat;		uses instance-stat;
	}		}
	container ietf-spf-delay {
	if-feature ietf-spf-delay;
	config false;
	uses ietf-spf-delay-state;
	description
	"IETF SPF delay state.";
	}
	container database {		container database {
	config false;		config false;
	description "AS-scope LSA database.";		description "AS-scope LSA database.";
	list as-scope-lsa-type {		list as-scope-lsa-type {
	key "lsa-type";		key "lsa-type";
	description "List OSPF AS-scope LSA databases.";		description "List OSPF AS-scope LSA databases.";
	leaf lsa-type {		leaf lsa-type {
	type uint16;		type uint16;
	description "OSPF AS scope LSA type.";		description "OSPF AS scope LSA type.";
	}		}
	skipping to change at page 102, line 23 ¶		skipping to change at page 106, line 18 ¶
	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.
	7. Normative References		7. Normative References
	[I-D.ietf-bfd-yang]		[I-D.ietf-bfd-yang]
	Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and		Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and
	G. Mirsky, "YANG Data Model for Bidirectional Forwarding		G. Mirsky, "YANG Data Model for Bidirectional Forwarding
	Detection (BFD)", draft-ietf-bfd-yang-13 (work in		Detection (BFD)", draft-ietf-bfd-yang-16 (work in
	progress), March 2018.		progress), June 2018.
	[I-D.ietf-rtgwg-backoff-algo]
	Decraene, B., Litkowski, S., Gredler, H., Lindem, A.,
	Francois, P., and C. Bowers, "SPF Back-off Delay algorithm
	for link state IGPs", draft-ietf-rtgwg-backoff-algo-10
	(work in progress), March 2018.
	[RFC0905] "ISO Transport Protocol specification ISO DP 8073",		[RFC0905] "ISO Transport Protocol specification ISO DP 8073",
	RFC 905, DOI 10.17487/RFC0905, April 1984,		RFC 905, DOI 10.17487/RFC0905, April 1984,
	<https://www.rfc-editor.org/info/rfc905>.		<https://www.rfc-editor.org/info/rfc905>.
	[RFC1765] Moy, J., "OSPF Database Overflow", RFC 1765,		[RFC1765] Moy, J., "OSPF Database Overflow", RFC 1765,
	DOI 10.17487/RFC1765, March 1995,		DOI 10.17487/RFC1765, March 1995, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc1765>.		editor.org/info/rfc1765>.
	[RFC1793] Moy, J., "Extending OSPF to Support Demand Circuits",		[RFC1793] Moy, J., "Extending OSPF to Support Demand Circuits",
	RFC 1793, DOI 10.17487/RFC1793, April 1995,		RFC 1793, DOI 10.17487/RFC1793, April 1995,
	<https://www.rfc-editor.org/info/rfc1793>.		<https://www.rfc-editor.org/info/rfc1793>.
	[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-
	<https://www.rfc-editor.org/info/rfc2119>.		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-
	<https://www.rfc-editor.org/info/rfc2328>.		editor.org/info/rfc2328>.
	[RFC3101] Murphy, P., "The OSPF Not-So-Stubby Area (NSSA) Option",		[RFC3101] Murphy, P., "The OSPF Not-So-Stubby Area (NSSA) Option",
	RFC 3101, DOI 10.17487/RFC3101, January 2003,		RFC 3101, DOI 10.17487/RFC3101, January 2003,
	<https://www.rfc-editor.org/info/rfc3101>.		<https://www.rfc-editor.org/info/rfc3101>.
	[RFC3623] Moy, J., Pillay-Esnault, P., and A. Lindem, "Graceful OSPF		[RFC3623] Moy, J., Pillay-Esnault, P., and A. Lindem, "Graceful OSPF
	Restart", RFC 3623, DOI 10.17487/RFC3623, November 2003,		Restart", RFC 3623, DOI 10.17487/RFC3623, November 2003,
	<https://www.rfc-editor.org/info/rfc3623>.		<https://www.rfc-editor.org/info/rfc3623>.
	[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering		[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
	(TE) Extensions to OSPF Version 2", RFC 3630,		(TE) Extensions to OSPF Version 2", RFC 3630,
	DOI 10.17487/RFC3630, September 2003,		DOI 10.17487/RFC3630, September 2003, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc3630>.		editor.org/info/rfc3630>.
	[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-
	<https://www.rfc-editor.org/info/rfc3688>.		editor.org/info/rfc3688>.
	[RFC4552] Gupta, M. and N. Melam, "Authentication/Confidentiality		[RFC4552] Gupta, M. and N. Melam, "Authentication/Confidentiality
	for OSPFv3", RFC 4552, DOI 10.17487/RFC4552, June 2006,		for OSPFv3", RFC 4552, DOI 10.17487/RFC4552, June 2006,
	<https://www.rfc-editor.org/info/rfc4552>.		<https://www.rfc-editor.org/info/rfc4552>.
	[RFC4576] Rosen, E., Psenak, P., and P. Pillay-Esnault, "Using a		[RFC4576] Rosen, E., Psenak, P., and P. Pillay-Esnault, "Using a
	Link State Advertisement (LSA) Options Bit to Prevent		Link State Advertisement (LSA) Options Bit to Prevent
	Looping in BGP/MPLS IP Virtual Private Networks (VPNs)",		Looping in BGP/MPLS IP Virtual Private Networks (VPNs)",
	RFC 4576, DOI 10.17487/RFC4576, June 2006,		RFC 4576, DOI 10.17487/RFC4576, June 2006,
	<https://www.rfc-editor.org/info/rfc4576>.		<https://www.rfc-editor.org/info/rfc4576>.
	skipping to change at page 104, line 7 ¶		skipping to change at page 107, line 46 ¶
	RFC 4915, DOI 10.17487/RFC4915, June 2007,		RFC 4915, DOI 10.17487/RFC4915, June 2007,
	<https://www.rfc-editor.org/info/rfc4915>.		<https://www.rfc-editor.org/info/rfc4915>.
	[RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., Ed., and C.		[RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., Ed., and C.
	Pignataro, "The Generalized TTL Security Mechanism		Pignataro, "The Generalized TTL Security Mechanism
	(GTSM)", RFC 5082, DOI 10.17487/RFC5082, October 2007,		(GTSM)", RFC 5082, DOI 10.17487/RFC5082, October 2007,
	<https://www.rfc-editor.org/info/rfc5082>.		<https://www.rfc-editor.org/info/rfc5082>.
	[RFC5185] Mirtorabi, S., Psenak, P., Lindem, A., Ed., and A. Oswal,		[RFC5185] Mirtorabi, S., Psenak, P., Lindem, A., Ed., and A. Oswal,
	"OSPF Multi-Area Adjacency", RFC 5185,		"OSPF Multi-Area Adjacency", RFC 5185,
	DOI 10.17487/RFC5185, May 2008,		DOI 10.17487/RFC5185, May 2008, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc5185>.		editor.org/info/rfc5185>.
	[RFC5187] Pillay-Esnault, P. and A. Lindem, "OSPFv3 Graceful		[RFC5187] Pillay-Esnault, P. and A. Lindem, "OSPFv3 Graceful
	Restart", RFC 5187, DOI 10.17487/RFC5187, June 2008,		Restart", RFC 5187, DOI 10.17487/RFC5187, June 2008,
	<https://www.rfc-editor.org/info/rfc5187>.		<https://www.rfc-editor.org/info/rfc5187>.
	[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-
	<https://www.rfc-editor.org/info/rfc5246>.		editor.org/info/rfc5246>.
	[RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The		[RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The
	OSPF Opaque LSA Option", RFC 5250, DOI 10.17487/RFC5250,		OSPF Opaque LSA Option", RFC 5250, DOI 10.17487/RFC5250,
	July 2008, <https://www.rfc-editor.org/info/rfc5250>.		July 2008, <https://www.rfc-editor.org/info/rfc5250>.
	[RFC5286] Atlas, A., Ed. and A. Zinin, Ed., "Basic Specification for		[RFC5286] Atlas, A., Ed. and A. Zinin, Ed., "Basic Specification for
	IP Fast Reroute: Loop-Free Alternates", RFC 5286,		IP Fast Reroute: Loop-Free Alternates", RFC 5286,
	DOI 10.17487/RFC5286, September 2008,		DOI 10.17487/RFC5286, September 2008, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc5286>.		editor.org/info/rfc5286>.
	[RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed.,		[RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed.,
	"Traffic Engineering Extensions to OSPF Version 3",		"Traffic Engineering Extensions to OSPF Version 3",
	RFC 5329, DOI 10.17487/RFC5329, September 2008,		RFC 5329, DOI 10.17487/RFC5329, September 2008,
	<https://www.rfc-editor.org/info/rfc5329>.		<https://www.rfc-editor.org/info/rfc5329>.
	[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>.
	[RFC5443] Jork, M., Atlas, A., and L. Fang, "LDP IGP		[RFC5443] Jork, M., Atlas, A., and L. Fang, "LDP IGP
	Synchronization", RFC 5443, DOI 10.17487/RFC5443, March		Synchronization", RFC 5443, DOI 10.17487/RFC5443, March
	2009, <https://www.rfc-editor.org/info/rfc5443>.		2009, <https://www.rfc-editor.org/info/rfc5443>.
	[RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D.		[RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D.
	Yeung, "OSPF Link-Local Signaling", RFC 5613,		Yeung, "OSPF Link-Local Signaling", RFC 5613,
	DOI 10.17487/RFC5613, August 2009,		DOI 10.17487/RFC5613, August 2009, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc5613>.		editor.org/info/rfc5613>.
	[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>.
	[RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework",		[RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework",
	RFC 5714, DOI 10.17487/RFC5714, January 2010,		RFC 5714, DOI 10.17487/RFC5714, January 2010,
	<https://www.rfc-editor.org/info/rfc5714>.		<https://www.rfc-editor.org/info/rfc5714>.
	[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		[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
	(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,		(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
	<https://www.rfc-editor.org/info/rfc5880>.		<https://www.rfc-editor.org/info/rfc5880>.
	[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection		[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
	(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881,		(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881,
	DOI 10.17487/RFC5881, June 2010,		DOI 10.17487/RFC5881, June 2010, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc5881>.		editor.org/info/rfc5881>.
	[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-
	<https://www.rfc-editor.org/info/rfc6020>.		editor.org/info/rfc6020>.
	[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types",		[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types",
	RFC 6021, DOI 10.17487/RFC6021, October 2010,		RFC 6021, DOI 10.17487/RFC6021, October 2010,
	<https://www.rfc-editor.org/info/rfc6021>.		<https://www.rfc-editor.org/info/rfc6021>.
	[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>.
	[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure		[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
	Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,		Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
	<https://www.rfc-editor.org/info/rfc6242>.		<https://www.rfc-editor.org/info/rfc6242>.
	[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration		[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
	Protocol (NETCONF) Access Control Model", RFC 6536,		Protocol (NETCONF) Access Control Model", RFC 6536,
	DOI 10.17487/RFC6536, March 2012,		DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc6536>.		editor.org/info/rfc6536>.
	[RFC6565] Pillay-Esnault, P., Moyer, P., Doyle, J., Ertekin, E., and		[RFC6565] Pillay-Esnault, P., Moyer, P., Doyle, J., Ertekin, E., and
	M. Lundberg, "OSPFv3 as a Provider Edge to Customer Edge		M. Lundberg, "OSPFv3 as a Provider Edge to Customer Edge
	(PE-CE) Routing Protocol", RFC 6565, DOI 10.17487/RFC6565,		(PE-CE) Routing Protocol", RFC 6565, DOI 10.17487/RFC6565,
	June 2012, <https://www.rfc-editor.org/info/rfc6565>.		June 2012, <https://www.rfc-editor.org/info/rfc6565>.
	[RFC6860] Yang, Y., Retana, A., and A. Roy, "Hiding Transit-Only		[RFC6860] Yang, Y., Retana, A., and A. Roy, "Hiding Transit-Only
	Networks in OSPF", RFC 6860, DOI 10.17487/RFC6860, January		Networks in OSPF", RFC 6860, DOI 10.17487/RFC6860, January
	2013, <https://www.rfc-editor.org/info/rfc6860>.		2013, <https://www.rfc-editor.org/info/rfc6860>.
	[RFC6987] Retana, A., Nguyen, L., Zinin, A., White, R., and D.		[RFC6987] Retana, A., Nguyen, L., Zinin, A., White, R., and D.
	McPherson, "OSPF Stub Router Advertisement", RFC 6987,		McPherson, "OSPF Stub Router Advertisement", RFC 6987,
	DOI 10.17487/RFC6987, September 2013,		DOI 10.17487/RFC6987, September 2013, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc6987>.		editor.org/info/rfc6987>.
	[RFC7490] Bryant, S., Filsfils, C., Previdi, S., Shand, M., and N.		[RFC7490] Bryant, S., Filsfils, C., Previdi, S., Shand, M., and N.
	So, "Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)",		So, "Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)",
	RFC 7490, DOI 10.17487/RFC7490, April 2015,		RFC 7490, DOI 10.17487/RFC7490, April 2015,
	<https://www.rfc-editor.org/info/rfc7490>.		<https://www.rfc-editor.org/info/rfc7490>.
	[RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W.,		[RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W.,
	Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute		Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute
	Advertisement", RFC 7684, DOI 10.17487/RFC7684, November		Advertisement", RFC 7684, DOI 10.17487/RFC7684, November
	2015, <https://www.rfc-editor.org/info/rfc7684>.		2015, <https://www.rfc-editor.org/info/rfc7684>.
	skipping to change at page 106, line 40 ¶		skipping to change at page 110, line 30 ¶
	[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF		[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
	Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,		Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
	<https://www.rfc-editor.org/info/rfc8040>.		<https://www.rfc-editor.org/info/rfc8040>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J.		[RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J.
	Zhang, "YANG Data Model for Key Chains", RFC 8177,		Zhang, "YANG Data Model for Key Chains", RFC 8177,
	DOI 10.17487/RFC8177, June 2017,		DOI 10.17487/RFC8177, June 2017, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc8177>.		editor.org/info/rfc8177>.
	[RFC8291] Thomson, M., "Message Encryption for Web Push", RFC 8291,		[RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
	DOI 10.17487/RFC8291, November 2017,		"Common YANG Data Types for the Routing Area", RFC 8294,
	<https://www.rfc-editor.org/info/rfc8291>.		DOI 10.17487/RFC8294, December 2017, <https://www.rfc-
			editor.org/info/rfc8294>.
	[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,		[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
	and R. Wilton, "Network Management Datastore Architecture		and R. Wilton, "Network Management Datastore Architecture
	(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,		(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
	<https://www.rfc-editor.org/info/rfc8342>.		<https://www.rfc-editor.org/info/rfc8342>.
	[RFC8343] Bjorklund, M., "A YANG Data Model for Interface		[RFC8343] Bjorklund, M., "A YANG Data Model for Interface
	Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,		Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
	<https://www.rfc-editor.org/info/rfc8343>.		<https://www.rfc-editor.org/info/rfc8343>.
	[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for		[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
	Routing Management (NMDA Version)", RFC 8349,		Routing Management (NMDA Version)", RFC 8349,
	DOI 10.17487/RFC8349, March 2018,		DOI 10.17487/RFC8349, March 2018, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc8349>.		editor.org/info/rfc8349>.
			[RFC8405] Decraene, B., Litkowski, S., Gredler, H., Lindem, A.,
			Francois, P., and C. Bowers, "Shortest Path First (SPF)
			Back-Off Delay Algorithm for Link-State IGPs", RFC 8405,
			DOI 10.17487/RFC8405, June 2018, <https://www.rfc-
			editor.org/info/rfc8405>.
	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
End of changes. 44 change blocks.
	91 lines changed or deleted		286 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/