Re: [Ianaplan] draft-ietf-ianaplan-icg-response-02 working group last call

Miles Fidelman <mfidelman@meetinghouse.net> Mon, 03 November 2014 17:38 UTC

Return-Path: <mfidelman@meetinghouse.net>
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 D8D401A1BB5 for <ianaplan@ietfa.amsl.com>; Mon, 3 Nov 2014 09:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.618
X-Spam-Level: *
X-Spam-Status: No, score=1.618 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, J_CHICKENPOX_46=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 s3Lvwrg8Fd_Q for <ianaplan@ietfa.amsl.com>; Mon, 3 Nov 2014 09:38:06 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id E0DF61A1BB3 for <ianaplan@ietf.org>; Mon, 3 Nov 2014 09:38:05 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 4D947CC06E for <ianaplan@ietf.org>; Mon, 3 Nov 2014 12:38:05 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id eZ2jCSbVt4IJ for <ianaplan@ietf.org>; Mon, 3 Nov 2014 12:38:01 -0500 (EST)
Received: from new-host-3.home (pool-96-237-159-213.bstnma.fios.verizon.net [96.237.159.213]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 3F115CC08C for <ianaplan@ietf.org>; Mon, 3 Nov 2014 12:37:48 -0500 (EST)
Message-ID: <5457BD6B.2040705@meetinghouse.net>
Date: Mon, 03 Nov 2014 12:37:47 -0500
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30
MIME-Version: 1.0
CC: ianaplan@ietf.org
References: <GLEAIDJPBJDOLEICCGMNCEMLCNAA.rhill@hill-a.ch>
In-Reply-To: <GLEAIDJPBJDOLEICCGMNCEMLCNAA.rhill@hill-a.ch>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/a85MVg19xiEe9bTp7idPONaId6g
Subject: Re: [Ianaplan] draft-ietf-ianaplan-icg-response-02 working group last call
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, 03 Nov 2014 17:38:08 -0000

+1

Richard Hill wrote:
> Sorry, I don't agree with that.  That language is too vague for me.
>
> If people are not comfortable with the language that is currently in 02,
> then I suggest that we develop language to the effect that the intellectual
> property rights and the domain name IANA.ORG will be transferred to the ISOC
> Trust (or whatever part of ISOC is the appropriate entity to receive it).
>
> In my view, the mark, and the domain name, belong to ISOC morally, if not
> legally and, as I said before, I'm sure that everybody would agree that ISOC
> will allow whatever entity or entities are providing the IANA function to
> use the mark and the domain name.
>
> Best,
> Richard
>
>> -----Original Message-----
>> From: Ianaplan [mailto:ianaplan-bounces@ietf.org]On Behalf Of Peterson,
>> Jon
>> Sent: lundi, 3. novembre 2014 17:20
>> To: Bernard Aboba; Stephen Farrell
>> Cc: Marc Blanchet; Alissa Cooper; ianaplan@ietf.org
>> Subject: Re: [Ianaplan] draft-ietf-ianaplan-icg-response-02 working
>> group last call
>>
>>
>>
>> Agreed. "Cooperation with subsequent operators to minimize confusion"
>> gives us enough wiggle-room to be able to manage some likely transition
>> situations. The prior language probably doesn't.
>>
>> Jon Peterson
>> Neustar, Inc.
>>
>> On 11/2/14, 7:16 AM, "Bernard Aboba" <bernard.aboba@gmail.com> wrote:
>>
>>> I agree as well.
>>>
>>>
>>>
>>>> On Nov 1, 2014, at 3:41 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
>>>> wrote:
>>>>
>>>>
>>>> Alissa's point goes a little beyond my comment on the same
>>>> text, but having read this, I share her concerns.
>>>>
>>>> S
>>>>
>>>>> On 01/11/14 00:11, Alissa Cooper wrote:
>>>>> I¹d like to pick up on one comment I made in my last review of the
>>>>> document that did not get sufficiently addressed. It concerns this
>>>>> text:
>>>>>
>>>>> "To address concerns regarding appropriate contingencies to
>>>>> transition to another operator, the IAOC is asked to conclude a
>>>>> supplemental agreement that- ...
>>>>>
>>>>> 2.  requires the transfer of any associated marks and identifiers to
>>>>> subsequent operators."
>>>>>
>>>>> My problem with this is that one mark cannot be transferred to two
>>>>> operators. So if we end up in a situation where there are multiple
>>>>> IANA operators for different registries, how will it be decided who
>>>>> gets the existing marks? If I were the current owner of such marks, I
>>>>> don¹t see how I could agree to this provision without foreclosing the
>>>>> possibility that there may be multiple simultaneous operators in the
>>>>> future. This is why I think this requirement should be stated as
>>>>> requiring ³cooperation with subsequent operators to minimize
>>>>> confusion" associated with marks and identifiers, or some similar
>>>>> language that provides a safeguard in the event of transition but
>>>>> does not mandate specific transfer actions related to marks and
>>>>> identifiers.
>>>>>
>>>>> I also still find it quite problematic that this section requires the
>>>>> IAOC to conclude supplemental agreements, instead of maintaining the
>>>>> existing relationship that the IETF has with the IAOC wherein it is
>>>>> the IAOC¹s responsibility to determine the format in which is carries
>>>>> out its responsibilities on behalf of the IETF.
>>>>>
>>>>> Alissa
>>>>>
>>>>> On Oct 28, 2014, at 7:42 AM, Marc Blanchet
>>>>> <marc.blanchet@viagenie.ca> wrote:
>>>>>
>>>>>> Hello, given the proposed timeline agreed during our last interim
>>>>>> meeting and based on that the outstanding issues should have been
>>>>>> addressed in the -02 version, this message starts a working group
>>>>>> last call on draft-ietf-ianaplan-icg-response-02.  This working
>>>>>> group last call will end november 11, 23h59 UTC. Given that our
>>>>>> meeting is scheduled on november 10th, it would be useful if people
>>>>>> send their comments prior to the meeting so they can be addressed
>>>>>> or discussed before or during the meeting.
>>>>>>
>>>>>> Draft:
>>>>>> http://www.ietf.org/id/draft-ietf-ianaplan-icg-response-02.txt
>>>>>>
>>>>>> Please send comments to the list.
>>>>>>
>>>>>> Regards, Marc&Leslie, co-chairs.
>>>>>> _______________________________________________ Ianaplan mailing
>>>>>> list Ianaplan@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/ianaplan
>>>>> _______________________________________________ Ianaplan mailing
>>>>> list Ianaplan@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/ianaplan
>>>> _______________________________________________
>>>> Ianaplan mailing list
>>>> Ianaplan@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ianaplan
>>> _______________________________________________
>>> Ianaplan mailing list
>>> Ianaplan@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ianaplan
>> _______________________________________________
>> Ianaplan mailing list
>> Ianaplan@ietf.org
>> https://www.ietf.org/mailman/listinfo/ianaplan
>>
>>
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra