Re: [regext] Confusion around non-uniqueness of nameserver objects

How funny that history repeats itself. This exact issue is how I got involved in EPP now 20 years ago: https://mailarchive.ietf.org/arch/msg/provreg/P19uXw4zn8GGxH0jc8XS2qNpYO4/ I had the exact same issue because

Re: [regext] Confusion around non-uniqueness of nameserver objects

On 21 Dec 2021, at 16:16, Hollenbeck, Scott wrote: > >> [snip] >> >> I was recently contacted by an otherwise clueful person who was confused >> because an RDAP query for a particular nameserver object seemingly >> showed the wrong sponsoring registrar. >> >> Upon investigation, it was

Re: [regext] Confusion around non-uniqueness of nameserver objects

On Mon, Dec 20, 2021, at 12:09, Gavin Brown wrote: > It occurred to me that it may be possible to mitigate this confusion: > in response to nameserver queries, an RDAP server can include a > "related" link to the "authoritative" RDAP server (constructed using > the bootstrap registry). This

Re: [regext] Confusion around non-uniqueness of nameserver objects

Inviato da iPhone > Il giorno 21 dic 2021, alle ore 17:16, Hollenbeck, Scott > ha scritto: > >  >> >> -Original Message- >> From: regext On Behalf Of Gavin Brown >> Sent: Monday, December 20, 2021 12:10 PM >> To: regext@ietf.org >> S

Re: [regext] Confusion around non-uniqueness of nameserver objects

> -Original Message- > From: regext On Behalf Of Gavin Brown > Sent: Monday, December 20, 2021 12:10 PM > To: regext@ietf.org > Subject: [EXTERNAL] [regext] Confusion around non-uniqueness of > nameserver objects > > Caution: This email originated from outs

[regext] Confusion around non-uniqueness of nameserver objects

Hi all, I was recently contacted by an otherwise clueful person who was confused because an RDAP query for a particular nameserver object seemingly showed the wrong sponsoring registrar. Upon investigation, it was revealed that the nameserver in question was subordinate to domain in another