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

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, t

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

stered in EPPROID" >> >> At the moment we let it empty and got a warning instead of error. >> >> Marco >> >> >> On 30 January 2025 22:00:50 CET, "Andrew Newton (andy)" wrote: >>> Marco, >>> >>> Assuming you are talk

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

those writing the (test) requirements. > >Thanks, >James > >From: InterNetX - Marco Schrieck >Organization: InterNetX GmbH >Date: Thursday, January 30, 2025 at 7:14 AM >To: "regext@ietf.org" >Subject: [Ext] [regext] Clarification on ROID Usage for Registr

[regext] NIS2 and impact on EPP

Hi all, I send this already to gtld-tech group and was then pointed to this group. I wanted to ask if anyone has thought about the impact of NIS2 on EPP, especially the validation of domain holder? There are many issues here regarding protocol and processes. It would be good to work together

Re: [regext] Re-chartering REGEXT?

___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext Marco Schrieck Bereichsleiter Entwicklung -- InterNetX GmbH Johanna-Dachs-Str. 55 • 93055 Regensburg • Germany Tel. +49 941 59559-0 internetx.com • internetx.com/linke

[regext] Host update and removing V6 glues aka comparison normalized and compressed representation

:624:1:0:0:0:b051 and it failed on registry side. What should be the correct behave in such situations ? Regards Marco Schrieck PS: IP addresses are anonymized. -- InterNetX GmbH Johanna-Dachs-Str. 55 93055 Regensburg Germany Tel. +49 941 59559-0 Fax +49 941 59579-050 www.internetx.com

Re: [regext] EPP and rate-limiting

Hello, Best rate limiting from my side is done by slowing down the requests. It does not break the client even in other situations. Regeards, Marco Am 17.01.20 um 15:30 schrieb Stephane Bortzmeyer: > Sometimes, some clients are too talkative and, for instance, try > too often to grab a domain.

Re: [regext] Use of Internationalized Email Addresses in EPP protocol: placeholder value

Hi All, I am completely with Ulrich. >From policy side and also from aspect of clean data. Using dummy values in objects was always a bad idea. And even in GTLD space, the registrar usually have requirements to verify the contacts. So not only registry must support the EAI also the registrar hav

Re: [regext] Use of Internationalized Email Addresses in EPP protocol: placeholder value

> JG > >   > >   > >   > > James Gould > > Fellow Engineer > > jgo...@verisign.com > > >   > > 703-948-3271 > > 12061 Bluemont Way > > Reston, VA 20190 > >   > > Verisign.com <http://verisigninc.com

Re: [regext] Use of Internationalized Email Addresses in EPP protocol: placeholder value

ourse the issue may be more > "pressing"/urgent in case > of some IDN ccTLDs than gTLDs. > >   > The ccTLDs are less limited in their practice and can provide their own > schemas and even protocols. > > -- > SY, Dmitry Belyavsky > >

Re: [regext] pass on the lower fee

owever, registrars >> supporting the fee extension are unlikely to expect fee information in >> this place. >> >> But I think support for this use case should be added to a revised >> version of RFC 8748. >> >> Best regards, >> >> Thomas >&g

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

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