Re: [Ianaplan] what *is* IANA?

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 11 September 2014 01:17 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7BE31A0114 for <ianaplan@ietfa.amsl.com>; Wed, 10 Sep 2014 18:17:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 7Z0JjHMUSuN5 for <ianaplan@ietfa.amsl.com>; Wed, 10 Sep 2014 18:17:56 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8B1F1A010E for <ianaplan@ietf.org>; Wed, 10 Sep 2014 18:17:53 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id fp1so4402832pdb.29 for <ianaplan@ietf.org>; Wed, 10 Sep 2014 18:17:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DXq/tLgmcej734DUpe9NL+/4654ODovfS/wB2ejofs8=; b=MI+lJ55zzsGgapVoCIBjbkqEg7uGH/1VkvqBvxG3Zb6O6nAZ+V2dyOEBvkvAYc1OLO hsElV/TNq3bPShoEEAq32aa1Bd6JJXspAWejTAHWe4lJSJz/COq7mMy3QBbreiLIwo0Y tgImC1iDlv6zu4QQiEoPzVrCa1rN9pjyatbxRy/k4YXiaiQ/c4EtdFzfnW9G8mnwtqic kzJY/EN/4Ud8KGqPaTUz2tlZ4O4KTagVLomdJmYUBKr6hbCq+blpPfSr5GN/wnq5PzxB /yhmTwnlEUb7RaIBtyfzUYq9Gds63tleTg12Rw1B4CPLydtlrBnNIvvRT9Hgi1F7wKaF YQTA==
X-Received: by 10.68.202.225 with SMTP id kl1mr42196154pbc.21.1410398273606; Wed, 10 Sep 2014 18:17:53 -0700 (PDT)
Received: from [192.168.178.23] (4.195.69.111.dynamic.snap.net.nz. [111.69.195.4]) by mx.google.com with ESMTPSA id ki1sm5107127pdb.59.2014.09.10.18.17.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Sep 2014 18:17:53 -0700 (PDT)
Message-ID: <5410F848.4000007@gmail.com>
Date: Thu, 11 Sep 2014 13:18:00 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <5410778D.5090407@cisco.com>
In-Reply-To: <5410778D.5090407@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/WeuiVWLED2-RqZPlxjFlfbXTS8Y
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>
Subject: Re: [Ianaplan] what *is* IANA?
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 01:17:58 -0000

On 11/09/2014 04:08, Eliot Lear wrote:
> I draw your attention to the footnote included in the final RFP:
> 
>>       In this RFP, "IANA" refers to the functions currently
>>       specified in the agreement between NTIA and ICANN
>>       [http://www.ntia.doc.gov/page/iana-functions-purchase-order] as
>>       well as any other functions traditionally performed by the IANA
>>       functions operator. SAC-067
>>       [https://www.icann.org/en/system/files/files/sac-067-en.pdf]
>>       provides one description of the many different meanings of the
>>       term “IANA” and may be useful reading in addition to the
>>       documents constituting the agreement itself.
> 
> Here is the question: do we need additional text to make clear that we
> are referring to the function and not the agreement, as we respond? 
> Perhaps the use of the term IANA throughout the text needs some review?

I don't really see much room for doubt, since the very first sentence
of the draft responses identifies the scope as the "IANA protocol parameters
function".

This did cause me to notice that although RFC2850 is listed as a reference,
it isn't cited in the text. Maybe the sentence I suggested previously:
"Among other duties, the IAB must approve the appointment
of an organization to act as IANA on behalf of the IETF."
needs a supplement such as

  In March 2000, the IAB and IETF signed an agreement with ICANN
  for ICANN to host the IANA protocol parameters function [RC2850].

     Brian