RFC 8675: A YANG Data Model for Tunnel Interface Types
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8675
- Published
- November 2019
- Authors
- M. Boucadair; I. Farrer; R. Asati
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8539Softwire Provisioning Using DHCPv4 over DHCPv6Current
March 2019
- RFC 8026Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization MechanismCurrent
November 2016
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 6334Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack LiteCurrent
August 2011
- RFC 5619Softwire Security Analysis and RequirementsCurrent
August 2009
- RFC 5571Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2)Current
June 2009
- RFC 5512The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation AttributeObsoleted
April 2009
- RFC 6127IPv4 Run-Out and IPv4-IPv6 Co-Existence ScenariosCurrent
May 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?