News for hackers. Stuff that matters.

A comment on HTTP/3 is everywhere but nowhere. Parent comment

Re:HTTP/3 is everywhere but nowhere by yyyk on Monday March 17, 2025 @10:17PM (#43395092)
>That, and basically guaranteeing you don't have to deal with the company you just acquired having deployed their accounts with the same 10/16 subnet your own company uses.

I always found that to be a desperate talking point. 'Prepare your network for the incredibly rare event where you intend to integrate directly' (didn't anyone hear of network segmentation?). It makes a lot more sense to worry about the ISP unilaterally changing your prefix - something that can only happen in IPv6.

[ Parent | on HN ]
Re:HTTP/3 is everywhere but nowhere by bigstrat2003 on Tuesday March 18, 2025 @02:00AM (#43396185)
> It makes a lot more sense to worry about the ISP unilaterally changing your prefix - something that can only happen in IPv6.

ISPs unilaterally change your DHCP address on IPv4 all the time. And in any situation where you would have a static address for IPv4, your ISP should have no problem giving you a static v6 prefix. This argument makes no sense at all.

[ Parent | on HN ]
Re:HTTP/3 is everywhere but nowhere by shawabawa3 on Tuesday March 18, 2025 @06:29AM (#43397719)
Your ISP provided ipv4 has no relation to your internal private network space

My understanding is that for some bizarre reason this is not usually the case with IPv6

[ Parent | on HN ]