<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.thaler-iftype-reg" target="https://datatracker.ietf.org/doc/html/draft-thaler-iftype-reg-07">
   <front>
      <title>Guidelines and Registration Procedures for Interface Types and Tunnel Types</title>
      <author initials="D." surname="Thaler" fullname="Dave Thaler">
         <organization>Microsoft</organization>
      </author>
      <author initials="D." surname="Romascanu" fullname="Dan Romascanu">
         <organization>Independent</organization>
      </author>
      <date month="January" day="16" year="2020" />
      <abstract>
	 <t>This document provides guidelines and procedures for those who are
defining, registering, or evaluating definitions of new interface
types (&quot;ifType&quot; values) and tunnel types.  The original definition of
the IANA interface type registry predated the use of IANA
Considerations sections and YANG modules, so some confusion arose
over time.  Tunnel types were added later, with the same requirements
and allocation policy as interface types.  This document updates RFC
2863 and provides updated guidance for these registries.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-thaler-iftype-reg-07" />
   
</reference>
