Hello,
On 10/27/20 15:37, Gould, James wrote:
> A compromise is to formally define the original intent of the <extValue>
> element, as defined in RFC 5730, and be explicit that
> draft-ietf-regext-unhandled-namespaces extends its usage to cover this use
> case within section 3 "Use of EPP <extValue> for Unhandled Namespace Data".
> To address the concern for the client potentially ignoring the content
> returned by the server per draft-ietf-regext-unhandled-namespaces, text could
> be added to recommend that the server monitor for the usage of
> draft-ietf-regext-unhandled-namespaces in both General EPP Responses and Poll
> Message EPP Responses to inform the client out-of-band of their lack of
> support for a particular extension. In addition, it could be recommended for
> the client to monitor for the usage of draft-ietf-regext-unhandled-namespaces
> to proactively identify extensions that they need to add support for. An
> Implementation Considerations section could be added for this. Thoughts to
> this compromise?
Sounds reasonable to me. With the current EPP RFCs, there's really no
"100% clean" solution here, but the approach makes a good effort to
somehow convey that there's data available without disrupting client
implementations.
If a registry really wants registrars to understand and process their
custom poll messages, it can still resort to simply reject the <login>
command if it doesn't contain the namespace in question.
Best regards,
Thomas
--
____________________________________________________________________
| |
| knipp | Knipp Medien und Kommunikation GmbH
------- Technologiepark
Martin-Schmeißer-Weg 9
44227 Dortmund
Deutschland
Dipl.-Informatiker Tel: +49 231 9703-0
Thomas Corte Fax: +49 231 9703-200
Stellvertretender Leiter SIP: thomas.co...@knipp.de
Software-Entwicklung E-Mail: thomas.co...@knipp.de
Registereintrag:
Amtsgericht Dortmund, HRB 13728
Geschäftsführer:
Dietmar Knipp, Elmar Knipp
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
