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

[Thomas Corte <[e-mail]>]

Hello,

I've noticed two more issues with the latest EPP fee extensions draft,
detailed below.

Generally, I wonder if this mailing list is the right place to report
such issues. Should I rather contact the authors directly, or is there a
bug tracker set up for this purpose?


Issues:

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".


2) In the description for the <fee:check> response, the draft says:

     "If a <fee:object> element in the client command contains no
      <fee:command> element the server SHOULD return a <fee:command>
      element for each server billable transaction combination of the
      <fee:object>."

However, such a case cannot occur since the definition of the
"objectCheckType" complex type currently requires at least one
<fee:command> element (minOccurs is not set and defaults to 1).
This should be changed in the schema so that the intended "command
wildcard" option becomes available.

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