Hello,
On 22.10.25 17:32, Gould, James wrote:
Does the RST 2.0 registration requirement also apply to implementations of
active extension
drafts? Imagine that a registry implemented a draft version of the registry
fee extension prior
to it becoming an RFC and the registry needed to pass RST 2.0. Would the
registry need to
register the draft version in the EPP extension registry or worse yet copy the
draft extension
and register it as a proprietary extension retaining the IETF namespace? The
XML namespace is
not easily changed when registries choose to implement the draft extension,
since it will impact
all registrars using that extension version. The implementation of draft
versions has been done
with EPP from the beginning. Consider the 04/02 days of EPP, when registries
implemented the
-04 version of the base EPP draft and the -02 version of the object mapping
drafts. The use of
point versioning of the XML namespace helped with the 04/02 days of EPP, but
draft versions of
EPP extensions have been implemented with the launch phase extension and the
registry fee
extension to name a couple. I believe we should encourage the implementation
of draft
extensions that hopefully do become RFCs, where there are instances that the
draft extensions
did not progress to RFC.
While I agree with the above, I'd also hate to see something like
"urn:ietf:params:xml:ns:fee-0.7"
being allowed to be registered and thereby possibly established as a permanently acceptable
implementation of the fee extension. Working on the registrar side of things, I'm not a fan of
having to maintain support for numerous incompatible versions in my client code.
In this sense, it's good to see ICANN requiring the use of registered extensions going forward, and
I assume they're doing this to make life easier for registrars, as it nudges registries towards
(finally, after 5 years) implementing the 1.0 version.
Allowing "urn:ietf:params:xml:ns:fee-0.7" to be registered alongside
"urn:ietf:params:xml:ns:epp:fee-1.0" would undermine this effort.
Best regards,
Thomas
--
TANGO REGISTRY SERVICES®
Knipp Medien und Kommunikation GmbH Thomas Corte
Technologiepark Phone: +49 231 9703-222
Martin-Schmeisser-Weg 9 Fax: +49 231 9703-200
D-44227 Dortmund E-Mail: [email protected]
Germany
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
