<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>

<!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.9 -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>

<?rfc rfcedstyle="yes"?>
<?rfc toc="yes"?>
<?rfc tocindent="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc strict="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc text-list-symbols="-o*+"?>
<?rfc docmapping="yes"?> "rfc2629-xhtml.ent">

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-thaler-iftype-reg-07" category="bcp" updates="2863"> number="8892" updates="2863" obsoletes="" submissionType="IETF" category="std" consensus="true" xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true" version="3">

  <!-- xml2rfc v2v3 conversion 2.44.0 -->
  <front>
    <title abbrev="ifType Guidelines">Guidelines and Registration Procedures for Interface Types and Tunnel Types</title>
    <seriesInfo name="RFC" value="8892"/>
    <author initials="D." surname="Thaler" fullname="Dave Thaler">
      <organization>Microsoft</organization>
      <address>
        <email>dthaler@microsoft.com</email>
      </address>
    </author>
    <author initials="D." surname="Romascanu" fullname="Dan Romascanu">
      <organization>Independent</organization>
      <address>
        <email>dromasca@gmail.com</email>
      </address>
    </author>
    <date month="August" year="2020" month="January" day="16"/> />
    <area>Internet</area>

    <keyword>Internet-Draft</keyword>

<keyword>ifType</keyword>
<keyword>tunnelType</keyword>
<keyword>Transmission Number</keyword>

    <abstract>
      <t>This document provides guidelines and procedures for those who are defining, registering,
or evaluating definitions of new interface types (“ifType” ("ifType" values) and tunnel types.
The original definition of the IANA interface type registry predated
the use of IANA Considerations sections and YANG modules, and so some confusion arose
over time. Tunnel types were added later, with the same requirements and allocation policy as
interface types. This document updates RFC 2863, 2863 and provides updated guidance for
these registries.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="intro" title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>The IANA IfType-MIB, which contains the list of interface type (ifType) values,
was originally defined in <xref target="RFC1573"/> target="RFC1573" format="default"/> as a separate MIB
module together with the Interfaces Group MIB (IF-MIB) module.  The IF-MIB module was
subsequently updated and is currently specified in <xref target="RFC2863"/>, target="RFC2863" format="default"/>, but this the latest IF-MIB
RFC no longer contains the IANA IfType-MIB. Instead, the IANA IfType-MIB is
maintained by IANA as a separate module.  Similarly, <xref target="RFC7224"/> target="RFC7224" format="default"/> created an initial
IANA Interface Type YANG Module, and the current version is maintained by IANA.</t>
      <t>The current IANA IfType registry is at <xref target="ifType-registry"/>, target="ifType-registry" format="default"/>, with the same values also
appearing in both <xref target="yang-if-type"/> target="yang-if-type" format="default"/> and the
      IANAifType textual convention at <xref target="IANAifType-MIB"/>.</t> target="IANAifType-MIB"
      format="default"/>.</t>

      <t>Although the ifType registry was originally defined in a MIB module,
the assignment and use of interface type values are not tied to MIB modules
or any other management mechanism.  An interface type value can be used
as the value of a data model object (MIB object, YANG object, etc.),
or
as part of a unique identifier of a data model for a given
interface type (e.g., in an OID), or simply as a value exposed by local
APIs or UI UIs on a device.</t>

      <t>The TUNNEL-MIB was defined in <xref target="RFC2667"/> target="RFC2667" format="default"/> (now obsoleted by <xref target="RFC4087"/>) target="RFC4087" format="default"/>),
which created a tunnelType registry (<xref target="tunnelType-registry"/> target="tunnelType-registry" format="default"/> and the IANAtunnelType textual
convention at <xref target="IANAifType-MIB"/>) target="IANAifType-MIB" format="default"/>), and it
defined the assignment policy for tunnelType values to always be identical to the policy for assigning
      ifType values.</t>
    </section>

    <section anchor="terminology" title="Terminology"> numbered="true" toc="default">
      <name>Terminology</name>
      <t>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”,
“SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>",
"<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>",
and “OPTIONAL” "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described
in BCP 14 <xref target="RFC2119"/> target="RFC2119" format="default"/> <xref target="RFC8174"/> target="RFC8174" format="default"/> when, and only when, they appear
in all capitals, as shown here.</t>
    </section>
    <section anchor="problems" title="Problems"> numbered="true" toc="default">
      <name>Problems</name>
      <t>This document addresses the following issues:</t>

<t><list style="numbers">
  <t>As
      <ol spacing="normal" type="1">
        <li>As noted in <xref target="intro"/>, target="intro" format="default"/>, the original guidance was written with wording
specific to MIB modules, and accordingly modules; accordingly, some confusion has resulted
when using YANG modules.  This document clarifies that ifTypes and tunnelTypes are
independent from the type of, or even existence of, a data model.</t>
  <t>The model.</li>
        <li>The use of and requirements around sub-layers and sub-types
were not well understood, but good examples of both now exist.
This is discussed in <xref target="sublayers"/>.</t>
  <t>Since target="sublayers" format="default"/>.</li>
        <li>Since the ifType "Interface Types (ifType)" and tunnelType "Tunnel Types
	(tunnelType)" registries were originally defined, and are
still retrievable, in the format of MIB modules (in addition to other formats),
confusion arose when adding YANG modules as another format, format as to whether
each is a separate registry.  This is discussed in <xref target="formats"/>.</t>
  <t>The target="formats" format="default"/>.</li>
        <li>The registries are retrievable in the format of MIB and YANG modules, but
there was previously no process guidance written to check that those formats were
syntactically correct as updates were made, which led to the registry having syntax errors
that broke tools.  <xref target="procedures"/> target="procedures" format="default"/> adds a validation step to the
documented assignment procedure.</t>
  <t>Various procedure.</li>
        <li>Various documents and registries previously said to submit requests via email,
but a web form exists for submitting requests, which caused
some confusion around which was to be used.  This is addressed
in <xref target="procedures"/>.</t>
  <t>Transmission target="procedures" format="default"/>.</li>
        <li>Transmission values <xref target="transmission-registry"/> target="transmission-registry" format="default"/> have generally been allocated as part
of ifType allocation, but no guidance existed as to whether a requester
must ask for it or not, and the request form had no such required field.
As a result, IANA has asked the Designated Expert designated expert to decide for each
allocation, but no relevant guidance for the Designated Expert designated expert has been
documented. This is remedied in <xref target="transmission-discussion"/>.</t>
</list></t> target="transmission-discussion" format="default"/>.</li>
      </ol>
    </section>
    <section anchor="sublayers" title="Interface Sub-Layers numbered="true" toc="default">
      <name>Interface Sub-layers and Sub-Types"> Sub-types</name>

      <t>When multiple sub-layers exist below the network layer,
each sub-layer can be represented by its own
row in the ifTable with its own ifType, with the ifStackTable being used to identify the
upward and downward multiplexing relationships between rows.
Section 3.1.1 of <xref target="RFC2863"/> provided
target="RFC2863" sectionFormat="of" section="3.1.1"/> provides more
discussion, and Section
3.1.2 of that RFC provided <xref target="RFC2863" sectionFormat="bare" section="3.1.2"/> provides guidance for defining interface
sub-layers. More recent experience shows that those guidelines were
phrased in a way that is now too restrictive, since at the time
<xref target="RFC2863"/> target="RFC2863" format="default"/> was written, MIB modules were the dominant data model.</t>
      <t>This document clarifies that the same guidance also applies to YANG
      modules.</t>

      <t>Some ifTypes may define sub-types.  For example, the tunnel(131)
      ifType defines sub-types, sub-types known as “tunnelTypes”, where each tunnelType can have its own MIB and/or YANG
module with protocol-specific information, but there is enough in common
that some information is exposed in a generic IP Tunnel MIB corresponding
to the tunnel(131) ifType.</t>

      <t>For requests that involve multiple sub-layers below the network layer,
requests MUST <bcp14>MUST</bcp14> include (or reference) a discussion of the multiplexing relationships
between sub-layers, ideally with a diagram. Various well-written examples exist of
such definitions, including <xref target="RFC3637"/> section 3.4.1, <xref target="RFC4087"/> section 3.1.1, target="RFC3637" sectionFormat="of" section="3.4.1"/>, <xref target="RFC4087" sectionFormat="of" section="3.1.1"/>,
and <xref target="RFC5066"/> section 3.1.1.</t> target="RFC5066" sectionFormat="of" section="3.1.1"/>.</t>

      <t>Definers of sub-layers and sub-types should consider which model is more
appropriate for their needs. A sub-layer is generally used whenever either a
dynamic relationship exists (i.e., which instances layer over which other when the set of instances above or below a
given instance can change over time) or a multiplexing relationship exists
with another sub-layer. A sub-type can be used when neither of these are true, is true
but where one interface type is conceptually a subclass of another interface type, as far
as a management data model is concerned.</t>

      <t>In general, the intent of an interface type or sub-type is that its definition should
