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 information. I agree that there
should be a choice between inclusion of the commands or the reason in
“objectCDType” to support returning either a successful list of commands or
optionally providing a reason that the fee information is not available. My
recommendation for “objectCDType” is below:
<complexType name="objectCDType">
<sequence>
<element name="objID" type="fee:objectIdentifierType" />
<choice minOccurs=”0”>
<element name="command" type="fee:commandType"
maxOccurs="unbounded" />
<element name="reason" type="eppcom:reasonType”/>
</choice>
</sequence>
<attribute name="avail" type="boolean" use=”required” />
</complexType>
The objectCDType can include the fee:objID, the fee:objID along with the
commands, or the fee:objID along with the reason. The “avail” flag is changed
to required without a default to be explicit, which is consistent with how the
“avail” flag works in the check response. The reason leverages the
“eppcom:reasonType” to support use of the optional “lang” attribute to be
consistent with the check response.
—
JG
James Gould
Distinguished Engineer
jgo...@verisign.com
703-948-3271
12061 Bluemont Way
Reston, VA 20190
VerisignInc.com <http://verisigninc.com/>
On 4/28/17, 8:09 AM, "Thomas Corte" <thomas.co...@knipp.de> wrote:
Hello,
On 27/04/2017 21:55, Gould, James wrote:
> ...
> h. In the example, I don’t believe any <fee:cd> elements other than
> <fee:objID> and <fee:reason> would be returned when avail=”0”. I
> recommend removing the <fee:period> from the example when avail=”0”.
Overall, I'm a bit puzzled regarding the usefulness of the "avail"
attribute at this level, especially since the <cd> element still requires
at least one command to be specified. The change log says
"Moved fee avail to objectCDType to allow fast failing on error situations."
However, if e.g. the domain name is invalid for the TLD, the XSD still
demands to include at least one command, meaning that all commands from
the check request would have to echoed here for no good reason. "command"
in objectCDType should IMO have minOccurs="0". Even better, there should
be a <choice> between a sequence of <command> or <reason> in the XSD
(either there are available commands, or there's a reason why they're not
available).
I'm also wondering how to report a wrong currency with this new version.
I think the only way to deal with it is to let the entire <epp:check>
fail with an error, since there's no way to (briefly) report a wrong
currency due to the way objectCDType is currently defined.
I don't think the "fast fail" objective was reached in this regard.
Best regards,
Thomas
--
TANGO REGISTRY SERVICES® is a product of:
Knipp Medien und Kommunikation GmbH
Technologiepark Phone: +49 231 9703-222
Martin-Schmeisser-Weg 9 Fax: +49 231 9703-200
D-44227 Dortmund E-Mail: supp...@tango-rs.com
Germany
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
