Re: IPv6 Pain Experiment

[Owen DeLong <owen () delong com>]

> On Oct 4, 2019, at 16:48 , Michel Py <michel.py () tsisemi com> wrote:
>
> > Owen DeLong wrote :
> > How would you have made it possible for a host that only understands 32-bit addresses to exchange traffic with a 
> > host that only has a 128-bit address?
>
> With some kind of NAT mechanism, naturally.
> Which is not possible with the current IPv6 address format, if you want something stateless and that does not rely on 
> DNS.

Well, what address format would you propose that would make it better? Let’s talk actual workable detailed proposals 
rather than just hand-waving.

We already have a number of such solutions:
        NAT64
        464XLAT
        B4/AFTR
        etc.

> > How would you have made a 128-bit address more human-readable? Does it really matter?
>
> I have found it difficult to talk hex with people from other countries.

I haven’t had that much trouble.

> Try to say FACEB00C to someone who does not speak your langage.

Well, your abuse of the phonetic alphabet might be part of the problem…

> Foxtrox Alpha Charlie Echo Bravo Zero Zero Charlie does not go through either.

Foxtrot, Alpha, Charlie, Echo, colon,  Bravo, Zero, Zero, Charlie has worked relatively well for me.

> 250.206.176.192 works all the time. Everyone gets the numbers.

Really? I’ve actually had more confusion over this… especially five vs. nine (unless I resort to pilot-speak which 
often confuses them even more).

two, five, zero, point, two, zero, six, point, one, seven, six, point, one, nine, two will almost invariably result in 
some random member of the set:
        290.206.176.152
        250.206.176.152
        250.206.176.192
        290.206.176.192

And that’s an address not particularly fraught… Consider, instead:

        193.159.155.159

Sometimes I get lucky with one, niner, tree, point, one, fife, niner, point, one, fife, fife, point, one, fife, niner. 
However, that’s rare.

I guess it depends in part on who you are speaking with.

Owen

> Michel.
>
>
>
>
> TSI Disclaimer:  This message and any files or text attached to it are intended only for the recipients named above 
> and contain information that may be confidential or privileged. If you are not the intended recipient, you must not 
> forward, copy, use or otherwise disclose this communication or the information contained herein. In the event you 
> have received this message in error, please notify the sender immediately by replying to this message, and then 
> delete all copies of it from your system. Thank you!...