be sufficient to identify an interoperable protocol.   In some cases, however,
a protocol might be defined in a way that is not sufficient to provide
interoperability with other compliant implementations of that protocol.
In such a case, an ifType definition should discuss whether specific
instantiations (or profiles) of behavior should use a sub-layer model
(e.g., each vendor might layer the protocol over its own sub-layer
that provides the missing details), details) or a sub-type model (i.e., each
vendor might subclass the protocol without any layering relationship).
If a sub-type model is more appropriate, then the data model for the
protocol might include a sub-type identifier so that management software
can discover objects specific to the subtype. sub-type.  In either case, such
discussion is important to guide definers of a data model for the more
specific information (i.e., a lower sub-layer or a subtype), sub-type), as well
as the Designated Expert that designated expert, who must review requests for any such
ifTypes or sub-types.</t>
      <section anchor="alternate-values" title="Alternate Values"> numbered="true" toc="default">
        <name>Alternate Values</name>
        <t>Another design decision is whether to reuse an existing ifType or tunnelType
value, possibly using a sub-type or sub-layer model for refinements, or
to use a different value for a new mechanism.</t>
        <t>If there is already an entry that could easily satisfy the modeling and functional
requirements for the requested entry, it should be reused so that
applications and tools that use the existing value can be used without changes.
If
If, however, the modeling and functional requirements are significantly different
enough such that having existing applications and tools use the existing value
would be seen as a problem, a new value should be used.</t>
        <t>For example, originally different ifType values were used for different
flavors of Ethernet (ethernetCsmacd(6), iso88023Csmacd(7), fastEther(62), etc.),
typically because they were registered by different vendors. Using different values
was, however, seen as problematic because all were functionally similar, and so <xref target="RFC3635"/> target="RFC3635" format="default"/> then deprecated all but
	ethernetCsmacd(6).</t>

        <t>As another example, a udp(8) tunnelType value was defined in <xref target="RFC2667"/> target="RFC2667" format="default"/>
with the description “The "The value UDP indicates that the payload packet is
encapsulated within a normal UDP packet (e.g., RFC 1234).” 1234)." The Teredo tunnel
protocol <xref target="RFC4380"/> target="RFC4380" format="default"/> was later defined and encapsulates packets over UDP, but the
protocol model is quite different between <xref target="RFC1234"/> target="RFC1234" format="default"/> and Teredo.  For
example, <xref target="RFC1234"/> target="RFC1234" format="default"/> supports encapsulation of multicast/broadcast traffic traffic,
whereas Teredo does not.  As such, it would be more confusing to applications
and tools to represent them using the same tunnel type, and so <xref target="RFC4087"/> target="RFC4087" format="default"/>
defined a new value for Teredo.</t>

        <t>In summary, definers of new interface or tunnel mechanisms should use a new ifType or
tunnelType value rather than reusing reuse an existing value when key aspects such
as the header format or the link model (point-to-point, non-broadcast multi-access,
broadcast capable
broadcast-capable multi-access, unidirectional broadcast, etc.) are significantly
different from existing values, but they should reuse the same value when the differences
can be expressed in terms of differing values of existing objects other than
ifType/tunnelType,
ifType/tunnelType in the standard YANG or MIB module.</t>
      </section>
    </section>
    <section anchor="formats" title="Available Formats"> numbered="true" toc="default">
      <name>Available Formats</name>
      <t>Many registries are available in multiple formats.  For example,
XML, HTML, CSV, and plain text are common formats in which many registries
are available.  This document clarifies that the <xref target="IANAifType-MIB"/>, target="IANAifType-MIB" format="default"/>,
<xref target="yang-if-type"/>, target="yang-if-type" format="default"/>, and <xref target="yang-tunnel-type"/> target="yang-tunnel-type" format="default"/> MIB and YANG modules
are merely additional formats in which the ifType "Interface Types (ifType)" and tunnelType "Tunnel Types (tunnelType)"
registries are available.  The MIB and YANG modules are not separate registries, and the same
values are always present in all formats of the same registry.</t>
      <t>The confusion stemmed in part from the fact that the IANA “Protocol Registries” "Protocol Registries"
<xref target="protocol-registries"/> target="protocol-registries" format="default"/> listed the YANG and MIB module formats separately,
as if they were separate registries. However, the entries for the
yang-if-type and iana-tunnel-type YANG modules said “See "See ifType definitions registry.” registry"
and “See "See tunnelType registry (mib-2.interface.ifTable.ifEntry.ifType.tunnelType).” (mib-2.interface.ifTable.ifEntry.ifType.tunnelType)"
respectively, although the entry for the IANAifType-MIB had no such note.
<xref target="module-formats"/> target="module-formats" format="default"/> addresses this.</t>
    </section>
    <section anchor="registration" title="Registration"> numbered="true" toc="default">
      <name>Registration</name>
      <t>The IANA policy (using terms defined in <xref target="RFC8126"/>) target="RFC8126" format="default"/>) for registration is
Expert Review, Review for both interface types and tunnel types.  The role of the
Designated Expert
designated expert in the procedure is to
raise possible concerns about wider implications of proposals for use and
deployment of interface types.  While it is recommended that the responsible
Area Director and the IESG take into consideration the Designated
Expert designated
expert opinions, nothing in the procedure empowers the
Designated Expert
designated expert to override properly arrived-at IETF or working group
consensus.</t>
      <section anchor="procedures" title="Procedures"> numbered="true" toc="default">
        <name>Procedures</name>
        <t>Someone wishing to register a new ifType or tunnelType value MUST:</t>

<t><list style="numbers">
  <t>Check <bcp14>MUST</bcp14>:</t>
        <ol spacing="normal" type="1">
          <li>Check the IANA registry to see whether there is already an entry that could
easily satisfy the modeling and functional requirements for the requested entry.
If there is already such an entry, use it or update the existing specification.
Text in an Internet-Draft, Internet-Draft or part of some other permanently
available, stable specification may be written to clarify the usage of an
existing entry or entries for the desired purpose.</t>
  <t>Check purpose.</li>
          <li>Check the IANA registry to see whether there is already some other entry with
the desired name.  If there is already an unrelated entry under the desired name, choose
a different name.</t>
  <t>Prepare name.</li>

          <li>Prepare a registration request using the template specified in <xref target="template"/>. target="template" format="default"/>.
The registration request can be contained in an Internet-Draft, submitted
alone, or submitted as part of some other permanently available, stable specification. The registration request can also be submitted in some
other form (as part of another document or as a stand-alone document),
but the registration request will be treated as an “IETF Contribution” "IETF Contribution"
under the guidelines of <xref target="RFC5378"/>.</t>
  <t>Submit target="RFC5378" format="default"/>.</li>

          <li>Submit the registration request (or pointer to a document containing it)
to IANA at iana@iana.org or (if requesting an ifType) via the web form
at &lt;https://www.iana.org/form/iftype&gt;.</t>
</list></t> <eref brackets="angle" target="https://www.iana.org/form/iftype"/>.</li>
        </ol>
        <t>Upon receipt of a registration request, the following steps MUST <bcp14>MUST</bcp14> be followed:</t>

<t><list style="numbers">
  <t>IANA
        <ol spacing="normal" type="1">
          <li>IANA checks the submission for completeness; if required information is
missing or any citations are not correct, IANA will reject the registration
request.  A registrant can resubmit a corrected request if desired.</t>
  <t>IANA desired.</li>
          <li>IANA requests Expert Review of the registration request against the
corresponding guidelines from this document.</t>
  <t>The Designated Expert document.</li>
          <li>The designated expert will evaluate the request against the criteria.</t>
  <t>Once criteria.</li>
          <li>Once the Designated Expert designated expert approves a registration, IANA updates <xref target="ifType-registry"/>, target="ifType-registry" format="default"/>,
<xref target="IANAifType-MIB"/>, target="IANAifType-MIB" format="default"/>, and <xref target="yang-if-type"/> target="yang-if-type" format="default"/> to show the registration for an interface type,
or <xref target="tunnelType-registry"/>, target="tunnelType-registry" format="default"/>, <xref target="IANAifType-MIB"/>, target="IANAifType-MIB" format="default"/>, and <xref target="yang-tunnel-type"/> target="yang-tunnel-type" format="default"/> to show the registration
for a tunnel type.
When adding values, IANA should verify that the updated
MIB module and YANG module formats are syntactically correct before publishing the update.  There are
various existing tools or web sites websites that can be used to do this verification.</t>
  <t>If verification.</li>
          <li>If instead the Designated Expert designated expert
does not approve registration (e.g., for any of the reasons in
<xref target="RFC8126"/> section 5), target="RFC8126" sectionFormat="comma" section="5"/>), a registrant can resubmit a corrected request
if desired, or the IESG can override the Designated Expert designated expert and approve
it per the process in Section 3.3 of <xref target="RFC8126"/>.</t>
</list></t> target="RFC8126" sectionFormat="of" section="3.3"/>.</li>
        </ol>
      </section>
      <section anchor="transmission-discussion" title="Media-specific OID-subtree assignments"> numbered="true" toc="default">
        <name>Media-Specific OID-Subtree Assignments</name>
        <t><xref target="IANAifType-MIB"/> target="IANAifType-MIB" format="default"/> notes:</t>

<t><list style='empty'>
  <t>The
