Re: [provreg] Fwd: New Version Notification for draft-brown-epp-fees-01.txt
Jens Wagner <jwagner@hexonet.net> Thu, 08 May 2014 15:42 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 D547D1A00BE for <provreg@ietfa.amsl.com>; Thu, 8 May 2014 08:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 9yWAOGE1Kthc for <provreg@ietfa.amsl.com>; Thu, 8 May 2014 08:42:19 -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 7E8AC1A00B9 for <provreg@ietf.org>; Thu, 8 May 2014 08:42:16 -0700 (PDT)
Received: from internal-mail-relay2.sls.de.hexonet.net (unknown [10.190.234.72]) by internal-mail-out2.ispapi.net (Postfix) with ESMTP id B2B8D9D20BC for <provreg@ietf.org>; Thu, 8 May 2014 15:42:11 +0000 (UTC)
Envelope-to: provreg@ietf.org
Received: from dslb-188-097-247-027.pools.arcor-ip.net ([188.97.247.27]:37135 helo=[192.168.52.112]) by internal-mail-relay2.sls.de.hexonet.net with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <jwagner@hexonet.net>) id 1WiQSZ-0003s3-Dl for provreg@ietf.org; Thu, 08 May 2014 15:42:11 +0000
Message-ID: <536BA5D2.9010205@hexonet.net>
Date: Thu, 08 May 2014 17:42:10 +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>
In-Reply-To: <53628077.8070402@centralnic.com>
Content-Type: multipart/alternative; boundary="------------090109070106030207020408"
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/hvosh0tNvHWE6_Kd645TigBTGY8
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, 08 May 2014 15:42:22 -0000
Thank you Gavin! Got a couple of questions regarding the fee extension: 1. Is there are reason, that a client provides the <fee:currency> element when sending a query command, e.g. <check>? 2. Do the <fee:domain> elements in <fee:check> need to match the <domain:name> elements in <domain:check>? 3. May a <fee:domain> element for a single domain get repeated in <domain:check>, e.g. for different periods? E.g. useful, when providing a [period => price] dropdown in a shoppingcart: C: <fee:domain> C: <fee:name>example.com</fee:name> C: <fee:currency>USD</fee:currency> C: <fee:command>create</fee:command> C: <fee:period unit="y">1</fee:period> C: </fee:domain> C: <fee:domain> C: <fee:name>example.com</fee:name> C: <fee:currency>USD</fee:currency> C: <fee:command>create</fee:command> C: <fee:period unit="y">2</fee:period> C: </fee:domain> ... C: <fee:domain> C: <fee:name>example.com</fee:name> C: <fee:currency>USD</fee:currency> C: <fee:command>create</fee:command> C: <fee:period unit="y">10</fee:period> C: </fee:domain> Btw, this would not be needed, if supporting price classes. 4. Some registries return an error on <domain:info>, if a different registrar manages the domain, so <fee:infData> wouldn't get returned either, correct? Does <fee:info> have any advantage over <fee:check>? 5. The EPP <renew> command example should use <fee:renew> instead of <fee:create>? Best, - jens Am 01.05.2014 19:12, schrieb Gavin Brown: > 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> > > > > _______________________________________________ > provreg mailing list > provreg@ietf.org > https://www.ietf.org/mailman/listinfo/provreg
- [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