Guidelines and Registration Procedures for Interface Types and Tunnel Types
draft-thaler-iftype-reg-05

Document Type Active Internet-Draft (individual in int area)
Last updated 2019-10-10 (latest revision 2019-10-03)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized bibtex
Reviews
Stream WG state (None)
Document shepherd Ian Farrer
Shepherd write-up Show (last changed 2019-09-30)
IESG IESG state In Last Call (ends 2019-11-07)
Consensus Boilerplate Yes
Telechat date
Responsible AD Suresh Krishnan
Send notices to (None)
IANA IANA review state IANA - Review Needed
Network Working Group                                          D. Thaler
Internet-Draft                                                 Microsoft
Updates: 2863 (if approved)                                 D. Romascanu
Intended status: Standards Track                             Independent
Expires: April 5, 2020                                  October 03, 2019

 Guidelines and Registration Procedures for Interface Types and Tunnel
                                 Types
                       draft-thaler-iftype-reg-05

Abstract

   The registration and use of interface types ("ifType" values)
   predated the use of IANA Considerations sections and YANG modules,
   and so confusion has arisen about the interface type allocation
   process.  Tunnel types were then added later, with the same
   requirements and allocation policy as interface types.  This document
   updates RFC 2863, and provides updated guidelines for the definition
   of new interface types and tunnel types, for consideration by those
   who are defining, registering, or evaluating those definitions.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 5, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Thaler & Romascanu        Expires April 5, 2020                 [Page 1]
Internet-Draft              ifType Guidelines               October 2019

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Problems  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Interface Sub-Layers and Sub-Types  . . . . . . . . . . . . .   4
     4.1.  Alternate Values  . . . . . . . . . . . . . . . . . . . .   5
   5.  Available Formats . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Registration  . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .   7
     6.2.  Media-specific OID-subtree assignments  . . . . . . . . .   8
     6.3.  Registration Template . . . . . . . . . . . . . . . . . .   9
       6.3.1.  ifType  . . . . . . . . . . . . . . . . . . . . . . .   9
       6.3.2.  tunnelType  . . . . . . . . . . . . . . . . . . . . .  10
   7.  Submitting Requests . . . . . . . . . . . . . . . . . . . . .  11
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     10.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   The IANA IfType-MIB was originally defined in [RFC1573] as a separate
   MIB module together with the Interfaces Group MIB (IF-MIB) module.
   The IF-MIB module has since been updated and is currently specified
   in [RFC2863], but this latest IF-MIB RFC no longer contains the IANA
   IfType-MIB.  Instead, the IANA IfType-MIB is now maintained as a
   separate module.  Similarly, [RFC7224] created an initial IANA
   Interface Type YANG Module, and the current version is maintained by
   IANA.

   The current IANA IfType registry is at [ifType-registry], with the
   same values also appearing in [yang-if-type], and the IANAifType
   textual convention at [IANAifType-MIB].

   Although the ifType registry was originally defined in a MIB module,
   the assignment and use of interface type values are not tied to MIB
   modules or any other management mechanism.  Interface type values can
   be used as values of data model objects (MIB objects, YANG objects,
Show full document text