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

Alissa Cooper <alissa@cooperw.in> Sat, 01 November 2014 00:11 UTC

Return-Path: <alissa@cooperw.in>
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 214631A874A for <ianaplan@ietfa.amsl.com>; Fri, 31 Oct 2014 17:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_LOW=-0.7] 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 wSa2pKNmycDt for <ianaplan@ietfa.amsl.com>; Fri, 31 Oct 2014 17:11:52 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4C261A86F9 for <ianaplan@ietf.org>; Fri, 31 Oct 2014 17:11:52 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 2B0A72082E for <ianaplan@ietf.org>; Fri, 31 Oct 2014 20:11:52 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Fri, 31 Oct 2014 20:11:52 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h= x-sasl-enc:content-type:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; s= mesmtp; bh=mj1n7JX+TmoS0iW/MOGhS/2LgkI=; b=DtPRDMJEXom6uW6UvRes8 gcmlHD9lpnregGbc7eHiZrRxtfWPQjsTi2DqEm+YcjdXK8bAieQ6k4sUxjmCst6I AmcWUqAuOkFPNZ+arPVW0fW+WnnQ1m7+pFULXfNGO/XlWNYMNySsT46iR9wzZasw zCpuuH5ZEYlhUf+9nJN9jk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:content-type:mime-version :subject:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; s=smtpout; bh=mj1n7JX+TmoS0iW/MOGhS/2 LgkI=; b=pqf7fYB5LYce6jXP0wFMYOQKSM5v88K1dJEobKf/LTY5e/04uGUxsjX eAShw+mw9zeOhd75g48Ya0C7yjGNkaKsar7d+aOW1wPJB+Zp6qZggi6wuk0XH5/M JJLKL9M+7XkasKZirBbx1s1zXssjlhPJpm3NEO7flQI8JMrK1j/I=
X-Sasl-enc: SR2CVHGFVvrgupLn12915Cl52yaZ5GsHvd3TVWDcNPyu 1414800711
Received: from [10.35.132.83] (unknown [128.107.239.233]) by mail.messagingengine.com (Postfix) with ESMTPA id B7F18C0000A; Fri, 31 Oct 2014 20:11:51 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <6ACE138D-0969-4D8F-9A64-3D1FBB96885A@viagenie.ca>
Date: Fri, 31 Oct 2014 17:11:55 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC8732DC-BB60-45A2-BF30-0B085CA5FEB9@cooperw.in>
References: <6ACE138D-0969-4D8F-9A64-3D1FBB96885A@viagenie.ca>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/wIY6R-omX9A_fbBPZLPZm_ENHT8
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 00:11:56 -0000

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