Re: [Ianaplan] Update on IANA Transition & Negotiations with ICANN

"Richard Hill" <> Thu, 30 April 2015 15:16 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 522C71A92B0 for <>; Thu, 30 Apr 2015 08:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nJeXLu8s5mLt for <>; Thu, 30 Apr 2015 08:16:39 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3153F1A01F0 for <>; Thu, 30 Apr 2015 08:16:38 -0700 (PDT)
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t3UFGWJS021547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 30 Apr 2015 17:16:33 +0200
Received: from Timea ( []) (authenticated bits=0) by (8.14.5/8.14.5) with ESMTP id t3UFGV3J010284; Thu, 30 Apr 2015 17:16:32 +0200
From: "Richard Hill" <>
To: "'Andrew Sullivan'" <>, <>
References: <>
In-Reply-To: <>
Date: Thu, 30 Apr 2015 17:16:36 +0200
Message-ID: <00c401d08358$a715f860$f541e920$@ch>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdCDPOZePD0hwP8dTHSAilNVV9Y64AAG2ibQ
Content-Language: fr-ch
Archived-At: <>
Subject: Re: [Ianaplan] Update on IANA Transition & Negotiations with ICANN
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, 30 Apr 2015 15:16:42 -0000

Dear Andrew,

Thank you for this. Can you please post the exact language that ICANN has
difficulty with?

I fully agree that the two bullets below seem to me to be consistent with
the current IANA contract between ICANN and NTIA.

However, we are discussing arrangements that would hold if there is no
longer any contract between ICANN and NTIA, so I don't understand how the
current contract conditions could prevent ICANN from agreeing to future


> -----Original Message-----
> From: Ianaplan [] On Behalf Of Andrew
> Sullivan
> Sent: jeudi, 30. avril 2015 13:58
> To:
> Subject: [Ianaplan] Update on IANA Transition & Negotiations with ICANN
> Dear colleagues,
> This is an update to the community on the current discussion between
> the IETF and ICANN regarding the annual SLA or Supplemental Agreement.
> Each year, the IETF (via the IAOC) and ICANN specify a supplemental
> agreement to our Memorandum of Understanding, in order to ensure that
> any gaps or identified operational issues are addressed.
> As you are aware, inspired by the request from the IANA Stewardship
> Transition Coordination Group (ICG), last year we formed the IANAPLAN
> working group and achieved IETF consensus on the state of affairs with
> IANA registries published under the direction of the IETF.  That
> consensus is captured in draft-ietf-ianaplan-icg-response-09, which was
> transmitted to the ICG.  In that document the community sought to have
> some facts acknowledged as part of any IANA transition plan:
>   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
> Understanding this consensus, the IETF leadership have been negotiating
> with ICANN to include text to satisfy these points in our annual
> Service Level Agreement.  After some iterations, we arrived at text
> that we think captures the IETF consensus, but ICANN has informed us
> that they are unable to agree to that text right now.  ICANN told us
> that, in their opinion, agreeing to that text now would possibly put
> them in breach of their existing agreement with the NTIA.
> It is our view that the substance of the statements above is already
> part of our agreement with ICANN, and that we are merely elaborating
> details of that existing agreement.  We expect that as we continue
> towards the orderly winding down of NTIA's involvement in the IANA
> processes, our existing arrangements will be preserved, in keeping with
> IETF consensus.
> We will of course continue to assess the situation, agreements, and
> next steps, as well as developments in other operational communities.
> We think that the existing agreement between ICANN and the IETF makes
> good sense, and is good for the Internet.  The IETF has stated very
> strongly that it supports that existing agreement.  That strong support
> is a necessary condition for success, and we shall not waver in our
> commitment to the IETF's continued responsible stewardship of the
> protocol parameters registries.
> We note that the IETF community remains very satisfied with ICANN's
> current level of performance.  The existing supplemental agreement,
> from last year, continues until it is replaced.
> We welcome your thoughts about this situation.  We will continue to use
> the IANAPLAN mailing list for these discussions.
> Best regards,
> Jari Arkko
> IETF Chair
> Tobias Gondrom
> IAOC Chair
> Andrew Sullivan
> IAB Chair
> --
> Andrew Sullivan
> _______________________________________________
> Ianaplan mailing list