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

"Gould, James" <JGould@verisign.com> Wed, 05 March 2014 15:36 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 AC51C1A0732; Wed, 5 Mar 2014 07:36:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 080RFsQTZBKQ; Wed, 5 Mar 2014 07:36:28 -0800 (PST)
Received: from exprod6og116.obsmtp.com (exprod6og116.obsmtp.com [64.18.1.37]) by ietfa.amsl.com (Postfix) with ESMTP id BC3E51A013E; Wed, 5 Mar 2014 07:36:26 -0800 (PST)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob116.postini.com ([64.18.5.12]) with SMTP ID DSNKUxdEd4k9GVw5ockq8zHdfW8GLutv+8y+@postini.com; Wed, 05 Mar 2014 07:36:25 PST
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s25FaMHJ020678 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Mar 2014 10:36:22 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0123.003; Wed, 5 Mar 2014 10:36:21 -0500
From: "Gould, James" <JGould@verisign.com>
To: Patrick Mevzek <Patrick.Mevzek@afnic.fr>, "provreg@ietf.org" <provreg@ietf.org>
Thread-Topic: [provreg] Inconsistency in number of status values in draft-tan-epp-launchphase-12 ?
Thread-Index: AQHPOIboKI3h0PNq90CKfHIzVQ1wPprSoDmA
Date: Wed, 05 Mar 2014 15:36:21 +0000
Message-ID: <CF3CAD62.58C04%jgould@verisign.com>
In-Reply-To: <1394032988.26535.58.camel@citrine>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3B15A6C5E1CC454582881FEA435423AB@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/lgQJDD2Ey7eVPkR8WYKbF9FGYLA
Cc: "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] [provreg] Inconsistency in number of status values in draft-tan-epp-launchphase-12 ?
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: Wed, 05 Mar 2014 15:36:31 -0000

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