Diff: draft-acee-lsr-isis-yang-augmentation-v1-03.txt - draft-acee-lsr-isis-yang-augmentation-v1-04.txt

	< draft-acee-lsr-isis-yang-augmentation-v1-03.txt	draft-acee-lsr-isis-yang-augmentation-v1-04.txt >

	Internet A. Lindem	Internet A. Lindem
	Internet-Draft S. Litkowski	Internet-Draft S. Litkowski

	Intended status: Informational Cisco Systems	Intended status: Standards Track Cisco Systems
	Expires: May 2, 2021 Y. Qu	Expires: July 9, 2021 Y. Qu
	Futurewei	Futurewei

	October 29, 2020	January 5, 2021

	IS-IS YANG Model Augmentations for Additional Features - Version 1	IS-IS YANG Model Augmentations for Additional Features - Version 1

	draft-acee-lsr-isis-yang-augmentation-v1-03	draft-acee-lsr-isis-yang-augmentation-v1-04

	Abstract	Abstract

	This document defines YANG data modules augmenting the IETF IS-IS	This document defines YANG data modules augmenting the IETF IS-IS
	YANG model to provide support for IS-IS Minimum Remaining Lifetime as	YANG model to provide support for IS-IS Minimum Remaining Lifetime as

	defined in RFC 7987.	defined in RFC 7987, and IS-IS Application-Specific Link Attributes
		as defined in RFC 8919.

	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 May 2, 2021.	This Internet-Draft will expire on July 9, 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
	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 . . . . . . . . . . . . . . . . . . 2	1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2

	2. YANG Module for IS-IS Minimum Remaining Lifetime . . . . . . 2	1.2. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 3
		2. YANG Module for IS-IS Minimum Remaining Lifetime . . . . . . 3
	3. YANG Module for IS-IS Application-Specific Link Attributes . 4	3. YANG Module for IS-IS Application-Specific Link Attributes . 4

	4. Security Considerations . . . . . . . . . . . . . . . . . . . 13	4. Security Considerations . . . . . . . . . . . . . . . . . . . 14
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
	6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14	6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
	7.1. Normative References . . . . . . . . . . . . . . . . . . 14	7.1. Normative References . . . . . . . . . . . . . . . . . . 15
	7.2. Informative References . . . . . . . . . . . . . . . . . 16	7.2. Informative References . . . . . . . . . . . . . . . . . 17
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17

	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 IS-IS	This document defines YANG data modules augmenting the IETF IS-IS
	YANG model [I-D.ietf-isis-yang-isis-cfg], which itself augments	YANG model [I-D.ietf-isis-yang-isis-cfg], which itself augments
	[RFC8349], to provide support for configuration and operational state	[RFC8349], to provide support for configuration and operational state
	for the following IS-IS features:	for the following IS-IS features:

	RFC7987: IS-IS Minimum Remaining Lifetime[RFC7987].	RFC7987: IS-IS Minimum Remaining Lifetime[RFC7987].


		RFC8919: IS-IS Application-Specific Link Attributes[RFC8919].

	The augmentations defined in this document requires support for the	The augmentations defined in this document requires support for the
	IS-IS base model[I-D.ietf-isis-yang-isis-cfg] which defines basic IS-	IS-IS base model[I-D.ietf-isis-yang-isis-cfg] which defines basic IS-
	IS configuration and state. The IS-IS YANG model augments the ietf-	IS configuration and state. The IS-IS YANG model augments the ietf-

	routing YANG model defined in [RFC8022].	routing YANG model defined in [RFC8349].

	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", "NOT RECOMMENDED", "MAY", and
	document are to be interpreted as described in [RFC2119].	"OPTIONAL" in this document are to be interpreted as described in BCP
		14 [RFC2119] [RFC8174] when, and only when, they appear in all
		capitals, as shown here.

		1.2. Tree diagram

		Tree diagrams used in this document follow the notation defined in
		[RFC8340].

	2. YANG Module for IS-IS Minimum Remaining Lifetime	2. YANG Module for IS-IS Minimum Remaining Lifetime

	This document defines a YANG module for IS-IS Minimum Remaining	This document defines a YANG module for IS-IS Minimum Remaining
	Lifetime as defined in [RFC7987]. It is an augmentation of the IS-IS	Lifetime as defined in [RFC7987]. It is an augmentation of the IS-IS
	base model.	base model.

	module: ietf-isis-remaining-lifetime	module: ietf-isis-remaining-lifetime

	notifications:	notifications:
	+---n corrupt-remaining-lifetime	+---n corrupt-remaining-lifetime
	+--ro routing-protocol-name? -> /rt:routing	+--ro routing-protocol-name? -> /rt:routing
	/control-plane-protocols	/control-plane-protocols
	/control-plane-protocol/name	/control-plane-protocol/name
	+--ro isis-level? level	+--ro isis-level? level
	+--ro lsp-id? isis:lsp-id	+--ro lsp-id? isis:lsp-id


	<CODE BEGINS> file "ietf-isis-remaining-lifetime@2020-05-06.yang"	<CODE BEGINS> file "ietf-isis-remaining-lifetime@2021-01-05.yang"
	module ietf-isis-remaining-lifetime {	module ietf-isis-remaining-lifetime {
	yang-version 1.1;	yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime";	namespace "urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime";

	prefix isis-remaining-lifetime;	prefix isis-remaining-lifetime;

	import ietf-isis {	import ietf-isis {
	prefix "isis";	prefix "isis";
	}	}

	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:yingzhen.qu@futurewei.com>	<mailto:yqu@futurewei.com>
	Author: Acee Lindem	Author: Acee Lindem
	<mailto:acee@cisco.com>	<mailto:acee@cisco.com>
	Author: Stephane Litkowski	Author: Stephane Litkowski
	<mailto:slitkows.ietf@gmail.com>";	<mailto:slitkows.ietf@gmail.com>";

	description	description
	"This YANG module defines the configuration and operational	"This YANG module defines the configuration and operational

	state for IS-IS Minimum Remaining Lifetime feature as defined	state for IS-IS Minimum Remaining Lifetime feature as defined
	in RFC 7987.	in RFC 7987.


	Copyright (c) 2019 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	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.";

	reference "RFC XXXX";	reference "RFC XXXX";


	revision 2020-05-06 {	revision 2021-01-05 {
	description	description
	"Initial version";	"Initial version";
	reference	reference
	"RFC XXXX: A YANG Data Model for IS-IS.";	"RFC XXXX: A YANG Data Model for IS-IS.";
	}	}

	notification corrupt-remaining-lifetime {	notification corrupt-remaining-lifetime {
	uses isis:notification-instance-hdr;	uses isis:notification-instance-hdr;
	leaf lsp-id {	leaf lsp-id {
	type isis:lsp-id;	type isis:lsp-id;
	description "LSP ID";	description "LSP ID";
	}	}
	description	description
	"This notification is sent when the system	"This notification is sent when the system
	detects correpted lifetime of an LSP.";	detects correpted lifetime of an LSP.";

		reference "RFC 7987: IS-IS Minimum Remaining Lifetime";
	}	}
	}	}
	<CODE ENDS>	<CODE ENDS>

	3. YANG Module for IS-IS Application-Specific Link Attributes	3. YANG Module for IS-IS Application-Specific Link Attributes

	This document defines a YANG module for IS-IS Application-Specific	This document defines a YANG module for IS-IS Application-Specific

	Link Attributes [I-D.ietf-isis-te-app]. It is an augmentation of the	Link Attributes [RFC8919]. It is an augmentation of the IS-IS base
	IS-IS base model.	model.

	module: ietf-isis-link-attr	module: ietf-isis-link-attr
	augment /rt:routing/rt:control-plane-protocols	augment /rt:routing/rt:control-plane-protocols
	/rt:control-plane-protocol/isis:isis/isis:interfaces	/rt:control-plane-protocol/isis:isis/isis:interfaces
	/isis:interface:	/isis:interface:
	+--rw isis-link-attr	+--rw isis-link-attr
	+--rw (link-attr-op-mode)	+--rw (link-attr-op-mode)
	+--:(legacy)	+--:(legacy)
	\| +--rw legacy? empty	\| +--rw legacy? empty
	+--:(transition)	+--:(transition)

	skipping to change at page 6, line 20 ¶	skipping to change at page 6, line 35 ¶
	\| \| +--ro ipv4-int-addr? inet:ipv4-address	\| \| +--ro ipv4-int-addr? inet:ipv4-address
	\| +--ro ipv4-neighbor-addr	\| +--ro ipv4-neighbor-addr
	\| \| +--ro ipv4-neighbor-addr? inet:ipv4-address	\| \| +--ro ipv4-neighbor-addr? inet:ipv4-address
	\| +--ro ipv6-interface-addr	\| +--ro ipv6-interface-addr
	\| \| +--ro ipv6-int-addr? inet:ipv6-address	\| \| +--ro ipv6-int-addr? inet:ipv6-address
	\| +--ro ipv6-neighbor-addr	\| +--ro ipv6-neighbor-addr
	\| +--ro ipv6-neighbor-addr? inet:ipv6-address	\| +--ro ipv6-neighbor-addr? inet:ipv6-address
	+--ro srlgs	+--ro srlgs
	+--ro srlg* uint32	+--ro srlg* uint32


	<CODE BEGINS> file "ietf-isis-link-attr@2020-10-29.yang"	<CODE BEGINS> file "ietf-isis-link-attr@2021-01-05.yang"
	module ietf-isis-link-attr {	module ietf-isis-link-attr {
	yang-version 1.1;	yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-isis-link-attr";	namespace "urn:ietf:params:xml:ns:yang:ietf-isis-link-attr";

	prefix isis-link-attr;	prefix isis-link-attr;

	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 6, line 38 ¶	skipping to change at page 7, line 4 ¶
	prefix inet;	prefix inet;
	reference "RFC 6991 - Common YANG Data Types";	reference "RFC 6991 - Common YANG Data Types";
	}	}

	import ietf-routing {	import ietf-routing {
	prefix "rt";	prefix "rt";
	}	}

	import ietf-isis {	import ietf-isis {
	prefix "isis";	prefix "isis";


	}	}

	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
	<mailto:acee@cisco.com>	<mailto:acee@cisco.com>
	Author: Stephane Litkowski	Author: Stephane Litkowski
	<mailto:slitkows.ietf@gmail.com>";	<mailto:slitkows.ietf@gmail.com>";

	description	description
	"This YANG module defines the configuration and operational	"This YANG module defines the configuration and operational
	state for IS-IS application specific link attributes feature as	state for IS-IS application specific link attributes feature as

	defined in RFC xxxx.	defined in RFC 8919.

	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	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.

	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.";

	reference "RFC XXXX";	reference "RFC XXXX";


	revision 2020-10-29 {	revision 2021-01-05 {
	description	description
	"Initial version";	"Initial version";


	reference	reference
	"RFC XXXX: A YANG Data Model for IS-IS.";	"RFC XXXX: A YANG Data Model for IS-IS.";
	}	}

	identity sabm-bit {	identity sabm-bit {
	description	description
	"Base identity for sabm bits.";	"Base identity for sabm bits.";

		reference "RFC 8919: IS-IS Application-Specific Link Attributes";
	}	}

	identity rsvp-te-bit {	identity rsvp-te-bit {
	base sabm-bit;	base sabm-bit;
	description	description
	"R bit, RSVP-TE.";	"R bit, RSVP-TE.";
	}	}


	identity sr-policy-bit {	identity sr-policy-bit {
	base sabm-bit;	base sabm-bit;
	description	description
	"S bit, Segment Routing Policy.";	"S bit, Segment Routing Policy.";
	}	}

	identity lfa-bit {	identity lfa-bit {
	base sabm-bit;	base sabm-bit;
	description	description
	"F bit, Loop Free Alternate (LFA). Includes all LFA types.";	"F bit, Loop Free Alternate (LFA). Includes all LFA types.";

	skipping to change at page 14, line 10 ¶	skipping to change at page 14, line 28 ¶
	The NETCONF access control model [RFC6536] provides the means to	The NETCONF access control model [RFC6536] provides the means to
	restrict access for particular NETCONF or RESTCONF users to a pre-	restrict access for particular NETCONF or RESTCONF users to a pre-
	configured subset of all available NETCONF or RESTCONF protocol	configured subset of all available NETCONF or RESTCONF protocol
	operations and content.	operations and content.

	There are a number of data nodes defined in the modules that are	There are a number of data nodes defined in the modules that are
	writable/creatable/deletable (i.e., config true, which is the	writable/creatable/deletable (i.e., config true, which is the
	default). These data nodes may be considered sensitive or vulnerable	default). These data nodes may be considered sensitive or vulnerable
	in some network environments. Write operations (e.g., edit-config)	in some network environments. Write operations (e.g., edit-config)
	to these data nodes without proper protection can have a negative	to these data nodes without proper protection can have a negative

	effect on network operations.	effect on network operations. These correspond to the following
		schema nodes:

		/isis:isis/isis:interfaces/isis:interface/isis-link-attr -
		Modification of link attributes operation mode could result in
		traffic being redirected or DoS attack.

	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.These
		correspond to the following schema nodes:

		/isis:isis/isis:database/isis:levels/isis:lsp/isis:mt-is-
		neighbor/isis:neighbor/isis:instances/isis:instance/application-
		specific-link-attributes-sub-tlvs

		/isis:isis/isis:database/isis:levels/isis:lsp/application-
		specific-srlg-tlv

	5. IANA Considerations	5. 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-isis-remaining-lifetime	URI: urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime
	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-isis-link-attr
		Registrant Contact: The IESG.
		XML: N/A, the requested URI is an XML namespace.

	This document registers the YANG modules in the YANG Module Names	This document registers the YANG modules in the YANG Module Names
	registry [RFC6020].	registry [RFC6020].

	name: ietf-isis-remaining-lifetime	name: ietf-isis-remaining-lifetime
	namespace: urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime	namespace: urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime
	prefix: isis-remaining-lifetime	prefix: isis-remaining-lifetime
	reference: RFC XXXX	reference: RFC XXXX


		name: ietf-isis-link-attr
		namespace: urn:ietf:params:xml:ns:yang:ietf-isis-link-attr
		prefix: isis-link-attr
		reference: RFC XXXX

	6. Acknowledgements	6. 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.

	7. References	7. References

	7.1. Normative References	7.1. Normative References


		[I-D.ietf-isis-yang-isis-cfg]
		Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L.
		Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf-
		isis-yang-isis-cfg-42 (work in progress), October 2019.

	[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

	skipping to change at page 16, line 5 ¶	skipping to change at page 16, line 47 ¶

	[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",	[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
	RFC 7950, DOI 10.17487/RFC7950, August 2016,	RFC 7950, DOI 10.17487/RFC7950, August 2016,
	<https://www.rfc-editor.org/info/rfc7950>.	<https://www.rfc-editor.org/info/rfc7950>.

	[RFC7987] Ginsberg, L., Wells, P., Decraene, B., Przygienda, T., and	[RFC7987] Ginsberg, L., Wells, P., Decraene, B., Przygienda, T., and
	H. Gredler, "IS-IS Minimum Remaining Lifetime", RFC 7987,	H. Gredler, "IS-IS Minimum Remaining Lifetime", RFC 7987,
	DOI 10.17487/RFC7987, October 2016,	DOI 10.17487/RFC7987, October 2016,
	<https://www.rfc-editor.org/info/rfc7987>.	<https://www.rfc-editor.org/info/rfc7987>.


	[RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
	Management", RFC 8022, DOI 10.17487/RFC8022, November
	2016, <https://www.rfc-editor.org/info/rfc8022>.

	[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
		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
		May 2017, <https://www.rfc-editor.org/info/rfc8174>.

	[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-editor.org/info/rfc8349>.	<https://www.rfc-editor.org/info/rfc8349>.


	7.2. Informative References	[RFC8919] Ginsberg, L., Psenak, P., Previdi, S., Henderickx, W., and

	[I-D.ietf-isis-te-app]
	Ginsberg, L., Psenak, P., Previdi, S., Henderickx, W., and
	J. Drake, "IS-IS Application-Specific Link Attributes",	J. Drake, "IS-IS Application-Specific Link Attributes",

	draft-ietf-isis-te-app-19 (work in progress), June 2020.	RFC 8919, DOI 10.17487/RFC8919, October 2020,
		<https://www.rfc-editor.org/info/rfc8919>.


	[I-D.ietf-isis-yang-isis-cfg]	7.2. Informative References
	Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L.
	Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf-	[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
	isis-yang-isis-cfg-42 (work in progress), October 2019.	BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
		<https://www.rfc-editor.org/info/rfc8340>.

	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


End of changes. 36 change blocks.
	45 lines changed or deleted	87 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/