Re: maximum ipv4 bgp prefix length of /24 ?

[borg () uu3 net]

Well, I think the sane solution would be to push customers/clients
into IPv6 and keep services IPv4. Then start moving services to dualstack.

Most of todays customers/clients are consumers. They just connect to server
to get data, watch movies, listen to music. Gaming is similar. That way,
ISPs could do NAT64 thingie to provide IPv6 -> IPv4 bridges. More IPv4
addresses would be freed for power users. After decade, IPv4 could be nearly 
gone.

If only IPv6 would suck so badly... ;)


---------- Original message ----------

From: Delong.com via NANOG <nanog () nanog org>
To: Matthew Petach <mpetach () netflight com>
Cc: Geoff Huston <gih () apnic net>, Delong.com via NANOG <nanog () nanog org>
Subject: Re: maximum ipv4 bgp prefix length of /24 ?
Date: Tue, 10 Oct 2023 15:43:28 -0700

Im not sure that we never acknowledged it, but we did fail to address it,
largely because I think we basically determined that its too hard.

Theres really no way for a machine with a >32 bit address to
feasibly/reliably talk to a machine that only understands 32-bit addresses
short of involving some sort of intermediate proxy host doing some form of
address translation. Weve actually got LOTS of those solutions deployed with
varying levels of success/failure/idiosyncrasies. Ive spent a fair amount of
time thinking about alternatives and admit that I, myself am stumped as to
how one would go about this.

Do you have a proposal for how this problem could have been/could be solved?