IPv4 in IPv6 in AAAA records

[Phil Howard]

On Mon, Aug 23, 2004 at 09:48:10AM +0100, Colm MacCarthaigh wrote:

| There is also the IPv4-compatible-IPv6 address prefix, ::/96 and
| addresses look like: ::193.1.193.194. Using either in AAAA records
| is a *really* terrible idea.

Could you provide me with more enlightenment on this?  If applicable
to the list topic, post here.  If not applicable to the list topic,
you can reply privately by removing "-nsd-users" from my email address.


| This is still a bug in NSD though, as the IPv6 standards allow for the 
| low order 32 bits to be represented as dotted quads for any address, for 
| example:
| 
|   colmmacccc at byron:~$ ping6 2001:770:18:2:206:5bff:254.63.170.218
|   PING 2001:770:18:2:206:5bff:254.63.170.218(2001:770:18:2:206:5bff:fe3f:aada) from ::1 : 56 data bytes
|   64 bytes from 2001:770:18:2:206:5bff:fe3f:aada: icmp_seq=1 ttl=64 time=0.066 ms

Would it be presumed that someone would be allowed to reach some IPv4
address internal on some LAN if there was some IPv6 translator that
could be addressed publically to do so, by expressing it with that
translator's /96 address and appending the dotted-quad?  I never did
think about that before, but now it seems like an interesting way to
some services functional without implementing or deploying IPv6 on
each server.  Now this is getting way off from "nsd-users" topic but
NSD would be a tool I'd be using with such a thing if I did so.

-- 
-----------------------------------------------------------------------------
| Phil Howard KA9WGN       | http://linuxhomepage.com/      http://ham.org/ |
| (first name) at ipal.net | http://phil.ipal.org/   http://ka9wgn.ham.org/ |
-----------------------------------------------------------------------------