Skip to main content

A YANG Data Model for Tunnel Interface Types

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: The IESG <>,, Yong Cui <>,,,,,
Subject: Protocol Action: 'Tunnel Interface Types YANG Module' to Proposed Standard (draft-ietf-softwire-iftunnel-07.txt)

The IESG has approved the following document:
- 'Tunnel Interface Types YANG Module'
  (draft-ietf-softwire-iftunnel-07.txt) as Proposed Standard

This document is the product of the Softwires Working Group.

The IESG contact persons are Éric Vyncke and Suresh Krishnan.

A URL of this Internet Draft is:

Ballot Text

Technical Summary

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.

Working Group Summary

During the publication process and IANA review of draft-ietf-softwire-yang, IANA  requested that the YANG module for the [iana-iftunnel registry was put into a separate document from softwire-yang. draft-ietf-softwire-iftunne was published containing just 
the module.

There’s no controversy in softwire wg on this doc.

Document Quality

Currently there’s no implementations of this doc, but some vendors will implement it to support softwire-yang and some functions.
This was a part of softwire-yang, which has been thoroughly  reviewed.

YANG doctors have reviewed this document and found not issue.

Please note that during the IETF wide last call, there was a comment about the poor/incomplete state of the IANA tunnel type registry (lacking some entries) and as this document refers to the IANA tunnel type registry, it was flagged as an issue. On the other hand, the expert in charge of this IANA registry has agreed that this should not be a blocking factor for this document.


Yong Cui is the Document Shepherd. 

Éric Vyncke is the Responsible AD.


There are multiple actions required by IANA as specified in the IANA considerations section of the document. It is about creating new registries and updating tunnel type registry.

RFC Editor Note