[RSSAC Caucus] Checking whether current RSOs are authoritative for TLDs: nope

[Wessels, Duane]

Thanks Wes.  I unfortunately had a lot of connectivity problems during today's meeting, so I missed some of the discussion towards the end.  I think there was a question about the behavior of j.root-servers.net related to this topic?

The addresses for j.root-servers.net are dedicated to serving the root zone.  There are no TLDs or other Verisign customer zones served by j.root-servers.net, as I believe Wes' data also shows.

DW


> On May 1, 2020, at 8:15 AM, Wes Hardaker <hardaker at isi.edu> wrote:
> 
> There was discussion today on the newly forming work party about rogue behavior (a work party name change may occur, but I'm using the current one) about whether existing RSOs were serving data other than the root, arpa and root-servers.net from their existing root server infrastructure.  One of the questions was whether TLDs were being served authoritatively from some  instances.  I threw together a few quick bash scripts to do minimal checking of this and determined that based on advertised addresses and the root zone data, there are no RSOs currently advertising TLD service within the root zone data.  Details here:
> 
> https://www.isi.edu/~hardaker/news/20200501-rso-addresses.html
> 
> (feel free to embrace and extend)
> -- 
> Wes Hardaker
> USC/ISI
> _______________________________________________
> rssac-caucus mailing list
> rssac-caucus at icann.org
> https://secure-web.cisco.com/1ahIWCZXPlykQpPs3moVuigcfbQeGBv5aQcblanePHTOh28YlSzaDxzZcdva2kDxW29L_hKsJGmF0EBfh7VjLCyeJMEcDE5cqt77Y-3OzPs10g5X3Acm9l3R56pDQgllpr53OWkO9KaKVYVHDKsZZtSWmCi5QGgLexyFWVZssE5n2BL9bQQ5xqZWx5FWOJz97L_nYd15v7aSAUAw5IAyQwhQcQQPLJE0zYaq85CtjIaHALUuG4HFLYa5cDQr7og47o1FH8FnAYO5PVRYbRmsUZg/https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Frssac-caucus
> 
> _______________________________________________
> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://secure-web.cisco.com/1i8CSrtfV0VHHLJXVjED198A4EhkUu7GRPBVukAarSH-VSch--PETDKaejtK16xHsWPSOd0qy3G_w-sZ2eTtxLJ5T0RPJSlv-7SxtdrAY-4Pfu54XBLy8mljepeI5X97gIgPBf9zZdlf24PpfeUB6MLC6I8nYjMA5WwBiOdvVawZkxqcUD1TAKq0MfAujLjzHFJgwX5SbYNQVtaiAOWzlN3BtvkNNhXHu5eLrHufhwY2fGbcZU2v2v8nSpM4e1suGXHT51ZrAg9X0ZHv_sEhF8w/https%3A%2F%2Fwww.icann.org%2Fprivacy%2Fpolicy) and the website Terms of Service (https://secure-web.cisco.com/12fcJjAeS9MJQVNqeJgjE3s1C6NjikyLaGS8q-KpVUITT4fs57PMGbJ6BSlwwlrSzQba7-2Vb6zNywwAUGE5HGJLm9nXa36EI0XURV97kGeYw6FaO9GSokJmp8M9b-xVdNL5cJBa9af81ss5JOizA9ErSjkxQWvvil8q7fz0qQUzZs9WBQ0s4BtpigwNbzDNm0hUs3Ju4pkJSdMUpeih-LQqGCx8zFihmWlzCq8uIYNhDYDHpMeNlgXvo0aeFrOqCyBPWLqd4SmCiepp882S29A/https%3A%2F%2Fwww.icann.org%2Fprivacy%2Ftos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4695 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/rssac-caucus/attachments/20200501/5be705c0/smime.p7s>