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

MICHAEL W YOUNG <michael@mwyoung.ca> Thu, 01 May 2014 18:52 UTC

Return-Path: <michael@mwyoung.ca>
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 625871A0933 for <provreg@ietfa.amsl.com>; Thu, 1 May 2014 11:52:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 65MtAil7GYKb for <provreg@ietfa.amsl.com>; Thu, 1 May 2014 11:52:13 -0700 (PDT)
Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) by ietfa.amsl.com (Postfix) with ESMTP id 473D61A0919 for <provreg@ietf.org>; Thu, 1 May 2014 11:52:13 -0700 (PDT)
Received: by mail-ie0-f180.google.com with SMTP id as1so3970925iec.39 for <provreg@ietf.org>; Thu, 01 May 2014 11:52:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=qdgUm3zzjaFXTTobJZWN6kpxecc2IzPsNDwMbq7yWA4=; b=WFsejhcNI09hk69RaruUg/qHseQSIJzhklKafhlq+v28TWWUZmMa6o4W5XyvSfDs0j ZA+D+rc1KEIJjs1t/thUGatNfC/5yPVIfqqJioRyed86G5xI2DJQsMHzOGhTh22fb/6j NPxtL1KyYX9IIiMvgWH7vEx0uFD1TY0rNsW6kNEtyW8VJL8Zi6yKSxIwroGwc++EezzG 5VTFW/pfoRgNPUg56/7tVt6pdMDFgmkP4fdtPBIfC0HwkVJ1KGKMFe2mCMpxuJ52DF8f GrQAJyaoQ+NHug3OHII2bbAfmL5lmPyb5qs14nbIISf2y8Mv+UhRfh3EJ1Pe5OCK88zx uP5g==
X-Gm-Message-State: ALoCoQmJrBFE5TD3Qvvrlgec7Swy2GmMn9zVt/IdeGsMtgyStQYKStRtelHWfg3S3PyFNQKrbZRm
X-Received: by 10.50.40.103 with SMTP id w7mr5115801igk.33.1398970331304; Thu, 01 May 2014 11:52:11 -0700 (PDT)
Received: from [172.16.1.16] (CPE7073cbb4404e-CM78cd8ece2635.cpe.net.cable.rogers.com. [174.119.38.58]) by mx.google.com with ESMTPSA id b8sm11282931igx.3.2014.05.01.11.52.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 May 2014 11:52:10 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_29080624-E8D6-405F-A2C9-50E8E2261B64"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: MICHAEL W YOUNG <michael@mwyoung.ca>
In-Reply-To: <CADJsPYwLj3uPCU=VenL2rVYkf7ZeD7=TXHjevL2WRgC44Vwx_g@mail.gmail.com>
Date: Thu, 01 May 2014 14:52:08 -0400
Message-Id: <ADB9498D-943E-41D3-B357-CE96C4348530@mwyoung.ca>
References: <CF7FD1F2.5DB6E%jgould@verisign.com> <53628077.8070402@centralnic.com> <CADJsPYwLj3uPCU=VenL2rVYkf7ZeD7=TXHjevL2WRgC44Vwx_g@mail.gmail.com>
To: Pat Moroney <pmoroney@name.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/provreg/PJThUveqs2IqddLX05uiycAByDs
Cc: "provreg@ietf.org" <provreg@ietf.org>
Subject: Re: [provreg] Fwd: 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, 01 May 2014 18:52:17 -0000

Hi Pat,

This sounds to me like you are starting to overlap with a "program" problem.  For example, many of the existing registries support some type of "program identifier" or "token" submitted as an extension during a registration to associate that registration with an existing marketing discount/rebate/specialized pricing.

I don't want to spin this into something overtly complicated, but it seems this extension, since its all about querying fees, could extend to query fees by domain, by "program" as well.

It would be interesting to query a given domain for an answer on which programs its applicable for.  Lets say I am a registrar that signed up for marketing programs (out of registry band) "A1" and program "B2" with the registry operator, instead of keeping track of that in my registrar systems, whenever I go to check pricing on a domain, I would also receive any current programs that are applicable to that domain along with the base pricing I originally queried.  I can then do subsequent lookups on the program pricing if I don't have the program pricing handy, or if the program pricing varies depending on the specific string.

When I registered the domain, I can then opt to submit "A1" or "B2" with the registration, etc based on having been told the relevant "special" or "program" pricing for each.


-Michael

On May 1, 2014, at 2:03 PM, Pat Moroney <pmoroney@name.com> wrote:

