Re: New addresses for b.root-servers.net

On Fri, Jun 2, 2023 at 10:40 AM William Herrin wrote: > On Fri, Jun 2, 2023 at 9:57 AM Jim wrote: > > A major concern would be if the IP address were eventually re-assigned > to something else that > > ended up reporting false answers due to a malicious or misconfigured DNS > service. > > Hi

(IETF I-D) Implications of IPv6 Addressing on Security Operations (Fwd: New Version Notification for draft-ietf-opsec-ipv6-addressing-00.txt)

Folks, The IETF OPSEC WG has adopted our IETF I-D entitled "Implications of IPv6 Addressing on Security Operations". The IETF-ID is available at: * TXT: * HTML:

Weekly Global IPv4 Routing Table Report

This is an automated weekly mailing describing the state of the Global IPv4 Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to

Re: New addresses for b.root-servers.net

On Fri, Jun 2, 2023 at 9:57 AM Jim wrote: > A major concern would be if the IP address were eventually re-assigned to > something else that > ended up reporting false answers due to a malicious or misconfigured DNS > service. Hi Jim, That's one reason I suggested intentionally making it a

Re: New addresses for b.root-servers.net

On Thu, Jun 1, 2023 at 5:59 PM William Herrin wrote: A server generation is about 3 years before it's obsolete and is > generally replaced. I suggest making the old address operable for two . > generations (6 years) and black-holed for another generation (3 more > As you mention.. there

Re: New addresses for b.root-servers.net

I know when I did the openresolver project stuff I saw a number that would send glue or referrals from before they moved to the root servers domain names. - Jared Sent via RFC1925 compliant deviceOn Jun 2, 2023, at 8:49 AM, Nathan Ward wrote: On 2/06/2023 at 10:22:46 AM, Wes Hardaker

Re: New addresses for b.root-servers.net

On 2/06/2023 at 10:22:46 AM, Wes Hardaker wrote: > > 2. I'll note that we are still serving DNS requests at the addresses that > we switched away from in 2017 [1][2]. At that time we actually only > promised 6 months and we've doubled that time length with our latest > announced change. But we