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

"Peterson, Jon" <jon.peterson@neustar.biz> Mon, 03 November 2014 16:20 UTC

Return-Path: <jon.peterson@neustar.biz>
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 70B971A0469 for <ianaplan@ietfa.amsl.com>; Mon, 3 Nov 2014 08:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.667
X-Spam-Level:
X-Spam-Status: No, score=-101.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 4MGeGM7T1D0O for <ianaplan@ietfa.amsl.com>; Mon, 3 Nov 2014 08:20:20 -0800 (PST)
Received: from mx0a-0018ba01.pphosted.com (mx0a-0018ba01.pphosted.com [67.231.149.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA77E1A008D for <ianaplan@ietf.org>; Mon, 3 Nov 2014 08:20:12 -0800 (PST)
Received: from pps.filterd (m0049402.ppops.net [127.0.0.1]) by m0049402.ppops.net-0018ba01. (8.14.7/8.14.7) with SMTP id sA3GGcvG005398; Mon, 3 Nov 2014 11:19:42 -0500
Received: from stntexhc12.cis.neustar.com ([156.154.17.216]) by m0049402.ppops.net-0018ba01. with ESMTP id 1qeb3y0at1-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 03 Nov 2014 11:19:41 -0500
Received: from STNTEXMB10.cis.neustar.com ([169.254.5.97]) by stntexhc12.cis.neustar.com ([::1]) with mapi id 14.03.0158.001; Mon, 3 Nov 2014 11:19:40 -0500
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: Bernard Aboba <bernard.aboba@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Thread-Topic: [Ianaplan] draft-ietf-ianaplan-icg-response-02 working group last call
Thread-Index: AQHP9Wh3zRkHbuzPgUScACcGUqfEBZxL2QwAgAIAnACAAQ0+gA==
Date: Mon, 03 Nov 2014 16:19:39 +0000
Message-ID: <D07CEABF.1357FC%jon.peterson@neustar.biz>
References: <6ACE138D-0969-4D8F-9A64-3D1FBB96885A@viagenie.ca> <FC8732DC-BB60-45A2-BF30-0B085CA5FEB9@cooperw.in> <5454B8DE.8040308@cs.tcd.ie> <E5F99046-6C9D-4170-B408-9CA9B7CD6476@gmail.com>
In-Reply-To: <E5F99046-6C9D-4170-B408-9CA9B7CD6476@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [192.168.129.162]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5849E3B6853A3240A37E98759CBA317F@neustar.biz>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=nai engine=5600 definitions=7610 signatures=670571
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 kscore.is_bulkscore=0 kscore.compositescore=0 circleOfTrustscore=0 compositescore=0.993311949948012 urlsuspect_oldscore=0.993311949948012 suspectscore=0 recipient_domain_to_sender_totalscore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=0 rbsscore=0.993311949948012 spamscore=0 recipient_to_sender_domain_totalscore=0 urlsuspectscore=0.9 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1411030143
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/V3Bv-6ZJvG9-fJmIqaQbME1TnSU
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, Alissa Cooper <alissa@cooperw.in>, "ianaplan@ietf.org" <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: Mon, 03 Nov 2014 16:20:21 -0000

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