Re: [Ianaplan] Time frame inquiry

Jari Arkko <jari.arkko@piuha.net> Thu, 04 June 2015 12:04 UTC

Return-Path: <jari.arkko@piuha.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 AC7031ACEEC for <ianaplan@ietfa.amsl.com>; Thu, 4 Jun 2015 05:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level:
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 XANoNKiZ2fWa for <ianaplan@ietfa.amsl.com>; Thu, 4 Jun 2015 05:04:14 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 3E91C1AD0B2 for <ianaplan@ietf.org>; Thu, 4 Jun 2015 05:03:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 96A292CED9; Thu, 4 Jun 2015 15:03:39 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yGGNzqIKrqPP; Thu, 4 Jun 2015 15:03:37 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id C22AA2CED5; Thu, 4 Jun 2015 15:03:37 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Content-Type: multipart/signed; boundary="Apple-Mail=_441F88A9-0B56-4DC3-BDB1-596789D394D3"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <556CDDD4.8070507@gmail.com>
Date: Thu, 4 Jun 2015 15:03:36 +0300
Message-Id: <E7F5E724-D58D-4A8C-90E4-ADB65C8DB819@piuha.net>
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> <6BCB4C30-034A-4D13-AD89-88B0719DB75C@vigilsec.com> <7B6FC84D-CE19-435F-A87A-87AEF3FDB305@thinkingcat.com> <556CBF1F.20503@gmail.com> <CAP4=Vciz9noosd=04mxWineNVYwtESve0991JwGWbmC52OViRA@mail.gmail.com> <556CDDD4.8070507@gmail.com>
To: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/kXTxbARg0WREwzzXw01mmPDKw_g>
Cc: "Leslie Daigle \(ThinkingCat\)" <ldaigle@thinkingcat.com>
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: Thu, 04 Jun 2015 12:04:16 -0000

I wouldn’t worry too much about the signatories that is perhaps more of a practical
matter than anything else. In general, reducing the reliance on persons in official
roles and highlighting the role of the community is important in this and many
other topics.

But being clear about the status of any opinion is important, and we
didn’t make that yet clear in the previous text.

I plan to send this note to the ICG later today unless someone screams
otherwise. I also plan to send a copy to the CWG list for information,
given our reference relating to the PTI arrangements.

—

This is a response to a query regarding transition finalisation and
implementation time frames, sent to the IANAPLAN working
group list by the chairs of the IANA Transition Coordination
Group (ICG) on May 27th.

While I am carrying this response back to the ICG, the substance
of this response has been discussed in the IANAPLAN working
group and the relevant parts of IETF leadership. I believe this
response represents the (rough) consensus opinion that
emerged in the discussion, as well as the current state
of IANA arrangement updates that our leadership bodies
have been working on.

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 of 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 and domains. The
IETF Trust has signalled that it would be willing to do this,
if asked. We are awaiting 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​ 
transition 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 Arkko, IETF Chair
(reporting his summary of the situation)