[regext] Re: [Ext] Clarification on ROID Usage for Registrars in Thin Registry RDAP Implementations

2025-01-30 Thread Marco Schrieck
Hi Yes the registry should generate them, but what with thin Registries. Only we as registrar have the contact data. So we don't have a registry generated roid. I can generate on but the rdap profile checker require me to register the suffix at iana. Eg 1234567-IX If i don't register it we

[regext] Re: [Ext] Clarification on ROID Usage for Registrars in Thin Registry RDAP Implementations

2025-01-30 Thread Rubens Kuhl
Don’t the remaining thin registries allow for thin to thick migration on a granular basis ? Rubens > Em 30 de jan. de 2025, à(s) 18:24, Marco Schrieck > escreveu: > > Hi > > Yes the registry should generate them, but what with thin Registries. > > Only we as registrar have the contact d

[regext] Re: [Ext] Clarification on ROID Usage for Registrars in Thin Registry RDAP Implementations

2025-01-30 Thread Marco Schrieck
Hi Rubens, No its the other way. More and more gTLDs will get thin. Ciao Marco On 31 January 2025 00:31:45 CET, Rubens Kuhl wrote: > >Don’t the remaining thin registries allow for thin to thick migration on a >granular basis ? > > >Rubens > > >> Em 30 de jan. de 2025, à(s) 18:24, Marco Schr

[regext] Re: [Ext] Clarification on ROID Usage for Registrars in Thin Registry RDAP Implementations

2025-01-30 Thread Andrew Newton (andy)
Marco, Assuming you are talking about the 2019 gTLD profile, the registry should be generating the ROIDs because it is also required of them. -andy On Thu, Jan 30, 2025 at 1:52 PM Marco Schrieck wrote: > > As I understand it must be registered there. But as i can oversee it, there > are only R

[regext] Clarification on ROID Usage for Registrars in Thin Registry RDAP Implementations

2025-01-30 Thread InterNetX - Marco Schrieck
Hi All, I am writing to seek guidance on the handling of*ROID (Repository Object IDentifier)*in RDAP implementations for registrars together with*thin registry models*(where registrars hold domain/contact/host data). Our organization acts as a registrar and is working to comply with the RDAP

[regext] draft-ietf-regext-epp-delete-bcp: new telechat date

2025-01-30 Thread Orie
Hi, I moved this out to help outgoing ADs clear their plate. Thanks for your patience regarding processing time for this document. Regards, OS, ART AD ___ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org

[regext] Re: AD Evaluation: draft-ietf-regext-rdap-rir-search-13

2025-01-30 Thread Orie Steele
Hi Tom, Thanks for addressing my comments. I'm marking the document revised I-D needed, and awaiting your updates. Regards, OS, ART AD On Wed, Jan 29, 2025 at 5:09 PM Tom Harrison wrote: > Hi Orie, > > Thanks for your review, much appreciated. > > On Tue, Jan 28, 2025 at 05:15:49PM -0600, Or

[regext] Re: [Ext] Clarification on ROID Usage for Registrars in Thin Registry RDAP Implementations

2025-01-30 Thread James Mitchell
My understanding is the EPP ROID is an identifier that is composed of a suffix that identifies the registry/repository to which an object belongs. That repository identifier should be registered in the IANA registry of EPP Repository Identifiers at https://www.iana.org/assignments/epp-repository

[regext] Re: [Ext] Clarification on ROID Usage for Registrars in Thin Registry RDAP Implementations

2025-01-30 Thread Marco Schrieck
As I understand it must be registered there. But as i can oversee it, there are only Registries. Marco On 30 January 2025 19:42:38 CET, James Mitchell wrote: >My understanding is the EPP ROID is an identifier that is composed of a suffix >that identifies the registry/repository to which an obj