Hi Erik,
<snip>--
> So IPv4-compatible addresses (6to4 addresses, "native" IPv6 address) must
> be configured on the nodes and must be retrieved from something like the DNS.
>
> > This seems to suggest that we need to have a PTR record for
> > IPv4-compatible-IPv6 addresses in in-addr.arpa domain as is the
> > case with A records (IPv4 addresses) and not IP6.INT domain.
>
> I'm aware of that optimization but it isn't clear to me that it
> is needed or desired.
Please find a section (page 25) of RFC2553, Mar 1999 enclosed below:
One possible source of confusion is the handling of IPv4-mapped IPv6
addresses and IPv4-compatible IPv6 addresses, but the following logic
should apply.
1. If af is AF_INET6, and if len equals 16, and if the IPv6
address is an IPv4-mapped IPv6 address or an IPv4-compatible
IPv6 address, then skip over the first 12 bytes of the IPv6
address, set af to AF_INET, and set len to 4.
The question is:
If IPv4 compatible address is a proper IPv6 address and
searching of IPv4 compatible address in in-addr.arpa domain is
just for optimization, then why not just search the record in
in-addr.arpa domain and return hostent structure filled with v6
address and not v4 address.
Setting af to AF_INET in returning hostent structure means that
we are treating this address as IPv4 address. But that is not
true. IPv4 compatible address is a IPv6 address and so the
resultant hostent structure should contain IPv4 compatible
address in network format in h_addr_list array and family should
be set to AF_INET6 only.
Or does af being mentioned does not refer to family field in hostent
structure being returned to application.
I feel that phrase is not correct w.r.t IPv4-compatible address.
Anybody has any comments in this regard?
-Praveen
>
> Erik
>
>
--
==============================================================================
Praveen Kumar Amritaluru Phone (Off) : (91)(80)2251554 x 1306
HP India Software Operations Telnet : 847-1306
Bangalore 560 052
India.
==============================================================================
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