<blockquote>The relationship between the assignment of ifType
  values and of OIDs to particular media-specific MIBs
  is solely the purview of IANA and is subject to change
  without notice.  Quite often, a media-specific MIB’s MIB's
  OID-subtree assignment within MIB-II’s ‘transmission’ MIB-II's 'transmission'
  subtree will be the same as its ifType value.
  However, in some circumstances this will not be the
  case, and implementors must not pre-assume any
  specific relationship between ifType values and
  transmission subtree OIDs.</t>
</list></t> OIDs.</blockquote>

        <t>The advice above remains unchanged, but this document changes the allocation procedure
to streamline the process, so that an ifType value and a transmission number value
with the same value will be assigned at the same time.</t>

<t>Rationale: (1)
<t>Rationale:</t>
<ol type="(%d)">
<li> This saves effort in the future since effort if a
transmission number is later needed, deemed necessary, since no IANA request is
needed that would then require another Expert Review. (2) The Review.</li>
<li>The transmission numbering space is not scarce, so there seems to be little need to reserve the number for a different purpose than what the ifType
is for. (3) The Designated Expert for.</li>
<li>The designated expert need not review whether a transmission
number value should be registered when processing each ifType request, thus
reducing the possibility of delaying assignment of ifType values. (4) There values.</li>
<li>There is no case on record where allocating the same value could have
caused any problem.</t> problems.</li>
</ol>
      </section>
      <section anchor="template" title="Registration Template"> numbered="true" toc="default">
        <name>Registration Template</name>
        <section anchor="iftype-template" title="ifType"> numbered="true" toc="default">
          <name>ifType</name>
          <t>The following template describes the fields that MUST <bcp14>MUST</bcp14> be supplied in a registration request
suitable for adding to the ifType "Interface Types (ifType)" registry:</t>

<t><list style="hanging">
  <t hangText='Label
          <dl newline="false" spacing="normal">
            <dt>Label for IANA ifType requested:'> requested:</dt>
            <dd>
  As explained in Section 7.1.1 of <xref target="RFC2578"/>, target="RFC2578" sectionFormat="of" section="7.1.1"/>, a label for a named-number enumeration
must consist of one or more letters or digits, up to a maximum of 64 characters, and
the initial character must be a lower-case lowercase letter. (However, labels longer than 32
characters are not recommended.) Note that hyphens are not allowed.</t>
  <t hangText='Name allowed.</dd>
            <dt>Name of IANA ifType requested:'> requested:</dt>
            <dd>
  A short description (e.g., a protocol name), name) suitable to appear in a comment in the registry.</t>
  <t hangText='Description registry.</dd>
            <dt>Description of the proposed use of the IANA ifType:'> ifType:</dt>
            <dd>
              <t>
  Requesters MUST <bcp14>MUST</bcp14> include answers, either directly or via a link to some a document
with the answers, to the following questions in the explanation
of the proposed use of the IANA IfType:

      <list style="symbols">
        <t>How

              </t>
              <ul spacing="normal">
                <li>How would IP run over your ifType?</t>
        <t>Would ifType?</li>
                <li>Would there be another interface sublayer sub-layer between your
		ifType and IP?</t>
        <t>Would IP?</li>
                <li>Would your ifType be vendor-specific or vendor specific / proprietary? (If so, the label
MUST
<bcp14>MUST</bcp14> start with a string that shows that. For example, if your company’s company's
name or acronym is xxx, then the ifType label would be something like
xxxSomeIfTypeLabel.)</t>
        <t>Would
xxxSomeIfTypeLabel.)</li>
                <li>Would your ifType require or allow vendor-specific extensions?  If so,
would the vendor use their own ifType in a sub-layer below the requested ifType,
or
a sub-type of the ifType, or some other mechanism?</t>
      </list>
  </t>
  <t hangText='Reference, mechanism?</li>
              </ul>
            </dd>

            <dt>Reference, Internet-Draft, or Specification:'> Specification:</dt>
            <dd>
  A link to some a document is required.</t>
  <t hangText='Additional required.</dd>
            <dt>Additional information or comments:'>
  Optionally comments:</dt>

            <dd>
  Optional; any additional comments for IANA or the Designated Expert.</t>
</list></t> designated expert.</dd>
          </dl>
        </section>
        <section anchor="tunneltype-template" title="tunnelType"> numbered="true" toc="default">
          <name>tunnelType</name>
          <t>Prior to this document, no form existed for tunnelType (and new tunnelType requests did not
need to use the ifType form that did exist). This document therefore specifies a tunnelType
form.</t>
          <t>The following template describes the fields that MUST <bcp14>MUST</bcp14> be supplied in a
registration request suitable for adding to the tunnelType "Tunnel Types (tunnelType)" registry:</t>

<t><list style="hanging">
  <t hangText='Label
          <dl newline="false" spacing="normal">
            <dt>Label for IANA tunnelType requested:'> requested:</dt>
            <dd>
  As explained in Section 7.1.1 of <xref target="RFC2578"/>, target="RFC2578" sectionFormat="of" section="7.1.1"/>, a label for a named-number enumeration
must consist of one or more letters or digits, up to a maximum of 64 characters, and
the initial character must be a lower-case lowercase letter. (However, labels longer than 32
characters are not recommended.) Note that hyphens are not allowed.</t>
  <t hangText='Name allowed.</dd>
            <dt>Name of IANA tunnelType requested:'> requested:</dt>
            <dd>
  A short description (e.g., a protocol name), name) suitable to appear in a comment in the registry.</t>
  <t hangText='Description registry.</dd>
            <dt>Description of the proposed use of the IANA tunnelType:'> tunnelType:</dt>
            <dd>
              <t>
  Requesters MUST <bcp14>MUST</bcp14> include answers, either directly or via a link to some a document
with the answers, to the following questions in the explanation
of the proposed use of the IANA tunnelType:

      <list style="symbols">
        <t>How

              </t>
              <ul spacing="normal">
                <li>How would IP run over your tunnelType?</t>
        <t>Would tunnelType?</li>
                <li>Would there be another interface sublayer sub-layer between your tunnelType and IP?</t>
        <t>Would IP?</li>
                <li>Would your tunnelType be vendor-specific or proprietary? (If so, the label
MUST
<bcp14>MUST</bcp14> start with a string that shows that. For example, if your company’s company's
name or acronym is xxx, then the tunnelType label would be something like
xxxSomeTunnelTypeLabel.)</t>
        <t>Would
xxxSomeTunnelTypeLabel.)</li>
                <li>Would your tunnelType require or allow vendor-specific extensions?  If so,
would the vendor use their own tunnelType in a sub-layer below the requested tunnelType,
or some sort of sub-type of the tunnelType, or some other mechanism?</t>
      </list>
  </t>
  <t hangText='Reference, mechanism?</li>
              </ul>
            </dd>
            <dt>Reference, Internet-Draft, or Specification:'> Specification:</dt>
            <dd>
  A link to some a document is required.</t>
  <t hangText='Additional required.</dd>
            <dt>Additional information or comments:'> comments:</dt>
            <dd>
  Optionally any additional comments for IANA or the Designated Expert.</t>
</list></t> designated expert.</dd>
          </dl>
        </section>
      </section>
    </section>
    <section anchor="iana-considerations" title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This entire document is about IANA considerations, but this section
      discusses actions taken by and to be taken by IANA.
There are three registries affected:</t>

<t><list style="numbers">
  <t>ifType definitions
      <ol spacing="normal" type="1">

        <li>Interface Types (ifType) <xref target="ifType-registry"/>: target="ifType-registry" format="default"/>: The registration process
 is updated in <xref target="procedures"/>, target="procedures" format="default"/>, and the template is updated in <xref target="iftype-template"/>.</t>
  <t>tunnelType definitions target="iftype-template" format="default"/>.</li>
        <li>Tunnel Types (tunnelType) <xref target="tunnelType-registry"/>: target="tunnelType-registry" format="default"/>: The registration
 process is updated in <xref target="procedures"/>, target="procedures" format="default"/>, and the template is updated in <xref target="tunneltype-template"/>.</t>
  <t>transmission numbers target="tunneltype-template" format="default"/>.</li>
        <li>Transmission Number Values <xref target="transmission-registry"/>: target="transmission-registry" format="default"/>:
 The assignment process is updated in <xref target="transmission-discussion"/>.</t>
</list></t> target="transmission-discussion" format="default"/>.</li>
      </ol>
<t>At the time of publication of this document, IANA is unable to
perform some of the actions requested below due to limitations of their current
platform and toolset. In such cases, IANA is requested to perform these actions
as and when the migration to a new platform that would enable
these actions is complete.
</t>
      <section anchor="module-formats" title="MIB numbered="true" toc="default">

<name>MIB and YANG Modules">

<t>The following actions are Modules</name>
<t>
   IANA is to be taken complete the following to clarify the relationship
   between MIB modules, YANG modules, and the relevant registries:</t>

<t><list style="numbers">
  <t>Add the registries.
