Re: [regext] WG LAST CALL: draft-ietf-regext-rfc7482bis
Hello, On 10/7/20 03:17, Tom Harrison wrote: >>> The question is whether the RDAP protocol should provide guidance with >>> how to handle overlapping non-unique handles. >> >> I don't think it should. A Jasdip pointed out, the definition of a >> handle notes that they're supposed to be registry-unique. > > I agree with Scott and Jasdip on this point. I think it's problematic to have a standard like this (which will eventually have to be implemented by all ICANN-regulated registries) impose such a requirement (unique handles across all object types) out of the blue when there are already hundreds of databases out there that were not build with this assumption in mind. Sure, a migration of non-unique handles is possible, and we did that when ICANN demanded a specific ROID prefix per TLD, but that was a minor change as the ROID isn't really used for operationally addressing anything. Renaming contact IDs and/or registrar IDs would have more of an impact, as it would also require all registrars to update their own databases/configurations as well to reflect the new handles. If "using a precedence order" means that a server can choose to e.h. just deliver the contact when there's a registrar with the same handle, that's an acceptably lenient interpretation. Otherwise, no assumption about the uniqueness of entity handles should be made long after the fact. Best regards, Thomas -- TANGO REGISTRY SERVICES® Knipp Medien und Kommunikation GmbHThomas Corte Technologiepark Phone: +49 231 9703-222 Martin-Schmeisser-Weg 9 Fax: +49 231 9703-200 D-44227 Dortmund E-Mail: thomas.co...@knipp.de Germany ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
Re: [regext] WG LAST CALL: draft-ietf-regext-rfc7482bis
On Wed, Oct 07, 2020 at 10:46:52AM +0200, Thomas Corte (TANGO support) wrote: > On 10/7/20 03:17, Tom Harrison wrote: The question is whether the RDAP protocol should provide guidance with how to handle overlapping non-unique handles. >>> >>> I don't think it should. A Jasdip pointed out, the definition of a >>> handle notes that they're supposed to be registry-unique. >> >> I agree with Scott and Jasdip on this point. > > I think it's problematic to have a standard like this (which will > eventually have to be implemented by all ICANN-regulated registries) > impose such a requirement (unique handles across all object types) > out of the blue when there are already hundreds of databases out > there that were not build with this assumption in mind. Entity identifiers aren't RDAP 'entry points', though, in that there are no guarantees that you can take an identifier from some other context and construct a usable query like 'https://rdap.example.net/entity/$identifier' (putting RFC 8521 object tags to one side), so it's not clear that it actually imposes this requirement. For example, it's open to an implementor to prefix their existing identifiers with strings describing the underlying object types, in order to construct unique entity handles. -Tom ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
[regext] Fwd: New Version Notification for draft-belyavskiy-epp-eai-00.txt
Dear colleagues, This is an initial version of the IETF draft allowing usage of Internationalized Email Addresses in the EPP protocol. -- Forwarded message - From: Date: Wed, Oct 7, 2020 at 4:25 PM Subject: New Version Notification for draft-belyavskiy-epp-eai-00.txt To: Dmitry Belyavskiy A new version of I-D, draft-belyavskiy-epp-eai-00.txt has been successfully submitted by Dmitry Belyavskiy and posted to the IETF repository. Name: draft-belyavskiy-epp-eai Revision: 00 Title: Use of Internationalized Email Addresses in EPP protocol Document date: 2020-10-07 Group: Individual Submission Pages: 4 URL:https://www.ietf.org/id/draft-belyavskiy-epp-eai-00.txt Status: https://datatracker.ietf.org/doc/draft-belyavskiy-epp-eai/ Htmlized: https://datatracker.ietf.org/doc/html/draft-belyavskiy-epp-eai Htmlized: https://tools.ietf.org/html/draft-belyavskiy-epp-eai-00 Abstract: This document permits usage of Internationalized Email Addresses in the EPP protocol. TO BE REMOVED on turning to RFC: The document is edited in the dedicated github repo [1]. Please send your submissions via GitHub. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat -- SY, Dmitry Belyavsky ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
