Re: [eppext] Seemingly contradictory/ambiguous language in draft-ietf-eppext-launchphase-04

"Gould, James" <JGould@verisign.com> Fri, 06 March 2015 12:08 UTC

Return-Path: <JGould@verisign.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 E6BB41ACDAF for <eppext@ietfa.amsl.com>; Fri, 6 Mar 2015 04:08:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 fC9KE9SndFmZ for <eppext@ietfa.amsl.com>; Fri, 6 Mar 2015 04:08:34 -0800 (PST)
Received: from mail-oi0-f100.google.com (mail-oi0-f100.google.com [209.85.218.100]) (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 9A7AD1ACD9C for <eppext@ietf.org>; Fri, 6 Mar 2015 04:08:34 -0800 (PST)
Received: by oiba3 with SMTP id a3so2397265oib.1 for <eppext@ietf.org>; Fri, 06 Mar 2015 04:08:34 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:mime-version; bh=HJ6BhR+xe8Sr/L+FzvnF/05rEeEhlXTgO/zelDichOo=; b=A4GdHEJvXi8Jd43rsvdrzdUyuNdiiBR3SQWz7OpfaUB0mA4P7XucVuXcz/ghgZ6sTT E9CQiAJ/4eSwqVBqzo6Pf7R+HWfX3sgS5bJi6Y5RBuEBGvWw/c/XNYszsSAJRj6W98LZ F/EaT7HKUkKA32aS1aRG1NkXJ+kJpnoFcf4MHGs5iPyAuTE8FCIGzzWZ5kbgF+4x1gbh P66NcLR5HMAC9S+zPuzYBVZccF0/qX8xlSn42Ju2eHGM+y7v9wg534w1gd4U0+wq1pYD gwaRVgafPgEZg9R5P0aDZ6hqxZacbCKZiv/Nhuau9OgvIdx6mmAGT5mMZ9fpEUZZp1TB p/Kw==
X-Gm-Message-State: ALoCoQnLL6uq8w/TenIM4dys6nF8W9ZiUqamGSXmu2qEu76ROKnWYHLvnN4I8y1GGH3BI1JaLQ0lNT3+ILJ8QZiOqfqpovsnPg==
X-Received: by 10.55.16.83 with SMTP id a80mr16010604qkh.86.1425643713979; Fri, 06 Mar 2015 04:08:33 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by mx.google.com with ESMTPS id jy4sm2925092qcb.0.2015.03.06.04.08.33 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 06 Mar 2015 04:08:33 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t26C8X0t000426 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Mar 2015 07:08:33 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Fri, 6 Mar 2015 07:08:32 -0500
From: "Gould, James" <JGould@verisign.com>
To: Keith Gaughan <keith@blacknight.com>
Thread-Topic: [eppext] Seemingly contradictory/ambiguous language in draft-ietf-eppext-launchphase-04
Thread-Index: AQHQWAOvVdHofzTd+k6eyZCV/v+cPZ0PsFgA
Date: Fri, 6 Mar 2015 12:08:13 +0000
Message-ID: <928D2CA3-CB8E-475F-96DE-36734AAE4074@verisign.com>
References: <54F99463.6090101@blacknight.com>
In-Reply-To: <54F99463.6090101@blacknight.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/related; boundary="_004_928D2CA3CB8E475F96DE36734AAE4074verisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/PEmJtxF7MIUQIpHvzN6RA-nazg0>
Cc: "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] Seemingly contradictory/ambiguous language in draft-ietf-eppext-launchphase-04
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 12:08:37 -0000

Keith,

I agree adding a comma would be helpful to separate the two cases of the use of the “name” attribute; although I don’t believe the implementers have had an issue with how it’s currently defined.  Any additional nit feedback like this would be very helpful.

Thanks,


—


JG


[cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://VerisignInc.com>

On Mar 6, 2015, at 11:49 AM, Keith Gaughan <keith@blacknight.com<mailto:keith@blacknight.com>> wrote:

In SS2.3, it states:

  For extensibility, the <launch:phase> element includes an OPTIONAL
  "name" attribute that can define a sub-phase or the full name of the
  phase when the <launch:phase> element has the "custom" value.

Which seems to imply that the 'name' attribute is only meant to be used
when <launch:phase> has a value of 'custom'.

The I-D seem to immediately contradict itself with the following:

  For example, the "claims" launch phase could have two sub-phases that
  include "landrush" and "open".

The only way I can reconcile these is if the first sentence has a
punctuation error in it and should read:

  For extensibility, the <launch:phase> element includes an OPTIONAL
  "name" attribute that can define a sub-phase, or the full name of the
  phase when the <launch:phase> element has the "custom" value.

The addition of the comma after 'sub-phase' clarifies that 'sub-phase'
refers to phase values other than 'custom' and that the 'name' attribute
can be used with phases other than 'custom'.

K.

--
Keith Gaughan, Development Lead
PGP/GPG key ID: 82AC3634
Blacknight Internet Solutions Ltd. <http://blacknight.host/>
12A Barrowside Business Park, Carlow, Ireland
Registered in Ireland, Company No.: 370845

_______________________________________________
EppExt mailing list
EppExt@ietf.org<mailto:EppExt@ietf.org>
https://www.ietf.org/mailman/listinfo/eppext