</t>
        <ol spacing="normal" type="1">
          <li><t>The following note has been added to the entry for the IANAifType-MIB at
	  <xref target="protocol-registries"/>:
  “This target="protocol-registries" format="default"/>:
          "This is one of the available formats of the ifType Interface Types
	  (ifType) and tunnelType registries.”</t>
  <t>Change the Tunnel Types (tunnelType) registries."</t></li>
          <li><t>The note on the entry for the iana-if-type YANG module
	  at <xref target="protocol-registries"/> target="protocol-registries" format="default"/> has been
	  updated to read:
  “This
	  "This is one of the available formats of the ifType registry.”</t>
  <t>Change the Interface Types (ifType) registry."</t></li>
          <li><t>The note on the entry for the the iana-tunnel-type YANG
	  module at <xref target="protocol-registries"/> target="protocol-registries" format="default"/> has
	  been updated to read:
  “This
	  "This is one of the available formats of the tunnelType registry.”</t>
  <t>Create a section for “Interface Parameters” Tunnel Types (tunnelType) registry."</t></li>

          <li>The new "Interface Parameters" category at <xref target="protocol-registries"/>, with
	  target="protocol-registries" format="default"/> includes entries for
“Interface
	  "Interface Types (ifType)” (ifType)" <xref target="ifType-registry"/>, “Tunnel target="ifType-registry"
	  format="default"/>, "Tunnel Types (tunnelType)” (tunnelType)" <xref target="tunnelType-registry"/>,
	  target="tunnelType-registry" format="default"/>, and “Transmission Values” "Transmission
	  Number Values" <xref target="transmission-registry"/>.</t>
  <t>Update target="transmission-registry"
	  format="default"/>.</li>
          <li>Update the ifType definitions "Interface Types (ifType)" registry <xref target="ifType-registry"/>
	  target="ifType-registry" format="default"/> to list MIB <xref target="IANAifType-MIB"/>
	  target="IANAifType-MIB" format="default"/> and YANG <xref target="yang-if-type"/>
	  target="yang-if-type" format="default"/> as Available Formats.</t>
  <t>Update Formats.</li>
          <li>Update the tunnelType definitions "Tunnel Types (tunnelType)" registry <xref target="tunnelType-registry"/>
	  target="tunnelType-registry" format="default"/> to list MIB <xref target="IANAifType-MIB"/>
	  target="IANAifType-MIB" format="default"/> and YANG <xref target="yang-tunnel-type"/>
	  target="yang-tunnel-type" format="default"/> as Available Formats, and change the title to
“tunnelType Definitions” for consistency with the <xref target="ifType-registry"/> title.</t>
  <t>Replace
	  Formats.</li>
          <li>Replace the <xref target="yang-if-type"/> target="yang-if-type" format="default"/> page
	  with the YANG module content, content rather than having a page that itself claims
	  to have multiple Available Formats.</t>
  <t>Replace Formats.</li>
          <li>Replace the <xref target="yang-tunnel-type"/> target="yang-tunnel-type" format="default"/>
	  page with the YANG module content, content rather than having a page that itself
	  claims to have multiple Available Formats.</t>
</list></t>

<t>In addition Formats.</li>

        <li><t>In addition, <xref target="IANAifType-MIB"/> target="IANAifType-MIB" format="default"/> is to
	be updated as follows:</t>

<t>OLD:

        <t>OLD:</t>
<blockquote>
Requests for new values should be made to IANA via email (iana@iana.org).</t>

<t>NEW: (iana@iana.org).</blockquote>
        <t>NEW:</t>
<blockquote>
Interface types must not be directly added to the IANAifType-MIB MIB module.
They must instead be added to the “ifType definitions” "Interface Types (ifType)" registry at
<xref target="ifType-registry"/>.</t> target="ifType-registry" format="default"/>.</blockquote>
        <t>(Note that <xref target="yang-if-type"/> target="yang-if-type" format="default"/> was
	previously updated with this language.)</t>

</section>
<section anchor="transmission-number-assignments" title="Transmission Number Assignments">

<t>Per the discussion
	</li>

	<li>IANA has added this document as a reference in the "Interface Types
	(ifType)", "Tunnel Types (tunnelType)", and "Transmission Number
	Values" registries, as well as the iana-if-type
	YANG Module, iana-tunnel-type YANG Module, and IANAifType-MIB.</li>
        </ol>
      </section>
      <section anchor="transmission-number-assignments" numbered="true" toc="default">
        <name>Transmission Number Assignments</name>
        <t>Per the discussion in <xref target="transmission-discussion"/>, target="transmission-discussion"
	format="default"/>, <xref target="ifType-registry"/> is to be target="ifType-registry" format="default"/>
	has been updated as follows:</t>

<t>OLD:
        <t>OLD:</t>
<blockquote>
For every ifType registration, the corresponding transmission
number value should be registered or marked “Reserved.”</t>

<t>NEW: "Reserved".</blockquote>
        <t>NEW:</t>
<blockquote>
For future ifType assignments, an OID-subtree assignment MIB-II’s
‘transmission’ MIB-II's
'transmission' subtree will be made with the same value.</t> value.</blockquote>
        <t>Similarly, the following change is to be has been made to <xref target="transmission-registry"/>:</t>

<t>OLD: target="transmission-registry" format="default"/>:</t>
        <t>OLD:</t>
<blockquote>
For every transmission number registration, the corresponding
ifType value should be registered or marked “Reserved.”</t>

<t>NEW: For "Reserved".</blockquote>
        <t>NEW:</t> <blockquote>For future transmission number assignments, an ‘ifType’ 'ifType' will be made with the same value.</t> value.</blockquote>
      </section>
    </section>
    <section anchor="security-considerations" title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>Since this document does not introduce any technology or protocol,
there are no security issues to be considered for this document
itself.</t>
      <t>For security considerations related to MIB and YANG modules that
expose these values, see Section 9 of <xref target="RFC2863"/>, Section 6 of <xref target="RFC4087"/>, target="RFC2863" sectionFormat="of" section="9"/>, <xref target="RFC4087" sectionFormat="of" section="6"/>,
and Section 3 of <xref target="I-D.ietf-softwire-iftunnel"/>.</t> target="RFC8675" sectionFormat="of" section="3"/>.</t>
    </section>
  </middle>
  <back>

    <references title='Normative References'>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2863.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5378.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2578.xml"/>
      </references>
      <references>
        <name>Informative References</name>

        <reference  anchor="RFC2863" target='https://www.rfc-editor.org/info/rfc2863'> anchor="ifType-registry" target="https://www.iana.org/assignments/smi-numbers">
          <front>
<title>The Interfaces Group MIB</title>
<author initials='K.' surname='McCloghrie' fullname='K. McCloghrie'><organization /></author>
<author initials='F.' surname='Kastenholz' fullname='F. Kastenholz'><organization /></author>
<date year='2000' month='June' />
<abstract><t>This memo discusses the 'interfaces' group of MIB-II, especially the experience gained from the definition of numerous media-specific MIB modules for use in conjunction with the 'interfaces' group for managing various sub-layers beneath the internetwork-layer.  It specifies clarifications to, and extensions of, the architectural issues within the MIB-II model of the 'interfaces' group.  [STANDARDS-TRACK]</t></abstract>
            <title>Interface Types (ifType)</title>
            <author>
              <organization>IANA</organization>
            </author>
          </front>
<seriesInfo name='RFC' value='2863'/>
<seriesInfo name='DOI' value='10.17487/RFC2863'/>
        </reference>

        <reference  anchor="RFC2119" target='https://www.rfc-editor.org/info/rfc2119'> anchor="IANAifType-MIB" target="http://www.iana.org/assignments/ianaiftype-mib">
          <front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></author>
<date year='1997' month='March' />
<abstract><t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
            <title>IANAifType-MIB Definitions</title>
            <author>
              <organization>IANA</organization>
            </author>
          </front>
<seriesInfo name='BCP' value='14'/>
<seriesInfo name='RFC' value='2119'/>
<seriesInfo name='DOI' value='10.17487/RFC2119'/>
        </reference>

        <reference  anchor="RFC8174" target='https://www.rfc-editor.org/info/rfc8174'> anchor="yang-if-type" target="http://www.iana.org/assignments/iana-if-type">
          <front>
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
<author initials='B.' surname='Leiba' fullname='B. Leiba'><organization /></author>
<date year='2017' month='May' />
<abstract><t>RFC 2119 specifies common key words that may be used in protocol  specifications.  This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the  defined special meanings.</t></abstract>
            <title>iana-if-type YANG Module</title>
            <author>
              <organization>IANA</organization>
            </author>
          </front>
<seriesInfo name='BCP' value='14'/>
<seriesInfo name='RFC' value='8174'/>
<seriesInfo name='DOI' value='10.17487/RFC8174'/>
        </reference>

        <reference  anchor="RFC8126" target='https://www.rfc-editor.org/info/rfc8126'>
<front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
<author initials='M.' surname='Cotton' fullname='M. Cotton'><organization /></author>
<author initials='B.' surname='Leiba' fullname='B. Leiba'><organization /></author>
<author initials='T.' surname='Narten' fullname='T. Narten'><organization /></author>
<date year='2017' month='June' />
<abstract><t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters.  To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper.  For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t><t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed.  This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t><t>This is the third edition of this document; it obsoletes RFC 5226.</t></abstract>
</front>
<seriesInfo name='BCP' value='26'/>
<seriesInfo name='RFC' value='8126'/>
<seriesInfo name='DOI' value='10.17487/RFC8126'/>
</reference>

