Re: [provreg] New Version Notification for draft-brown-epp-fees-01.txt

[Jens Wagner <[e-mail]>]

+1
That would work, but according to the draft, EPP clients provide the 
<fee:name> element on <check> requests only.
Would also need the attribute for <domain:create>, renew, transfer and 
so on.
Maybe we could use an element e.g. <class>, instead of an attribute? Or 
also assign the attribute to the <fee:create>, <fee:renew> ... elements?

Best,
- jens

Am 08.05.2014 20:13, schrieb Pat Moroney:
> 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 
> <[e-mail] <mailto:[e-mail]>> 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 <http://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
>     <http://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
>