IETF Logo Mail Archive

Re: [eppext] Working Group Last call for draft-ietf-eppext-launchphase

Gustavo Lozano <gustavo.lozano@icann.org> Tue, 08 September 2015 18:08 UTC

Return-Path: <gustavo.lozano@icann.org>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A27EF1A6EDC for <eppext@ietfa.amsl.com>; Tue, 8 Sep 2015 11:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.428
X-Spam-Level:
X-Spam-Status: No, score=-3.428 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_BASE64_BLANKS=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] 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 Df4QmBm66rCe for <eppext@ietfa.amsl.com>; Tue, 8 Sep 2015 11:08:50 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0543A1ACD1D for <eppext@ietf.org>; Tue, 8 Sep 2015 11:08:50 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Tue, 8 Sep 2015 11:08:48 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1044.021; Tue, 8 Sep 2015 11:08:48 -0700
From: Gustavo Lozano <gustavo.lozano@icann.org>
To: "Gould, James" <JGould@verisign.com>, Antoin Verschuren <ietf@antoin.nl>
Thread-Topic: [eppext] Working Group Last call for draft-ietf-eppext-launchphase
Thread-Index: AQHQ6mFoGbf7RCJ080aun0VGWRFwaw==
Date: Tue, 08 Sep 2015 18:08:47 +0000
Message-ID: <D21471F4.BAA62%gustavo.lozano@icann.org>
References: <B785119F-67E7-4B34-9995-6A6F5806DF10@antoin.nl> <831693C2CDA2E849A7D7A712B24E257F4A022CD2@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F4A022D7F@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <C41D7AF7FCECBE44940E9477E8E70D7A4AE9BCF3@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F4A0246A7@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <9843E2BC-3B81-4453-9C74-6D698CC1CD37@antoin.nl> <D1D7C62A.B1D22%gustavo.lozano@icann.org> <9EB25C37-7061-45F9-81CF-1E54DCAF57B6@verisign.com>
In-Reply-To: <9EB25C37-7061-45F9-81CF-1E54DCAF57B6@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.4.150722
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.35.2]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3524555322_2207717"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/0VEbCU-1lzrB2IL1OPHOpuZu7kY>
Cc: "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] Working Group Last call for draft-ietf-eppext-launchphase
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Sep 2015 18:08:52 -0000

Jim,

I have not asked the WG (on the mailing list) to formally adopt the draft as
a WG document, because I was working on a new version to clean up the text
and add the missing security section.

I have not been able to invest time on the draft in the previous weeks,
therefore if there are no objections from the chairs or the WG, I will
rename draft-lozano-tmch-func-spec-10 to draft-ietf-eppext-tmch-func-spec-00
on Fri COB, and publish version 01 with the missing security section asap.

Regards,
Gustavo

From:  "Gould, James" <JGould@verisign.com>
Date:  Tuesday, September 8, 2015 at 06:04
To:  Antoin Verschuren <ietf@antoin.nl>
Cc:  "eppext@ietf.org" <eppext@ietf.org>, Gustavo Lozano
<gustavo.lozano@icann.org>
Subject:  Re: [eppext] Working Group Last call for
draft-ietf-eppext-launchphase

> What is the status of the WG adopting draft-lozano-tmch-func-spec and moving
> draft-ietf-eppext-launchphase forward?
> 
> Thanks,
> 
> ‹
> 
> 
> 
> JG
> 
> 
> 
> 
> James Gould
> Distinguished Engineer
> jgould@Verisign.com
> 
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
> 
> VerisignInc.com <http://VerisignInc.com>
> 
>> On Jul 24, 2015, at 4:40 AM, Gustavo Lozano <gustavo.lozano@icann.org> wrote:
>> 
>> Hi Antoin,
>> 
>> Comments inline.
>> 
>> Regards,
>> Gustavo
>> 
>> On 7/23/15, 14:10, "EppExt on behalf of Antoin Verschuren"
>> <eppext-bounces@ietf.org on behalf of ietf@antoin.nl> wrote:
>> 
>>> 
>>> We have 2 options for this:
>>> -Replace the normative reference to another stable document, perhaps an
>>> ICANN document?
>>> -Revive draft-lozano-tmch-func-spec and take it up as a WG document and
>>> proceed that one first.
>> 
>> draft-lozano-tmch-func-spec has been revived.
>> 
>> 
>>> 
>>> Gustavo: Are you willing to revive your document as it is currently
>>> expired,
>> 
>> Yes 
>> 
>>> and make a request to the WG to adopt it?
>> 
>> I will request the adoption of this ID as a WG document.
>> 
>>> The WG can perhaps already review this document in parallel and provide
>>> you with feedback.
>> 
>> This will be great.
>> 
>> Regards,
>> Gustavo
>> _______________________________________________
>> EppExt mailing list
>> EppExt@ietf.org
>> https://www.ietf.org/mailman/listinfo/eppext
>

v2.23.0 | Report a Bug | By Email