A YANG Data Model for Tunnel Interface Types
RFC 8675, “A YANG Data Model for Tunnel Interface Types”, is a Proposed Standard document published in November 2019 by M. Boucadair, I. Farrer, R. Asati. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8675 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8674 The "safe" HTTP Preference
- RFC 8676 YANG Modules for IPv4-in-IPv6 Address plus Port Softwires
- RFC 8673 HTTP Random Access and Live Content
- RFC 8677 Name-Based Service Function Forwarder Component within a Service Function Chaining Framework
- RFC 8672 TLS Server Identity Pinning with Tickets
- RFC 8678 Enterprise Multihoming using Provider-Assigned IPv6 Addresses without Network Prefix Translation: Requirements and Solutions
- RFC 8671 Support for Adj-RIB-Out in the BGP Monitoring Protocol
- RFC 8679 MPLS Egress Protection Framework