Re: Last Call: <draft-thaler-iftype-reg-05.txt> (Guidelines and Registration Procedures for Interface Types and Tunnel Types) to Proposed Standard
Russ Housley <housley@vigilsec.com> Thu, 10 October 2019 17:00 UTC
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 006091200E6 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2019 10:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 qqS2xhRMYr63 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2019 10:00:05 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 124CC1200DF for <ietf@ietf.org>; Thu, 10 Oct 2019 10:00:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 6C667300AF2 for <ietf@ietf.org>; Thu, 10 Oct 2019 13:00:03 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id uPqYpI7n-MJW for <ietf@ietf.org>; Thu, 10 Oct 2019 13:00:01 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id 32B3930021A; Thu, 10 Oct 2019 13:00:01 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Last Call: <draft-thaler-iftype-reg-05.txt> (Guidelines and Registration Procedures for Interface Types and Tunnel Types) to Proposed Standard
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <157072389716.20372.10161326732499866740.idtracker@ietfa.amsl.com>
Date: Thu, 10 Oct 2019 13:00:00 -0400
Cc: Suresh Krishnan <suresh@kaloom.com>, draft-thaler-iftype-reg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D650CB5-B751-430D-AA71-485F4C0775B8@vigilsec.com>
References: <157072389716.20372.10161326732499866740.idtracker@ietfa.amsl.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jliHzQfrfQP-VZn-IRB7TRWX1_s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Oct 2019 17:00:07 -0000
The IANA Considerations is one sentence: This entire document is about IANA considerations. I agree that the entire document is about IANA considerations; however, I think it would be useful to list the registries that are impacted, and how they are impacted. Russ > On Oct 10, 2019, at 12:11 PM, The IESG <iesg-secretary@ietf.org> wrote: > > > The IESG has received a request from an individual submitter to consider the > following document: - 'Guidelines and Registration Procedures for Interface > Types and Tunnel > Types' > <draft-thaler-iftype-reg-05.txt> as Proposed Standard > > The IESG plans to make a decision in the next few weeks, and solicits final > comments on this action. Please send substantive comments to the > ietf@ietf.org mailing lists by 2019-11-07. Exceptionally, comments may be > sent to iesg@ietf.org instead. In either case, please retain the beginning of > the Subject line to allow automated sorting. > > 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. > > > > > The file can be obtained via > https://datatracker.ietf.org/doc/draft-thaler-iftype-reg/ > > IESG discussion can be tracked via > https://datatracker.ietf.org/doc/draft-thaler-iftype-reg/ballot/ > > > No IPR declarations have been submitted directly on this I-D.
- Re: Last Call: <draft-thaler-iftype-reg-05.txt> (… Russ Housley
- Re: Last Call: <draft-thaler-iftype-reg-05.txt> (… S Moonesamy