Re: [Ianaplan] Time frame inquiry

Bob Hinden <> Thu, 28 May 2015 17:11 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 833A31A82E2 for <>; Thu, 28 May 2015 10:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nMTVcHxAzC-h for <>; Thu, 28 May 2015 10:11:06 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 49D0B1A1F16 for <>; Thu, 28 May 2015 10:11:06 -0700 (PDT)
Received: by iepj10 with SMTP id j10so43318841iep.3 for <>; Thu, 28 May 2015 10:11:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=Or8jDlc+dIlUy3tMbbAV5WElg6R9RLYv18qpJfwHdbs=; b=uXSpxUfcEOUv75yeRsrPsr+qPu6RIc+SvfmNsPlAZm7eLwNT6nxt1094qWemc2R7a2 RRy82qJQWFwynOLdUzrZOBypCSEr0TLWnjIVbqz8QyyEXpSeqqjumWhZLiZ03z+WjTMQ 8XsiNumeFK+ZoKwMO1DqIpTMbnB6FeMa/cQkBE/tlpuRQkfyNUgAh4IDL32yDN6lR68c a/kNg6+MjBGM5OHh0TDylRb8LFevc2aGhea7ZcFoqfWaAHcgvkfxV9C3HM1cwUOuhYMa E/zU2UFfBj8tjZ5a/wBYtvc9s2J2Yy6n5mE/Utd6JDrGYtrDT0xwstQXcG+Ne3F1hUaR moGQ==
X-Received: by with SMTP id a9mr10884870icl.9.1432833065830; Thu, 28 May 2015 10:11:05 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id h33sm2185074iod.12.2015. (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 May 2015 10:11:05 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E62AB7AE-008D-4507-8747-D9A93D953616"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Bob Hinden <>
In-Reply-To: <>
Date: Thu, 28 May 2015 10:11:03 -0700
Message-Id: <>
References: <> <> <> <> <> <> <> <> <> <>
To: Andrew Sullivan <>
X-Mailer: Apple Mail (2.2098)
Archived-At: <>
Cc:, Bob Hinden <>
Subject: Re: [Ianaplan] Time frame inquiry
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 28 May 2015 17:11:08 -0000

> On May 28, 2015, at 10:04 AM, Andrew Sullivan <> wrote:
> I like this text.

As do I.  Ship it!


> 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
>> 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
> --
> Andrew Sullivan
> _______________________________________________
> Ianaplan mailing list