nanog mailing list archives
Re: V6 still not supported
From: "John Levine" <johnl () iecc com>
Date: 19 Mar 2022 22:14:13 -0400
It appears that Matt Hoppes <mattlists () rivervalleyinternet net> said:
Just like with IPv6, there would be a transition period, but during that time software updates would very easily bring equipment up to spec much faster and quicker. Eventually, 192.168.0.1 would be represented (for example) as 0.0.0.0.192.168.0.1 (or something similar - I haven't really sketched out the logistics on paper).
Sounds just like an IPv4-mapped IPv6 address, which is ::ffff:192.168.0.1. See RFC 1884, written in 1995, and the other RFCs which update it but don't change this particular aspect. What's the difference? R's, John
Current thread:
- Re: BOOTP & ARP history, (continued)
- Re: BOOTP & ARP history Michael Thomas (Mar 19)
- Re: BOOTP & ARP history Masataka Ohta (Mar 20)
- Re: V6 still not supported bzs (Mar 10)
- Re: V6 still not supported Randy Bush (Mar 10)
- Re: V6 still not supported Joe Maimon (Mar 10)
- Re: V6 still not supported Matt Hoppes (Mar 17)
- Re: V6 still not supported borg (Mar 18)
- Re: V6 still not supported Owen DeLong via NANOG (Mar 18)
- Re: V6 still not supported Matt Hoppes (Mar 19)
- Re: V6 still not supported Tom Beecher (Mar 19)
- Re: V6 still not supported John Levine (Mar 19)
- Re: V6 still not supported Mark Delany (Mar 19)
- RE: V6 still not supported Vasilenko Eduard via NANOG (Mar 21)
- Re: V6 still not supported Owen DeLong via NANOG (Mar 21)
- Re: V6 still not supported Bjørn Mork (Mar 21)
- Re: V6 still not supported Owen DeLong via NANOG (Mar 22)
- Re: V6 still not supported Randy Carpenter (Mar 19)
- Re: V6 still not supported borg (Mar 20)
- Re: V6 still not supported John Levine (Mar 18)
- Re: V6 still not supported bzs (Mar 18)
- Re: V6 still not supported Saku Ytti (Mar 19)