IETF Logo Mail Archive

Re: [Ianaplan] numbers community plan

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Tue, 13 January 2015 07:40 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 60E671A8A3F for <ianaplan@ietfa.amsl.com>; Mon, 12 Jan 2015 23:40:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.199
X-Spam-Level:
X-Spam-Status: No, score=0.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=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 oxXwRTW-qMUQ for <ianaplan@ietfa.amsl.com>; Mon, 12 Jan 2015 23:40:24 -0800 (PST)
Received: from scintmta01-14.scbb.aoyama.ac.jp (scintmta01-14.scbb.aoyama.ac.jp [133.2.253.64]) by ietfa.amsl.com (Postfix) with ESMTP id 507601A8A3C for <ianaplan@ietf.org>; Mon, 12 Jan 2015 23:40:24 -0800 (PST)
Received: from scmeg01-14.scbb.aoyama.ac.jp (scmse.scbb.aoyama.ac.jp [133.2.253.15]) by scintmta01-14.scbb.aoyama.ac.jp (Postfix) with ESMTP id BE47C32E583; Tue, 13 Jan 2015 16:39:39 +0900 (JST)
Received: from itmail2.it.aoyama.ac.jp (unknown [133.2.206.134]) by scmeg01-14.scbb.aoyama.ac.jp with smtp id 399f_8cd6_d3a74f61_a431_4abc_a1b7_d243f2019242; Tue, 13 Jan 2015 16:39:39 +0900
Received: from [133.2.210.64] (unknown [133.2.210.64]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 0F827BF4E3; Tue, 13 Jan 2015 16:39:39 +0900 (JST)
Message-ID: <54B4CBBA.5090004@it.aoyama.ac.jp>
Date: Tue, 13 Jan 2015 16:39:38 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 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> <54B4224A.5000200@gmail.com>
In-Reply-To: <54B4224A.5000200@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/8J3zNcaow-zV9J8Vt6RX3_QXEjI>
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: Tue, 13 Jan 2015 07:40:25 -0000

On 2015/01/13 04:36, Brian E Carpenter wrote:
> Eliot,

>> 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.

Agreed.

I'd note that one reason that was brought up for not saying anything 
about the IETF Trust in the draft we worked on was that we didn't want 
to impose that on the other communities. At least for the numbers 
community, that obstacle clearly is out of the way.

Regards,   Martin.

v2.23.0 | Report a Bug | By Email