Hi Don,
Am 14.08.2025 um 22:34 schrieb Don Slaunwhite:
Hi Folks,
I'd like to provide a bit of background as to why I believe this is coming up.
CIRA is going through ICANN RSP evaluation for Round 2. (and so is SIDN)
As part of that, one of the requirements is that your IDN EPP extension must be
registered with the IANA EPP Extension Registry.
https://www.iana.org/assignments/epp-extensions/epp-extensions.xhtml
Now for years I think many organizations, CIRA included, have been using the
draft idnmap-02 as our basis for our IDN EPP implementation.
https://datatracker.ietf.org/doc/html/draft-ietf-eppext-idnmap-02
In previous RST testing for ICANN we just referenced the DRAFT RFC and
everything was fine.
But now ICANN is saying It must be registered in the EPP Extension Registry.
And I assumed earlier on that at some point that DRAFT made it to RFC and was
registered. But found out it wasn't.
In order to move forward with Round 2 RST Testing, we need to be able to
reference an EPP Extension in the table.
We are in the process of writing up a new CIRA IDN EPP Extension which is
derived from idnmap-02 and submit it for entry into the registry. Much like
Identity Digital did.
But realistically from a global point of view, it would be nice if the original
DRAFT would move forward into full RFC and be submitted.
Or even if you can submit the draft itself. (I'll be honest I'm not sure
exactly what the rules are there.)
That way we don't end up with a bunch of Backend Registry Operator specific EPP
extensions (all based off of idnmap-02) in the registry, just to meet this
requirement.
Thoughts?
Jim Galvin and I are currently working on a new IDN EPP extension.
It's still an early draft, but we're trying to create a new extension
that is going to cover all policies created by the IDN EPDP and the
ongoing Latin Script Diacritics (LD) PDP. Both of them have specific
requirements, in particular about the same entity principle and also
having to select/define a primary domain name for the variant set *per
TLD* (in case you are using variant TLDs).
Currently we (TANGO) are still using our own proprietary EPP extension,
but going forward for the next round we'll be switching to the new
extension.
I see the problem with yet another IDN/variant EPP extension, but with
the new policies, the existing extensions (including our own) don't
really cover all of those new requirements.
Our hope is that most RSPs will adapt that new extension (if they are
offering variants in the next round) making life easier for registrars
to support variants, too.
Cheers,
Michael
--
____________________________________________________________________
| |
| knipp | Knipp Medien und Kommunikation GmbH
------- Technologiepark
Martin-Schmeisser-Weg 9
44227 Dortmund
Germany
Dipl.-Informatiker Fon: +49 231 9703-0
Fax: +49 231 9703-200
Dr. Michael Bauland SIP: [email protected]
Software Development E-mail: [email protected]
Register Court:
Amtsgericht Dortmund, HRB 13728
Chief Executive Officers:
Dietmar Knipp, Elmar Knipp
Certified according
DIN ISO/IEC 27001:2017
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