<reference  anchor="RFC5378" target='https://www.rfc-editor.org/info/rfc5378'>
<front>
<title>Rights Contributors Provide to the IETF Trust</title>
<author initials='S.' surname='Bradner' fullname='S. Bradner' role='editor'><organization /></author>
<author initials='J.' surname='Contreras' fullname='J. Contreras' role='editor'><organization /></author>
<date year='2008' month='November' />
<abstract><t>The IETF policies about rights in Contributions to the IETF are designed to ensure that such Contributions can be made available to the IETF and Internet communities while permitting the authors to retain as many rights as possible.  This memo details the IETF policies on rights in Contributions to the IETF.  It also describes the objectives that the policies are designed to meet.  This memo obsoletes RFCs 3978 and 4748 and, with BCP 79 and RFC 5377, replaces Section 10 of RFC 2026.  This document  specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
</front>
<seriesInfo name='BCP' value='78'/>
<seriesInfo name='RFC' value='5378'/>
<seriesInfo name='DOI' value='10.17487/RFC5378'/>
</reference>

<reference  anchor="RFC2578" target='https://www.rfc-editor.org/info/rfc2578'>
<front>
<title>Structure of Management Information Version 2 (SMIv2)</title>
<author initials='K.' surname='McCloghrie' fullname='K. McCloghrie' role='editor'><organization /></author>
<author initials='D.' surname='Perkins' fullname='D. Perkins' role='editor'><organization /></author>
<author initials='J.' surname='Schoenwaelder' fullname='J. Schoenwaelder' role='editor'><organization /></author>
<date year='1999' month='April' />
<abstract><t>It is the purpose of this document, the Structure of Management Information Version 2 (SMIv2), to define that adapted subset, and to assign a set of associated administrative values.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='STD' value='58'/>
<seriesInfo name='RFC' value='2578'/>
<seriesInfo name='DOI' value='10.17487/RFC2578'/>
</reference>

    </references>

    <references title='Informative References'>

<reference anchor="ifType-registry" target="https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-5">
  <front>
    <title>ifType definitions</title>
    <author >
      <organization>IANA</organization>
    </author>
    <date year="2019" month="June" day="25"/>
  </front>
</reference>
<reference anchor="IANAifType-MIB" target="http://www.iana.org/assignments/ianaiftype-mib">
  <front>
    <title>IANAifType-MIB</title>
    <author >
      <organization>IANA</organization>
    </author>
    <date year="2019" month="February" day="08"/>
  </front>
</reference>
<reference anchor="yang-if-type" target="http://www.iana.org/assignments/iana-if-type">
  <front>
    <title>iana-if-type YANG Module</title>
    <author >
      <organization>IANA</organization>
    </author>
    <date year="2019" month="February" day="08"/>
  </front>
</reference>
<reference anchor="yang-tunnel-type" target="https://www.iana.org/assignments/iana-tunnel-type"> anchor="yang-tunnel-type" target="https://www.iana.org/assignments/iana-tunnel-type">
          <front>
            <title>iana-tunnel-type YANG Module</title>
    <author >
            <author>
              <organization>IANA</organization>
            </author>
    <date year="2019" month="June" day="25"/>
          </front>
        </reference>

        <reference anchor="protocol-registries" target="https://www.iana.org/protocols">
          <front>
            <title>Protocol Registries</title>
    <author >
            <author>
              <organization>IANA</organization>
            </author>
    <date year="2019" month="June" day="25"/>
          </front>
        </reference>

        <reference anchor="tunnelType-registry" target="https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-6"> target="https://www.iana.org/assignments/smi-numbers">
          <front>
    <title>Internet-standard MIB - mib-2.interface.ifTable.ifEntry.ifType.tunnelType</title>
    <author >
            <title>Tunnel Types (tunnelType)</title>
            <author>
              <organization>IANA</organization>
            </author>
    <date year="2019" month="June" day="25"/>
          </front>
        </reference>

        <reference anchor="transmission-registry" target="https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-7"> target="https://www.iana.org/assignments/smi-numbers">
          <front>
    <title>transmission definitions</title>
    <author >
            <title>Transmission Number Values</title>
            <author>
              <organization>IANA</organization>
            </author>
    <date year="2019" month="June" day="25"/>
  </front>
</reference>

<reference  anchor="RFC1573" target='https://www.rfc-editor.org/info/rfc1573'>
<front>
<title>Evolution of the Interfaces Group of MIB-II</title>
<author initials='K.' surname='McCloghrie' fullname='K. McCloghrie'><organization /></author>
<author initials='F.' surname='Kastenholz' fullname='F. Kastenholz'><organization /></author>
<date year='1994' month='January' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community.  In particular, it describes managed objects used for managing Network Interfaces. [STANARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='1573'/>
<seriesInfo name='DOI' value='10.17487/RFC1573'/>
</reference>

<reference  anchor="RFC7224" target='https://www.rfc-editor.org/info/rfc7224'>
<front>
<title>IANA Interface Type YANG Module</title>
<author initials='M.' surname='Bjorklund' fullname='M. Bjorklund'><organization /></author>
<date year='2014' month='May' />
<abstract><t>This document defines the initial version of the iana-if-type YANG module.</t></abstract>
          </front>
<seriesInfo name='RFC' value='7224'/>
<seriesInfo name='DOI' value='10.17487/RFC7224'/>
</reference>

<reference  anchor="RFC2667" target='https://www.rfc-editor.org/info/rfc2667'>
<front>
<title>IP Tunnel MIB</title>
<author initials='D.' surname='Thaler' fullname='D. Thaler'><organization /></author>
<date year='1999' month='August' />
<abstract><t>This memo defines a Management Information Base (MIB) for use with network management protocols in the Internet community.  In particular, it describes managed objects used for managing tunnels of any type over IPv4 networks.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='2667'/>
<seriesInfo name='DOI' value='10.17487/RFC2667'/>
</reference>

<reference  anchor="RFC4087" target='https://www.rfc-editor.org/info/rfc4087'>
<front>
<title>IP Tunnel MIB</title>
<author initials='D.' surname='Thaler' fullname='D. Thaler'><organization /></author>
<date year='2005' month='June' />
<abstract><t>This memo defines a Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing tunnels of any type over IPv4 and IPv6 networks.  Extension MIB modules may be designed for managing protocol-specific objects. Likewise, extension MIB modules may be designed for managing security-specific objects.  This MIB module does not support tunnels over non-IP networks.  Management of such tunnels may be supported by other MIB modules.  This memo obsoletes RFC 2667.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4087'/>
<seriesInfo name='DOI' value='10.17487/RFC4087'/>
</reference>

<reference  anchor="RFC3637" target='https://www.rfc-editor.org/info/rfc3637'>
<front>
<title>Definitions of Managed Objects for the Ethernet WAN Interface Sublayer</title>
<author initials='C.M.' surname='Heard' fullname='C.M. Heard' role='editor'><organization /></author>
<date year='2003' month='September' />
<abstract><t>This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets.  In particular, it defines objects for managing the Ethernet Wide Area Network (WAN) Interface Sublayer (WIS).  The MIB module defined in this memo is an extension of the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface MIB and is implemented in conjunction with it and with the Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB, the Interfaces Group MIB, and the Inverted Stack Table MIB.</t></abstract>
</front>
<seriesInfo name='RFC' value='3637'/>
<seriesInfo name='DOI' value='10.17487/RFC3637'/>
</reference>

<reference  anchor="RFC5066" target='https://www.rfc-editor.org/info/rfc5066'>
<front>
<title>Ethernet in the First Mile Copper (EFMCu) Interfaces MIB</title>
<author initials='E.' surname='Beili' fullname='E. Beili'><organization /></author>
<date year='2007' month='November' />
<abstract><t>This document defines Management Information Base (MIB) modules for use with network management protocols in TCP/IP-based internets. This document describes extensions to the Ethernet-like Interfaces MIB and Medium Attachment Unit (MAU) MIB modules with a set of objects for managing Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL, defined in IEEE Std 802.3ah-2004 (note: IEEE Std 802.3ah-2004 has been integrated into IEEE Std 802.3- 2005).  In addition, a set of objects is defined, describing cross- connect capability of a managed device with multi-layer (stacked) interfaces, extending the stack management objects in the Interfaces Group MIB and the Inverted Stack Table MIB modules.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='5066'/>
<seriesInfo name='DOI' value='10.17487/RFC5066'/>
</reference>

<reference  anchor="RFC3635" target='https://www.rfc-editor.org/info/rfc3635'>
<front>
<title>Definitions of Managed Objects for the Ethernet-like Interface Types</title>
<author initials='J.' surname='Flick' fullname='J. Flick'><organization /></author>
<date year='2003' month='September' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community.  In particular, it defines objects for managing Ethernet-like interfaces.  This memo obsoletes RFC 2665.  It updates that specification by including management information useful for the management of 10 Gigabit per second (Gb/s) Ethernet interfaces.</t></abstract>
</front>
<seriesInfo name='RFC' value='3635'/>
<seriesInfo name='DOI' value='10.17487/RFC3635'/>
</reference>

<reference  anchor="RFC4380" target='https://www.rfc-editor.org/info/rfc4380'>
<front>
<title>Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)</title>
<author initials='C.' surname='Huitema' fullname='C. Huitema'><organization /></author>
<date year='2006' month='February' />
<abstract><t>We propose here a service that enables nodes located behind one or more IPv4 Network Address Translations (NATs) to obtain IPv6 connectivity by tunneling packets over UDP; we call this the Teredo service.  Running the service requires the help of &quot;Teredo servers&quot; and &quot;Teredo relays&quot;.  The Teredo servers are stateless, and only have to manage a small fraction of the traffic between Teredo clients; the Teredo relays act as IPv6 routers between the Teredo service and the &quot;native&quot; IPv6 Internet.  The relays can also provide interoperability with hosts using other transition mechanisms such as &quot;6to4&quot;.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4380'/>
<seriesInfo name='DOI' value='10.17487/RFC4380'/>
</reference>

