Re: [regext] I-D Action: draft-ietf-regext-epp-fees-03.txt

2017-04-28 Thread Thomas Corte
Hello, On 27/04/2017 21:55, Gould, James wrote: > ... > h. In the example, I don’t believe any elements other than > and would be returned when avail=”0”. I > recommend removing the from the example when avail=”0”. Overall, I'm a bit puzzled regarding the usefulness of the "avail" a

Re: [regext] I-D Action: draft-ietf-regext-epp-fees-03.txt

2017-04-28 Thread Gould, James
Thomas, I don’t agree that failing the entire check command if someone passes invalid input in the fee extension, unless it is syntactically incorrect. The point is to communicate whether the fee information is available for the given object and commands, and if it is return the fee informatio

Re: [regext] I-D Action: draft-ietf-regext-epp-fees-03.txt

2017-04-28 Thread Thomas Corte
Hello James, On 28/04/2017 14:32, Gould, James wrote: > Thomas, > > I don’t agree that failing the entire check command if someone passes invalid > input in the fee extension, unless it is syntactically incorrect. The point > is to communicate whether the fee information is available for the

Re: [regext] I-D Action: draft-ietf-regext-epp-fees-03.txt

2017-04-28 Thread Gould, James
Thomas, There are three classifications of errors that can occur with the fee extension to the check command: 1. Syntax error – This should result in an error for the entire check command. 2. Object (domain) name error (incorrect domain name, reserved domain name, blocked doma

Re: [regext] I-D Action: draft-ietf-regext-epp-fees-03.txt

2017-04-28 Thread Thomas Corte
James, On 28/04/2017 15:27, Gould, James wrote: > Thomas, > > There are three classifications of errors that can occur with the fee > extension to the check command: > > 1. Syntax error – This should result in an error for the entire > check command. > > 2. Object (domain) name er

Re: [regext] I-D Action: draft-ietf-regext-epp-fees-03.txt

2017-04-28 Thread Jody Kolker
Thanks James. Comments in line below. From: regext [mailto:regext-boun...@ietf.org] On Behalf Of Gould, James Sent: Thursday, April 27, 2017 2:56 PM To: Roger D Carney ; regext@ietf.org Subject: Re: [regext] I-D Action: draft-ietf-regext-epp-fees-03.txt Roger, Thanks for posting the updated dr

Re: [regext] I-D Action: draft-ietf-regext-epp-fees-03.txt

2017-04-28 Thread Gould, James
Jody, My feedback is included inline below prefixed with “JG-“. — JG [cid:image001.png@01D2C03D.ADF24700] James Gould Distinguished Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 VerisignInc.com From: regext on behalf of Jody Kolker

Re: [regext] I-D Action: draft-ietf-regext-epp-fees-03.txt

2017-04-28 Thread Gould, James
Thomas, I’m sorry, I missed the existence of a reason under the command since I thought the “avail” attribute and the reason element moved from the command level to the object level. My main concern with providing a highly feature rich fee extension to the domain check is ensuring that the d

Re: [regext] I-D Action: draft-ietf-regext-epp-fees-03.txt

2017-04-28 Thread Rubens Kuhl
James, I understand your concern with option #1, but I think option #3 goes into a different set of issues where we mix the domain sales pipeline with domain management activities, for which domain:info is commonly used. I'm neutral between option #1 and option #2, but while both work me, I w