Re: [Ianaplan] numbers community plan

Eliot Lear <lear@cisco.com> Mon, 12 January 2015 13:31 UTC

Return-Path: <lear@cisco.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 A0B2C1A904D for <ianaplan@ietfa.amsl.com>; Mon, 12 Jan 2015 05:31:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 c5U_18Vplwse for <ianaplan@ietfa.amsl.com>; Mon, 12 Jan 2015 05:31:25 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6714C1A8A90 for <ianaplan@ietf.org>; Mon, 12 Jan 2015 05:31:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5437; q=dns/txt; s=iport; t=1421069485; x=1422279085; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=AovqCPK18Ykz4l6lvwlQtTnlqo9VJJ6D1/IyjtKf2tY=; b=h6HLCscXSjNWYqb1ZPsfoPnKs2hRpCyFFmZ0tG6lg3T6IVjzH+ikN/nT C0oQDGYt+9tBRjT4uGAwqV1QC3sd8RiieLZ6dhTCYdUslKj7f3jHpjuIM HxO2bOLy0TQTCgjV9U7VGnDN5wTKZcruFiv+Gv7CGMxFYfjuseun1HOPB w=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkEALLLs1StJssW/2dsb2JhbABbg1iDXcJ8hXECgVQBAQEBAX2EDAEBAQMBI1UGCwsECgoJFgsCAgkDAgECAUUGAQwIAQEQiBAIDbhmkzABAQEBAQEBAwEBAQEBAQEBGpAAgmiBQQWQCoEpT4VIgT+EW4teIoNvPTGCQwEBAQ
X-IronPort-AV: E=Sophos;i="5.07,744,1413244800"; d="asc'?scan'208,217";a="304873338"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 12 Jan 2015 13:31:23 +0000
Received: from [10.61.175.170] ([10.61.175.170]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t0CDVMGt014446; Mon, 12 Jan 2015 13:31:22 GMT
Message-ID: <54B3CCAA.5090500@cisco.com>
Date: Mon, 12 Jan 2015 14:31:22 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Suzanne Woolf <suzworldwide@gmail.com>, IANAPLAN WG <ianaplan@ietf.org>
References: <53675CAE-BB02-41EF-9E4B-04EA0E047FF2@viagenie.ca> <C48FAA87-2DF2-4AFB-8FA6-1F6E5DB3FDCA@gmail.com>
In-Reply-To: <C48FAA87-2DF2-4AFB-8FA6-1F6E5DB3FDCA@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="qFOAInxTdLn1soIGJmLrdoHfffB2nd92R"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/kAgXecBkD_ccjBaeZbE7VhmNOl4>
Subject: Re: [Ianaplan] numbers community plan
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: Mon, 12 Jan 2015 13:31:27 -0000

Hi Suzanne,

Speaking only for myself...

On 1/8/15 9:12 PM, Suzanne Woolf wrote:
> Marc,

> (...)

> The consensus on the IPR issue in the WG as I understood it was that
> the WG wasn't instructing the IAOC/IAB to seek additional agreements
> about the iana.org <http://iana.org> name, but also was not ruling it
> out. So the current document doesn't really provide guidance on what
> to do if the IETF Trust is asked by other operational communities to
> accept the role hypothesized here, or to enter into a conversation
> about possible terms for doing so.
>
> Is there a need for such guidance from the WG?
>

I hope it always helps those who are going to be engaged in the
discussions if smart people express their opinion.  In addition, it
seems that the IESG intended this WG to be the forum to review and
comment on proposals from other communities when they wrote into the
charter the following:

> Should proposals made by other communities regarding the
> transition of other IANA functions affect the IETF protocol parameter
> registries or the IETF, the WG may also review and comment on them.[1]
Obviously IPR can impact us.  We should stay focused on the impact to
the IETF.  Discussions that don't impact the IETF seem better homed in
the other communities.

Eliot
[1]http://datatracker.ietf.org/wg/ianaplan/charter/