Re: [Int-area] practical issues with using v4-mapped addresses for nat64
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Int-area] practical issues with using v4-mapped addresses for nat64
From: Iljitsch van Beijnum <iljitsch at muada.com>
Subject: Re: [Int-area] practical issues with using v4-mapped addresses for nat64
Date: Thu, 24 Jul 2008 10:33:16 +0200
> I.e., when I was at the LACNIC meeting IPv4 was turned off, but unlike
> at the last IETF meeting, there was a NAT-PT translator present. So I
> could browse the web, connect to Jabber, send/receive email etc even
> though the servers didn't have IPv6 addresses.
Google cache (for example, http://www.google.com/search?q=IETF and
please go to "chache" section of it) is using IPv4 address in the URL like
http://72.14.235.104/search?q=cache:vtraHFRvKEsJ:www.ietf.org/rfc.html+IETF&hl=ja&ct=clnk&cd=2
Which means you could not browse those types of URLs through NAT-PT translator.
So, as a commercial ISP, we do not think NAT-PT can be acceptable by customers.
This is the reason why we have to do dual stack (by 4-4 NAT, dual stack lite,
snat or whatever).
> However, a SIP client, Skype and BitTorrent didn't work: they
> explicitly use IPv4 addresses, which weren't reachable.
True. But again, please note that not only those applications
but also many web pages like google cache are not compatible with NAT-PT.
> Obviously those clients can be upgraded, but it would be extremely useful if
> existing IPv4 applications could work through a NAT64 translator.
True. But it is very hard or impossible I think.
It seems to me that just making those applications IPv6 compatible is
the easiest and the least expensive way....
Best wishes,
Shin Miyakawa
_______________________________________________
Int-area mailing list
Int-area at ietf.org
https://www.ietf.org/mailman/listinfo/int-area
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.