<reference  anchor="RFC1234" target='https://www.rfc-editor.org/info/rfc1234'>
<front>
<title>Tunneling IPX traffic through IP networks</title>
<author initials='D.' surname='Provan' fullname='D. Provan'><organization /></author>
<date year='1991' month='June' />
<abstract><t>This memo describes a method of encapsulating IPX datagrams within UDP packets so that IPX traffic can travel across an IP internet. [STANDARDS-TRACK] This memo defines objects for managing DS1 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='1234'/>
<seriesInfo name='DOI' value='10.17487/RFC1234'/>
</reference>

<reference anchor="I-D.ietf-softwire-iftunnel">
<front>
<title>Tunnel Interface Types YANG Module</title>

<author initials='M' surname='Boucadair' fullname='Mohamed Boucadair'>
    <organization />
</author>

<author initials='I' surname='Farrer' fullname='Ian Farrer'>
    <organization />
</author>

<author initials='R' surname='Asati' fullname='Rajiv Asati'>
    <organization />
</author>

<date month='June' day='13' year='2019' />

<abstract><t>This 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.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-ietf-softwire-iftunnel-07' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-softwire-iftunnel-07.txt' />
        </reference>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.1573.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7224.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2667.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4087.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3637.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5066.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3635.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4380.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.1234.xml"/>
         <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8675.xml"/>
      </references>
    </references>

  </back>

