Re: [Ianaplan] feedback regarding the combined proposal

John Curran <jcurran@arin.net> Sun, 09 August 2015 16:00 UTC

Return-Path: <jcurran@arin.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 D48081ACE49 for <ianaplan@ietfa.amsl.com>; Sun, 9 Aug 2015 09:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level:
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 BDzsECliip4O for <ianaplan@ietfa.amsl.com>; Sun, 9 Aug 2015 09:00:49 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 20CBE1ACE48 for <ianaplan@ietf.org>; Sun, 9 Aug 2015 09:00:49 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id C6314164EF7; Sun, 9 Aug 2015 12:00:48 -0400 (EDT)
Received: from chaedge01.corp.arin.net (chaedge01.corp.arin.net [192.149.252.118]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id 0D222164ECC; Sun, 9 Aug 2015 12:00:46 -0400 (EDT)
Received: from CHACAS01.corp.arin.net (10.1.30.107) by chaedge01.corp.arin.net (192.149.252.118) with Microsoft SMTP Server (TLS) id 14.3.210.2; Sun, 9 Aug 2015 12:08:55 -0400
Received: from CHAMBX02.corp.arin.net ([fe80::905e:9b4d:2909:f55a]) by CHACAS01.corp.arin.net ([fe80::a98b:1e52:e85a:5979%13]) with mapi id 14.03.0224.002; Sun, 9 Aug 2015 12:00:36 -0400
From: John Curran <jcurran@arin.net>
To: Bernard Aboba <bernard.aboba@gmail.com>, Eliot Lear <lear@cisco.com>, Jari Arkko <jari.arkko@piuha.net>
Thread-Topic: [Ianaplan] feedback regarding the combined proposal
Thread-Index: AQHQ0ryGScQ3DwGnI0SvLaHO1+YBXA==
Date: Sun, 9 Aug 2015 16:00:35 +0000
Message-ID: <B3BFE2FA-2FBF-4E76-98ED-9745E5B6B25F@arin.net>
References: <7DAC25D2-2321-4918-806C-A598C97F562C@piuha.net> <55C74A93.2090300@cisco.com> <F9E7BCC9-9D38-4B40-9A30-DF22E7210AFC@gmail.com>
In-Reply-To: <F9E7BCC9-9D38-4B40-9A30-DF22E7210AFC@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.149.252.96]
Content-Type: multipart/alternative; boundary="_000_B3BFE2FA2FBF4E7698ED9745E5B6B25Farinnet_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/A2kJOggR906KmLiZwMe0WmJytw4>
Cc: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>
Subject: Re: [Ianaplan] feedback regarding the combined proposal
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 09 Aug 2015 16:00:51 -0000

On Aug 9, 2015, at 10:11 AM, Bernard Aboba <bernard.aboba@gmail.com<mailto:bernard.aboba@gmail.com>> wrote:

On Aug 9, 2015, at 5:41 AM, Eliot Lear <lear@cisco.com<mailto:lear@cisco.com>> wrote:

If this agreement is in place, great.  That should be stated.  If the
agreement is not yet in place, then that should be stated in the
transition section (Section V) of the ICG summary.

[BA] The ICG proposal includes requirements for agreements. Compared to an actual agreement this is akin to the sound of one hand clapping.

Due to legal concerns relating to current NTIA-ICANN contract limitations, agreements cannot be signed at this time.  We do not even really know when discussions will be able to resume, what additional concerns might arise when they do, or even whether the requirements can be met once all the obstacles to discussion are removed.

I will observe that the numbers community ran into a similar difficulty when we
proposed that a Service Level Agreement for IANA Numbering Services be
entered in advance of the transition of the stewardship of the IANA functions.

As a result of some discussion of the topic with ICANN, we have now made explicit
a "Condition Precedent” in the second draft of the SLA, such that entry into the
agreement would still result in no effect if ICANN has not been released from its
obligations to provide substantially similar services per its NTIA contract by a specific
date (more information, including the second draft of the SLA, can be found here:
https://www.nro.net/news/call-for-comments-for-the-second-draft-sla-for-the-iana-numbering-services)

It is unclear if this approach would work for implementation of the IANAplan
proposal, as: 1) we have not received a formal response back from ICANN on
this approach, 2) the IETF already has an existing relationship and agreement,
and it is unclear whether a similar mechanism could be applied to only to a
specific set of rights/duties rather than the entire agreement.  I mention it solely
because it may provide a potential avenue of exploration which would allow
further progress on establishing necessary foundational pieces for transition.

/John