< draft-ietf-softwire-iftunnel-06.txt		draft-ietf-softwire-iftunnel-07.txt >
	Softwire Working Group M. Boucadair		Softwire Working Group M. Boucadair
	Internet-Draft Orange		Internet-Draft Orange
	Intended status: Standards Track I. Farrer		Intended status: Standards Track I. Farrer
	Expires: November 22, 2019 Deutsche Telekom AG		Expires: December 15, 2019 Deutsche Telekom AG
	R. Asati		R. Asati
	Cisco Systems, Inc.		Cisco Systems, Inc.
	May 21, 2019		June 13, 2019
	Tunnel Interface Types YANG Module		Tunnel Interface Types YANG Module
	draft-ietf-softwire-iftunnel-06		draft-ietf-softwire-iftunnel-07
	Abstract		Abstract
	This document specifies the initial version of a YANG module		This document specifies the initial version of a YANG module
	containing a collection of IANA maintained YANG identities, used as		containing a collection of IANA maintained YANG identities, used as
	interface types for tunnel interfaces. The module reflects the		interface types for tunnel interfaces. The module reflects the
	"tunnelType" registry maintained by IANA. The latest revision of		"tunnelType" registry maintained by IANA. The latest revision of
	this YANG module can be obtained from the IANA web site.		this YANG module can be obtained from the IANA web site.
	Tunnel type values are not directly added to the Tunnel Interface		Tunnel type values are not directly added to the Tunnel Interface
	skipping to change at page 2, line 20 ¶		skipping to change at page 2, line 20 ¶
	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 November 22, 2019.		This Internet-Draft will expire on December 15, 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
	(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 3, line 21 ¶		skipping to change at page 3, line 21 ¶
	revision of this module can be obtained from the IANA web site.		revision of this module can be obtained from the IANA web site.
	Tunnel-specific extensions may be added to the Interface module		Tunnel-specific extensions may be added to the Interface module
	[RFC8343] as a function of the tunnel type. An example of this is		[RFC8343] as a function of the tunnel type. An example of this is
	provided in Appendix A. It is not the intention of this document to		provided in Appendix A. It is not the intention of this document to
	define tunnel-specific extensions for every tunnel encapsulation		define tunnel-specific extensions for every tunnel encapsulation
	technology; those are discussed in dedicated documents such as		technology; those are discussed in dedicated documents such as
	[I-D.ietf-softwire-yang]. Likewise, it is out of the scope of this		[I-D.ietf-softwire-yang]. Likewise, it is out of the scope of this
	document to update the existing IANA registry		document to update the existing IANA registry
	[TUNNELTYPE-IANA-REGISTRY] with a comprehensive list of tunnel		[TUNNELTYPE-IANA-REGISTRY] with a comprehensive list of tunnel
	technologies.		technologies. Guidelines and registration procedures for interface
			types and sub-types are discussed in [I-D.thaler-iftype-reg].
	This document uses the common YANG types defined in [RFC6991] and		This document uses the common YANG types defined in [RFC6991] and
	adopts the Network Management Datastore Architecture (NMDA		adopts the Network Management Datastore Architecture (NMDA
	[RFC8342]).		[RFC8342]).
	The terminology for describing YANG modules is defined in [RFC7950].		The terminology for describing YANG modules is defined in [RFC7950].
	The meanings of the symbols used in the tree diagram are defined in		The meanings of the symbols used in the tree diagram are defined in
	[RFC8340].		[RFC8340].
	2. IANA Tunnel Type YANG Module		2. IANA Tunnel Type YANG Module
	skipping to change at page 7, line 52 ¶		skipping to change at page 8, line 6 ¶
	transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer		transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
	is HTTPS, and the mandatory-to-implement secure transport is TLS		is HTTPS, and the mandatory-to-implement secure transport is TLS
	[RFC8446].		[RFC8446].
	The Network Configuration Access Control Model (NACM) [RFC8341]		The Network Configuration Access Control Model (NACM) [RFC8341]
	provides the means to restrict access for particular NETCONF or		provides the means to restrict access for particular NETCONF or
	RESTCONF users to a preconfigured subset of all available NETCONF or		RESTCONF users to a preconfigured subset of all available NETCONF or
	RESTCONF protocol operations and content.		RESTCONF protocol operations and content.
	The module defined in this document defines YANG identities for the		The module defined in this document defines YANG identities for the
	iana-tunnel-types registry. These identies are intended to be		iana-tunnel-types registry. These identities are intended to be
	referenced by other YANG modules, and by themselves do not expose any		referenced by other YANG modules, and by themselves do not expose any
	nodes which are writable, contain read-only state, or RPCs. As such,		nodes which are writable, contain read-only state, or RPCs. As such,
	there are no additional security issues to be considered relating to		there are no additional security issues to be considered relating to
	the module defined in this document.		the module defined in this document.
	4. IANA Considerations		4. IANA Considerations
	4.1. YANG Module		4.1. YANG Module
	This document requests IANA to register the following URI in the "ns"		This document requests IANA to register the following URI in the "ns"
	skipping to change at page 11, line 47 ¶		skipping to change at page 11, line 47 ¶
	tunnelType", <https://www.iana.org/assignments/smi-		tunnelType", <https://www.iana.org/assignments/smi-
	numbers/smi-numbers.xhtml#smi-numbers-6>.		numbers/smi-numbers.xhtml#smi-numbers-6>.
	6.2. Informative References		6.2. Informative References
	[I-D.ietf-softwire-yang]		[I-D.ietf-softwire-yang]
	Farrer, I. and M. Boucadair, "YANG Modules for IPv4-in-		Farrer, I. and M. Boucadair, "YANG Modules for IPv4-in-
	IPv6 Address plus Port (A+P) Softwires", draft-ietf-		IPv6 Address plus Port (A+P) Softwires", draft-ietf-
	softwire-yang-16 (work in progress), January 2019.		softwire-yang-16 (work in progress), January 2019.
			[I-D.thaler-iftype-reg]
			Thaler, D. and D. Romascanu, "Guidelines and Registration
			Procedures for Interface Types", draft-thaler-iftype-
			reg-02 (work in progress), March 2019.
	[RFC1701] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic		[RFC1701] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic
	Routing Encapsulation (GRE)", RFC 1701,		Routing Encapsulation (GRE)", RFC 1701,
	DOI 10.17487/RFC1701, October 1994,		DOI 10.17487/RFC1701, October 1994,
	<https://www.rfc-editor.org/info/rfc1701>.		<https://www.rfc-editor.org/info/rfc1701>.
	[RFC1702] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic		[RFC1702] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic
	Routing Encapsulation over IPv4 networks", RFC 1702,		Routing Encapsulation over IPv4 networks", RFC 1702,
	DOI 10.17487/RFC1702, October 1994,		DOI 10.17487/RFC1702, October 1994,
	<https://www.rfc-editor.org/info/rfc1702>.		<https://www.rfc-editor.org/info/rfc1702>.
	skipping to change at page 14, line 20 ¶		skipping to change at page 14, line 26 ¶
	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>.
	[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>.
	Appendix A. Example Usage		Appendix A. Example Usage
	The following example illustrates how the Interface YANG module can		The following example illustrates how the Interface YANG module can
	be augmented with tunnel-specific paramters. In this example, the		be augmented with tunnel-specific parameters. In this example, the
	module is augmented with a 'remote-endpoint' for the tunnel. A tree		module is augmented with a 'remote-endpoint' for the tunnel. A tree
	structure is provided below:		structure is provided below:
	module: example-iftunnel-extension		module: example-iftunnel-extension
	augment /if:interfaces/if:interface:		augment /if:interfaces/if:interface:
	+--rw remote-endpoint? inet:ipv6-address		+--rw remote-endpoint? inet:ipv6-address
	The 'example-iftunnel-extension' module imports the modules defined		The 'example-iftunnel-extension' module imports the modules defined
	in [RFC6991] and [RFC8343] in addition to the "iana-tunnel-type"		in [RFC6991] and [RFC8343] in addition to the "iana-tunnel-type"
	module defined in this document.		module defined in this document.
	module example-iftunnel-extension {		module example-iftunnel-extension {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-extension-example";		namespace "urn:ietf:params:xml:ns:yang:example-iftunnel-extension";
	prefix example;		prefix example;
	import ietf-inet-types {		import ietf-inet-types {
	prefix inet;		prefix inet;
	reference		reference
	"Section 4 of RFC 6991";		"Section 4 of RFC 6991";
	}		}
	import ietf-interfaces {		import ietf-interfaces {
	prefix if;		prefix if;
End of changes. 9 change blocks.
	8 lines changed or deleted		14 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/