Re: [provreg] Fwd: New Version Notification for draft-brown-epp-fees-01.txt
Pat Moroney <pmoroney@name.com> Thu, 01 May 2014 18:04 UTC
Return-Path: <pmoroney@name.com>
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 E30D11A700F for <provreg@ietfa.amsl.com>; Thu, 1 May 2014 11:04:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 VGxplJYUfwIQ for <provreg@ietfa.amsl.com>; Thu, 1 May 2014 11:03:58 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id 9CFF51A700C for <provreg@ietf.org>; Thu, 1 May 2014 11:03:57 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id f8so1153640wiw.3 for <provreg@ietf.org>; Thu, 01 May 2014 11:03:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=GqkHcOBCzjtc4Ho4mk5tjcrbpEDW/Kti5t8pIpFp2OU=; b=eSZJVcXh6xDjjQAQY07kg5iZeOX0DipeJh3Igqr0pM2ryQhSej72aoJ15iO8NUgEvo alARVg2Tc2X1FhJFvXgeLEEtF9Hp295uYOiIgAcFs5MDujoee1b2PJgHWwCRrxd9Nylf ydFJSU1EhGT2R9aOwCEowBGtDzQAoDpcn4Tzi2P2rzBra70NXyFqjCG495qJ/b4FKaHu Yq1Qk1RJrRe6C71uICHh5EJ7Yi6Yy3Xvab/hpRxmBbzTyjJoE2aR4TlUC0eyUsYbnWzc 9Mx+/68Bauf9hpGQzpZCH2GPoSEl5h6TxaRMuonBIi2iBYTwuctZ9WpsIJBkm28ix/FC EkVw==
X-Gm-Message-State: ALoCoQnmO+ecK+QHTLChUq8xG1ew0rROfoaL9LmISonZ4SQmTopqsAudbaEQewKwpuVPbGMAo4U6
MIME-Version: 1.0
X-Received: by 10.194.205.161 with SMTP id lh1mr9928978wjc.40.1398967435242; Thu, 01 May 2014 11:03:55 -0700 (PDT)
Received: by 10.194.22.9 with HTTP; Thu, 1 May 2014 11:03:55 -0700 (PDT)
In-Reply-To: <53628077.8070402@centralnic.com>
References: <CF7FD1F2.5DB6E%jgould@verisign.com> <53628077.8070402@centralnic.com>
Date: Thu, 01 May 2014 12:03:55 -0600
Message-ID: <CADJsPYwLj3uPCU=VenL2rVYkf7ZeD7=TXHjevL2WRgC44Vwx_g@mail.gmail.com>
From: Pat Moroney <pmoroney@name.com>
To: Gavin Brown <gavin.brown@centralnic.com>
Content-Type: multipart/alternative; boundary="047d7b6d950207bca204f85a7d9c"
Archived-At: http://mailarchive.ietf.org/arch/msg/provreg/MdMUK-8dkSZlTfVeoI4DlC7qPfM
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:04:01 -0000
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] Fwd: New Version Notification for draft… Gavin Brown
- Re: [provreg] Fwd: New Version Notification for d… Bruno Prémont
- Re: [provreg] Fwd: New Version Notification for d… Gavin Brown
- Re: [provreg] New Version Notification for draft-… Luis Muñoz
- Re: [provreg] New Version Notification for draft-… Gavin Brown
- Re: [provreg] Fwd: New Version Notification for d… Seth Goldman
- Re: [provreg] Fwd: New Version Notification for d… Klaus Malorny
- Re: [provreg] Fwd: New Version Notification for d… Gould, James
- Re: [provreg] Fwd: New Version Notification for d… Gavin Brown
- Re: [provreg] Fwd: New Version Notification for d… Gavin Brown
- Re: [provreg] Fwd: New Version Notification for d… Pat Moroney
- Re: [provreg] New Version Notification for draft-… Luis Muñoz
- Re: [provreg] New Version Notification for draft-… Seth Goldman
- Re: [provreg] New Version Notification for draft-… Luis Muñoz
- Re: [provreg] Fwd: New Version Notification for d… MICHAEL W YOUNG
- Re: [provreg] New Version Notification for draft-… Luis Muñoz
- Re: [provreg] New Version Notification for draft-… Pat Moroney
- Re: [provreg] New Version Notification for draft-… Rubens Kuhl
- Re: [provreg] New Version Notification for draft-… Seth Goldman
- Re: [provreg] New Version Notification for draft-… Jens Wagner
- Re: [provreg] Fwd: New Version Notification for d… Jens Wagner
- Re: [provreg] Fwd: New Version Notification for d… Seth Goldman
- Re: [provreg] New Version Notification for draft-… Pat Moroney
- Re: [provreg] Fwd: New Version Notification for d… Gavin Brown
- Re: [provreg] Fwd: New Version Notification for d… Gavin Brown
- Re: [provreg] Fwd: New Version Notification for d… Gavin Brown
- Re: [provreg] Fwd: New Version Notification for d… Gavin Brown
- Re: [provreg] New Version Notification for draft-… Gavin Brown
- Re: [provreg] New Version Notification for draft-… Pat Moroney
- Re: [provreg] New Version Notification for draft-… Jens Wagner
- Re: [provreg] New Version Notification for draft-… Gavin Brown
- Re: [provreg] New Version Notification for draft-… Jens Wagner
- Re: [provreg] Fwd: New Version Notification for d… Seth Goldman
- Re: [provreg] Fwd: New Version Notification for d… Seth Goldman