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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sat, 01 November 2014 10:41 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 EA6261A701D for <ianaplan@ietfa.amsl.com>; Sat, 1 Nov 2014 03:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level:
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_46=0.6, 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 rnM_VAwiPFDp for <ianaplan@ietfa.amsl.com>; Sat, 1 Nov 2014 03:41:38 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 687FD1A1B8C for <ianaplan@ietf.org>; Sat, 1 Nov 2014 03:41:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id DC188BE1C; Sat, 1 Nov 2014 10:41:36 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 98PhvucjmPvu; Sat, 1 Nov 2014 10:41:35 +0000 (GMT)
Received: from [10.87.48.12] (unknown [86.41.50.206]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2C694BE0D; Sat, 1 Nov 2014 10:41:35 +0000 (GMT)
Message-ID: <5454B8DE.8040308@cs.tcd.ie>
Date: Sat, 01 Nov 2014 10:41:34 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Alissa Cooper <alissa@cooperw.in>, Marc Blanchet <marc.blanchet@viagenie.ca>
References: <6ACE138D-0969-4D8F-9A64-3D1FBB96885A@viagenie.ca> <FC8732DC-BB60-45A2-BF30-0B085CA5FEB9@cooperw.in>
In-Reply-To: <FC8732DC-BB60-45A2-BF30-0B085CA5FEB9@cooperw.in>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/9DclXZi_IKKzkiK9JVNrlrz7SCg
Cc: ianaplan@ietf.org
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: Sat, 01 Nov 2014 10:41:41 -0000

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
>