<!-- ##markdown-source:
H4sIAF0cIV4AA+VdW3MbuZV+ZxX/A1Z6sJQlaUuyZY92K45ieSaq8i22nNlU
pWoLZIMk4mY3t9Etiqvyf99zAxpoNm2Pk9lsalNTMyLZAA4OzuU7F3TG4/Fw
UNs6Nxfqp8ZmJreFcUoXmXpvFtbVla5tWah3VTkzWVPBb/OyUtdFbaq5nhl1
s13L8zdNUZicvxgO9HRamdsLZef4RTT3cJCVs0KvYMGs0vN6XC91bqqxndfw
4Lgyi/Gjp8PBTNdmUVbbCzWdrYeDZp3BF+5CnT47PxsOhgO7ri5UXTWuPn30
6IdHp7BiZfQFU1aYejj4ZLabssrar8ZXuB4OdjUQ/J86LwugYos0re3FcKBU
NYddunqb+++VqstZ/LctMlPU4RtXVnVl5q79YrtKP9eVnbXPz8rVCsa3v9sC
udKuYO7qcQ58H8NE0zKHB8flb/4VfwK2rfR6bYuFPK2bellWSPcYf6f/2QJG
XE3UDTE1fM38vtK3pvtLWS10Yf+bTvlCvbazqnQlckl+NyttczgqPqXfrfwD
E9hJ78rvy5V2M100O4sXPb+ly18Dc9eGOLxDQMVjf7fAz7w6SEEB0riC0beG
zo+lDYUIRXd7wbO0jPJrwlKXby75C5H+A5HUzMxtYZEed8APoOSB4D06+WH8
6Hx8+kSG6Wph4GCXdb12Fw8fbjabidWFnsD0D7VzdlHQST90KzsumtXUVMnf
k7tlvcoPo2/GNDMSJtt4ff37X7SDdGgP9afjR892qf8S8filaObKTnHsVhcL
UNYxfvfL+AtT+YHqz5dvflKvy6zJzd+NTj95oLImi/SdlEaDv0Ltd8hEdwUc
vq5KsC9l7qXXgrn7JVS/k/HecMP47yfWE8NGiQj9fs0KBpjsrq4yBeKpxgok
anw6sd6XTEB29TTH/74sYI0Jy/KkXf5/WyHPafeVLuBLmKAsvm//8Qz/SPvy
FE3meDxWeoqOfUa+8GZpHfqWBmdDIbwFT+3UIgUD69T/w66dUZtlqcDrypaK
xUgxe0xFH4YDeNLc6rwBA10s4p2rcq4Ks1Hh7FVNOOJIrPCBwmHGHdPiLAD8
yAQpNsBpu7CFzqNJcc4afkL+dyZW/thgHwbZnQHogUcb2ASMohEvgCzYMuMd
p5yZ8R9IAOn/ivTfjegbV8I/KwP+vJg3dK4a/CLocXlrgD12ZSYeEPHONgYY
pbPMZCoHAqqR2th6SQQ78I9A4X81tjJ0pLSCzvNyxuBrXeZ2tlXaocNLGIaO
Pj4+gUnq/Y8vCCmN/OHxofLPGR2uLmASOEvihAssssRiFpOVzbLc4Kfh4BBh
VAUsILao+0OLHz+zBAnTr4Pvgd0t7WyJ7Kk1IAPaJ8IaZHfnbI74yI/lyEfD
wUa7cMD5lo8YqLaw7P1z2NrJk6dnnz8DP5SGc1prODODJmU44DMCnAaqs4SD
CDwOgNWpn6qyWZMFOrr+EYk9lqOdKEVboS/lO7VBrrtm6uB8gMNAjmcichZ4
P2uqin9wazOzc+sp/RegFM/g8+eRmjY1kAFP49kDF3iN4QDPqSgVANEFUJtw
q8PRCWwBNEtno75fgRDYPIzF8UDAdMtPpCwK2/xgVzbXVb4dCUefnp4+Bo7O
AELz1hQplc6HA14pwfuxP2QJQ5KEEQoUgBQCdrtL0cQLjH862kirpTBU10Ba
B84hJ1OtYZEBXXEl4OH12mg0Pcj/aQnP3d/HaAVFRmhtkRIh7gYMCTD/Fggi
Vca1UzD1+TNRfpmD5WsWTIHtUL1fbLVqJWrEpqe14ESUWKKOavjtgekoSpAg
lK26jCZzZGN1sVUlyfsKHMSCjIhamdkSoLVbwXlfFr0zK4DiakpmEAyiZrnj
X4AWjY5J40JgxMrpX8EgqiNcmv8esRT4D6aeTY5HTI5TIHA1z9EUFhRHWcT0
qBzVztToT7RaAIQvuvZNHZnJYjIiFhbq7fXV8Qg4rJxdrfMtCzeTa+7WYH1J
ytBqgthevrvG01AfrxWeKJzGrQWI4cXv5uObNy9fkergse2YmNPz86cgL0dF
uYEtujI3NU/PPz9+9Ax+PgZTxWbO600ElVq5OLq/70FQHWmMBopEQgz8FZFk
7+hp70gVO43hgNx1O7mIFEiRzjd66/D8+XCAbfg1TiMOh06GZiSlmkcTTNgn
3JhqZYsyLxdbz1kIuxXG3U4dvP744eZgxP9Vb97S3+9f/vHj9fuXV/j3hz9c
vnoV/uAnhgP49PbjK3kA/2qHvnj7+vXLN1c8Gr5Vna9eX/4ZZ0CuHLx9d3P9
9s3lqwM81DrxkqhPsFPcOYobYAI6PBQDN6vsFLUBBv3+xTt18thb8pOTH+DI
+MOzk6doLjdLU7D9KwuQR/4I/APRJFNEs4AtAD1b2xqM1AgXcctyUyjQViNM
BOAOqHfldtEY4AVAXM6wZs5LgAQbOgrnGooOhoOTibp0aB289LJf/sxuIsCk
4PFR2jeVrWtTsC3Fs4I5CXSKB5t1jAzvUc9m/Ci6uhT7LGFSILTJCVnBRMgK
MCtIa4ydyMPGG5yBF0KrgBsEEWcRcxHok88VRUjKtvkBNa/KFe2RDEU5J8tg
QF/AGCAGxc3it7GtIYafTsjNi8XFpVLsBfAAAV4zHed6C76M8R58rDmzhdsz
YpE3Bk4XHofH6rLM2NEv4C8gQoORMoR0yRehJSHKJjQF8QFZYd2scc6fHqzD
q4rDOZuAs8atRA4n5U4E3JiuXRck5ydMdLUFokHmYcgtxlsj1hBCgytNdjs6
fMBnBQoiY2wQDPY0/KxDk69UFwbz+eOgjgCQzS7iGUglYFYYgd/SbEaDTbUJ
dPFWc7KXc0KQ8O0xH3LEG1T6aNP9e94F+3CgRBMSx9oD5uLWlo0D/gJ0o8DI
uUjBRLlgT7OlmX1iyeaASWikc+Kz2AI+mpHthelAvyr0stoFIE8nutKZ8Yg6
ZwhQLyMHs9S3yGia7E6ZqiorJ0TD0tOq/IT2DoJ54N79fRvKoQvKMvGiQD6d
MKjOWlagObyukoVsvYufxHP7T6DIwJTwuBPNCvyP2Oa0pU2AsK9sTeoHoNip
W6s53cdChbqkgQNT4hsrD4efPJCCSj84RBya0QwydydAQ8XmxzYsdQJ+Iqny
JjcTg9NhGG33HIQrDunFp4Kb70sVAJeXmHhdmAKiSzznqTGFj+/Y8SBeogUR
A4qWh/iPrQrIWpAxtnBZqjrAK2GGqNGqcShLn4hlwGf4N6heC9jlaebuUme4
hGuAOWIPMwWWOc/YXl06mh9t/IhBOxp9mF2Qx5VB2aD9vLxbG4B/QFkG7iQj
sSedpol69lWZHJQSpCqOS/fMiqsi/zqyOQkHiHY8C0FYciJiMeBPOcjDKLD5
ABb+VWvw8SM7n/vD1ijjoJ/Rtq2ADxbse+wn6FSAOHDSRHxhanCunxT9DCJN
Zi0878F3ZUAzHCsY4EsLIg74YDioyo23UZIXY38tD4iYRAGRnX8AW/KJH50a
VA6UbTwHQd9bVupmvcEcHGFHmIk++P3csU7lnAVZ2jVyu96gwAJBCPs+cGJE
nU1OJicor/f3IdD1mQaYr8S8UOA3C50MRa92MjnlfA0YKAyCw8BEBHxiqY1e
KBYXhk8gBCWjPkOLZFA+LLl9RFgutrtRMotN73pZaedjM4DBAj8ceWkwlSjp
VLiBqGQE8QbOSrMZyu0MB/GmI0g1SjwnGW8ck5WAklHAO1Dki2AoBLmBJRjm
IrTMLSP4BFrhfB/Q4nkQtdIeALToBQzdj6iMDE4YIzKUODo5OzmWscMBj3Pt
QDSvuBuS4Qh8oBCTdfNiKV70IayC5IWUDIlpSHEHoBkKON4csJ8FtpiCAm04
IayZodQQV8ioR6PoUYn+6DTJzMLM1+98Ag5JItfq1mXBWFc86O7WiY3IouCU
WDKK2zKHXfap/X6FD3NQAARClDdgDY9o9jlsE870GPFpUBOfwtyvjcOBV8eW
ghHqNzkWYjJOqBeVXrVOGWHq2AOTgEzZXpVz1Ck41Sg9OxJicXkOeM/OzzAe
dkH5H09ORkkwHP0GhkGiMH7gyaPz8+4DxOgrErOKQPI+wI3a3OQZOnLKz4oD
59wB5phKVGjQiqpcVxaxojgPC+7OmAxl/jIyuzCk9cRkIBGsQuAATtNYcaTZ
ttArEKKY9x6AHNmJmXi4YQusaWBakWen9C//xCg3PIAlbZDlpS4WRoUs8bGi
7MfeA/eL8skKcg6bASZeBk7F2RwG4IXsh6UK7CAFvlVjWNVYo8vCxOaVZsK0
ZglErzEPgZkWXATMk3McMvmtxbkaAvJzDHopLxNloqJcj5+4gqiEJOC68KfB
xgjnLDh1tJOzYuA39hSyYtYuLgGwrKCSwKNzMDAWZ4s9oJ+2BG9BntLbJBAT
QAMCGsE5gBKAG0G5QFkOj6mVXSzRy6f5vdSH1J3VxbtJeouXtrmtRWOZnWDm
wLKjl8D0FrFOh2IJzR1IJb6R0mqidUTb6tavveaIfQk40RtfJAeFs7ayDlom
WGNuc6y8YOBqMLRAvvNMGDPrSJfoUIcDydKRb4AAPIMBzCV+ijJKnn0k+d5Z
hJnEuIdCBRlBRG1UNqohJHCc+tOtCLBEiTYyvEwWDyKbrI8MLzGwKLZMXlfj
jpG7892FxNSoyNKQyDJE6+QzCWd1RMbb/2jmKCvqSj7jSG+wzWJDUTtqNp4i
MY8zri5J1hBWaKY46YTEWDSfhQMlBXx662YQKa/WZYWHj8MJH4lAszXeydDS
ieD+wVv0OG9/DlqBM4xNVDg0pO2YjAR6o5Bu7okbiA0Yu2DEaDatK55Lrpv3
43FOZBYkLXmoLnOsOKMz+BPFZpS7F7OV0YoUm3hmeM2oEfiRkEsWKcp7JmlU
EDWcd6QAeDg7JU+Cz0ZnW1ZdRSH6K2IyRcgo0ARFWK0yOydQUEtOm/PiWCVt
U/lkMuctSNJ5ZXRGVs1gyZyZNyNlNdpZCrZr6xj6MxlEJ3jYeVOQP8ZMc5IB
88fto8mM5x5hDCmGgOIWcjQit+SBczvTbdGUMg5MEG4QZww83Sk/BL1kB+lY
Cb0B/hLx3ewdKAImrEE+NVXlAlvBvTOkJMNJdEniJJC1Zw/95A8HG88LRwE9
ur0153JHcnK8z5ZplGzwEDOg8DhjF4QgSbdzKEGMorio3dM817cl6+xLFAvA
oOrIyF8v3ErPsqNz0DvrymfPHp2eyVdP4au5djWNOTo/PW4rOCC9ko+aGsqm
cEqbKPD1fY5VI4klwwtQ6yOb7FSUHZV0W38a+CXcAobPwmKYL6e12iNGKeaK
JcWRYIHKFpY+AWRJZjjDQFoyKjAHIpwdPnARr81BhiPQqsnWR8+Od0olXyoP
wbZ88M2VgzWZwoObUEb7ePUOk9YoU3FYt9bbvNQZ/Hf2yRBmQOGc6bVrctoA
zku4okADm9M88rA4WwyaT07PHh9PDijTeYOHUgr5ke8RiH727JFEqtR9EHaE
Qh6t7GQVx34alg1RWezPvEMExatNdNo+NpEyPZAnVS6mjqNP2KrnevKca9bo
klxEj4REhI7BldUPpxWwDf/Crpw5YRhCsbAvYUBWGkJgE0pZoaqT3QqqSj5M
koIgqXWZKD1HLWK5yjY3gwxYiY0PcXnUlhKaQuKIyIfRWWIMUH8DOwQCu2a1
0mhhYxec9scE99N6A5fCMnre+ypQ464gV5p9HAwm482mtGuTKXDAGp5GN187
cbbirZfgbULqXomfAKP8yaOxdQkkj+tyTH+M4CSKcXtodJBjPcOMOVia9gc4
cALjyQNYO85sZbyhD4+Lreox9ohyvDBSgSjdHefzxcenTQS8cVJlmSHEbFOq
L3NWmFJyplrRCfGT7ez4XVjQw7Sy5brHLA/bswm1l9Aax1X1KkokSary8hZg
MHHpRykj3B/6ogc+8RqhUafgocMYG+UsZVQnGTQc/MfrVyP1hxv894sPf5Le
oVzTlu+4bMq5mFDIgJ8kHE8Xp27sdvWv1f2QAbvl7RGm2dIGDqZJvo36J8F8
9JVvmIwVnCYGsVLD0vku+XurawiN+jkq3UJ9y4aGjW75yvpaqpc9wZEyNRfk
vcmR2rGnVVJD0iwm1bDQTROqHOCdVyuWU2rCCGVSsCJ1y23K4O9pGaWKR7cV
FTicc9EBh9NucSNRp5Qn1G86347Ibth5BCB6ODJRf4hhHmJNG9oMgUOxBHDT
VW97ruc9FZcOPhizGxC7lnEH0iWAz/X2bPzi3tRjnBNzjIayxthbpeNuIcbn
Hlunsp5UX7CWP8FT4B2NQ2EzaQewvgUjvqaRdONJE8eReC0yWgmQ4U6G03Ns
JOHQJLrwgQ1lEpC9pzBsRM9QKbvbtbnTo8mqUZW58WKLub5uoCeWL5TXKKlT
AhO1dcZHVsYnjGCZKQYIG0oCYookIHVYA2Py0umc5YZDuAwd8DovtytJKe00
T6qflxZtY82FI76ckZGMi55w0pgIAeAIQENdkUeiSFS6d15++EnV+hMlr8qQ
p2Q2piFuYGm5BpGkRCsCUWlZS5lhIEDfIBQgJegtryFGqzByX1NOCW0cfL41
2Riov3558yP6EcxI4wILbHukniKwLq4JoXJ0s+f+MCp1+noC5gc31i0FLfkI
oAs4doEzJr19i8oLqYSLaAY1wyKwMW38/Q1xrXQIfGtsq74ltOUSZ19gzUm2
wkfAKFhcSeUCfRoW+sQIHb20eaDj5Pa19BoSZbN8mxwlHRkowDmCL6WGUi6X
en8zQoiA+pCsQlWeadp1QL6VmdI4vZA2F+abJ5W5it4/NbeUHcHwbt1UWFTx
HTPfe4DRznhJjGx8Q0VYDG8ITfoPABjXFJSf84fF/TZccIFxIzVbltR6jdyK
ghGaVHpo3lXodwyVsCMj5yvgLbAH77nGtbrNvP57KhwrFTeXpFMJYJRWXkkP
7x6+dDBImwHdROP8pvuKUOwKRNK5xaL3FfqojkgpciECicTluAUhdOeoo7iV
06fPPIZjajUj1zFtIfx43HZw1Pso2WAb0hQLEsa3QQBtB2S3XpQoljAcBvAt
ifbQo2IuVZ/RjT05e/qs7fz5wH0le1emPHdJ3oACwAiX8rGRQa6PWU5LaaWu
CXj8zt/BwP0fAbaRSSWaCr3sVtP6vnuFj7lWf/n33vsc+MhDvmf1l9/SNj6u
ieCZsWvppO3byqjTGIjNO1JunPrvTeatMO2DmpKczxj7FhZUfypAGLAigDH+
TcnWSD/Teis3l0h2XlKyM+uLFR77SjOTNItsuOeMmoi750LzyYaoWOd/LFhc
seuEDlT7SU0WzhLIFCviTZUYKMkZJxjGo5FeqdAL7L2vQ+NTUjKOpU4gdRTP
eDNz05vQpr3LPRiTdN5ES6oZWHAIJrUX4re+6293QipB3BqX7EMY7RvH+prn
aVs9cVYcVLW98mjal1LZThjGafhu+Y9tR6X2NDuPvrZwGs3tW5xW4cx4hDjZ
Jv8cNR36cJ94ImkSQEvsFwXbyUUOGhvFMZ1oLsQ1lG3o7debmjlmldbNNPdA
KUzPtrgyof3yVmrywRVztgmRGtgKZ0OiMM6OYy9VyTJHu2gxxnDwZIKO0/Lt
kH6JkWYpzox58UkPVdKKvsQSFEU7VGpbiOyEkCFU859gUeeXqCw31gW1Hfk0
EuFoHBxg7R7px15W3gJPVaN/bNGzo7i+bVM6C01KTLkHvq9NZnXbifL2+mqM
ZarKxG30CIr39ZDhPLtCTfEb92b/NgCFqKDvc6R12q4fGv94mE8LYG/5HGmj
fCT6YjtrAOCpVUo9LO14JIgIXlfIGQACjPOGj70YX1qCjbIpLqXgwmN9EQa2
gJcllPojJXjLObU26Z5FH8iq/dzzeWx4cHx9/cCpBzEvH/BQPyzgAZ/lwNwB
JmmiQsiEh4SEgfUFe1uBJfatGKQnNB2KO0/JA32xPGtr7Fg8oWojPruuzBjI
b3D1Yiv0+e32HmNapqGgEwclVz79DvEYQ8pGZ3ghBYNaUsUVXfyCsIWOI4uu
jLXghEtjLDnR7UAfs1Et0SGcWqGjijViFOrLOiWZtSkll6+LhiLX7oWrcFR8
0ojdonY1uvyIu3yvOQQzF+ro5JgzgE6j3zJzsDMhATBv6oYyuejx7LyfnOHA
+toFdvUgh4oy8fXUekE/8U455U+lIQEyHsN2MhsTdXR6TIrasy7HdejlfGfH
TFczIwzllBbd3cgBSeeGKOA42Znqlg9BGMpuqw1QJMTi3PDGeyVvBSzFZEDb
2fEeXEFLIUlSJ2/7gON9DAfxeSYF3FDLo9y3iApFh9SA76+3BaTZOMxwZc3M
uzjO0XAnC+bDQUG2BIR77Jq/OKSOHh+zS6Q9wiGiUipGu2WVSVuSF/C44CJV
Y9oANR1yszc5LCkleuOevLzkxgd1YMt9HMfPHXri7g/lLQfJAzcJuA6xob8m
JNdysElafLZH3ljLyq1vDuqDm9h0ZzmgJ7lg2CKtHJ2bheRMXumptBDwBefk
dAjjX2DFy9xRxp6X9k7wadurS3eZnmC0RM0aYVJN8XImd8Uh0gab00IuMpCU
2eIrvBjrYaMNwh4IGWoqWWFdemGxr6FZc1y10nd21axwxPljtF946Zw6FtHs
0OV66vmiq6bt77wc2hfuJhmThPA6ID/B+hP1zt+eJTU6O6Vp26VCPBKl9ybH
6k1JUBx7ALZrkP72Oc0xEwnSG5Q67zr7OY4KBboY138FSkU9Y8jaYwz65cS5
6mh0xfIhL4Xx9jDJ7l9FEwso41ynCZdGQ1aGKSS63vubAJ3mU7ALGzoAaRDi
+lpOqSCMWTVX82q53u59D/I0OIIwh0hrqyEcCTNglNQYSGMRxOhrG+B7wBdU
FlXqN+jnxYxfv1NVw9BQbcumkr0+D4/+7K19ZUhydnoUfRN/8NzRNCSO1++6
s8VPwJzc5NDCH+6WW1fW1LraPldH15i04ZCcRJNf5ED8B2hS1b4/F+seZNd0
HfWqT9LWbHCEtD5G5WDgHnDYTaJEQfesKovtCr3S3d1d1Ikm9LJmtx0qcJqc
aM7tJ8bNOA4TvMx0Mi+gGPs54J0oLo4HvsMPcwcwEV2Oe065POAFLxQ8se8O
lPKrraKbDKwKbctU21bdJmvlzgPPmnYDihj5WxHYfdXmz0LJ/DnhEt98PerL
yX6IM2mi4706wTUDzpBwX0lbYIwTJpxZ4bc+4XRv16GrBR1XVJb0j7VWft81
mIl3X1HWHZwbfdh1Y+8q7OGsyxRPEoBqb1ZJa1E04RFqBSb5kwKZ5FUyS9gD
0IUAHl9Sl9OkiUnC8Ula4bj7tgrSVgqdfbbVJVeo6fLyavJ39MShnJumfr7g
inuKg33ueJdF/4wu+dfxyL+WQ97P8/9LTrml8p/YMSeb+Kpvbp9+/je65+iI
xUX3+KfooX8aLx3R/O2e+iYMEm/9ZWb8ag47WuMbnHbU7BQcN8kwvjvR3/yJ
fXjcHfX/wo/3vYAqXA/EGwJVSi03QnA1JxkUZY18etbfkodR8kIrvvaMDQtF
9FaekKSG4Ziritue5nNK4PoyUk9fTU+14WK3BikZBpYC276OaueWddskFTx9
9/FuuP7Zl38i4Uwp7C1L7FLJ1IVM8t9GZR8iCy926Mk2feES+YViym7SvPE+
Qr9y8fkwbVx7Lc1T94edpqNd7OXFqH2JCotSp/OgN1kav1NkONh9q5oM5Mvg
yWsQ+UUnWdbxawWhBvZ2X2ywovfn9La10cv7DvztcUJRbIba3slOC97XXsOB
jWDSNEGX/SgFiIRKP1BK6O5rMX0dai/JnF/U2XeTHrfBkSh+O6V7+u5+FWp7
sDdT/Bgopq4BekXILFQlD9rr/O8Ab4IjBZU6+AJtcn0+aoIhJTtI33fmwjvq
DvpfSnYQv/tYHUVNgQd766HcEYA9iMm7JPi+0sF+O+Brfh/bBqQvNDr20YsH
Qu/iQ8XYLWAFwuh4d1+h5nY7kf1bMSKa9pjhiK7+d2J9B21p5biPPrYus1bI
6c2c1GyIpx3RehW9nVOaIijCApixbYF2L1NxSmLE0wmgfLD1Ur/f4eAae7LC
XLESYfsJReZxrz5fUpL2Jhrrb76afI42167IqVNGPPR495/Rs17SUgb+A8m7
jt401FNZteGdLf4VjE58AbuIt6+uQoDF4Ctcu3BR4QNfpxPaesI7Z0DH4/Ye
vir05uXPF9E7QrjdNVQL8RKwD9P41Z7iijrOJ2nlv8FeaJrCl+ynJh3d9ybq
VnHwrl2P/BG5R20UvSN1nVcXeRbKQVNxrVg0cH4cVgBCSOzSG05CXLaVccos
SeE9vlv6RfQx6tWdbzrYH/n9Xvh6yMSLSfcL9dAkLTsJvvqWMhimT3SFb7Q5
eM/lu4z9DYkBri+lSo8AWmaM5AWFfUVwX/0eDtLy907lmwSzp97K7/Zo39mZ
YiAxa4GHXrz3I8kelvYVgL/CX3+b5e/C0b71u+x9wOs9+DZ+HWKqramwNLkb
Wfl3qsXZyNAfY+VFt9QDANh+tuQ3HEoqgVAEv8VTIibs3Pdr8av55Ch8dOZz
q/F6wD4ykeE6aJgijemUb36Vd/LtXDbh67f8DhRkhDOh+wlbc33C8YfOu3pG
4Zfz8AvfW8M3N0ev61HSQPP8enw1saaej+liOhg+/P9sINch5gffGTzVs0/D
wf8APr46f1diAAA=

-->
</rfc>