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

[Bernhard Reutner-Fischer <[e-mail]>]

On 22 March 2017 at 12:08, Thomas Corte <[e-mail]> wrote:

> 1) There seem to be contradictory requirements regarding the handling of
> invalid currency codes. In section 3.2, the draft says:
>
>   "Servers SHOULD NOT perform a currency conversion if a client uses an
>    incorrect currency code.  Servers SHOULD return a 2004 "Parameter
>    value range" error instead."
>
> However, in 5.1.1, it says:
>
>      "An OPTIONAL <fee:currency> element.  If the server does not
>       support <fee:currency> value, it MUST return a 2306 error
>       response;"
>
> Further below, the draft offers a third option:
>
>   "The <fee:command> element also has an OPTIONAL "avail" attribute
>    which is a boolean.  If the value of this attribute evaluates to
>    false, this indicates that the server cannot calculate the relevant
>    fees, because the object, command, currency, period or class is
>    invalid according to server policy."
>
> So this would indicate that an invalid currency in a <fee:check> should
> not result in an EPP error at all, but merely cause a non-available fee
> check result (an option which I would prefer).
>
> I believe this requires some unification, or clarification as to when to
> use which code (in the responses to transform commands at least), or when
> to use avail="false".

In my view 2004 is more on the protocol-layer, i.e. value supplied not in
curl -s -o- https://www.currency-iso.org/dam/downloads/lists/list_one.xml | \
 sed -n -e "/<Ccy>/s/.*>\([^<]*\)<.*/\1/p" | sort | uniq | tr "\n" " "

2306 is a policy violation, i.e. may be a valid currencyType but is
not supported by your registry.

HTH,