Skip to main content

A YANG Data Model for Tunnel Interface Types
RFC 8675

Revision differences

Document history

Date By Action
2019-11-20
(System) IANA registries were updated to include RFC8675
2019-11-17
(System)
Received changes through RFC Editor sync (created alias RFC 8675, changed title to 'A YANG Data Model for Tunnel Interface Types', changed abstract to …
Received changes through RFC Editor sync (created alias RFC 8675, changed title to 'A YANG Data Model for Tunnel Interface Types', changed abstract to '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.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-11-17, changed IESG state to RFC Published)
2019-11-17
(System) RFC published