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

[Seth Goldman <[e-mail]>]

I think most/any of these scenarios are possible, depending on the
registry's business logic. For example, perhaps the price returned on an
<info> is different price than on a <check> because the registry has some
special incentive program for existing renewals versus new registrations
(assuming that's allowable under ICANN rules). Same might go for a repeated
<fee:domain> element.

In general, I'd advocate for making the protocol as flexible as possible
for expressing the data (within reason), while leaving the exact semantics
of that data as "server policy". Otherwise you end up embedding a lot of
business logic into the protocol, which then forces registries and
resellers to modify or add extensions when their use case doesn't exactly
match the canonical use case of the spec.

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

>  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 [e-mail]://www.ietf.org/mailman/listinfo/provreg
>
>
> _______________________________________________
> provreg mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/provreg
>
>