IETF Logo Mail Archive

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

Rik Ribbers <rik.ribbers@sidn.nl> Tue, 21 July 2015 14:28 UTC

Return-Path: <rik.ribbers@sidn.nl>
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 832EB1B2D7B for <eppext@ietfa.amsl.com>; Tue, 21 Jul 2015 07:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.294
X-Spam-Level:
X-Spam-Status: No, score=0.294 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] 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 KnWuWDc8Fhch for <eppext@ietfa.amsl.com>; Tue, 21 Jul 2015 07:28:37 -0700 (PDT)
Received: from arn2-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 447841A8847 for <eppext@ietf.org>; Tue, 21 Jul 2015 07:28:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn-nl; c=relaxed/relaxed; h=from:to:subject:thread-topic:thread-index:date:message-id:references:in-reply-to:accept-language:content-language:x-ms-has-attach:x-ms-tnef-correlator:x-originating-ip:content-type:content-transfer-encoding:mime-version; bh=qfanAd+Tk/NI/Gk6vnf64wyfSfQfDGJXwgPSDaGNXAA=; b=IVtLhWEPHwal7z3jEg5LkBKPRmWyMaPTus39t+kOBBHLMY0P8Wjiyh/phDHpNIuAo8Q8DMu0sON108yoLXGkvw6a0zO8Y4EOoOv/NJvL0qk8qQZZu1aY14i3i72XtAMbbaPOsP3VPHpiNjJyIAa5s1Zc5fcWSKTep2r4nwd31+gcqHLNzgcx+l+Ig4tSbyp7AApdHzlqs5rQGWljC0yXNM1tWdBEKnwmpuHjjNLJn07mTXUMYoO+bx/IIhanCZwTc5302ntXCC0gwkTmx0VWPqCcmHZMxVHXLbYr1KUM93cNOs51lI9XM1qJjV2KfWUD+vjSJCYm9tw+xCgPsvK0Sw==
Received: from ka-mbx02.SIDN.local ([192.168.2.178]) by arn2-kamx.sidn.nl with ESMTP id t6LESZF5011350-t6LESZF7011350 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=CAFAIL); Tue, 21 Jul 2015 16:28:35 +0200
Received: from KAHUBCASN02.SIDN.local (192.168.2.76) by ka-mbx02.SIDN.local (192.168.2.178) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Tue, 21 Jul 2015 16:28:35 +0200
Received: from KAMBX1.SIDN.local ([fe80::501d:affc:30a9:4edf]) by kahubcasn02 ([192.168.2.74]) with mapi id 14.03.0224.002; Tue, 21 Jul 2015 16:28:31 +0200
From: Rik Ribbers <rik.ribbers@sidn.nl>
To: 'Antoin Verschuren' <ietf@antoin.nl>, "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: [eppext] Working Group Last call for draft-ietf-eppext-launchphase
Thread-Index: AQHQwybpf1JbAhh/WUeMhfVetA5MEJ3l+4tw
Date: Tue, 21 Jul 2015 14:28:30 +0000
Message-ID: <C80127C588F8F2409E2B535AF968B768BA20273B@kambx1.SIDN.local>
References: <B785119F-67E7-4B34-9995-6A6F5806DF10@antoin.nl>
In-Reply-To: <B785119F-67E7-4B34-9995-6A6F5806DF10@antoin.nl>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.2.172]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/UvQWpcfS3aDkO3ccksT9X0N6EbI>
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, 21 Jul 2015 14:28:39 -0000

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

v2.23.0 | Report a Bug | By Email