Re: [eppext] Inconsistency in number of status values in draft-tan-epp-launchphase-12 ?
Wil Tan <[email protected]> Fri, 7 Mar 2014 19:44:01 +1100
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <CACnMJCOCv8fQPXbSv3wks_pB3X=ZOCooLLuAHx6ra1ktjMTX0A@mail.gmail.com> |
--===============5420387159390810209== Content-Type: multipart/alternative; boundary=047d7b3a893a70d8a004f400418d --047d7b3a893a70d8a004f400418d Content-Type: text/plain; charset=UTF-8 On 06/03/2014 3:26 am, "Gavin Brown" <[email protected]> wrote: > > +1. Our implementation only supports a single status. Are there any > implementations which require this design? +1 we should keep it simple. already the spec supports quite a few use cases, so unless this is a blocker for a common scenario we should not allow multiple status values. .wil > > I'll add this point to my slides for discussion tomorrow. > > G. > > On 05/03/2014 15:36, Gould, James 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? > > > > -- > Gavin Brown > Chief Technology Officer > CentralNic Group plc (LSE:CNIC) > Innovative, Reliable and Flexible Registry Services > for ccTLD, gTLD and private domain name registries > https://www.centralnic.com/ > > CentralNic Group plc is a company registered in England and Wales with > company > number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR. > > > _______________________________________________ > provreg mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/provreg > --047d7b3a893a70d8a004f400418d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <p dir=3D"ltr"><br> On 06/03/2014 3:26 am, "Gavin Brown" <<a href=3D"mailto:gavin.= [email protected]">[email protected]</a>> wrote:<br> ><br> > +1. Our implementation only supports a single status. Are there any<br= > > implementations which require this design?</p> <p dir=3D"ltr">+1 we should keep it simple. already the spec supports quite= a few use cases, so unless this is a blocker for a common scenario we shou= ld not allow multiple status values.</p> <p dir=3D"ltr">.wil</p> <p dir=3D"ltr">><br> > I'll add this point to my slides for discussion tomorrow.<br> ><br> > G.<br> ><br> > On 05/03/2014 15:36, Gould, James wrote:<br> > > Patrick,<br> > ><br> > > Good catch. My recommendation is for the text to be tightened up = to<br> > > support only a single status, since the status really reflects th= e status<br> > > or state within the state diagram of Figure 1. =C2=A0Adding suppo= rt for<br> > > multiple statuses in the XML schema would make it more difficult = for the<br> > > client to determine the state of the application. Thoughts?<br> > ><br> ><br> > --<br> > Gavin Brown<br> > Chief Technology Officer<br> > CentralNic Group plc (LSE:CNIC)<br> > Innovative, Reliable and Flexible Registry Services<br> > for ccTLD, gTLD and private domain name registries<br> > <a href=3D"https://www.centralnic.com/">https://www.centralnic.com/</a= ><br> ><br> > CentralNic Group plc is a company registered in England and Wales with= <br> > company<br> > number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR.<= br> ><br> ><br> > _______________________________________________<br> > provreg mailing list<br> > <a href=3D"mailto:[email protected]">[email protected]</a><br> > <a href=3D"https://www.ietf.org/mailman/listinfo/provreg">https://www.= ietf.org/mailman/listinfo/provreg</a><br> ><br> </p> --047d7b3a893a70d8a004f400418d-- --===============5420387159390810209== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg --===============5420387159390810209==--