Re: [Ianaplan] Time frame inquiry

Tobias Gondrom <tobias.gondrom@gondrom.org> Wed, 27 May 2015 21:42 UTC

Return-Path: <tobias.gondrom@gondrom.org>
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 841171AC44E for <ianaplan@ietfa.amsl.com>; Wed, 27 May 2015 14:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.665
X-Spam-Level:
X-Spam-Status: No, score=-96.665 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_HELO_EQ_D_D_D_D=1.597, HELO_DYNAMIC_IPADDR=1.951, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no
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 dJZ5tG_2x1re for <ianaplan@ietfa.amsl.com>; Wed, 27 May 2015 14:42:51 -0700 (PDT)
Received: from lvps5-35-241-16.dedicated.hosteurope.de (www.gondrom.org [5.35.241.16]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C048E1AC439 for <ianaplan@ietf.org>; Wed, 27 May 2015 14:42:51 -0700 (PDT)
Received: from [192.168.178.26] (x590f21b4.dyn.telefonica.de [89.15.33.180]) by lvps5-35-241-16.dedicated.hosteurope.de (Postfix) with ESMTPSA id D7B7C637C4; Wed, 27 May 2015 23:42:49 +0200 (CEST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gondrom.org; b=iF+PUfyVqLDUz1MCN1jTRFoJiIueYRSKIMWaKFgg/vpoCLOfyDB7gUyQsEO34vkxbajJf7qvtAAtDDE7stxoC1svTpPDksLSwgIW7Mt2yZrJAYDuyoOuCmLW4Q5qJ8h6fxwpj7l9PAia+d/qdi4h7IyUjqt9MVy4IOEZngoqt50=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
Message-ID: <55663A59.8000309@gondrom.org>
Date: Wed, 27 May 2015 23:42:49 +0200
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: housley@vigilsec.com, jcurran@istaff.org
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>
In-Reply-To: <893FE3E3-A2DD-40D8-B39F-1EB24DFE1806@vigilsec.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/aQe8umCL6vcGoSTf0le5rfG-f5k>
Cc: 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 21:42:53 -0000


On 27/05/15 20:59, Russ Housley wrote:
> John:
>
>> On May 27, 2015, at 1:33 PM, Russ Housley <housley@vigilsec.com> wrote:
>>> ...
>>> However, we also do not believe that we have accomplished a transition until that updated SLA is signed.  We have no way to know when ICANN will get the needed permission.  So, from that perspective, the answer to the question from the ICG leadership is "we do not know”.
>> It would probably be best to provide an answer with sufficient context to allow NTIA
>> (as the eventual receipt of the information) with the ability to interpolate based on its
>> own knowledge.   For example -
>>
>> “In order to be ready for the stewardship transition, the IETF requires an updated SLA
>> with ICANN which addresses these two issues.  An updated SLA has been drafted and
>> the protocol parameter community can be ready for stewardship transition immediately
>> after its has been executed with ICANN.   At this time, we do not have any information
>> regarding when ICANN will be able to enter into the updated SLA.”
> I was trying to start the conversation on this list ...
>
> I agree with your proposed formulation.
>
> Russ

I agree with Russ.
Best regards, Tobias



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