IPv6 Pain Experiment

[valdis.kletnieks at vt.edu (Valdis Klētnieks)]

On Sun, 06 Oct 2019 17:47:24 -0400, bzs at theworld.com said:

> All a strictly IPv4 only host/router would need to understand in that
> case is the IHL, which it does already, and how to interpret whatever
> flag/option is used to indicate the presence of additional address
> bits mostly to ignore it or perhaps just enough to know to drop it if
> it's not implemented.

So... how would a strict IPv4 router handle the case where 8.8.4.5.13.9/40
should be routed to Cogent, but 8.8.4.5.17.168/40 should be routed via
Hurricane Electric, and no you can't just route to wherever 8.8.4.5 goes
because there's yet another peering war and nobody's baked a cake yet, so
sending packets for either route to the wrong link will cause blackholing?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20191006/e42b592d/attachment.sig>