RFC 8892 on Guidelines and Registration Procedures for Interface Types and Tunnel Types
rfc-editor@rfc-editor.org Fri, 28 August 2020 23:31 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D97A23A0DE5 for <ietf-announce@ietfa.amsl.com>; Fri, 28 Aug 2020 16:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YV4ZcjtttI-e for <ietf-announce@ietfa.amsl.com>; Fri, 28 Aug 2020 16:31:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F9373A0DDC for <ietf-announce@ietf.org>; Fri, 28 Aug 2020 16:31:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DDDE5F40768; Fri, 28 Aug 2020 16:31:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8892 on Guidelines and Registration Procedures for Interface Types and Tunnel Types
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200828233137.DDDE5F40768@rfc-editor.org>
Date: Fri, 28 Aug 2020 16:31:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ItCnUqMnkyFvzAJ-WGc5eFghASc>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Aug 2020 23:31:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8892
Title: Guidelines and Registration Procedures
for Interface Types and Tunnel Types
Author: D. Thaler,
D. Romascanu
Status: Standards Track
Stream: IETF
Date: August 2020
Mailbox: dthaler@microsoft.com,
dromasca@gmail.com
Pages: 13
Updates: RFC 2863
I-D Tag: draft-thaler-iftype-reg-07.txt
URL: https://www.rfc-editor.org/info/rfc8892
DOI: 10.17487/RFC8892
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.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC