< draft-ietf-isis-yang-isis-cfg-36.txt		draft-ietf-isis-yang-isis-cfg-37.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: March 8, 2020 Arrcus, Inc		Expires: March 12, 2020 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
	September 5, 2019		September 9, 2019
	YANG Data Model for IS-IS Protocol		YANG Data Model for IS-IS Protocol
	draft-ietf-isis-yang-isis-cfg-36		draft-ietf-isis-yang-isis-cfg-37
	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 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 March 8, 2020.		This Internet-Draft will expire on March 12, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 22, line 38 ¶		skipping to change at page 22, line 38 ¶
	The module reuses types from [RFC6991] and [RFC8294].		The module reuses types from [RFC6991] and [RFC8294].
	To support BFD for fast detection, the module relies on		To support BFD for fast detection, the module relies on
	[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], [RFC2966], [RFC4090],[RFC5029], [RFC5130],		[ISO-10589], [RFC1195], [RFC4090],[RFC5029], [RFC5130], [RFC5302],
	[RFC5305], [RFC5306], [RFC5307], [RFC5308], [RFC5880], [RFC5881],		[RFC5305], [RFC5306], [RFC5307], [RFC5308], [RFC5880], [RFC5881],
	[RFC6119], [RFC6232], [RFC7794], [RFC7981], [RFC8570], [RFC7917],		[RFC6119], [RFC6232], [RFC7794], [RFC7981], [RFC8570], [RFC7917],
	[RFC8405].		[RFC8405].
	<CODE BEGINS> file "ietf-isis@2019-09-05.yang"		<CODE BEGINS> file "ietf-isis@2019-09-09.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)";
	skipping to change at page 25, line 9 ¶		skipping to change at page 25, line 9 ¶
	The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL		The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
	NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',		NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
	'MAY', and 'OPTIONAL' in this document are to be interpreted as		'MAY', and 'OPTIONAL' in this document are to be interpreted as
	described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,		described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
	they appear in all capitals, as shown here.		they appear in all capitals, as shown here.
	This version of this YANG module is part of RFC XXXX;		This version of this YANG module is part of RFC XXXX;
	see the RFC itself for full legal notices.";		see the RFC itself for full legal notices.";
	revision 2019-09-05 {		revision 2019-09-09 {
	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 43, line 41 ¶		skipping to change at page 43, line 41 ¶
	}		}
	leaf-list tag {		leaf-list tag {
	type uint64;		type uint64;
	description		description
	"List of tags associated with the route. The leaf		"List of tags associated with the route. The leaf
	describes both 32-bit and 64-bit tags.";		describes both 32-bit and 64-bit tags.";
	}		}
	leaf route-type {		leaf route-type {
	type enumeration {		type enumeration {
	enum l2-intra-area {		enum l2-intra-area {
	description "Level 2 internal route. As per RFC2966,		description "Level 2 internal route. As per RFC5302,
	the prefix is directly connected to the		the prefix is directly connected to the
	advertising router. It cannot be		advertising router. It cannot be
	distinguished from an L1->L2 inter-area		distinguished from an L1->L2 inter-area
	route.";		route.";
	}		}
	enum l1-intra-area {		enum l1-intra-area {
	description "Level 1 internal route. As per RFC2966,		description "Level 1 internal route. As per RFC5302,
	the prefix is directly connected to the		the prefix is directly connected to the
	advertising router.";		advertising router.";
	}		}
	enum l2-external {		enum l2-external {
	description "Level 2 external route. As per RFC2966,		description "Level 2 external route. As per RFC5302,
	such a route is learned from other IGPs.		such a route is learned from other IGPs.
	It cannot be distinguished from an L1->L2		It cannot be distinguished from an L1->L2
	inter-area external route.";		inter-area external route.";
	}		}
	enum l1-external {		enum l1-external {
	description "Level 1 external route. As per RFC2966,		description "Level 1 external route. As per RFC5302,
	such a route is learned from other IGPs.";		such a route is learned from other IGPs.";
	}		}
	enum l1-inter-area {		enum l1-inter-area {
	description "These prefixes are learned via L2 routing.";		description "These prefixes are learned via L2 routing.";
	}		}
	enum l1-inter-area-external {		enum l1-inter-area-external {
	description "These prefixes are learned via L2 routing		description "These prefixes are learned via L2 routing
	towards an l2-external route.";		towards an l2-external route.";
	}		}
	}		}
	description "IS-IS route type.";		description "IS-IS route type.";
	}		}
	}		}
	/* Grouping definitions for configuration and ops state */		/* Grouping definitions for configuration and ops state */
	grouping adjacency-state {		grouping adjacency-state {
	container adjacencies {		container adjacencies {
	skipping to change at page 108, line 21 ¶		skipping to change at page 108, line 21 ¶
	[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and		[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
	dual environments", RFC 1195, DOI 10.17487/RFC1195,		dual environments", RFC 1195, DOI 10.17487/RFC1195,
	December 1990, <https://www.rfc-editor.org/info/rfc1195>.		December 1990, <https://www.rfc-editor.org/info/rfc1195>.
	[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>.
	[RFC2966] Li, T., Przygienda, T., and H. Smit, "Domain-wide Prefix
	Distribution with Two-Level IS-IS", RFC 2966,
	DOI 10.17487/RFC2966, October 2000,
	<https://www.rfc-editor.org/info/rfc2966>.
	[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>.
	[RFC4090] Pan, P., Ed., Swallow, G., Ed., and A. Atlas, Ed., "Fast		[RFC4090] Pan, P., Ed., Swallow, G., Ed., and A. Atlas, Ed., "Fast
	Reroute Extensions to RSVP-TE for LSP Tunnels", RFC 4090,		Reroute Extensions to RSVP-TE for LSP Tunnels", RFC 4090,
	DOI 10.17487/RFC4090, May 2005,		DOI 10.17487/RFC4090, May 2005,
	<https://www.rfc-editor.org/info/rfc4090>.		<https://www.rfc-editor.org/info/rfc4090>.
	[RFC5029] Vasseur, JP. and S. Previdi, "Definition of an IS-IS Link		[RFC5029] Vasseur, JP. and S. Previdi, "Definition of an IS-IS Link
	skipping to change at page 109, line 14 ¶		skipping to change at page 109, line 5 ¶
	[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-editor.org/info/rfc5286>.		<https://www.rfc-editor.org/info/rfc5286>.
	[RFC5301] McPherson, D. and N. Shen, "Dynamic Hostname Exchange		[RFC5301] McPherson, D. and N. Shen, "Dynamic Hostname Exchange
	Mechanism for IS-IS", RFC 5301, DOI 10.17487/RFC5301,		Mechanism for IS-IS", RFC 5301, DOI 10.17487/RFC5301,
	October 2008, <https://www.rfc-editor.org/info/rfc5301>.		October 2008, <https://www.rfc-editor.org/info/rfc5301>.
			[RFC5302] Li, T., Smit, H., and T. Przygienda, "Domain-wide Prefix
			Distribution with Two-Level IS-IS", RFC 5302,
			DOI 10.17487/RFC5302, October 2008,
			<https://www.rfc-editor.org/info/rfc5302>.
	[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic		[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
	Engineering", RFC 5305, DOI 10.17487/RFC5305, October		Engineering", RFC 5305, DOI 10.17487/RFC5305, October
	2008, <https://www.rfc-editor.org/info/rfc5305>.		2008, <https://www.rfc-editor.org/info/rfc5305>.
	[RFC5306] Shand, M. and L. Ginsberg, "Restart Signaling for IS-IS",		[RFC5306] Shand, M. and L. Ginsberg, "Restart Signaling for IS-IS",
	RFC 5306, DOI 10.17487/RFC5306, October 2008,		RFC 5306, DOI 10.17487/RFC5306, October 2008,
	<https://www.rfc-editor.org/info/rfc5306>.		<https://www.rfc-editor.org/info/rfc5306>.
	[RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions		[RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions
	in Support of Generalized Multi-Protocol Label Switching		in Support of Generalized Multi-Protocol Label Switching
End of changes. 14 change blocks.
	27 lines changed or deleted		27 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/