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

[Pat Moroney <[e-mail]>]

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.


On Thu, May 8, 2014 at 9:19 AM, Jens Wagner <[e-mail]> wrote:

>  I'd also be in favour of adding an optional(?) special or type attribute
> or element to the fee extensions, that reflects the price class of domains
> differing from the standard pricing e.g.
>
> *<special>Tier1</special>* or <fee:cd ... *type="Tier1"*>
>
> The extension right now reflects the billing between the registry and a
> registrar. But when dealing with customers or resellers, this would limit
> the flexibility for reseller and retail pricing models. Domains are
> typically sold through a chain:
>
>     REGISTRY -> REGISTRAR (-> RESELLER)* -> CUSTOMER
>
> For registries offering premium domains, it makes sense to limit the
> number of different premium price classes. That way registrars and
> resellers can define their own pricing models for those classes. Otherwise
> registrars and resellers would be limited to fix increments or percentage
> based markups.
>
> A fee check response could look like this:
>
> S:  <fee:cd xmlns:fee="urn:ietf:params:xml:ns:fee-0.5" *type="AAA+"*>
> S:    <fee:name>somepremium.tld</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>1234.00</fee:fee>
> S:  </fee:cd>
>
> If the registry uses an attribute that reflects the price class, then it
> should also be required on create, renew, transfer and restore. E.g.
>
> C:  <fee:create xmlns:fee="urn:ietf:params:xml:ns:fee-0.4" *type="AAA+"*>
>
> C:    <fee:currency>USD</fee:currency>
> C:    <fee:fee>12.00</fee:fee>
> C:  </fee:create>
>
>
> This would also cover the following case: A registry could come up with a
> business model, where the registration fee for premium domains matches the
> standard fee for that TLD, but those premium domains have a higher renewal
> price. Requiring the attribute (that indicates a premium domain) for those
> domains would prevent an accidental premium registration.
>
> Best regards,
> - jens
>
>
> Am 01.05.2014 21:41, schrieb Rubens Kuhl:
>
>
>  Recent events showed there is a need for a reliable way of knowing it.
>
> http://domainincite.com/16534-guy-hit-with-1600-bill-a-month-after-registering-premium-name-for-12-99
>
> http://domainincite.com/16555-101domain-shifts-blame-to-google-as-premium-buyers-offered-50-discount
>
>
>
>  Rubens
>
>  On May 1, 2014, at 4:21 PM, Pat Moroney <[e-mail]> wrote:
>
>  Seth, you hit the nail on the head. We currently have to figure out if
> the domain is a premium domain name via numerous methods, some of which can
> take time or are unreliable. It would be safer to get that information in a
> standard way which is guaranteed to be up to date.
>
>  A type attribute could work for that nicely.
>
>
> On Thu, May 1, 2014 at 12:38 PM, Seth Goldman <[e-mail]> wrote:
>
>> I have heard from at least one registrar that they'd like premium domain
>> names delineated from non-premium. I'd suggest adding an optional "type"
>> attribute that can be extended for custom types.
>>
>>  On May 1, 2014 2:35 PM, "Luis Muñoz" <[e-mail]> wrote:
>> >
>> >
>> > On May 1, 2014, at 11:03 AM, Pat Moroney <[e-mail]> wrote:
>> >
>> > > Let me know if any of this makes sense or if there is a better venue
>> or way for me to make these suggestions since I am new to this list.
>> >
>> > Why does it matter if the price is "special" (or "exceptional" as
>> opposed to "regular")? The reason I ask is that I suspect you intent to
>> convey some other meaning into the transaction.
>> >
>> > Perhaps you're thinking about a promotional price that can be valid
>> only during a certain period?
>> >
>> > Best regards
>> >
>> > -lem
>> >
>>   > _______________________________________________
>> > provreg mailing list
>> > [e-mail]
>> > https://www.ietf.org/mailman/listinfo/provreg
>>
>>
>
>
>  --
>  -Pat Moroney
> SVP of Accounting / Sr. Software Engineer
> Name.com
> http://www.youtube.com/watch?v=V1GKGXXF12c
>  720-663-0025
>
>   _______________________________________________
> provreg mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/provreg
>
>
>
>
> _______________________________________________
> provreg mailing [e-mail]://www.ietf.org/mailman/listinfo/provreg
>
>
>
> --
> Jens Wagner
> Chief Executive Officer
> HEXONET GmbH
>
> T: [phone]
> F: [phone]
> E: [e-mail]
> W: http://www.hexonet.net
>
> HEXONET GmbH, Talstrasse 27, 66424 Homburg, Germany.  CEO & General Manager: Jens Wagner, HRB 2839 (HOM), Amtsgericht Saarbrücken, VAT-ID: DE-138316882
> HEXONET Services Inc., #104 - 7455 132nd Street, Surrey, B.C., V3W 1J8, Canada.  CSO & General Manager: Robert Birkner
>
> This email and any files transmitted are confidential and intended only or the person(s) directly addressed. If you are not the intended recipient, any use, copying, transmission, distribution, or other forms of dissemination is strictly prohibited. If you have received this email in error, please notify the sender immediately and permanently delete this email with any files that may be attached.
>
>
> _______________________________________________
> provreg mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/provreg
>
>


-- 
-Pat Moroney
SVP of Accounting / Sr. Software Engineer
Name.com
http://www.youtube.com/watch?v=V1GKGXXF12c
720-663-0025