draft-ietf-isis-yang-isis-cfg-34.txt		draft-ietf-isis-yang-isis-cfg-35.txt
	IS-IS Working Group S. Litkowski		IS-IS Working Group S. Litkowski
	Internet-Draft Orange		Internet-Draft Orange
	Intended status: Standards Track D. Yeung		Intended status: Standards Track D. Yeung
	Expires: July 25, 2019 Arrcus, Inc		Expires: September 8, 2019 Arrcus, Inc
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	J. Zhang		J. Zhang
	Juniper Networks		Juniper Networks
	L. Lhotka		L. Lhotka
	CZ.NIC		CZ.NIC
	January 21, 2019		March 7, 2019
	YANG Data Model for IS-IS Protocol		YANG Data Model for IS-IS Protocol
	draft-ietf-isis-yang-isis-cfg-34		draft-ietf-isis-yang-isis-cfg-35
	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 IS-IS protocol on network elements.		and manage IS-IS protocol on network elements.
	Requirements Language		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", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	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 http://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 July 25, 2019.		This Internet-Draft will expire on September 8, 2019.
	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
	(http://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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3		2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3
	2.1. IS-IS Configuration . . . . . . . . . . . . . . . . . . . 9		2.1. IS-IS Configuration . . . . . . . . . . . . . . . . . . . 9
	2.2. Multi-topology Parameters . . . . . . . . . . . . . . . 10		2.2. Multi-topology Parameters . . . . . . . . . . . . . . . 9
	2.3. Per-Level Parameters . . . . . . . . . . . . . . . . . . 10		2.3. Per-Level Parameters . . . . . . . . . . . . . . . . . . 10
	2.4. Per-Interface Parameters . . . . . . . . . . . . . . . . 12		2.4. Per-Interface Parameters . . . . . . . . . . . . . . . . 11
	2.5. Authentication Parameters . . . . . . . . . . . . . . . 19		2.5. Authentication Parameters . . . . . . . . . . . . . . . 19
	2.6. IGP/LDP synchronization . . . . . . . . . . . . . . . . 20		2.6. IGP/LDP synchronization . . . . . . . . . . . . . . . . 19
	2.7. ISO parameters . . . . . . . . . . . . . . . . . . . . . 20		2.7. ISO parameters . . . . . . . . . . . . . . . . . . . . . 19
	2.8. IP FRR . . . . . . . . . . . . . . . . . . . . . . . . . 20		2.8. IP FRR . . . . . . . . . . . . . . . . . . . . . . . . . 19
	2.9. Operational States . . . . . . . . . . . . . . . . . . . 21		2.9. Operational States . . . . . . . . . . . . . . . . . . . 20
	3. RPC Operations . . . . . . . . . . . . . . . . . . . . . . . 21		3. RPC Operations . . . . . . . . . . . . . . . . . . . . . . . 20
	4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 21		4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 20
	5. Interaction with Other YANG Modules . . . . . . . . . . . . 23		5. Interaction with Other YANG Modules . . . . . . . . . . . . 22
	6. IS-IS YANG Module . . . . . . . . . . . . . . . . . . . . . . 23		6. IS-IS YANG Module . . . . . . . . . . . . . . . . . . . . . . 22
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 104		7. Security Considerations . . . . . . . . . . . . . . . . . . . 103
	8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 105		8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 104
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 105		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 104
	10. Change log for ietf-isis YANG module . . . . . . . . . . . . 105		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 104
	10.1. From version -29 to version -30 . . . . . . . . . . . . 105		10.1. Normative References . . . . . . . . . . . . . . . . . . 104
	10.2. From version -28 to version -29 . . . . . . . . . . . . 106		10.2. Informative References . . . . . . . . . . . . . . . . . 108
	10.3. From version -27 to version -28 . . . . . . . . . . . . 106		Appendix A. Example of IS-IS configuration in XML . . . . . . . 108
	10.4. From version -26 to version -27 . . . . . . . . . . . . 106		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 111
	10.5. From version -25 to version -26 . . . . . . . . . . . . 106
	10.6. From version -24 to version -25 . . . . . . . . . . . . 106
	10.7. From version -22 to version -24 . . . . . . . . . . . . 107
	10.8. From version -21 to version -22 . . . . . . . . . . . . 107
	10.9. From version -20 to version -21 . . . . . . . . . . . . 108
	10.10. From version -19 to version -20 . . . . . . . . . . . . 108
	10.11. From version -18 to version -19 . . . . . . . . . . . . 108
	10.12. From version -17 to version -18 . . . . . . . . . . . . 108
	10.13. From version -16 to version -17 . . . . . . . . . . . . 108
	10.14. From version -15 to version -16 . . . . . . . . . . . . 108
	10.15. From version -14 to version -15 . . . . . . . . . . . . 109
	10.16. From version -13 to version -14 . . . . . . . . . . . . 109
	10.17. From version -12 to version -13 . . . . . . . . . . . . 109
	10.18. From version -09 to version -12 . . . . . . . . . . . . 109
	10.19. From version -08 to version -09 . . . . . . . . . . . . 110
	10.20. From version -07 to version -08 . . . . . . . . . . . . 110
	10.21. From version -05 to version -07 . . . . . . . . . . . . 110
	10.22. From version -03 to version -05 . . . . . . . . . . . . 110
	10.23. From version -02 to version -03 . . . . . . . . . . . . 111
	10.24. From version -01 to version -02 . . . . . . . . . . . . 111
	10.25. From version -00 to version -01 . . . . . . . . . . . . 111
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 112
	11.1. Normative References . . . . . . . . . . . . . . . . . . 112
	11.2. Informative References . . . . . . . . . . . . . . . . . 116
	Appendix A. Example of IS-IS configuration in XML . . . . . . . 116
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 118
	1. Introduction		1. Introduction
	This document defines a YANG ([RFC7950]) data model for IS-IS routing		This document defines a YANG ([RFC7950]) data model for IS-IS routing
	protocol.		protocol.
	The data model covers configuration of an IS-IS routing protocol		The data model covers configuration of an IS-IS routing protocol
	instance as well as operational states.		instance as well as operational states.
	A simplified tree representation of the data model is presented in		A simplified tree representation of the data model is presented in
	skipping to change at page 23, line 44 ¶		skipping to change at page 22, line 47 ¶
	[I-D.ietf-bfd-yang].		[I-D.ietf-bfd-yang].
	6. IS-IS YANG Module		6. IS-IS YANG Module
	The following RFCs, drafts and external standards are not referenced		The following RFCs, drafts and external standards are not referenced
	in the document text but are referenced in the ietf-isis.yang module:		in the document text but are referenced in the ietf-isis.yang module:
	[ISO-10589], [RFC1195], [RFC5029], [RFC5130], [RFC5305], [RFC5306],		[ISO-10589], [RFC1195], [RFC5029], [RFC5130], [RFC5305], [RFC5306],
	[RFC5308], [RFC5880], [RFC5881], [RFC6119], [RFC6232], [RFC7794],		[RFC5308], [RFC5880], [RFC5881], [RFC6119], [RFC6232], [RFC7794],
	[RFC7810], [RFC7917], [RFC8405].		[RFC7810], [RFC7917], [RFC8405].
	<CODE BEGINS> file "ietf-ospf@2019-01-24.yang"		<CODE BEGINS> file "ietf-isis@2019-03-07.yang"
	module ietf-isis {		module ietf-isis {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-isis";		namespace "urn:ietf:params:xml:ns:yang:ietf-isis";
	prefix isis;		prefix isis;
	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-inet-types {		import ietf-inet-types {
	prefix inet;		prefix inet;
	skipping to change at page 26, line 18 ¶		skipping to change at page 25, line 20 ¶
	see the RFC itself for full legal notices.		see the RFC itself for full legal notices.
	The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',		The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
	'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',		'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
	'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document		'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
	are to be interpreted as described in BCP 14 [RFC2119]		are to be interpreted as described in BCP 14 [RFC2119]
	[RFC8174] when, and only when, they appear in all capitals,		[RFC8174] when, and only when, they appear in all capitals,
	as shown here.		as shown here.
	";		";
	revision 2019-01-24 {		revision 2019-03-07 {
	description		description
	"Initial revision.";		"Initial revision.";
	reference "RFC XXXX";		reference "RFC XXXX";
	}		}
	/* Identities */		/* Identities */
	identity isis {		identity isis {
	base rt:routing-protocol;		base rt:routing-protocol;
	description "Identity for the IS-IS routing protocol.";		description "Identity for the IS-IS routing protocol.";
	skipping to change at page 105, line 39 ¶		skipping to change at page 104, line 39 ¶
	XML: N/A, the requested URI is an XML namespace		XML: N/A, the requested URI is an XML namespace
	This document also requests one new YANG module name in the YANG		This document also requests one new YANG module name in the YANG
	Module Names registry ([RFC6020]) with the following suggestion:		Module Names registry ([RFC6020]) with the following suggestion:
	name: ietf-isis		name: ietf-isis
	namespace: urn:ietf:params:xml:ns:yang:ietf-isis		namespace: urn:ietf:params:xml:ns:yang:ietf-isis
	prefix: isis		prefix: isis
	reference: RFC XXXX		reference: RFC XXXX
	10. Change log for ietf-isis YANG module		10. References
	10.1. From version -29 to version -30
	o Set a maximum-length of 255 for the non-best-reason leaf.
	o Updated some descriptions.
	o Renamed "level-db" container to "levels" for consistency reasons.
	o Added some RFC references in the YANG model.
	o Leaf default-metric of container prefix-ipv4-std is now a
	container.
	o Changed the description of the authentication and removed the
	reference to MD5 as a possible way to hide the password.
	o Changed leaf type for authentication type within
	tlv10-authentication container. Moved from string to
	keychain:crypto-algorithm identity.
	o Some admin strings are now limited to a range of 1..255.
	o Hostname string in hostname DB is limited to 255 as per RFC5301.
	o In FRR stats, "prefix" is now encoded as inet:ip-prefix rather
	than a string. "alternate" is now encoded as ip-address.
	10.2. From version -28 to version -29
	o Fixed area-address type pattern. The authorized number of bytes
	was wrong.
	10.3. From version -27 to version -28
	o Fixed inaccurate description of level-type leaf.
	10.4. From version -26 to version -27
	o Fixed XPATH to switching-capability leaf in "when" statement of
	psc-specific and tdm-specific containers.
	10.5. From version -25 to version -26
	o Modify BFD reference descriptions.
	o Fix indentation.
	o "uses interface-state" was missing.
	10.6. From version -24 to version -25
	o RPC clear-adjacency uses now an interface reference instead of a
	string.
	o Use expanded "address-family" rather than "af" in the model.
	o Fix pattern for area-address.
	o Removed unnecessary identities.
	o Added an instances container and list in the modeling of neighbors
	in the LSDB. This is to manage the case where there are parallel
	links between two neighbors.
	o Notification instance header: removed routing-instance leaf
	(alignment with OSPF).
	o Notification instance header: changed routing-protocol-name to a
	reference.
	o Notification interface header: changed interface to a reference.
	o RPCs: changed instance-state-ref typedef to a leafref. Removed
	associated typedef.
	o Revised some groupings and their names (alignment with OSPF).
	o Some description alignment with OSPF.
	o auto-cost container alignment with OSPF.
	o MT-ID leaf in database description renamed (lower-case) mt-id.
	o In the lsp-log grouping, leaf change is renamed reason to align
	with OSPF.
	o Added some link attributes (GMPLS, TE, extended TE, SRLGs) in the
	LSDB.
	o Added extended-system-id typedef which contains the system-id plus
	the pseudonode number.
	o Add support of POI Purge Originator Identification.
	10.7. From version -22 to version -24
	o Fix revision date of the module.
	10.8. From version -21 to version -22
	o TE router-id modeling alignment with OSPF.
	o Add max-ecmp + feature in spf-control container (alignment with
	OSPF).
	10.9. From version -20 to version -21
	o Model revision date fix
	10.10. From version -19 to version -20
	o Moved to Yang 1.1
	o Lower case enumerations
	o Add RFC references to features
	o Remove segment-routing feature
	o Modified BFD activation modeling
	10.11. From version -18 to version -19
	o Align with draft-ietf-netmod-rfc8022bis.
	o Modify address family types as per draft-ietf-rtgwg-routing-types-
	17.
	10.12. From version -17 to version -18
	o NMDA compliancy.
	o Set some default values.
	o Align with iana-rt-types module.
	10.13. From version -16 to version -17
	o Cosmetic fixes.
	o Use of rt-types model.
	10.14. From version -15 to version -16
	o Alignment with last IETF key chain model.
	o lsp-log "change" leaf moved as an identity.
	o Incremental SPF removed from spf-log types.
	10.15. From version -14 to version -15
	o Alignment with OSPF model done:
	* Added spf-control container with IETF SPF delay algorithm as a
	feature.
	* Added graceful-restart options.
	* Added nsr as a feature.
	* Removed per topology FRR. Need to be augmented if necessary.
	* Created an ldp container within mpls.
	* Renamed igp-ldp-sync to igp-sync.
	* Added auto-cost container.
	* Moved reference-bandwidth under auto-cost container.
	* Added IS-IS local RIB as operational state.
	* Added decode-completed and raw-data leaves in the LSDB model.
	* Modified the notification header.
	10.16. From version -13 to version -14
	o Segment Routing extensions are now in a separate document.
	10.17. From version -12 to version -13
	o Move feature nlpid-control to container rather than list.
	o Rename multi-topology to topologies to align with OSPF.
	o Rename bfd/enabled to bfd/enable for consistency reason.
	o Add support for NSR with a feature.
	10.18. From version -09 to version -12
	o Rename node-tag container to node-tags.
	10.19. From version -08 to version -09
	o Added container before af list.
	o Added container before topology list.
	o Aligned LFA if per level cfg.
	o Align to draft-ietf-netmod-routing-cfg-23.
	10.20. From version -07 to version -08
	o Remove selector from system-id type.
	o Add some default values.
	o Moved lists to containers and groupings for per level
	configuration.
	o Remove routing-instance as per core routing model v21.
	o added BFD leaf (no more BFD protocol model).
	o changed keychain module reference.
	10.21. From version -05 to version -07
	o Move Overload config from list to container.
	o Move Overload-max-metric config from list to container.
	o Move preference config from list to container.
	o Add Node flag in config.
	o Removed BFD config => moved to isis-bfd module.
	o Remove call to routing policy model.
	10.22. From version -03 to version -05
	o Correct invalid references to previous versions of core routing
	model.
	o Remove BFD config and replace by groupings from ietf-bfd.
	o Adding routing-policy support through routing-policy model.
	10.23. From version -02 to version -03
	o Reviewed config and op state groupings.
	o Add default value to lfa candidate-disabled.
	o Add enable leaf to isis container to reflect admin state.
	o Move to VRF centric only.
	o Segment routing is part of a separate module.
	10.24. From version -01 to version -02
	o Adding IPFRR.
	o Adding igp-ldp-sync.
	o Adding segment-routing.
	o Adding instance reference to operational states.
	o Move AF type from string to identity.
	o Updated router-capability in LSDB description.
	o packet counters moved to interface-packet-counters.
	o Added modification information in lsp-log.
	o Removing igp-ldp-sync timer in IS-IS.
	o Defining hierarchy for operational states.
	o Adding clns-mtu.
	o Adding key-chain.
	10.25. From version -00 to version -01
	o Interface metric move from af container to interface container.
	o Hello-padding on interface moved to hello-padding-disable with
	empty type.
	o three-way-handshake removed.
	o route preference changed to a choice.
	o csnp-authentication/psnp-authentication merged to authentication
	container.
	o lsp-gen-interval-exp-delay removed.
	o Added overload-max-metric feature.
	o overload-max-metric is in a separate container.
	o Change hello-padding to container.
	o Change bfd to container.
	o Make BFD a feature.
	o Create mpls-te container and put router-id inside.
	o Remove GR helper disable and timers.
	11. References
	11.1. Normative References		10.1. 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-17 (work in		Detection (BFD)", draft-ietf-bfd-yang-17 (work in
	progress), August 2018.		progress), August 2018.
	[ISO-10589]		[ISO-10589]
	ISO, , "Intermediate System to Intermediate System intra-		ISO, , "Intermediate System to Intermediate System intra-
	domain routing information exchange protocol for use in		domain routing information exchange protocol for use in
	skipping to change at page 116, line 9 ¶		skipping to change at page 108, line 24 ¶
	[RFC8405] Decraene, B., Litkowski, S., Gredler, H., Lindem, A.,		[RFC8405] Decraene, B., Litkowski, S., Gredler, H., Lindem, A.,
	Francois, P., and C. Bowers, "Shortest Path First (SPF)		Francois, P., and C. Bowers, "Shortest Path First (SPF)
	Back-Off Delay Algorithm for Link-State IGPs", RFC 8405,		Back-Off Delay Algorithm for Link-State IGPs", RFC 8405,
	DOI 10.17487/RFC8405, June 2018, <https://www.rfc-		DOI 10.17487/RFC8405, June 2018, <https://www.rfc-
	editor.org/info/rfc8405>.		editor.org/info/rfc8405>.
	[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol		[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
	Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,		Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
	<https://www.rfc-editor.org/info/rfc8446>.		<https://www.rfc-editor.org/info/rfc8446>.
	11.2. Informative References		10.2. Informative References
	[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>.
	[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",		[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
	BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,		BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
	<https://www.rfc-editor.org/info/rfc8340>.		<https://www.rfc-editor.org/info/rfc8340>.
	Appendix A. Example of IS-IS configuration in XML		Appendix A. Example of IS-IS configuration in XML
End of changes. 14 change blocks.
	368 lines changed or deleted		28 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/