Re: [Ianaplan] Time frame inquiry

Benson Schliesser <bensons@queuefull.net> Sat, 30 May 2015 23:47 UTC

Return-Path: <bensons@queuefull.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 890821A8A50 for <ianaplan@ietfa.amsl.com>; Sat, 30 May 2015 16:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 sniBWSLl7SXs for <ianaplan@ietfa.amsl.com>; Sat, 30 May 2015 16:47:44 -0700 (PDT)
Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) (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 6BD641A892F for <ianaplan@ietf.org>; Sat, 30 May 2015 16:47:44 -0700 (PDT)
Received: by iebgx4 with SMTP id gx4so86451819ieb.0 for <ianaplan@ietf.org>; Sat, 30 May 2015 16:47:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=14jjCI/oqjVJ79q7s/cH6A/G34QYLcipqEJALojmAkk=; b=PplXFNiZjRaRTeq/f9Dy54Kf7gY30KjZ3764JDqkUw1NN/yIHwbyrhTPWpa9YOoQju F4O20idpM/S4wFGjJQmj3Ep0NlsZRjoE322Fo2ygsNCk13DjLBXW7B02xkyz3tSJQqsh n9zwWk6aPXO5iPJa0JN8eV5sfWFuNkZbCph3mb4J5K4E2uG27UzWsxE4hTtCYIfgg/0X U9IbZsrccwkHnITC/UbXFnROea2mMngNtdgHDe3XdLxEIrYbcZw9SO0Vh5wsMb4CLKZE 60r4m2x/0nQuhUS0bopSviM//ZrczgQw6ttReRhKVCSbVZqjMD+gFQw4azgSujV0RcTU gsKw==
X-Gm-Message-State: ALoCoQnUoCGKUhOX/FH0x+t+7dGTckZyazKLLhTyjF5Hs1iMPsl00MGusP4STH4oxzR7bK2gTL7L
MIME-Version: 1.0
X-Received: by 10.50.64.243 with SMTP id r19mr5096204igs.5.1433029663719; Sat, 30 May 2015 16:47:43 -0700 (PDT)
Received: by 10.107.11.16 with HTTP; Sat, 30 May 2015 16:47:43 -0700 (PDT)
In-Reply-To: <5569EDCC.2060807@queuefull.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> <CA+9kkMBZq_U+CC5Jzv5T3pL7qasUHSfv-Gu8q4P36+phABXxzg@mail.gmail.com> <4AB120DC-AFB1-4915-B6C5-7417FB989878@piuha.net> <55669A78.3020309@cisco.com> <C8B9D0E8-C363-4618-8941-D0027B86EB7A@piuha.net> <5569EDCC.2060807@queuefull.net>
Date: Sat, 30 May 2015 19:47:43 -0400
Message-ID: <CAP4=VchFM2Bp2ZJ5ePKVEbZWtW_DazCvmfL5TGAD8eE_Mv0RUw@mail.gmail.com>
From: Benson Schliesser <bensons@queuefull.net>
To: Jari Arkko <jari.arkko@piuha.net>, "ianaplan@ietf.org" <ianaplan@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bdc9d880f1fc50517553832
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/qF2C2VvYcbWAVUEZBjDC0EfPy5E>
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: Sat, 30 May 2015 23:47:45 -0000

Just to clarify one point, in response to an off-list conversation:

On Saturday, May 30, 2015, Benson Schliesser <bensons@queuefull.net> wrote:
>
>
> The approach that we've undertaken (updating the MOU with ICANN) is
> probably the most simple,


To be clear, I'm referring to our update of the SLA with ICANN. I was being
lazy in referring to that as "updating the MOU". Sorry if that was
confusing in any way.

-Benson