Re: [Ianaplan] numbers community plan

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 12 January 2015 19:36 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 9583C1ACDA6 for <ianaplan@ietfa.amsl.com>; Mon, 12 Jan 2015 11:36:54 -0800 (PST)
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 fC6WmPcbBXR2 for <ianaplan@ietfa.amsl.com>; Mon, 12 Jan 2015 11:36:52 -0800 (PST)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AB101ACDBE for <ianaplan@ietf.org>; Mon, 12 Jan 2015 11:36:45 -0800 (PST)
Received: by mail-pa0-f53.google.com with SMTP id kq14so33740835pab.12 for <ianaplan@ietf.org>; Mon, 12 Jan 2015 11:36:44 -0800 (PST)
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 :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/T5L/wXUJEvtHuPjMrVdvPUj4dwmVRu/El1r41rpSwA=; b=IpNruKCPPhLsdqxHYktyXa6Co3G65hdVgUovjReTo7alKExM3qw3971orCawKtuXGz SPPXHkx6iwdRw2SJmN0ymMBKRFXMFp2nRe/XLOnf9JxCRAOkOHn+RKZPy2nyytvHvGgB ossYa9p/RY+QbtjjAUrtd1ck77b4lHtfdVS4sjVzSiOUNAY5GUUszXbG6EIsGu6JpE/Y +LS6BxLukNkey4OMfERLmIAGPfF2NqljnkJEi72aSZVrk5bo06Da7EZzp0HMtGT/xzbJ pMp+ysBEcKuNzmYHYX7zNpbI3//LAtDa0Fa6OAwOl9rVKpMmz58FJa9RYjcmLbu+Iik7 5sVQ==
X-Received: by 10.66.148.6 with SMTP id to6mr44717442pab.9.1421091404561; Mon, 12 Jan 2015 11:36:44 -0800 (PST)
Received: from ?IPv6:2406:e007:7927:1:28cc:dc4c:9703:6781? ([2406:e007:7927:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id ju5sm15220464pab.42.2015.01.12.11.36.41 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Jan 2015 11:36:43 -0800 (PST)
Message-ID: <54B4224A.5000200@gmail.com>
Date: Tue, 13 Jan 2015 08:36:42 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>, 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> <54B3CCAA.5090500@cisco.com>
In-Reply-To: <54B3CCAA.5090500@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/RyvUR0DwbU1aERqVHgU5DulyAxU>
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 19:36:54 -0000

Eliot,

Below...

On 13/01/2015 02:31, Eliot Lear wrote:
> 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.

Correct, but if the IETF Trust is asked (as seems possible) to accept
IPR that affects the names and numbers communities as well as the IETF,
then they (the Trust) will need clear input from the IETF, since the
sole beneficiary of the Trust is "the IETF as a whole". (They will also
need legal and tax advice to be sure that they will not violate
the Trust Agreement and 501(c)(3) status.)

I think this WG would be the obvious sounding board for that discussion,
but there's not much point in crossing that bridge until we come to it,
i.e. a specific request is made to the Trust from outside the IETF.

    Brian