Tunnel Interface Types YANG
ModuleOrangeRennes35000Francemohamed.boucadair@orange.comDeutsche Telekom AGCTO-ATI,Landgrabenweg 151BonnNRW53227Germanyian.farrer@telekom.deCisco Systems, Inc.7025 Kit Creek Rd.RTPNC27709USARajiva@cisco.comSoftwire Working GroupsoftwireAugment tunneltunnel managementtunnel provisioningtunnel activationtunnel automationThis document specifies the initial version of a YANG module
containing a collection of IANA maintained YANG identities, used as
interface types for tunnel interfaces. The module reflects the
"tunnelType" registry maintained by IANA. The latest revision of this
YANG module can be obtained from the IANA web site.Tunnel type values are not directly added to the Tunnel Interface
Types YANG module; they must instead be added to the "tunnelType" IANA
registry. Once a new tunnel type registration is made by IANA for a new
tunneling scheme or even an existing one that is not already listed in
the current registry (e.g., LISP, NSH), IANA will update the Tunnel
Interface Types YANG module accordingly.Some of the IETF-defined tunneling techniques are not listed in the
current IANA registry. It is not the intent of this document to update
the existing IANA registry with a comprehensive list of tunnel
technologies. Registrants must follow the IETF registration procedure
for interface types whenever a new tunnel type is needed.Please update these statements in the document with the RFC number to
be assigned to this document:"This version of this YANG module is part of RFC XXXX;""RFC XXXX: Tunnel Interface Types YANG Module";"reference: RFC XXXX""...must be updated as defined in RFCXXXX."Please update the "revision" date of the YANG modules.This document specifies the initial version of the iana-tunnel-type
YANG module containing a collection of IANA maintained YANG identities
identifying tunnel interface types. The module reflects IANA's registry
maintained at . The
latest revision of this module can be obtained from the IANA web
site.Tunnel-specific extensions may be added to the Interface module as a function of the tunnel type. An example of
this is provided in . It is not the
intention of this document to define tunnel-specific extensions for
every tunnel encapsulation technology; those are discussed in dedicated
documents such as .
Likewise, it is out of the scope of this document to update the existing
IANA registry with a
comprehensive list of tunnel technologies. Guidelines and registration
procedures for interface types and sub-types are discussed in .This document uses the common YANG types defined in and adopts the Network Management Datastore
Architecture (NMDA ).The terminology for describing YANG modules is defined in . The meanings of the symbols used in the tree
diagram are defined in .The iana-tunnel-type module imports the 'iana-if-type' module defined
in .The initial version of the module includes tunnel types defined in
, , , and .The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such as
NETCONF or RESTCONF . The lowest NETCONF layer is the secure
transport layer, and the mandatory-to-implement secure transport is
Secure Shell (SSH) . The lowest RESTCONF
layer is HTTPS, and the mandatory-to-implement secure transport is TLS
.The Network Configuration Access Control Model (NACM) provides the means to restrict access for
particular NETCONF or RESTCONF users to a preconfigured subset of all
available NETCONF or RESTCONF protocol operations and content.The module defined in this document defines YANG identities for the
iana-tunnel-types registry. These identities are intended to be
referenced by other YANG modules, and by themselves do not expose any
nodes which are writable, contain read-only state, or RPCs. As such,
there are no additional security issues to be considered relating to the
module defined in this document.This document requests IANA to register the following URI in the
"ns" subregistry within the "IETF XML Registry" : This document requests IANA to register the following
following YANG module in the "YANG Module Names" subregistry within the "YANG Parameters" registry.This document defines the initial version of the IANA-maintained
iana-tunnel-type YANG module. IANA is requested to add this note:Tunnel type values must not be directly added to the
iana-tunnel-type YANG module. They must instead be respectively
added to the "tunnelType" sub-registry (under the "ifType
definitions" registry).When a tunnel type is added to the "tunnelType" sub-registry, a new
"identity" statement must be added to the iana-tunnel-type YANG
module. The name of the "identity" is the lower-case of the
corresponding enumeration in the IANAifType-MIB (i.e.,
IANAtunnelType). The "identity" statement should have the following
sub-statements defined:Contains 'ift:tunnel'.Replicates the description
from the registry.Replicates the reference from
the registry and add the title of the document.Unassigned or reserved values are not present in the module.When the iana-tunnel-type YANG module is updated, a new "revision"
statement must be added in front of the existing revision
statements.IANA is requested to add this note to "tunnelType"
sub-registry:When this registry is modified, the YANG module
iana-tunnel-type must be updated as defined in RFCXXXX.This document requests IANA to update the following entries
available at
https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-6:
Special thanks to Tom Petch and Martin Bjorklund for the detailed
review and suggestions.Thanks to Andy Bierman for the Yangdoctors review.Thanks to Dale Worley, David Black, and Yaron Sheffer for the
review.ifType definitions: tunnelTypeInternet Assigned Numbers
AuthorityThe following example illustrates how the Interface YANG module can
be augmented with tunnel-specific parameters. In this example, the
module is augmented with a 'remote-endpoint' for the tunnel. A tree
structure is provided below:The 'example-iftunnel-extension' module imports the modules defined
in and in
addition to the "iana-tunnel-type" module defined in this document.