> Another addition I was hoping we could consider is a flag of some sort that would signal that the fee is somehow special or unusual.
> A good example of this would be where a certain tld has different pricing for 2 character domains then the normal base price.
> This would be particularly useful if we have to account for those differently or perform additional checks in those cases.
> 
> I feel that the best place for such a flag would be as an attribute to the fee:fee element. I'm not sure of the best name for such an element, but as an example I'll use "special":
> <fee:fee description="Renewal Fee" special="0">5.00</fee:fee>
> or
> <fee:fee description="Renewal Fee" special="1">5.00</fee:fee>
> And omission of that attribute would imply that the value is 0.
> 
> Another option is that if the base fee is always one of the listed fees and they are differentiated by their descriptions. The problem I see with that is it could get messy with different registries utilizing different descriptions for their fees. Also I could see that a registry could use something like "Registration Fee" as a description for both premium and non premium registrations, thus removing the ability to discern if it is a premium or not.
> 
> 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.
> 
> 
> 
> On Thu, May 1, 2014 at 11:12 AM, Gavin Brown <gavin.brown@centralnic.com> wrote:
> Thanks to all for the feedback. I am working on a revised draft that
> will use a single <fee:check> element in commands and a single
> <fee:chkData> element in responses.
> 
> Here are some example commands and responses: let me know what you think.
> 
> Thanks,
> 
> C: <?xml version="1.0" encoding="utf-8" standalone="no"?>
> C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
> C:   <command>
> C:     <check>
> C:       <domain:check
> C:         xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
> C:         <domain:name>example.com</domain:name>
> C:         <domain:name>example.net</domain:name>
> C:         <domain:name>example.org</domain:name>
> C:       </domain:check>
> C:     </check>
> C:     <extension>
> C:       <fee:check
> C:         xmlns:fee="urn:ietf:params:xml:ns:fee-0.5">
> C:         <fee:domain>
> C:           <fee:name>example.com</fee:name>
> C:           <fee:currency>USD</fee:currency>
> C:           <fee:command phase="sunrise">create</fee:command>
> C:           <fee:period unit="y">1</fee:period>
> C:         </fee:domain>
> C:         <fee:domain>
> C:           <fee:name>example.net</fee:name>
> C:           <fee:currency>EUR</fee:currency>
> C:           <fee:command phase="claims" subphase="landrush">
> C:           create</fee:command>
> C:           <fee:period unit="y">2</fee:name>
> C:         </fee:domain>
> C:         <fee:domain>
> C:           <fee:name>example.org</fee:name>
> C:           <fee:currency>EUR</fee:currency>
> C:           <fee:command>transfer</fee:command>
> C:         </fee:domain>
> C:         <fee:domain>
> C:           <fee:name>example.xyz</fee:name>
> C:           <fee:command>restore</fee:command>
> C:           <fee:period unit="y">1</fee:period>
> C:         </fee:domain>
> C:       </fee:check>
> C:     </extension>
> C:     <clTRID>ABC-12345</clTRID>
> C:   </command>
> C: </epp>
> 
> S: <?xml version="1.0" encoding="utf-8" standalone="no"?>
> S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
> S:   <response>
> S:     <result code="1000">
> S:       <msg>Command completed successfully</msg>
> S:     </result>
> S:     <resData>
> S:       <domain:chkData
> S:         xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
> S:         <domain:cd>
> S:           <domain:name avail="1">example.com</domain:name>
> S:         </domain:cd>
> S:         <domain:cd>
> S:           <domain:name avail="0">example.net</domain:name>
> S:           <domain:reason>In use</domain:reason>
> S:         </domain:cd>
> S:         <domain:cd>
> S:           <domain:name avail="0">example.org</domain:name>
> S:           <domain:reason>In use</domain:reason>
> S:         </domain:cd>
> S:       </domain:chkData>
> S:     </resData>
> S:     <extension>
> S:       <fee:chkData
> S:         xmlns:fee="urn:ietf:params:xml:ns:fee-0.5">
> S:         <fee:cd
> S:           xmlns:fee="urn:ietf:params:xml:ns:fee-0.5">
> S:           <fee:name>example.com</fee:name>
> S:           <fee:currency>USD</fee:currency>
> S:           <fee:command phase="sunrise">create</fee:command>
> S:           <fee:period unit="y">1</fee:period>
> S:           <fee:fee description="Application Fee">5.00</fee:fee>
> S:           <fee:fee description="Registration Fee">5.00</fee:fee>
> S:         </fee:cd>
> S:         <fee:cd
> S:           xmlns:fee="urn:ietf:params:xml:ns:fee-0.5">
> S:           <fee:name>example.net</fee:name>
> S:           <fee:currency>EUR</fee:currency>
> S:           <fee:command phase="claims" subphase="landrush">
> S:           create</fee:command>
> S:           <fee:period unit="y">2</fee:period>
> S:           <fee:fee>5.00</fee:fee>
> S:         </fee:cd>
> S:         <fee:cd
> S:           xmlns:fee="urn:ietf:params:xml:ns:fee-0.5">
> S:           <fee:name>example.org</fee:name>
> S:           <fee:currency>EUR</fee:currency>
> S:           <fee:command>transfer</fee:command>
> S:           <fee:period unit="y">2</fee:period>
> S:           <fee:fee description="Transfer Fee">2.50</fee:fee>
> S:           <fee:fee description="Renewal Fee">10.00</fee:fee>
> S:         </fee:cd>
> S:         <fee:cd
> S:           xmlns:fee="urn:ietf:params:xml:ns:fee-0.5">
> S:           <fee:name>example.xyz</fee:name>
> S:           <fee:currency>GBP</fee:currency>
> S:           <fee:command>restore</fee:command>
> S:           <fee:period unit="y">1</fee:period>
> S:           <fee:fee description="Restore Fee">25</fee:fee>
> S:           <fee:fee description="Renewal Fee">5.00</fee:fee>
> S:         </fee:cd>
> S:       </fee:chkData>
> S:     </extension>
> S:     <trID>
> S:       <clTRID>ABC-12345</clTRID>
> S:       <svTRID>54322-XYZ</svTRID>
> S:     </trID>
> S:   </response>
> S: </epp>
> 
> --
> 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
> provreg@ietf.org
> 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
> provreg@ietf.org
> https://www.ietf.org/mailman/listinfo/provreg



MICHAEL W YOUNG
michael@mwyoung.ca