Re: I-D Action: draft-leiba-cotton-iana-5226bis-19.txt

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 10 January 2017 20:19 UTC

Return-Path: <ajs@anvilwalrusden.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 C2A45120727 for <ietf@ietfa.amsl.com>; Tue, 10 Jan 2017 12:19:20 -0800 (PST)
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] 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 W4LG8Av2tYeU for <ietf@ietfa.amsl.com>; Tue, 10 Jan 2017 12:19:19 -0800 (PST)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id 828B7129443 for <ietf@ietf.org>; Tue, 10 Jan 2017 12:19:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 8901F1151F for <ietf@ietf.org>; Tue, 10 Jan 2017 20:19:24 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GfKjoVsa60zA for <ietf@ietf.org>; Tue, 10 Jan 2017 20:19:23 +0000 (UTC)
Received: from mx2.yitter.info (192-0-220-231.cpe.teksavvy.com [192.0.220.231]) by mx2.yitter.info (Postfix) with ESMTPSA id B286A114EE for <ietf@ietf.org>; Tue, 10 Jan 2017 20:19:23 +0000 (UTC)
Date: Tue, 10 Jan 2017 15:19:14 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: I-D Action: draft-leiba-cotton-iana-5226bis-19.txt
Message-ID: <20170110201914.GK1426@mx2.yitter.info>
References: <148406571988.22226.2636377293389742409.idtracker@ietfa.amsl.com> <b82941e6-c551-f5c3-0ebd-cc0e9a95dfdb@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b82941e6-c551-f5c3-0ebd-cc0e9a95dfdb@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y0ihkN8EvvCbp7eQJWbm-Ssyy2s>
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: Tue, 10 Jan 2017 20:19:21 -0000

Hi,

On Wed, Jan 11, 2017 at 08:44:49AM +1300, Brian E Carpenter wrote:

> Sorry, but I find the replacement of "IANA" by "IANA Services" throughout
> the draft to be both ugly and plain wrong.

Well, we need something other than "IANA", because the IETF is but one
user of that mark, and the license that the IETF Trust gave to PTI
does not permit them to refer to themselves as "IANA".

Would "IANA Services Operator" do?

> But it doesn't matter: this document is about what IANA does.

I think that's not quite correct.  It's about what the IANA Services
Operator for the protocol parameters registries (and other registries
for which the IETF is policy authority) does.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com