Re: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice

"John Levine" <johnl@taugh.com> Sun, 05 June 2016 14:34 UTC

Return-Path: <johnl@taugh.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 74704127078 for <ietf@ietfa.amsl.com>; Sun, 5 Jun 2016 07:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 hnoaeKulsrdl for <ietf@ietfa.amsl.com>; Sun, 5 Jun 2016 07:34:07 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9F3D126BF7 for <ietf@ietf.org>; Sun, 5 Jun 2016 07:34:06 -0700 (PDT)
Received: (qmail 74979 invoked from network); 5 Jun 2016 14:34:04 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 5 Jun 2016 14:34:04 -0000
Date: 5 Jun 2016 14:33:42 -0000
Message-ID: <20160605143342.25017.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice
In-Reply-To: <20160605131713.6A4FB4AD1488@rock.dv.isc.org>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CcPHaWvbfdOAKzJi3cIyArX9G08>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 05 Jun 2016 14:34:08 -0000

>> Me too (for IMAP and other things). Maybe IANA is a starting point for
>> "advanced" users, but I think it does serve a very useful purpose for
>> developers.
>
>And same here for DNS types.

Yes, indeed.  There's no other reasonable way to figure out what some
random rrtype is supposed to do.  (Grepping the RFC collection, while
possible, is not reasonable.)

I'd say I look at IANA protocol registries a couple of times a month
both for DNS and other stuff.  No doubt there are programmers and
designers who never look at the registries, but there are also plenty
of them who never look at RFCs either.  Let's not go down that rat
hole.

R's,
John