Re: New Version Notification for draft-brown-epp-fees-01.txt
Pat Moroney <[email protected]> Thu, 8 May 2014 12:13:47 -0600
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <CADJsPYxSsm=TYf2J-ZyMAXL0o71zMiDCWzXAMDL6Ggtf3d0mfg@mail.gmail.com> |
--===============6277558392558638258== Content-Type: multipart/alternative; boundary=001a1134d6d441532504f8e77166 --001a1134d6d441532504f8e77166 Content-Type: text/plain; charset=UTF-8 Hi Gavin, That works for me. I am indifferent in the terminology: class vs type vs category. Thanks, On Thu, May 8, 2014 at 11:55 AM, Gavin Brown <[email protected]>wrote: > On 08/05/2014 17:07, Pat Moroney wrote: > > Hi Jens, > > > > I like the optional type attribute being added to the <fee:cd> as well > > as required on the <fee:create> if it was set. > > Especially if that optional description attribute is added to the > > <fee:fee> element as well, which was hinted at in Gavin's email about > > the new draft. > > > > He had the following example: > > S: <fee:cd > > S: xmlns:fee="urn:ietf:params:xml:ns:fee-0.5"> > > > > S: <fee:fee description="Application Fee">5.00</fee:fee> > > S: <fee:fee description="Registration Fee">5.00</fee:fee> > > S: </fee:cd> > > > > That, combined with the type attribute, allows a lot of flexability for > > registries. > > For example, Donuts, if they used this extension, could then return the > > following for a premium domain during their Early Access Period day 2: > > > > S: <fee:cd > > S: xmlns:fee="urn:ietf:params:xml:ns:fee-0.5" type="BBB+"> > > S: <fee:name>example.com</fee:name> > > S: <fee:currency>USD</fee:currency> > > S: <fee:command>create</fee:command> > > S: <fee:period unit="y">1</fee:period> > > S: <fee:fee description="Early Access Fee">2500.00</fee:fee> > > S: <fee:fee description="Registration Fee">66.00</fee:fee> > > S: </fee:cd> > > > > That allows a registrar to recognize that the domain is a premium as > > well as there being added fees, and differentiating what those fees are > for. > > The current working draft includes a "description" attribute on the > <fee:fee> elements. If we're going to add additional syntax to describe > the domain itself, then I think that syntax should be added to the > <fee:name> element, like so: > > S: <fee:cd> > S: <fee:name class="premium">example.com</fee:name> > S: <fee:currency>USD</fee:currency> > S: <fee:command>create</fee:command> > S: <fee:period unit="y">1</fee:period> > S: <fee:fee description="Early Access Fee">2500.00</fee:fee> > S: <fee:fee description="Registration Fee">66.00</fee:fee> > S: </fee:cd> > > The above example uses "class" as the attribute name, but it could just > as easily be "category" or "type" or something similar. The value of the > attribute would be a token, which would presumably come from a set of > possible tokens that the server would provide to clients out-of-band. > > 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. > > -- -Pat Moroney SVP of Accounting / Sr. Software Engineer Name.com http://www.youtube.com/watch?v=V1GKGXXF12c 720-663-0025 --001a1134d6d441532504f8e77166 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi Gavin,<div><br></div><div>That works for me. I am indif= ferent in the terminology: class vs type vs category.</div><div><br></div><= div>Thanks,</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gma= il_quote"> On Thu, May 8, 2014 at 11:55 AM, Gavin Brown <span dir=3D"ltr"><<a href= =3D"mailto:[email protected]" target=3D"_blank">gavin.brown@centra= lnic.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style= =3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class=3D"HOEnZb"><div class=3D"h5">On 08/05/2014 17:07, Pat Moroney wr= ote:<br> > Hi Jens,<br> ><br> > I like the optional type attribute being added to the <fee:cd> a= s well<br> > as required on the <fee:create> if it was set.<br> > Especially if that optional description attribute is added to the<br> > <fee:fee> element as well, which was hinted at in Gavin's em= ail about<br> > the new draft.<br> ><br> > He had the following example:<br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 <fee:cd<br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 xmlns:fee=3D"urn:ietf:param= s:xml:ns:fee-0.5"><br> ><br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <fee:fee description=3D"= Application Fee">5.00</fee:fee><br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <fee:fee description=3D"= Registration Fee">5.00</fee:fee><br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 </fee:cd><br> ><br> > That, combined with the type attribute, allows a lot of flexability fo= r<br> > registries.<br> > For example, Donuts, if they used this extension, could then return th= e<br> > following for a premium domain during their Early Access Period day 2:= <br> ><br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 <fee:cd<br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 xmlns:fee=3D"urn:ietf:param= s:xml:ns:fee-0.5" type=3D"BBB+"><br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <fee:name><a href=3D"http:= //example.com" target=3D"_blank">example.com</a></fee:name><br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <fee:currency>USD</fee:= currency><br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <fee:command>create</fe= e:command><br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <fee:period unit=3D"y&qu= ot;>1</fee:period><br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <fee:fee description=3D"= Early Access Fee">2500.00</fee:fee><br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <fee:fee description=3D"= Registration Fee">66.00</fee:fee><br> > S: =C2=A0 =C2=A0 =C2=A0 =C2=A0 </fee:cd><br> ><br> > That allows a registrar to recognize that the domain is a premium as<b= r> > well as there being added fees, and differentiating what those fees ar= e for.<br> <br> </div></div>The current working draft includes a "description" at= tribute on the<br> <fee:fee> elements. If we're going to add additional syntax to de= scribe<br> the domain itself, then I think that syntax should be added to the<br> <fee:name> element, like so:<br> <br> S: =C2=A0<fee:cd><br> S: =C2=A0 =C2=A0<fee:name class=3D"premium"><a href=3D"http= ://example.com" target=3D"_blank">example.com</a></fee:name><br> <div class=3D"">S: =C2=A0 =C2=A0<fee:currency>USD</fee:currency>= ;<br> S: =C2=A0 =C2=A0<fee:command>create</fee:command><br> S: =C2=A0 =C2=A0<fee:period unit=3D"y">1</fee:period>= <br> S: =C2=A0 =C2=A0<fee:fee description=3D"Early Access Fee">2= 500.00</fee:fee><br> S: =C2=A0 =C2=A0<fee:fee description=3D"Registration Fee">6= 6.00</fee:fee><br> S: =C2=A0</fee:cd><br> <br> </div>The above example uses "class" as the attribute name, but i= t could just<br> as easily be "category" or "type" or something similar.= The value of the<br> attribute would be a token, which would presumably come from a set of<br> possible tokens that the server would provide to clients out-of-band.<br> <br> Thoughts?<br> <div class=3D"HOEnZb"><div class=3D"h5"><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/" target=3D"_blank">https://www.centr= alnic.com/</a><br> <br> CentralNic Group plc is a company registered in England and Wales with<br> company number 8576358. Registered Offices: 35-39 Moorgate, London,<br> EC2R 6AR.<br> <br> </div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>= <div dir=3D"ltr"><div>-Pat Moroney</div><div>SVP of Accounting / Sr. Softwa= re Engineer</div><div>Name.com</div><div><div><a href=3D"http://www.youtube= .com/watch?v=3DV1GKGXXF12c" target=3D"_blank">http://www.youtube.com/watch?= v=3DV1GKGXXF12c</a><br> </div></div><div>720-663-0025</div><div><br></div></div> </div> --001a1134d6d441532504f8e77166-- --===============6277558392558638258== 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 --===============6277558392558638258==--