Re: [Ianaplan] Fwd: [CWG-Stewardship] ICG request concerning IANA trademark and iana.org domain name

Avri Doria <avri@acm.org> Tue, 23 June 2015 12:57 UTC

Return-Path: <avri@acm.org>
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 05F461A0194 for <ianaplan@ietfa.amsl.com>; Tue, 23 Jun 2015 05:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.664
X-Spam-Level:
X-Spam-Status: No, score=0.664 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] 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 VhAw6WffE3Ta for <ianaplan@ietfa.amsl.com>; Tue, 23 Jun 2015 05:56:59 -0700 (PDT)
Received: from atl4mhob01.myregisteredsite.com (atl4mhob01.myregisteredsite.com [209.17.115.39]) by ietfa.amsl.com (Postfix) with ESMTP id 627C61A00F5 for <ianaplan@ietf.org>; Tue, 23 Jun 2015 05:56:57 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.208]) by atl4mhob01.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id t5NCutoB014701 for <ianaplan@ietf.org>; Tue, 23 Jun 2015 08:56:55 -0400
Received: (qmail 29071 invoked by uid 0); 23 Jun 2015 12:56:55 -0000
X-TCPREMOTEIP: 199.91.193.8
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?127.0.0.1?) (avri@ella.com@199.91.193.8) by 0 with ESMTPA; 23 Jun 2015 12:56:54 -0000
Message-ID: <55895793.3060004@acm.org>
Date: Tue, 23 Jun 2015 09:56:51 -0300
From: Avri Doria <avri@acm.org>
Organization: Technicalities
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: ianaplan@ietf.org
References: <20150619170708.84611.qmail@ary.lan> <3F18936E1587B5F2BB89E800@JcK-HP8200.jck.com> <55847BE9.9040507@gmail.com> <5584BC64.7060403@gmail.com> <alpine.OSX.2.11.1506192151170.47260@ary.local> <5584D664.90003@gmail.com> <alpine.OSX.2.11.1506201928040.47864@ary.local> <55863ABF.8020903@dcrocker.net> <alpine.OSX.2.11.1506211008240.48224@ary.local> <5586EB11.5030404@dcrocker.net> <alpine.OSX.2.11.1506211400250.48860@ary.local> <5587A015.9030700@cisco.com> <alpine.OSX.2.11.1506221032250.50421@ary.local> <55881331.9070902@dcrocker.net> <alpine.OSX.2.11.1506221056420.50578@ary.local> <5588FE8B.3040806@gmail.com> <CAKFn1SGxChn3kK=DXApAhpn6y=HB69wOWnYjDPzFmz_QmGUxjg@mail.gmail.com>
In-Reply-To: <CAKFn1SGxChn3kK=DXApAhpn6y=HB69wOWnYjDPzFmz_QmGUxjg@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 150622-3, 06/22/2015), Outbound message
X-Antivirus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/a4Mmf9ADwgqHMw_B0uA2KwtJT08>
Subject: Re: [Ianaplan] Fwd: [CWG-Stewardship] ICG request concerning IANA trademark and iana.org domain name
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: avri@acm.org
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Jun 2015 12:57:01 -0000

Hi,

I thought they had suggested it as one example, one possibility.

I think many, even among the  Names community, are coming to a general
sense that putting the property into a Trust may be necessary.  Whether
it is an existing trust belonging to one operational community or one
set up for the specific purposes of IANA Function Operations that gives
all operational communities an equal set of expectations, may be an item
still to be discussed.

avri


On 23-Jun-15 07:41, Roger Jørgensen wrote:
> On Tue, Jun 23, 2015 at 8:36 AM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>> On 23/06/2015 01:57, John R Levine wrote:
>>>> Unfortunately it does not suit the requirements for carefully
>>>> considering and anticipating issues downstream, during negotiation of
>>>> changes at this juncture, to align IETF interests with the fundamental
>>>> modification of ICANN oversight.
>>> Well, OK.  You know what my plan is, which I belive to be eminently realistic and founded in the practicalities of trademark law.
>>>
>>> What's your plan?
>> I'm not sure I understood Dave's plan, but what I would suggest (which
>> doesn't involve any bargaining chips as far as I can see) is:
>>
>> 1. State that the IETF Trust is the most appropriate vehicle to hold
>> the IANA IPR as an asset for the entire Internet community. I think
>> that would be a useful addendum to the IANAPLAN document, but it
>> shouldn't be allowed to hold up the RFC publication.
> The RIR side has suggested this, I can't see many reasons for why
> we can't support that view. It does make sense, maybe except for
> the names-people that so far don't like it for whatever reason.
>
>
>
>> 2. Have an emergency plan ready, with the following steps:
>>  a) create a domain registrar.ietf.org with duplicate servers in
>>     several countries and the same CDN support as www.ietf.org.
>>  b) copy all the relevant files across, patching the relevant
>>     URLs in the process. (Also issue a short BCP making a global
>>     fix to all other RFCs referring to IANA.)
>>  c) kick off a volunteer pool of acting registrars for a few months.
>>  d) request the IAOC to start a CFP process.
> Or any other name than registrar, it's just a name. Anyway,
> some actual steps on how we could move away from iana.org
> if everything else fails.
>
>
>> It really seems highly unlikely to me that things will ever come
>> to that, but we don't need to talk as if a complete collapse on
>> the ICANN side, whether caused by silliness over the domain name
>> and TM or by anything else, would create a collapse in the protocol
>> parameters community.
>>
>> No doubt the numbers community could quickly come up with a similar
>> plan, or join the registrar.ietf.org plan.
> registrar.nro.net ?
>


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus