RFC 8892: Guidelines and Registration Procedures for Interface Types and Tunnel Types
In plain English — editorial summary, not part of the RFC
This document provides guidelines and procedures for those who are defining, registering, or evaluating definitions of new interface types ("ifType" 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.
Document record
- Document ID
- RFC8892
- Published
- August 2020
- Authors
- D. Thaler; D. Romascanu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 13
- Also known as
- —
- Updates:
- RFC 2863
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?