rfc8675xml2.original.xml   rfc8675.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF"
<?rfc tocdepth="3"?> docName="draft-ietf-softwire-iftunnel-07" category="std" consensus="yes" nu
<?rfc tocindent="yes"?> mber="8675" ipr="trust200902"
<?rfc symrefs="yes"?> obsoletes="" updates="" tocInclude="true" tocDepth="3" symRefs="true"
<?rfc sortrefs="yes"?> sortRefs="true" xml:lang="en" version="3">
<?rfc comments="yes"?> <!-- 10/21 xml2rfc v2v3 conversion 2.33.0 -->
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-ietf-softwire-iftunnel-07"
ipr="trust200902">
<front> <front>
<title abbrev="Tunnel Interface Types">Tunnel Interface Types YANG
Module</title>
<title abbrev="Tunnel Interface Types">A YANG Data Model for Tunnel Interfac
e Types</title>
<seriesInfo name="RFC" value="8675"/>
<author fullname="Mohamed Boucadair" initials="M." surname="Boucadair"> <author fullname="Mohamed Boucadair" initials="M." surname="Boucadair">
<organization>Orange</organization> <organization>Orange</organization>
<address> <address>
<postal> <postal>
<street></street> <street/>
<city>Rennes</city> <city>Rennes</city>
<code>35000</code> <code>35000</code>
<country>France</country> <country>France</country>
</postal> </postal>
<email>mohamed.boucadair@orange.com</email> <email>mohamed.boucadair@orange.com</email>
</address> </address>
</author> </author>
<author fullname="Ian Farrer" initials="I." surname="Farrer"> <author fullname="Ian Farrer" initials="I." surname="Farrer">
<organization>Deutsche Telekom AG</organization> <organization>Deutsche Telekom AG</organization>
<address> <address>
<postal> <postal>
<street>CTO-ATI,Landgrabenweg 151</street> <street>CTO-ATI, Landgrabenweg 151</street>
<city>Bonn</city> <city>Bonn</city>
<region>NRW</region> <region>NRW</region>
<code>53227</code> <code>53227</code>
<country>Germany</country> <country>Germany</country>
</postal> </postal>
<email>ian.farrer@telekom.de</email> <email>ian.farrer@telekom.de</email>
</address> </address>
</author> </author>
<author fullname="Rajiv Asati" initials="R." surname="Asati"> <author fullname="Rajiv Asati" initials="R." surname="Asati">
<organization>Cisco Systems, Inc.</organization> <organization>Cisco Systems, Inc.</organization>
<address> <address>
<postal> <postal>
<street>7025 Kit Creek Rd.</street> <street>7025 Kit Creek Rd.</street>
<city>RTP</city> <city>RTP</city>
<region>NC</region> <region>NC</region>
<code>27709</code> <code>27709</code>
<country>United States of America</country>
<country>USA</country>
</postal> </postal>
<email>Rajiva@cisco.com</email> <email>Rajiva@cisco.com</email>
</address> </address>
</author> </author>
<date year="2019" month="November"/>
<date />
<workgroup>Softwire Working Group</workgroup> <workgroup>Softwire Working Group</workgroup>
<keyword>softwire</keyword> <keyword>softwire</keyword>
<keyword>Augment tunnel</keyword> <keyword>Augment tunnel</keyword>
<keyword>tunnel management</keyword> <keyword>tunnel management</keyword>
<keyword>tunnel provisioning</keyword> <keyword>tunnel provisioning</keyword>
<keyword>tunnel activation</keyword> <keyword>tunnel activation</keyword>
<keyword>tunnel automation</keyword> <keyword>tunnel automation</keyword>
<abstract> <abstract>
<t>This document specifies the initial version of a YANG module <t>This document specifies the initial version of a YANG module
containing a collection of IANA maintained YANG identities, used as "iana-tunnel-type", which
contains 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 this "tunnelType" registry maintained by IANA. The latest revision of this
YANG module can be obtained from the IANA web site.</t> YANG module can be obtained from the IANA website.</t>
<t>Tunnel type values are not directly added to the Tunnel Interface <t>Tunnel type values are not directly added to the Tunnel Interface
Types YANG module; they must instead be added to the "tunnelType" IANA 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 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 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 the current registry (e.g., LISP, NSH), IANA will update the Tunnel
Interface Types YANG module accordingly.</t> Interface Types YANG module accordingly.</t>
<t>Some of the IETF-defined tunneling techniques are not listed in the <t>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 current IANA registry. It is not the intent of this document to update
the existing IANA registry with a comprehensive list of tunnel the existing IANA registry with a comprehensive list of tunnel
technologies. Registrants must follow the IETF registration procedure technologies. Registrants must follow the IETF registration procedure
for interface types whenever a new tunnel type is needed.</t> for interface types whenever a new tunnel type is needed.</t>
</abstract> </abstract>
<note title="Editorial Note (To be removed by RFC Editor)">
<t>Please update these statements in the document with the RFC number to
be assigned to this document:<list style="symbols">
<t>"This version of this YANG module is part of RFC XXXX;"</t>
<t>"RFC XXXX: Tunnel Interface Types YANG Module";</t>
<t>"reference: RFC XXXX"</t>
<t>"...must be updated as defined in RFCXXXX."</t>
</list>Please update the "revision" date of the YANG modules.<!-- o C
APWAP (Control And Provisioning of Wireless Access Points)
[RFC5415];
o LISP (Locator/Identifier Separation Protocol) [RFC6830];
o AMT (Automatic Multicast Tunneling) [RFC7450];
o VXLAN (Virtual eXtensible Local Area Network) [RFC7348] and VXLAN-
GPE [I-D.ietf-nvo3-vxlan-gpe];
o The Network Service Header (NSH [RFC8300]) for Service Function
Chaining (SFC);
o Geneve [I-D.ietf-nvo3-geneve];
o GUE (Generic UDP Encapsulation) [I-D.ietf-intarea-gue];
o TCP Encapsulation of IKE and IPsec Packets (see Section 12.5 of
[RFC8229]).--></t>
</note>
</front> </front>
<middle> <middle>
<section title="Introduction"> <section numbered="true" toc="default">
<name>Introduction</name>
<t>This document specifies the initial version of the iana-tunnel-type <t>This document specifies the initial version of the iana-tunnel-type
YANG module containing a collection of IANA maintained YANG identities YANG module containing a collection of IANA-maintained YANG identities
identifying tunnel interface types. The module reflects IANA's registry identifying tunnel interface types. The module reflects IANA's
maintained at <xref target="TUNNELTYPE-IANA-REGISTRY"></xref>. The tunnelType registry under the SMI Numbers registry <xref target="TUNNELTYP
latest revision of this module can be obtained from the IANA web E-IANA-REGISTRY" format="default"/>. The
site.</t> latest revision of this module can be obtained from the IANA website.</t>
<t>Tunnel-specific extensions may be added to the Interface module <xref t
<t>Tunnel-specific extensions may be added to the Interface module <xref arget="RFC8343" format="default"/> as a function of the tunnel type. An example
target="RFC8343"></xref> as a function of the tunnel type. An example of of
this is provided in <xref target="sample"></xref>. It is not the this is provided in <xref target="sample" format="default"/>. It is not th
e
intention of this document to define tunnel-specific extensions for intention of this document to define tunnel-specific extensions for
every tunnel encapsulation technology; those are discussed in dedicated every tunnel encapsulation technology; those are discussed in dedicated
documents such as <xref target="I-D.ietf-softwire-yang"></xref>. documents such as <xref target="RFC8676" format="default"/>.
Likewise, it is out of the scope of this document to update the existing Likewise, it is out of the scope of this document to update the existing
IANA registry <xref target="TUNNELTYPE-IANA-REGISTRY"></xref> with a IANA tunnelType registry <xref target="TUNNELTYPE-IANA-REGISTRY" format="d efault"/> with a
comprehensive list of tunnel technologies. Guidelines and registration comprehensive list of tunnel technologies. Guidelines and registration
procedures for interface types and sub-types are discussed in <xref procedures for interface types and sub-types are discussed in <xref target
target="I-D.thaler-iftype-reg"></xref>.</t> ="I-D.thaler-iftype-reg" format="default"/>.</t>
<t>This document uses the common YANG types defined in <xref target="RFC69
<t>This document uses the common YANG types defined in <xref 91" format="default"/> and adopts the Network Management Datastore
target="RFC6991"></xref> and adopts the Network Management Datastore Architecture (NMDA <xref target="RFC8342" format="default"/>).</t>
Architecture (NMDA <xref target="RFC8342"></xref>).</t>
<t>The terminology for describing YANG modules is defined in <xref <t>The terminology for describing YANG modules is defined in <xref target=
target="RFC7950"></xref>. The meanings of the symbols used in the tree "RFC7950" format="default"/>. The meanings of the symbols used in the tree
diagram are defined in <xref target="RFC8340"></xref>.</t> diagram are defined in <xref target="RFC8340" format="default"/>.</t>
</section> </section>
<section anchor="itt" numbered="true" toc="default">
<section anchor="itt" title="IANA Tunnel Type YANG Module"> <name>IANA Tunnel Type YANG Module</name>
<t>The iana-tunnel-type module imports the 'iana-if-type' module defined <t>The iana-tunnel-type module imports the 'iana-if-type' module defined
in <xref target="RFC7224"></xref>.</t> in <xref target="RFC7224" format="default"/>.</t>
<t>The initial version of the module includes tunnel types defined in <t>The initial version of the module includes tunnel types defined in
<xref target="RFC4087"></xref>, <xref target="RFC7856"></xref>, <xref <xref target="RFC4087" format="default"/>, <xref target="RFC7856" format="
target="RFC7870"></xref>, and <xref target="RFC6346"></xref>.</t> default"/>, <xref target="RFC7870" format="default"/>, and <xref target="RFC6346
" format="default"/>.</t>
<t><figure> <sourcecode name="iana-tunnel-type@2019-11-07.yang" type="yang" markers="t
<artwork><![CDATA[<CODE BEGINS> file "iana-tunnel-type@2019-04-04.yang rue"><![CDATA[
"
module iana-tunnel-type { module iana-tunnel-type {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:iana-tunnel-type"; namespace "urn:ietf:params:xml:ns:yang:iana-tunnel-type";
prefix iana-tunnel-type; prefix iana-tunnel-type;
import iana-if-type { import iana-if-type {
prefix ift; prefix ift;
reference reference
"RFC 7224: IANA Interface Type YANG Module"; "RFC 7224: IANA Interface Type YANG Module";
} }
organization organization
"IANA"; "IANA";
contact contact
"Internet Assigned Numbers Authority "Internet Assigned Numbers Authority
Postal: ICANN Postal: ICANN
12025 Waterfront Drive, Suite 300 12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536 Los Angeles, CA 90094-2536
United States of America United States of America
Tel: +1 310 301 5800 Tel: +1 310 301 5800
<mailto:iana@iana.org>"; <mailto:iana@iana.org>";
description description
"This module contains a collection of YANG identities defined "This module contains a collection of YANG identities defined
by IANA and used as interface types for tunnel interfaces. by IANA and used as interface types for tunnel interfaces.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2019 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). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC 8675; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2019-04-04 { revision 2019-11-07 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Tunnel Interface Types YANG Module"; "RFC 8675: A YANG Data Model for Tunnel Interface Types";
} }
identity other { identity other {
base ift:tunnel; base ift:tunnel;
description description
"None of the following values."; "None of the following values.";
reference reference
"RFC 4087: IP Tunnel MIB"; "RFC 4087: IP Tunnel MIB";
} }
identity direct { identity direct {
base ift:tunnel; base ift:tunnel;
description description
"No intermediate header."; "No intermediate header.";
reference reference
"RFC 2003: IP Encapsulation within IP "RFC 2003: IP Encapsulation within IP
RFC 4213: Basic Transition Mechanisms for IPv6 Hosts RFC 4213: Basic Transition Mechanisms for IPv6 Hosts
and Routers"; and Routers";
} }
identity gre {
base ift:tunnel; identity gre {
description base ift:tunnel;
"GRE encapsulation."; description
reference "GRE encapsulation.";
reference
"RFC 1701: Generic Routing Encapsulation (GRE) "RFC 1701: Generic Routing Encapsulation (GRE)
RFC 1702: Generic Routing Encapsulation over IPv4 networks RFC 1702: Generic Routing Encapsulation over IPv4 networks
RFC 7676: IPv6 Support for Generic Routing Encapsulation RFC 7676: IPv6 Support for Generic Routing Encapsulation
(GRE)"; (GRE)";
} }
identity minimal { identity minimal {
base ift:tunnel; base ift:tunnel;
description description
"Minimal encapsulation."; "Minimal encapsulation.";
reference reference
"RFC 2004: Minimal Encapsulation within IP"; "RFC 2004: Minimal Encapsulation within IP";
} }
identity l2tp { identity l2tp {
base ift:tunnel; base ift:tunnel;
description description
"L2TP encapsulation."; "L2TP encapsulation.";
reference reference
"RFC 2661: Layer Two Tunneling Protocol (L2TP)"; "RFC 2661: Layer Two Tunneling Protocol 'L2TP'";
} }
identity pptp { identity pptp {
base ift:tunnel; base ift:tunnel;
description description
"PPTP encapsulation."; "PPTP encapsulation.";
reference reference
"RFC 2637: Point-to-Point Tunneling Protocol (PPTP)"; "RFC 2637: Point-to-Point Tunneling Protocol (PPTP)";
} }
identity l2f { identity l2f {
base ift:tunnel; base ift:tunnel;
description description
"L2F encapsulation."; "L2F encapsulation.";
reference reference
"RFC 2341: Cisco Layer Two Forwarding (Protocol) (L2F)"; "RFC 2341: Cisco Layer Two Forwarding (Protocol) 'L2F'";
} }
identity udp { identity udp {
base ift:tunnel; base ift:tunnel;
description description
"UDP encapsulation."; "UDP encapsulation.";
reference reference
"Section 3.1.11 of RFC 8085"; "RFC 1234: Tunneling IPX Traffic through IP Networks,
RFC 8085: UDP Usage Guidelines, Section 3.1.11";
} }
identity atmp { identity atmp {
base ift:tunnel; base ift:tunnel;
description description
"ATMP encapsulation."; "ATMP encapsulation.";
reference reference
"RFC 2107: Ascend Tunnel Management Protocol - ATMP"; "RFC 2107: Ascend Tunnel Management Protocol - ATMP";
} }
identity msdp { identity msdp {
base ift:tunnel; base ift:tunnel;
description description
"MSDP encapsulation."; "MSDP encapsulation.";
reference reference
"RFC 3618: Multicast Source Discovery Protocol (MSDP)"; "RFC 3618: Multicast Source Discovery Protocol (MSDP)";
} }
identity sixtofour { identity sixtofour {
base ift:tunnel; base ift:tunnel;
description description
"6to4 encapsulation."; "6to4 encapsulation.";
reference reference
"RFC 3056: Connection of IPv6 Domains via IPv4 Clouds"; "RFC 3056: Connection of IPv6 Domains via IPv4 Clouds";
} }
identity sixoverfour { identity sixoverfour {
base ift:tunnel; base ift:tunnel;
description description
"6over4 encapsulation."; "6over4 encapsulation.";
reference reference
"RFC 2529: Transmission of IPv6 over IPv4 Domains without "RFC 2529: Transmission of IPv6 over IPv4 Domains without
Explicit Tunnels"; Explicit Tunnels";
} }
identity isatap { identity isatap {
base ift:tunnel; base ift:tunnel;
description description
"ISATAP encapsulation."; "ISATAP encapsulation.";
reference reference
"RFC 5214: Intra-Site Automatic Tunnel Addressing Protocol "RFC 5214: Intra-Site Automatic Tunnel Addressing Protocol
(ISATAP)"; (ISATAP)";
} }
identity teredo { identity teredo {
base ift:tunnel; base ift:tunnel;
description description
"Teredo encapsulation."; "Teredo encapsulation.";
reference reference
"RFC 4380: Teredo- Tunneling IPv6 over UDP through "RFC 4380: Teredo: Tunneling IPv6 over UDP through
Network Address Translations (NATs)"; Network Address Translations (NATs)";
} }
identity iphttps { identity iphttps {
base ift:tunnel; base ift:tunnel;
description description
"IP over HTTPS (IP-HTTPS) Tunneling Protocol."; "IP over HTTPS (IP-HTTPS) Tunneling Protocol.";
reference reference
"Microsoft Corporation, IP over HTTPS (IP-HTTPS) Tunneling "Microsoft Corporation, IP over HTTPS (IP-HTTPS) Tunneling
Protocol Specification, Protocol Specification,
https://msdn.microsoft.com/en-us/library/dd358571.aspx"; https://msdn.microsoft.com/en-us/library/dd358571.aspx";
} }
identity softwiremesh { identity softwiremesh {
base ift:tunnel; base ift:tunnel;
description description
"softwire mesh tunnel."; "softwire mesh tunnel.";
reference reference
"RFC 5565: Softwire Mesh Framework"; "RFC 5565: Softwire Mesh Framework";
} }
identity dslite { identity dslite {
base ift:tunnel; base ift:tunnel;
description description
"DS-Lite tunnel."; "DS-Lite tunnel.";
reference reference
"RFC 6333: Dual-Stack Lite Broadband Deployments Following "RFC 6333: Dual-Stack Lite Broadband Deployments Following
IPv4 Exhaustion"; IPv4 Exhaustion";
} }
identity aplusp { identity aplusp {
base ift:tunnel; base ift:tunnel;
description description
"A+P encapsulation."; "A+P encapsulation.";
reference reference
"RFC 6346: The Address plus Port (A+P) Approach to the IPv4 "RFC 6346: The Address plus Port (A+P) Approach to the IPv4
Address Shortage"; Address Shortage";
} }
} }
<CODE ENDS>]]></artwork> ]]></sourcecode>
</figure></t>
</section> </section>
<section numbered="true" toc="default">
<section title="Security Considerations"> <name>Security Considerations</name>
<t>The YANG module specified in this document defines a schema for data <t>The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such as that is designed to be accessed via network management protocols such as
NETCONF <xref target="RFC6241"></xref> or RESTCONF <xref NETCONF <xref target="RFC6241" format="default"/> or RESTCONF <xref
target="RFC8040"></xref>. The lowest NETCONF layer is the secure target="RFC8040" format="default"/>. The lowest NETCONF layer is the
transport layer, and the mandatory-to-implement secure transport is secure transport layer, and the mandatory-to-implement secure transport is
Secure Shell (SSH) <xref target="RFC6242"></xref>. The lowest RESTCONF Secure Shell (SSH) <xref target="RFC6242" format="default"/>. The lowest R
ESTCONF
layer is HTTPS, and the mandatory-to-implement secure transport is TLS layer is HTTPS, and the mandatory-to-implement secure transport is TLS
<xref target="RFC8446"></xref>.</t> <xref target="RFC8446" format="default"/>.</t>
<t>The Network Configuration Access Control Model (NACM) <xref target="RFC
<t>The Network Configuration Access Control Model (NACM) <xref 8341" format="default"/> provides the means to restrict access for
target="RFC8341"></xref> provides the means to restrict access for
particular NETCONF or RESTCONF users to a preconfigured subset of all particular NETCONF or RESTCONF users to a preconfigured subset of all
available NETCONF or RESTCONF protocol operations and content.</t> available NETCONF or RESTCONF protocol operations and content.</t>
<t>The module defined in this document defines YANG identities for the <t>The module defined in this document defines YANG identities for the
iana-tunnel-types registry. These identities 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 the there are no additional security issues to be considered relating to the
module defined in this document.</t> module defined in this document.</t>
</section> </section>
<section anchor="yang" numbered="true" toc="default">
<name>IANA Considerations</name>
<section numbered="true" toc="default">
<name>YANG Module</name>
<t>IANA has registered the following URI in the
"ns" subregistry within the "IETF XML Registry" <xref target="RFC3688" f
ormat="default"/>: </t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:iana-tunnel-type</dd>
<dt>Registrant Contact:</dt><dd>IANA</dd>
<dt>XML:</dt><dd>N/A; the requested URI is an XML namespace.</dd>
</dl>
<t>IANA registered the
following YANG module in the "YANG Module Names" subregistry <xref targe
t="RFC7950" format="default"/> within the "YANG Parameters" registry.</t>
<section anchor="yang" title="IANA Considerations"> <dl spacing="compact">
<section title="YANG Module"> <dt>Name:</dt><dd>iana-tunnel-type</dd>
<t>This document requests IANA to register the following URI in the <dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:iana-tunnel-type</dd>
"ns" subregistry within the "IETF XML Registry" <xref <dt>Prefix:</dt><dd>iana-tunnel-type</dd>
target="RFC3688"></xref>: <figure> <dt>Reference:</dt><dd>RFC 8675</dd>
<artwork><![CDATA[ URI: urn:ietf:params:xml:ns:yang:iana-tun </dl>
nel-type
Registrant Contact: IANA.
XML: N/A; the requested URI is an XML namespace.
]]></artwork>
</figure>This document requests IANA to register the following
following YANG module in the "YANG Module Names" subregistry <xref
target="RFC7950"></xref> within the "YANG Parameters" registry.<figure>
<artwork><![CDATA[ Name: iana-tunnel-type
Namespace: urn:ietf:params:xml:ns:yang:iana-tunnel-type
Prefix: iana-tunnel-type
Reference: RFC XXXX
]]></artwork>
</figure></t>
<t>This document defines the initial version of the IANA-maintained <t>This document defines the initial version of the IANA-maintained
iana-tunnel-type YANG module. IANA is requested to add this note:<list iana-tunnel-type YANG module. IANA has added this note to the registry:<
style="empty"> /t>
<t>Tunnel type values must not be directly added to the <ul empty="true" spacing="normal">
iana-tunnel-type YANG module. They must instead be respectively <li>
added to the "tunnelType" sub-registry (under the "ifType Tunnel type values must not be directly added to the iana-tunnel-type
definitions" registry).</t> YANG module. They must instead be added to the "tunnelType"
</list></t> subregistry (under the "ifType definitions" registry) at [IANA
registry smi-numbers].
<t>When a tunnel type is added to the "tunnelType" sub-registry, a new </li>
</ul>
<t>When a tunnel type is added to the "tunnelType" subregistry, a new
"identity" statement must be added to the iana-tunnel-type YANG "identity" statement must be added to the iana-tunnel-type YANG
module. The name of the "identity" is the lower-case of the module. The name of the "identity" is the lower-case of the
corresponding enumeration in the IANAifType-MIB (i.e., corresponding enumeration in the IANAifType-MIB (i.e.,
IANAtunnelType). The "identity" statement should have the following IANAtunnelType). The "identity" statement should have the following
sub-statements defined:</t> sub-statements defined:</t>
<dl newline="false" spacing="normal" indent="15">
<t><list hangIndent="15" style="hanging"> <dt>"base":</dt>
<t hangText="&quot;base&quot;:">Contains 'ift:tunnel'.</t> <dd>Contains 'ift:tunnel'.</dd>
<dt>"description":</dt>
<t hangText="&quot;description&quot;:">Replicates the description <dd>Replicates the description
from the registry.</t> from the registry.</dd>
<dt>"reference":</dt>
<t hangText="&quot;reference&quot;:">Replicates the reference from <dd>Replicates the reference from
the registry and add the title of the document.</t> the registry and adds the title of the document.</dd>
</list></t> </dl>
<t>Unassigned or reserved values are not present in the module.</t> <t>Unassigned or reserved values are not present in the module.</t>
<t>When the iana-tunnel-type YANG module is updated, a new "revision" <t>When the iana-tunnel-type YANG module is updated, a new "revision"
statement must be added in front of the existing revision statement must be added in front of the existing revision
statements.</t> statements.</t>
<t>IANA has added the following note to "tunnelType"
<t>IANA is requested to add this note to "tunnelType" subregistry:</t>
sub-registry:</t> <ul empty="true" spacing="normal">
<li>When this registry is modified, the YANG module
<t><list style="empty"> iana-tunnel-type must be updated as defined in RFC 8675.</li>
<t>When this registry is modified, the YANG module </ul>
iana-tunnel-type must be updated as defined in RFCXXXX.</t>
</list></t>
</section>
<section title="Updates to the IANA tunnelType Table">
<t>This document requests IANA to update the following entries
available at
https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbe
rs-6:
<figure>
<artwork><![CDATA[OLD:
Decimal Name Description References
2 direct no intermediate header [RFC4087]
3 gre GRE encapsulation [RFC4087]
4 minimal Minimal encapsulation [RFC4087]
5 l2tp L2TP encapsulation [RFC4087]
6 pptp PPTP encapsulation [RFC4087]
7 l2f L2F encapsulation [RFC4087]
8 udp UDP encapsulation [RFC4087]
9 atmp ATMP encapsulation [RFC4087]
10 msdp MSDP encapsulation [RFC4087]
11 sixToFour 6to4 encapsulation [RFC4087]
12 sixOverFour 6over4 encapsulation [RFC4087]
13 isatap ISATAP encapsulation [RFC4087]
14 teredo Teredo encapsulation [RFC4087]
16 softwireMesh softwire mesh tunnel [RFC7856]
17 dsLite DS-Lite tunnel [RFC7870] ]]></artwork>
</figure></t>
<t></t>
<t><figure>
<artwork><![CDATA[NEW:
Decimal Name Description References
2 direct no intermediate header [RFC2003]
[RFC4213]
3 gre GRE encapsulation [RFC1701]
[RFC1702]
[RFC7676]
4 minimal Minimal encapsulation [RFC2004]
5 l2tp L2TP encapsulation [RFC2661]
6 pptp PPTP encapsulation [RFC2637]
7 l2f L2F encapsulation [RFC2341]
8 udp UDP encapsulation [RFC8085]
9 atmp ATMP encapsulation [RFC2107]
10 msdp MSDP encapsulation [RFC3618]
11 sixToFour 6to4 encapsulation [RFC3056]
12 sixOverFour 6over4 encapsulation [RFC2529]
13 isatap ISATAP encapsulation [RFC5214]
14 teredo Teredo encapsulation [RFC4380]
16 softwireMesh softwire mesh tunnel [RFC5565]
17 dsLite DS-Lite tunnel [RFC6333]]]></artwork>
</figure></t>
<t></t>
</section> </section>
</section> <section numbered="true" toc="default">
<name>Updates to the IANA tunnelType Table</name>
<section anchor="ack" title="Acknowledgements"> <t>IANA has updated the following entries in the tunnelType registry und
<t>Special thanks to Tom Petch and Martin Bjorklund for the detailed er
review and suggestions.</t> the SMI Numbers registry <xref target="TUNNELTYPE-IANA-REGISTRY"/>.
</t>
<t>Thanks to Andy Bierman for the Yangdoctors review.</t> <t>OLD:</t>
<table>
<t>Thanks to Dale Worley, David Black, and Yaron Sheffer for the <thead>
review.</t> <tr>
</section> <th>Decimal</th>
</middle> <th>Name</th>
<th>Description</th>
<back> <th>References</th>
<references title="Normative References"> </tr>
<?rfc include='reference.RFC.7950'?> </thead>
<tbody>
<?rfc include='reference.RFC.3688'?> <tr>
<td>2</td>
<?rfc include='reference.RFC.6991'?> <td>direct</td>
<td>no intermediate header</td>
<?rfc include='reference.RFC.7224'?> <td><xref target="RFC4087"/></td>
</tr>
<?rfc include='reference.RFC.6241'?> <tr>
<td>3</td>
<td>gre</td>
<td>GRE encapsulation</td>
<td><xref target="RFC4087"/></td>
</tr>
<?rfc include='reference.RFC.6242'?> <tr>
<td>4</td>
<td>minimal</td>
<td>Minimal encapsulation</td>
<td><xref target="RFC4087"/></td>
</tr>
<?rfc include='reference.RFC.8341'?> <tr>
<td>5</td>
<td>l2tp</td>
<td>L2TP encapsulation</td>
<td><xref target="RFC4087"/></td>
</tr>
<?rfc include='reference.RFC.8342'?> <tr>
<td>6</td>
<td>pptp</td>
<td>PPTP encapsulation</td>
<td><xref target="RFC4087"/></td>
</tr>
<?rfc include='reference.RFC.8040'?> <tr>
<td>7</td>
<td>l2f</td>
<td>L2F encapsulation</td>
<td><xref target="RFC4087"/></td>
</tr>
<?rfc include='reference.RFC.8446'?> <tr>
<td>8</td>
<td>udp</td>
<td>UDP encapsulation</td>
<td><xref target="RFC4087"/></td>
</tr>
<reference anchor="TUNNELTYPE-IANA-REGISTRY" <tr>
target="https://www.iana.org/assignments/smi-numbers/smi-number <td>9</td>
s.xhtml#smi-numbers-6"> <td>atmp</td>
<front> <td>ATMP encapsulation</td>
<title>ifType definitions: tunnelType</title> <td><xref target="RFC4087"/></td>
</tr>
<tr>
<td>10</td>
<td>msdp</td>
<td>MSDP encapsulation</td>
<td><xref target="RFC4087"/></td>
</tr>
<author> <tr>
<organization abbrev="IANA">Internet Assigned Numbers <td>11</td>
Authority</organization> <td>sixToFour</td>
</author> <td>6to4 encapsulation</td>
<td><xref target="RFC4087"/></td>
</tr>
<date /> <tr>
</front> <td>12</td>
</reference> <td>sixOverFour</td>
</references> <td>6over4 encapsulation</td>
<td><xref target="RFC4087"/></td>
</tr>
<references title="Informative References"> <tr>
<?rfc include='reference.RFC.8340'?> <td>13</td>
<td>isatap</td>
<td>ISATAP encapsulation</td>
<td><xref target="RFC4087"/></td>
</tr>
<?rfc include='reference.I-D.ietf-softwire-yang'?> <tr>
<td>14</td>
<td>teredo</td>
<td>Teredo encapsulation</td>
<td><xref target="RFC4087"/></td>
</tr>
<?rfc include='reference.I-D.thaler-iftype-reg'?> <tr>
<td>16</td>
<td>softwireMesh</td>
<td>softwire mesh tunnel</td>
<td><xref target="RFC7856"/></td>
</tr>
<?rfc include='reference.RFC.8343'?> <tr>
<td>17</td>
<td>dsLite</td>
<td>DS-Lite tunnel</td>
<td><xref target="RFC7870"/></td>
</tr>
</tbody>
</table>
<?rfc include='reference.RFC.4087'?> <t>NEW:</t>
<table>
<thead>
<tr>
<th>Decimal</th>
<th>Name</th>
<th>Description</th>
<th>References</th>
</tr>
</thead>
<tbody>
<tr>
<td>2</td>
<td>direct</td>
<td>no intermediate header</td>
<td><xref target="RFC2003"/> <xref target="RFC4213"/></td>
</tr>
<?rfc include='reference.RFC.4380'?> <tr>
<td>3</td>
<td>gre</td>
<td>GRE encapsulation</td>
<td><xref target="RFC1701"/> <xref target="RFC1702"/> <xref target="RFC7676"/
></td>
</tr>
<?rfc include='reference.RFC.2003'?> <tr>
<td>4</td>
<td>minimal</td>
<td>Minimal encapsulation</td>
<td><xref target="RFC2004"/></td>
</tr>
<?rfc include='reference.RFC.4213'?> <tr>
<td>5</td>
<td>l2tp</td>
<td>L2TP encapsulation</td>
<td><xref target="RFC2661"/></td>
</tr>
<?rfc include='reference.RFC.7856'?> <tr>
<td>6</td>
<td>pptp</td>
<td>PPTP encapsulation</td>
<td><xref target="RFC2637"/></td>
</tr>
<?rfc include='reference.RFC.7870'?> <tr>
<td>7</td>
<td>l2f</td>
<td>L2F encapsulation</td>
<td><xref target="RFC2341"/></td>
</tr>
<?rfc include='reference.RFC.6346'?> <tr>
<td>8</td>
<td>udp</td>
<td>UDP encapsulation</td>
<td> <xref target="RFC8085"/></td>
</tr>
<?rfc include='reference.RFC.6333'?> <tr>
<td>9</td>
<td>atmp</td>
<td>ATMP encapsulation</td>
<td><xref target="RFC2107"/></td>
</tr>
<?rfc include='reference.RFC.1701'?> <tr>
<td>10</td>
<td>msdp</td>
<td>MSDP encapsulation</td>
<td><xref target="RFC3618"/></td>
</tr>
<?rfc include='reference.RFC.1702'?> <tr>
<td>11</td>
<td>sixToFour</td>
<td>6to4 encapsulation</td>
<td><xref target="RFC3056"/></td>
</tr>
<?rfc include='reference.RFC.7676'?> <tr>
<td>12</td>
<td>sixOverFour</td>
<td>6over4 encapsulation</td>
<td><xref target="RFC2529"/></td>
</tr>
<?rfc include='reference.RFC.2004'?> <tr>
<td>13</td>
<td>isatap</td>
<td>ISATAP encapsulation</td>
<td><xref target="RFC5214"/></td>
</tr>
<?rfc include='reference.RFC.2661'?> <tr>
<td>14</td>
<td>teredo</td>
<td>Teredo encapsulation</td>
<td><xref target="RFC4380"/></td>
</tr>
<?rfc include='reference.RFC.2637'?> <tr>
<td>16</td>
<td>softwireMesh</td>
<td>softwire mesh tunnel</td>
<td><xref target="RFC5565"/></td>
</tr>
<?rfc include='reference.RFC.2341'?> <tr>
<td>17</td>
<td>dsLite</td>
<td>DS-Lite tunnel</td>
<td><xref target="RFC6333"/></td>
</tr>
</tbody>
</table>
</section>
</section>
</middle>
<back>
<?rfc include='reference.RFC.2107'?> <displayreference target="I-D.thaler-iftype-reg" to="IFTYPE-REG"/>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.7950.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.3688.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.6991.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.7224.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.6241.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.6242.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.8341.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.8342.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.8040.xml"/>
<xi:include
href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.
8446.xml"/>
<?rfc include='reference.RFC.3618'?> <reference anchor="TUNNELTYPE-IANA-REGISTRY" target="https://www.iana.or
g/assignments/smi-numbers">
<front>
<title>Structure of Management Information (SMI) Numbers (MIB Module
Registrations)</title>
<author>
<organization>IANA</organization>
</author>
</front>
</reference>
</references>
<references>
<name>Informative References</name>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.8340.xml"/>
<?rfc include='reference.RFC.3056'?> <!-- <?rfc include='reference.I-D.ietf-softwire-yang'?>; Companion Document -->
<reference anchor='RFC8676' target='https://www.rfc-editor.org/info/rfc8676'>
<front>
<title>YANG Modules for IPv4-in-IPv6 Address plus Port (A+P) Softwires</title>
<author initials='I' surname='Farrer' fullname='Ian Farrer' role="editor">
<organization />
</author>
<author initials='M' surname='Boucadair' fullname='Mohamed Boucadair'
role="editor">
<organization />
</author>
<date month='November' year='2019' />
</front>
<?rfc include='reference.RFC.2529'?> <seriesInfo name='RFC' value='8676' />
<seriesInfo name="DOI" value="10.17487/RFC8676"/>
</reference>
<?rfc include='reference.RFC.5214'?> <!-- <?rfc include='reference.I-D.thaler-iftype-reg'?>; I-D Exists -->
<xi:include href="https://www.rfc-editor.org/refs/bibxml3/reference.I-D.thaler-i
ftype-reg.xml"/>
<?rfc include='reference.RFC.5565'?> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.8343.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.4087.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.4380.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2003.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.4213.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.7856.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.7870.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.6346.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.6333.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.1701.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.1702.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.7676.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2004.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2661.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2637.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2341.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2107.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.3618.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.3056.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.2529.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.5214.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.5565.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.8085.xml"/>
<?rfc include='reference.RFC.8085'?> </references>
</references> </references>
<section anchor="sample" numbered="true" toc="default">
<section anchor="sample" title="Example Usage"> <name>Example Usage</name>
<t>The following example illustrates how the Interface YANG module can <t>The following example illustrates how the Interface YANG module can
be augmented with tunnel-specific parameters. 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:</t> structure is provided below:</t>
<t><figure> <sourcecode name="" type="yangtree"><![CDATA[
<artwork><![CDATA[module: example-iftunnel-extension module: example-iftunnel-extension
augment /if:interfaces/if:interface: augment /if:interfaces/if:interface:
+--rw remote-endpoint? inet:ipv6-address]]></artwork> +--rw remote-endpoint? inet:ipv6-address]]>
</figure></t> </sourcecode>
<t>The 'example-iftunnel-extension' module imports the modules defined <t>The 'example-iftunnel-extension' module imports the modules defined
in <xref target="RFC6991"></xref> and <xref target="RFC8343"></xref> in in <xref target="RFC6991" format="default"/> and <xref target="RFC8343" fo
rmat="default"/> in
addition to the "iana-tunnel-type" module defined in this document.</t> addition to the "iana-tunnel-type" module defined in this document.</t>
<t><figure> <sourcecode name="" type="yang"><![CDATA[module example-iftunnel-extension
<artwork><![CDATA[module example-iftunnel-extension { {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:example-iftunnel-extension"; 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"; "RFC 6991: Common YANG Data Types, Section 4";
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference reference
"RFC 8343: A YANG Data Model for Interface Management"; "RFC 8343: A YANG Data Model for Interface Management";
} }
import iana-tunnel-type { import iana-tunnel-type {
prefix iana-tunnel-type; prefix iana-tunnel-type;
reference reference
"RFC XXXX: A Tunnel Extension to the Interface Management "RFC 8675: A Tunnel Extension to the Interface Management
YANG Module"; YANG Module";
} }
organization "IETF Softwire Working Group"; organization "IETF Softwire Working Group";
contact contact
"WG Web: <https://datatracker.ietf.org/wg/softwire/> "WG Web: <https://datatracker.ietf.org/wg/softwire/>
WG List: <mailto:softwire@ietf.org> WG List: <mailto:softwire@ietf.org>
skipping to change at line 682 skipping to change at line 779
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2019 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; see This version of this YANG module is part of RFC 8675; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2019-04-04 { revision 2019-10-21 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Tunnel Interface Types YANG Module"; "RFC 8675: Tunnel Interface Types YANG Module";
} }
augment "/if:interfaces/if:interface" { augment "/if:interfaces/if:interface" {
when "derived-from(if:type, 'iana-tunnel-type:gre')"; when "derived-from(if:type, 'iana-tunnel-type:gre')";
description description
"Augments Interface module with specific tunnel parameters."; "Augments Interface module with specific tunnel parameters.";
leaf remote-endpoint { leaf remote-endpoint {
type inet:ipv6-address; type inet:ipv6-address;
description description
"IPv6 address of the remote GRE endpoint."; "IPv6 address of the remote GRE endpoint.";
} }
} }
} }
]]></artwork> ]]></sourcecode>
</figure></t> </section>
<section anchor="ack" numbered="false" toc="default">
<name>Acknowledgements</name>
<t>Special thanks to Tom Petch and Martin Bjorklund for the detailed
review and suggestions.</t>
<t>Thanks to Andy Bierman for the Yangdoctors review.</t>
<t>Thanks to Dale Worley, David Black, and Yaron Sheffer for the
review.</t>
</section> </section>
</back> </back>
</rfc> </rfc>
 End of changes. 133 change blocks. 
350 lines changed or deleted 506 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/