Re: Last Call: <draft-ietf-ianaplan-icg-response-06.txt> (Draft Response to the Internet Coordination Group Request for Proposals on the IANA protocol parameters registries) to Informational RFC

Eliot Lear <lear@cisco.com> Tue, 16 December 2014 16:29 UTC

Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 406E61A1B93 for <ietf@ietfa.amsl.com>; Tue, 16 Dec 2014 08:29:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 s7uJA3Pvqz4y for <ietf@ietfa.amsl.com>; Tue, 16 Dec 2014 08:29:10 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D96671A1BC7 for <ietf@ietf.org>; Tue, 16 Dec 2014 08:29:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4982; q=dns/txt; s=iport; t=1418747350; x=1419956950; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=4ZyonBa3VVqwQ7+2k5D1ReOqZG1H5Kp4Uq/iyBEY7PY=; b=ADytZPKrlMKazuCI26iXLYp9dazDguaaTo6zZvkpXLveFunHJqcISAdQ NYI+C/Cy5eSd+AZFX4Is51kRDSH9dkrJ+0CccyyXCDX1KG6KBSBPP4aqi 0vAE4zsOkta2A8lSvkIQHyfrgXAg7aEvZAU3Ta9gwbUV70CieGz3OMBnE g=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArgEAGpckFStJssW/2dsb2JhbABahzbIZAKBLwEBAQEBfYQNAQEEI08GARAJAgQUCRYEBwICCQMCAQIBRQYBDAEHAQGIKKFxnGiWRAEBAQEBAQEBAQEBAQEBAQEBAQEBARePcgeCaIFBAQSPTIEnhAuBc4ELDYRhIYdngzgigjCBPT2CcwEBAQ
X-IronPort-AV: E=Sophos;i="5.07,587,1413244800"; d="asc'?scan'208,217";a="276484676"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 16 Dec 2014 16:29:08 +0000
Received: from [10.61.68.245] (ams3-vpn-dhcp1269.cisco.com [10.61.68.245]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id sBGGT7WF010268; Tue, 16 Dec 2014 16:29:07 GMT
Message-ID: <54905DD2.1020801@cisco.com>
Date: Tue, 16 Dec 2014 17:29:06 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-ianaplan-icg-response-06.txt> (Draft Response to the Internet Coordination Group Request for Proposals on the IANA protocol parameters registries) to Informational RFC
References: <20141203171430.30136.qmail@ary.lan> <547F49C2.8070306@cisco.com> <547F6728.4040809@gmail.com> <24117411-F52C-4024-ACBB-4D40B878139A@piuha.net>
In-Reply-To: <24117411-F52C-4024-ACBB-4D40B878139A@piuha.net>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="us0vFHhQDUo1R4kA1u4IVM3Tkm6Aanbge"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/i581aSAGi0RVSAyMFM-nHvldbF0
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Dec 2014 16:29:13 -0000

Hi Jari,


On 12/16/14, 4:57 PM, Jari Arkko wrote:
>>>> It sounds like we want the same thing here, but when I read the draft,
>>>> I don't see it actually saying that if there's a new IANA operator, we
>>>> need a new equally good contract. That seems to me to be worth making
>>>> explicit.
>>> I think that's a fine suggestion.  The discussions and conclusions of
>>> the WG, so far as I can tell, were exclusively focused on the ICANN/NTIA
>>> relationship, and your suggestion reinforces the conclusion by inference
>>> (we CAN change should the need arise) and it gives people a view as to
>>> how we would see to the continuity of the service.
>> Yes, I agree with that and indeed I suspect it is most people's working
>> assumption, to the extent that we overlooked writing it down ;-).
> I agree with all of the above. Eliot, did you make a change with regards to this?
>

Yes.  The text I propose to include for this purpose is as follows:

  
   The MoU also provides an option for either party to terminate the
   arrangement with six months notice.  Obviously such action would only
   be undertaken after serious consideration. 
+  In that case a new IANA
+  functions operator would be selected, and a new agreement with that
+  operator would be established.

Eliot