Re: [Ianaplan] Time frame inquiry

Eliot Lear <lear@cisco.com> Fri, 29 May 2015 15:34 UTC

Return-Path: <lear@cisco.com>
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 C26201AC41A for <ianaplan@ietfa.amsl.com>; Fri, 29 May 2015 08:34:41 -0700 (PDT)
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 WRdR-VIuTIjI for <ianaplan@ietfa.amsl.com>; Fri, 29 May 2015 08:34:38 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40F681AC427 for <ianaplan@ietf.org>; Fri, 29 May 2015 08:34:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11958; q=dns/txt; s=iport; t=1432913678; x=1434123278; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=jwmGJHHDRe+ri5B4lyOp5ViGSQDZIUb/wWlt149cZPI=; b=K6z6Sty7s2/+9gAFgy4MA+JNvBernve8MAIRXp/6s9npdOPc7VQbyjxN u4gVbPD4HHfOYQLWZTHVlrzZk9dMxfvJiIo4qIY61tuU0cVyh5nabGKhV Cetm7RafeTZJ1EzmUdA175yU1uvqWCul6nJnm/+M0rsN7coFTiY8CEBAv I=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CxAwC7hmhV/xbLJq1cg2Regx67BgmBUAEJhS1KAoF9FAEBAQEBAQGBCoQiAQEBAwEBAQEgSwoBEAsYCQwKCwICCQMCAQIBFTAGAQwBBQIBARCIEQgNsRikAQEBAQEBAQEBAQEBAQEBAQEBAQEBAReLQ4UGBwkBgl6BRQEEi1WEeYROgUNghl2BKT6GEYdah2AjggocgVQ8MYJHAQEB
X-IronPort-AV: E=Sophos;i="5.13,517,1427760000"; d="asc'?scan'208,217";a="520119498"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 29 May 2015 15:34:34 +0000
Received: from [10.61.168.115] ([10.61.168.115]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t4TFYYcJ002039; Fri, 29 May 2015 15:34:34 GMT
Message-ID: <5568870A.1010305@cisco.com>
Date: Fri, 29 May 2015 17:34:34 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>, Andrew Sullivan <ajs@anvilwalrusden.com>
References: <D15A3C14-F268-4CF1-B942-BAE57B281C58@cooperw.in> <556D3AAA-1655-4785-9395-8F6CD0B73E44@vigilsec.com> <5F8F0771-C77B-4D90-811B-501A4EC79268@istaff.org> <893FE3E3-A2DD-40D8-B39F-1EB24DFE1806@vigilsec.com> <97267ED7-D8A2-4A64-AB74-07434190DD89@piuha.net> <CA+9kkMBZq_U+CC5Jzv5T3pL7qasUHSfv-Gu8q4P36+phABXxzg@mail.gmail.com> <4AB120DC-AFB1-4915-B6C5-7417FB989878@piuha.net> <55669A78.3020309@cisco.com> <C8B9D0E8-C363-4618-8941-D0027B86EB7A@piuha.net> <20150528170435.GQ85071@mx2.yitter.info> <763565D0-92BF-4A1B-9C1D-C9AC94A57506@gmail.com>
In-Reply-To: <763565D0-92BF-4A1B-9C1D-C9AC94A57506@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="J4qRHT0wuLOKsWBMFLeSHd2LxiAIkHbml"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/6fCDn-lMrxirasVpI7214q47iBg>
Cc: ianaplan@ietf.org
Subject: Re: [Ianaplan] Time frame inquiry
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: Fri, 29 May 2015 15:34:42 -0000


On 5/28/15 7:11 PM, Bob Hinden wrote:
>> On May 28, 2015, at 10:04 AM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
>>
>> I like this text.
> As do I.  Ship it!
>
> Bob

Good enough.

Eliot

>> A
>>
>> On Thu, May 28, 2015 at 08:15:55AM +0300, Jari Arkko wrote:
>>> Eliot:
>>>
>>>> I like the text below modulo one issue: the IANAPLAN proposal did not specify how the IAOC would implement the requested changes (whether through the SLA or another side agreement).  I would prefer that we stuck to that approach and not name which agreement the changes go into (SLA or a one-time supplemental agreement).
>>> Ok.
>>>
>>> Trying to take this and Ted’s comments into account:
>>>
>>> “The IETF is ready today to take the next steps in the
>>> implementation of the transition of the stewardship.
>>> In our case, most of the necessary framework is already
>>> in place and implemented in preceding years.
>>>
>>> The remaining step is an updated agreement with
>>> ICANN which addresses two issues. These issues are
>>> outlined in Section 2.III in the Internet Draft
>>> draft-ietf-ianaplan-icg-response-09.txt:
>>>
>>>   o  The protocol parameters registries are in the public domain.  It
>>>      is the preference of the IETF community that all relevant parties
>>>      acknowledge that fact as part of the transition.
>>>
>>>   o  It is possible in the future that the operation of the protocol
>>>      parameters registries may be transitioned from ICANN to subsequent
>>>      operator(s).  It is the preference of the IETF community that, as
>>>      part of the NTIA transition, ICANN acknowledge that it will carry
>>>      out the obligations established under C.7.3 and I.61 of the
>>>      current IANA functions contract between ICANN and the NTIA
>>>      [NTIA-Contract] to achieve a smooth transition to subsequent
>>>      operator(s), should the need arise.  Furthermore, in the event of
>>>      a transition it is the expectation of the IETF community that
>>>      ICANN, the IETF, and subsequent operator(s) will work together to
>>>      minimize disruption in the use the protocol parameters registries
>>>      or other resources currently located at iana.org.
>>>
>>> The IETF Administrative Oversight Committee (IAOC) has
>>> decided to use an update of our yearly IETF-ICANN Service Level
>>> Agreement (SLA) as the mechanism for this updated
>>> agreement. They have drafted the update and from our
>>> perspective it could be immediately executed. Once the updated
>>> agreement is in place, the transition would be substantially
>>> complete, with only the NTIA contract lapse or termination
>>> as a final step.
>>>
>>> Of course, we are not alone in this process. Interactions
>>> with other parts of the process may bring additional
>>> tasks that need to be executed either before or
>>> after the transition. First, the ICG, the RIRs,
>>> and IETF have discussed the possibility of aligning
>>> the treatment of IANA trademarks. The IETF Trust
>>> has signalled that it would be willing to do this, if
>>> asked. We are awaiting to coordination on this
>>> to complete, but see no problem in speedy
>>> execution once the decision is made. From our
>>> perspective this is not a prerequisite for the transition,
>>> however.
>>>
>>> In addition, the names community has proposed the
>>> creation of a 'Post Transition IANA' (PTI).  If the existing
>>> agreements between the IETF and ICANN remain in place
>>> and the SLAs discussed above are not affected, the IETF​
>>> ransition would take place as described above.  That is
>>> our preference.  If the final details of the PTI plan require
>>> further action from the IETF, more work and community
>>> agreement would be required.  The timeline for that work
>>> cannot be set until the scope is known.”
>>>
>>> Jari
>>>
>>
>>
>>> _______________________________________________
>>> Ianaplan mailing list
>>> Ianaplan@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ianaplan
>>
>> --
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>>
>> _______________________________________________
>> 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