IETF Logo Mail Archive

Re: [provreg] [eppext] Inconsistency in number of status values in draft-tan-epp-launchphase-12 ?

Mike O <mcanix@gmail.com> Thu, 06 March 2014 04:35 UTC

Return-Path: <mcanix@gmail.com>
X-Original-To: provreg@ietfa.amsl.com
Delivered-To: provreg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25ACF1A0099; Wed, 5 Mar 2014 20:35:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 sGTXW4QPp0uV; Wed, 5 Mar 2014 20:34:59 -0800 (PST)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id C3C871A00B0; Wed, 5 Mar 2014 20:34:58 -0800 (PST)
Received: by mail-we0-f173.google.com with SMTP id w61so2398598wes.4 for <multiple recipients>; Wed, 05 Mar 2014 20:34:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=dNaXUr3NOKPsgtM+tBqda6v0Qp/UBUZrJaa2K8G7tlA=; b=RcFEKCIUVYCmCOhCpsyG+QXYc5lo2ti0UF2G4TOe4krAeVoLg7UcZle1AM9o/msoZk 44RwRSbTyrvn2MLKlj/VI6g3wzbifygzfEe8hJsqcp6I3mvup7G/BMckjDEZtQmgaovO JPYodBIi++7IL398CHB8pBMstcu1oZ0UMbgRpyHfmShjjpn206YhdzjNryAWlG7x8xS8 WfbNJHYqrOhvdnZoOtls8JRG8r+Mro8ydvezG51n0InbAzeKr1K5CYnLwwRUdTKVIseo Y+UTUO6HJ8SubUUmcx9I3OfXmDzp/lDL44dNtwavEO5LqChJ6umOHZC4k9PYw28PogEM CScA==
X-Received: by 10.194.6.8 with SMTP id w8mr6688615wjw.16.1394080494573; Wed, 05 Mar 2014 20:34:54 -0800 (PST)
Received: from nakal.int.coza.net.za ([206.223.136.247]) by mx.google.com with ESMTPSA id az1sm10613687wjb.11.2014.03.05.20.34.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Mar 2014 20:34:53 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_7C41DF94-0571-4D68-B2D5-40F8CC891B89"; protocol="application/pkcs7-signature"; micalg="sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Mike O <mcanix@gmail.com>
In-Reply-To: <CF3CAD62.58C04%jgould@verisign.com>
Date: Thu, 06 Mar 2014 06:34:47 +0200
Message-Id: <2CF458C6-2C8C-46F2-AF12-72B6516B215F@gmail.com>
References: <CF3CAD62.58C04%jgould@verisign.com>
To: "Gould, James" <JGould@verisign.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/provreg/y-YIcvTvakEPEqbwtl8KQdAS8xU
Cc: "eppext@ietf.org" <eppext@ietf.org>, "provreg@ietf.org" <provreg@ietf.org>
Subject: Re: [provreg] [eppext] Inconsistency in number of status values in draft-tan-epp-launchphase-12 ?
X-BeenThere: provreg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPP discussion list <provreg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/provreg>, <mailto:provreg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/provreg/>
List-Post: <mailto:provreg@ietf.org>
List-Help: <mailto:provreg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/provreg>, <mailto:provreg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 04:35:02 -0000

+1, We've coded according to the Schema, multiple statuses would require a redesign...

--

If you don't know where you are going, any road will get you there.

On 05 Mar 2014, at 5:36 PM, Gould, James <JGould@verisign.com> wrote:

> Patrick,
> 
> Good catch. My recommendation is for the text to be tightened up to
> support only a single status, since the status really reflects the status
> or state within the state diagram of Figure 1.  Adding support for
> multiple statuses in the XML schema would make it more difficult for the
> client to determine the state of the application. Thoughts?
> 
> -- 
> 
> JG
> 
> 
> 
> James Gould
> Principal Software Engineer
> jgould@verisign.com
> 
> 703-948-3271 (Office)
> 12061 Bluemont Way
> Reston, VA 20190
> VerisignInc.com
> 
> 
> 
> 
> On 3/5/14, 10:23 AM, "Patrick Mevzek" <Patrick.Mevzek@afnic.fr> wrote:
> 
>> Hello,
>> 
>> the text says :
>> Certain status values MAY be combined.  For example, an application
>>  or registration may be both "invalid" and "rejected"
>> 
>> the schema says :
>> <complexType name="infDataType">
>>      <sequence>
>>        <element name="phase" type="launch:phaseType"/>
>>       <element name="applicationID"
>>        type="launch:applicationIDType"
>>        minOccurs="0"/>
>>       <element name="status" type="launch:statusType"
>>        minOccurs="0"/>
>> 
>> so maybe a maxOccurs="unbounded" should be added there ?
>> or maxOccurs="7" to be extra conservative ?
>> 
>> -- 
>> Patrick Mevzek
>> 
>> _______________________________________________
>> provreg mailing list
>> provreg@ietf.org
>> https://www.ietf.org/mailman/listinfo/provreg
> 
> _______________________________________________
> EppExt mailing list
> EppExt@ietf.org
> https://www.ietf.org/mailman/listinfo/eppext

v2.23.0 | Report a Bug | By Email