Re: [Ianaplan] Time frame inquiry

Ted Hardie <ted.ietf@gmail.com> Wed, 27 May 2015 23:31 UTC

Return-Path: <ted.ietf@gmail.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 A1BC51AC3A5 for <ianaplan@ietfa.amsl.com>; Wed, 27 May 2015 16:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 9DVIGh_zg7Wg for <ianaplan@ietfa.amsl.com>; Wed, 27 May 2015 16:30:59 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC93F1A90C1 for <ianaplan@ietf.org>; Wed, 27 May 2015 16:30:58 -0700 (PDT)
Received: by wizo1 with SMTP id o1so41033951wiz.1 for <ianaplan@ietf.org>; Wed, 27 May 2015 16:30:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mBdgzvkPmpL8MBXNr+Bte8YZr+CZqMFVPxGxhmRlW28=; b=L9/+ZSJ3s9rOhjbJTmubfScAPbojWB4pwfgBpWOTXEWoQlIMmxSKY6G3BtLo/U/U96 bdg9ESBoZuunlZWnlAHCeme5JgYYuP2rLYiNAcJxmjwnzF/RtVjLzllyxh/gAW+/BuXs WOxdru8TC9NiwgCl+2jvCOI7VBpNkm73tRnHhVN3LTVxo5dohcnzJduxD0Z9BpLTOR1u oTdADYImQF73lNph5L4bKb9aVoHff8YeXRQAi1x1WuNuPU1knSSGUl5vQASE/R9rNH6S UtVDOHpSPJ04qfJ2iOishbny/LcV7p8KYkLxHfRwTzBPuU43unRFh3Eo2hNP/7hISWS1 KkDA==
MIME-Version: 1.0
X-Received: by 10.194.187.170 with SMTP id ft10mr63511335wjc.26.1432769457642; Wed, 27 May 2015 16:30:57 -0700 (PDT)
Received: by 10.194.91.133 with HTTP; Wed, 27 May 2015 16:30:57 -0700 (PDT)
In-Reply-To: <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> <97267ED7-D8A2-4A64-AB74-07434190DD89@piuha.net>
Date: Wed, 27 May 2015 16:30:57 -0700
Message-ID: <CA+9kkMBZq_U+CC5Jzv5T3pL7qasUHSfv-Gu8q4P36+phABXxzg@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=047d7bb03a92916342051718a2e9
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/782kIViTUfGU_QYZJP06WLydi7w>
Cc: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>, John Curran <jcurran@istaff.org>, Russ Housley <housley@vigilsec.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: Wed, 27 May 2015 23:31:01 -0000

Hi Jari,

Some thoughts on specific language below.

On Wed, May 27, 2015 at 4:00 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

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


​Should we not summarize these issues here?​



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

Would this also work: "
Once these SLAs are 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.
>
> 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.”
>
>
​I think we may want to highlight this slightly differently.

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

regards,

Ted




> Jari
>
>
>
>
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan
>
>