Re: [regext] draft-ietf-regext-epp-fees-02.txt: currency error handling, command wildcard

[Thomas Corte <[e-mail]>]

Hello Bernhard,

On 2017-03-24 16:52, Bernhard Reutner-Fischer wrote:

> That's what normative references are for IMHO. You wouldn't want to
> update the fee RFC if someone invents a new currency.

Agreed, that would be cumbersome.

> You might want to throw an error if someone configures the server to
> use a new/typoed currency and always 2306 when receiving a currency
> outside of the configured enumeration, thus ignoring 2004 completely
> at runtime.

This makes sense for the transform commands, yes.

However, for wrong currencies detected within some <fee:object> elements
of a <fee:check> extension, I'm not sure whether letting the entire
check command fail with a 2306 error is the best approach.

Instead, the server could still return useful results for other
<fee:object> elements in the command (which may have contained a correct
currency), or even return additional information in the <reason>
elements returned within the <fee:command avail="false"> elements
returned for all nested <fee:command> affected by the wrong currency.
I think the draft should be clarified regarding when to create an EPP
error result as opposed to <fee:command avail="false"> results in the
response to a <domain:check> command with fee extension.

Best regards,

Thomas

-- 
TANGO REGISTRY SERVICES® is a product of:
Knipp Medien und Kommunikation GmbH
Technologiepark                             Phone: [phone]
Martin-Schmeisser-Weg 9                       Fax: [phone]
D-44227 Dortmund                       E-Mail: [e-mail]
Germany