A YANG Data Model for Tunnel Interface Types
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 16
- Abstract
- This document specifies the initial version of a YANG module "iana-tunnel-type", which contains 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 website. 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.
- Publication Date
- 2019-11-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC8675- Link
- https://doi.org/10.17487/RFC8675
- Author(s)
- Mohamed BoucadairIan FarrerRajiv Asati
- Keyword(s)
- Softwire, Augment Tunnel, Tunnel Management, Tunnel Provisioning, Tunnel Activation, Tunnel Automation
Latest version of IETF RFC 8675
Document Versions — IETF RFC 8675
-
▶ IETF RFC 8675 (2019-11-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IANA, "Structure of Management Information (SMI) Numbers (MIB Module Registrations)", <https://www.iana.org/assignments/smi-numbers>. EXTERNAL
- IETF RFC 3688 [Active*]
- IETF RFC 6241 [Active*]
- IETF RFC 6242 [Active*]
- IETF RFC 6991 [Superseded*]
- IETF RFC 7224 [Active*]
- IETF RFC 7950 [Active, Amended*]
- IETF RFC 8040 [Active*]
- IETF RFC 8341 [Active*]
- IETF RFC 8342 [Active*]
- IETF RFC 8446 [Superseded*]
Bibliographic Reference(s)
- IETF.draft-thaler-iftype-reg-06 — I-D.thaler-iftype-reg EXTERNAL
- IETF RFC 1701 [Active*]
- IETF RFC 1702 [Active*]
- IETF RFC 2003 [Active*]
- IETF RFC 2004 [Active*]
- IETF RFC 2107 [Active*]
- IETF RFC 2341 [Active*]
- IETF RFC 2529 [Active*]
- IETF RFC 2637 [Active*]
- IETF RFC 2661 [Active*]
- IETF RFC 3056 [Active*]
- IETF RFC 3618 [Active*]
- IETF RFC 4087 [Active*]
- IETF RFC 4213 [Active*]
- IETF RFC 4380 [Active*]
- IETF RFC 5214 [Active*]
- IETF RFC 5565 [Active*]
- IETF RFC 6333 [Active*]
- IETF RFC 6346 [Active*]
- IETF RFC 7676 [Active*]
- RFC7856 — RFC7856 EXTERNAL
- RFC7870 — RFC7870 EXTERNAL
- IETF RFC 8085 [Active*]
- IETF RFC 8340 [Active*]
- IETF RFC 8343 [Active*]
- RFC8676 — RFC8676 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8675.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 8675, A YANG Data Model for Tunnel Interface Types. Available at https://doi.org/10.17487/RFC8675
Snippet:
IETF RFC 8675, A YANG Data Model for Tunnel Interface Types. Available at https://doi.org/10.17487/RFC8675
HTML (ISO 690 compliant)
Preview:
IETF RFC 8675, A YANG Data Model for Tunnel Interface Types. Available at https://doi.org/10.17487/RFC8675
Snippet:
<span class="citation"><cite>IETF RFC 8675</cite>, A YANG Data Model for Tunnel Interface Types. Available at <a href="https://doi.org/10.17487/RFC8675" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8675</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8675, A YANG Data Model for Tunnel Interface Types
doi: 10.17487/RFC8675
url: https://doi.org/10.17487/RFC8675
doi: 10.17487/RFC8675
url: https://doi.org/10.17487/RFC8675
Snippet:
<li> <cite id="bib-rfc8675">IETF RFC 8675</cite>, A YANG Data Model for Tunnel Interface Types <span class="doi">10.17487/RFC8675</span> </li>
Referenced By
- IETF RFC 8892 [Active*]
- IETF RFC 8969 [Active*]
- IETF RFC 9907 [Active*]