how about using an iana registry similar as described for rdap? see <https://www.iana.org/assignments/rdap-dns/rdap-dns.xhtml> Bootstrap Service Registry for Domain Name Space<https://www.iana.org/assignments/rdap-dns/rdap-dns.xhtml> iana.org<https://www.iana.org/assignments/rdap-dns/rdap-dns.xhtml> [apple-touch-icon.png]<https://www.iana.org/assignments/rdap-dns/rdap-dns.xhtml>
Op 20 mrt 2024 om 13:00 heeft Paul Ebersman <list-reg...@dragon.net> het volgende geschreven: [You don't often get email from list-reg...@dragon.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] jim> Surely clients get told about the EPP server's supported transports jim> as a result of signing the registry's contract? If so, do we jim> *really* need something else? My guess is that even though registry software updates aren't overly nimble, registry contracts are probably even slower and harder to update/change. _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
