mapped addreses permit very large ISVs to treat all addresses as IPv6 and
one code AF. IPv6. And large ISVs tell their suppliers what they want
not the other way around. So if database vendor X (who causes customers
to use computers for their business) tells sun, compaq, ibm, and hp and
others I want you to do it this way. We will. v4mapped permits them to
write their app to v6 once and only once. And most ISVs don't care about
10 years from now. They care about the $$$$$$ they will make this year
and next year and maybe the next 2 years. And the most efficient cost of
doing business engineering way to do that. And that is doing as the style
suggests in 2553-bus-03.
Now who did we build the api for (we being ipng and IEEE participants)
1. The goodness and social responsibility of man kind on planet earth.
No.
2. For the computer science purist.
No.
3. For the API purist maybe.
No.
4. For someones grandchildren.
No.
5. For people that built certain types of stacks.
No.
6. For ISVs who want the most efficient API possible to support ipv4 and
ipv6 and permit the eventual phase out of IPv4.
Yes.
/jim
"Shout it out G.L.O.R.I.A." (Them [Van Morrison])
On Mon, 25 Jun 2001 [EMAIL PROTECTED] wrote:
> �Hola!
>
> > duplication of code is (and - if we're not gonna change the API draft in a
> > significant way - will always be) inevitable. there are MANY problems in
> > handling both ipv6 and ipv4 (or better, ipv4-mapped) traffic with a single
> > AF_INET6 socket, and most of them are related to security.
>
> > => I disagree. There is *no* security issue with IPv4-mapped addresses
> > as soon as one doesn't forget them.
>
> The problem is that not forgeting them means the same amount of work that doing
> the port in the AF independent way. So the benefits of the IPv4-mapped addresses
> (easy porting) get lost.
>
> > [EMAIL PROTECTED]
>
> HoraPe
> ---
> Horacio J. Pe�a
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> --------------------------------------------------------------------
> 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]
> --------------------------------------------------------------------
>
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
