Re: [Ianaplan] Time frame inquiry

Jari Arkko <jari.arkko@piuha.net> Wed, 27 May 2015 23:00 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 90C971A8ADD for <ianaplan@ietfa.amsl.com>; Wed, 27 May 2015 16:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 m-7pU44GVblM for <ianaplan@ietfa.amsl.com>; Wed, 27 May 2015 16:00:17 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D3F891A1AD9 for <ianaplan@ietf.org>; Wed, 27 May 2015 16:00:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 65C452CED5; Thu, 28 May 2015 02:00:15 +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 0-g_d-NS9qI3; Thu, 28 May 2015 02:00:14 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 88EAD2CED3; Thu, 28 May 2015 02:00:14 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Content-Type: multipart/signed; boundary="Apple-Mail=_79C4CBC8-D784-4807-896F-8080B62336B4"; 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: <893FE3E3-A2DD-40D8-B39F-1EB24DFE1806@vigilsec.com>
Date: Thu, 28 May 2015 02:00:11 +0300
Message-Id: <97267ED7-D8A2-4A64-AB74-07434190DD89@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>
To: Russ Housley <housley@vigilsec.com>, John Curran <jcurran@istaff.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/KKL4Cdvwxkd_zR5H5WKtRuHCJsY>
Cc: "Ianaplan@Ietf. Org" <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: Wed, 27 May 2015 23:00:19 -0000

I think we are going about this from a slightly wrong direction.
I think there’s some desire on ICANN side to transition in an
atomic fashion. Right or wrong...

But I think the answer from our side is essentially: we are
ready to proceed with the (final) steps of the transition today,
if NTIA, ICANN, etc. are. And these steps are “final” because
much of the necessary structure in our case has been built
in earlier years. And at least from my perspective those
steps could also be seen as our normal course of yearly
business improvement, rather than some grandiose
moment that various people need to get very excited
about :-)

Anyway, also, as discussed in the last days, different directions
in the details for the CWG process might have effects that we have
to consider.

And of course, if at any point in time someone wants us to
do something different or more, that would have an effect.

But I think my answer today would be as follows. Basing it
on John’s excellent text:

“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.

From our perspective the remaining step is an updated
SLA with ICANN which addresses two issues. The update
has been drafted and from our perspective could be
immediately executed. When executed — and with
the NTIA contract with ICANN is voided -- from our
perspective the protocol parameter community
has completed the stewardship transition.

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.

Second, the names community has developed a
“Post Transition IANA” (PTI) structure in their
proposal. Not all details of that are clear at this
point in time. Depending on the final setting of
those details, this may require no further action
from the IETF, if we can keep our existing contracts
in place. That is our preference. However, if the names
community decides on a structure that requires changes
to our contracts or further participation in the internal
structure governing the PTI, this will require further
work and community agreement.”

Jari