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

Jens Wagner <jwagner@hexonet.net> Thu, 08 May 2014 15:19 UTC

Return-Path: <jwagner@hexonet.net>
X-Original-To: provreg@ietfa.amsl.com
Delivered-To: provreg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51E6E1A0057 for <provreg@ietfa.amsl.com>; Thu, 8 May 2014 08:19:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.801
X-Spam-Level:
X-Spam-Status: No, score=0.801 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=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 Axf564UmeM0M for <provreg@ietfa.amsl.com>; Thu, 8 May 2014 08:19:14 -0700 (PDT)
Received: from internal-mail-out2.ispapi.net (internal-mail-out2.ispapi.net [93.190.234.75]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3EB1A0053 for <provreg@ietf.org>; Thu, 8 May 2014 08:19:13 -0700 (PDT)
Received: from internal-mail-relay1.sls.de.hexonet.net (mx.hexonet.net [10.190.234.71]) by internal-mail-out2.ispapi.net (Postfix) with ESMTP id 69AAB9D2097 for <provreg@ietf.org>; Thu, 8 May 2014 15:19:08 +0000 (UTC)
Envelope-to: provreg@ietf.org
Received: from dslb-188-097-247-027.pools.arcor-ip.net ([188.97.247.27]:37038 helo=[192.168.52.112]) by internal-mail-relay1.sls.de.hexonet.net with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <jwagner@hexonet.net>) id 1WiQ6G-0004SG-2r for provreg@ietf.org; Thu, 08 May 2014 15:19:08 +0000
Message-ID: <536BA06C.4070004@hexonet.net>
Date: Thu, 08 May 2014 17:19:08 +0200
From: Jens Wagner <jwagner@hexonet.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: provreg@ietf.org
References: <CF7FD1F2.5DB6E%jgould@verisign.com> <53628077.8070402@centralnic.com> <CADJsPYwLj3uPCU=VenL2rVYkf7ZeD7=TXHjevL2WRgC44Vwx_g@mail.gmail.com> <A939B4D2-FF12-428D-A943-0A0A1DE94B9F@isc.org> <CAAHh_-+05Opw9vhiAAE=FPrQCaAFQ0aNGcxpNn-5Xn-fGgj5pg@mail.gmail.com> <CADJsPYzmxGm5NKnj35KLbHybih-3SQKJ3psi035okpqmvu2Epw@mail.gmail.com> <F0AA8F24-323D-4F32-A271-6FC2A0FDE746@nic.br>
In-Reply-To: <F0AA8F24-323D-4F32-A271-6FC2A0FDE746@nic.br>
Content-Type: multipart/alternative; boundary="------------070505060509090001000104"
X-SA-Exim-Connect-IP: 188.97.247.27
X-SA-Exim-Mail-From: jwagner@hexonet.net
Archived-At: http://mailarchive.ietf.org/arch/msg/provreg/f7H8cPoTquTjjPxijojLpi1DriI
Subject: Re: [provreg] New Version Notification for draft-brown-epp-fees-01.txt
X-BeenThere: provreg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPP discussion list <provreg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/provreg>, <mailto:provreg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/provreg/>
List-Post: <mailto:provreg@ietf.org>
List-Help: <mailto:provreg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/provreg>, <mailto:provreg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 May 2014 15:19:19 -0000

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 <pmoroney@name.com 
> <mailto:pmoroney@name.com>> 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 <sethamin@google.com 
>> <mailto:sethamin@google.com>> 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" <lem@isc.org
>>     <mailto:lem@isc.org>> wrote:
>>     >
>>     >
>>     > On May 1, 2014, at 11:03 AM, Pat Moroney <pmoroney@name.com
>>     <mailto:pmoroney@name.com>> 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
>>     > provreg@ietf.org <mailto:provreg@ietf.org>
>>     > https://www.ietf.org/mailman/listinfo/provreg
>>
>>
>>
>>
>> -- 
>> -Pat Moroney
>> SVP of Accounting / Sr. Software Engineer
>> Name.com <http://Name.com>
>> http://www.youtube.com/watch?v=V1GKGXXF12c
>> 720-663-0025
>>
>> _______________________________________________
>> provreg mailing list
>> provreg@ietf.org <mailto:provreg@ietf.org>
>> https://www.ietf.org/mailman/listinfo/provreg
>
>
>
> _______________________________________________
> provreg mailing list
> provreg@ietf.org
> https://www.ietf.org/mailman/listinfo/provreg


-- 
Jens Wagner
Chief Executive Officer
HEXONET GmbH

T: +49 6841 69 84 0
F: +49 6841 69 84 199
E: jwagner@hexonet.net
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.