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

James Galvin <galvin@elistx.com> Wed, 04 November 2015 20:29 UTC

Return-Path: <galvin@elistx.com>
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 92E381A0018 for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 12:29:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, USER_IN_WHITELIST=-100] 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 KCZHhezpRP2P for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 12:29:46 -0800 (PST)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (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 87B141A0020 for <eppext@ietf.org>; Wed, 4 Nov 2015 12:29:46 -0800 (PST)
Received: by qgeo38 with SMTP id o38so50883423qge.0 for <eppext@ietf.org>; Wed, 04 Nov 2015 12:29:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elistx_com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=EXxeOWHGuFb0vXJqBrUWLiZV7shCPzH8EZtKZE8GwOk=; b=b0g7fClcHwBqHZjbNhCulI0LqBWP1wBOXh+b2jPdNQLUIypS8umOc/St6JvrIb0Cme 2cIex+Hp48xVZBWpgJqhr/x0qJck7c7ipZXM49b8Wes7r1gV1c2FNrwLN8mi8kkAJojY L6/MhVU9Cx/TdPf1z+h0AoeNip9PYzXFUSfvZZMs9slNlhLjPkmRz9MGkHyllgxTzpCQ ibWKA1plNk1ggwljbBBiuFLooaAG40Zfmdl8HtE+tK3t/pkjs1tcLX/WeI+sgx6XC4rM cdfd60tBEgDyPJnfEI+QElicz4f9drJr0/tUpwgVG0JwHXWG35KYCJiZMvcavpH7g3O+ a57g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=EXxeOWHGuFb0vXJqBrUWLiZV7shCPzH8EZtKZE8GwOk=; b=JvlsgwUHLYc1zV99GCoEa39hhwCgqvSgfmNAm9hgWfQZooj6UAN43vKKBk8/a/+E3e BkAS1YB28xfETjZZ9fmX4Wtbf9VBxGvuFPn/M/u2KVxL+JRB67RsoIKGo9s9U68wLrHU qjDI1wOOThUZAhlXfZqaKFNJrB4pHqpoasBHCqZn1LVkIAQywB0/a0y9sw+FIVFe5EC6 ghzY0pSsPgildK7iJGO93uIjfIs7qVdkDxAQsVfSTs+QEHFdD+Shgwm6k4cQMJeg1HNl 45kUlf5WIon/fY2diZJzdUj6Y6MWTH6wDzGF1BE3le0XaU+Z6izrvTmsQJE13hAoOGp4 WEzw==
X-Gm-Message-State: ALoCoQkSXSLPGc4+1XMX4+HQezYPDrN5uE+pDaRBbd1F+xsy39k+CtnJOHl0EvLGw4o0tYZOeIea
X-Received: by 10.140.91.108 with SMTP id y99mr3705377qgd.68.1446668985714; Wed, 04 Nov 2015 12:29:45 -0800 (PST)
Received: from jgalvin-lt.local (c-73-133-108-218.hsd1.md.comcast.net. [73.133.108.218]) by smtp.googlemail.com with ESMTPSA id a64sm754446qka.47.2015.11.04.12.29.44 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Nov 2015 12:29:44 -0800 (PST)
To: "Gould, James" <JGould@verisign.com>
References: <B785119F-67E7-4B34-9995-6A6F5806DF10@antoin.nl> <C80127C588F8F2409E2B535AF968B768BA20273B@kambx1.SIDN.local> <563A6547.40308@elistx.com> <655334FD-E69C-4949-9B39-E12AA7EFA70B@verisign.com>
From: James Galvin <galvin@elistx.com>
Message-ID: <563A6AD8.6050309@elistx.com>
Date: Wed, 4 Nov 2015 15:30:16 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <655334FD-E69C-4949-9B39-E12AA7EFA70B@verisign.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/HltdD114mdL3oZzBLYE2946VO14>
Cc: Rik Ribbers <rik.ribbers@sidn.nl>, Antoin Verschuren <ietf@antoin.nl>, "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: Wed, 04 Nov 2015 20:29:48 -0000

The draft-ietf-eppext-tmch-smd draft is in "AD evaluation" state, i.e., 
it has already been submitted. Barry will comment on the details of its 
status during the meeting.

What is your response to Rik's suggested change?

Thanks,

Jim


On 11/4/15 3:19 PM, Gould, James wrote:
> Yes, this is stealing my thunder from the meeting, but I agree that they need to be moved up together.  I would actually move these two as well as the smd draft up together.
>
> Sent from my iPhone
>
>> On Nov 4, 2015, at 3:06 PM, James Galvin <galvin@elistx.com> wrote:
>>
>> This issue raised by Rik Ribbers has not been addressed by the working group.  Would the authors, and any one from the working group please comment?  Rik's suggestion seems reasonable to me but I would like to see confirmation from the authors.
>>
>> With this suggestion address this document is ready to move forward. However, it is dependent on draft-ietf-eppext-tmch-func-spec/, so I'd like to hold it in the working group and submit these two documents together.
>>
>> In addition to the change suggested above, we need a document shepherd to move this forward.  Would anyone like to volunteer?
>>
>> Jim
>>
>>
>>
>>
>>
>>
>>> On 7/21/15 10:28 AM, Rik Ribbers wrote:
>>> All,
>>>
>>> I finished the review. There is one issue that I raised earlier that (imho) needs some more clarification in the document.
>>>
>>> See http://www.ietf.org/mail-archive/web/eppext/current/msg00585.html
>>>
>>> We have interpreted section 2.3 different then the other implementers with respect to the normal or vanilla (as Alexander suggested) domain check.
>>>
>>> Having fully re-read the draft I am not sure if this issue should be addressed here or in the lozano functional specification
>>> (https://datatracker.ietf.org/doc/draft-lozano-tmch-func-spec/). However the last is expired and not getting any attention. In this draft there are several requirements concerning Domain Registration, there are no requirements concerning Domain Availability. So if nothing is specified the vanilla domain check can be used.
>>>
>>> However section 2.3 suggest one MUST provide a launchphase...... so what to do....
>>>
>>> My suggestion is to add a few wording (slightly different then my previous proposal):
>>>
>>> ** old **
>>> The <launch:phase> element MUST be included by the client to define the target launch phase of the command.
>>>
>>> ** new **
>>> The <launch:phase> element MUST be included by the client to define the target launch phase of the command when using this EPP extension.
>>>
>>> Gr,
>>> Rik
>>>
>>>
>>> -----Original Message-----
>>> From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Antoin Verschuren
>>> Sent: maandag 20 juli 2015 22:02
>>> To: eppext@ietf.org
>>> Subject: [eppext] Working Group Last call for draft-ietf-eppext-launchphase
>>>
>>> Greetings,
>>>
>>> This is the starting of the WGLC on the Launch Phase Mapping for the Extensible Provisioning Protocol (EPP).
>>> There was extensive discussion on the mailing list, an we believe the outcome is incorporated in the document and is ready for WGLC.
>>> The current version of this document can be found here:
>>>
>>>    https://www.ietf.org/id/draft-ietf-eppext-launchphase-05.txt
>>>
>>> We'll have a 1,5 week period for comments, closing on Friday, 31 July 2015.
>>>
>>> During last call the chairs are looking for a document shepherd for this document.
>>> If you're interested, please contact the chairs. The document authors can not be the shepherd.
>>>
>>> thanks,
>>>
>>> - --
>>> Antoin Verschuren
>>>
>>> Tweevoren 6, 5672 SB Nuenen, NL
>>> M: +31 6 37682392
>>> xmpp:antoinverschuren@gmail.com
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> EppExt mailing list
>>> EppExt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/eppext
>>
>> _______________________________________________
>> EppExt mailing list
>> EppExt@ietf.org
>> https://www.ietf.org/mailman/listinfo/eppext
>>
>