IPv4-mapped API [Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt]
Mika Liljeberg <mika.liljeberg@welho.com> Sat, 22 February 2003 13:25 UTC
From: Mika Liljeberg <mika.liljeberg@welho.com>
Subject: IPv4-mapped API [Re: [dhcwg] Re: WG last call on draft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt]
Date: Sat, 22 Feb 2003 15:25:31 +0200
Lines: 41
Sender: owner-ipng@sunroof.eng.sun.com
References: <200302221254.h1MCs1I04267@boreas.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Cc: pekkas@netcore.fi, Alain.Durand@Sun.COM, rdroms@cisco.com, dhcwg@ietf.org, ipng@sunroof.eng.sun.com, namedroppers@ops.ietf.org
Return-path: <owner-ipng@sunroof.eng.sun.com>
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ipng@sunroof.eng.sun.com using -f
X-Authentication-Warning: devil.pp.htv.fi: liljeber set sender to mika.liljeberg@welho.com using -f
To: Bill Manning <bmanning@ISI.EDU>
In-Reply-To: <200302221254.h1MCs1I04267@boreas.isi.edu>
X-Mailer: Ximian Evolution 1.2.2
Precedence: bulk
X-Message-ID:
Message-ID: <20140418071705.2560.83288.ARCHIVE@ietfa.amsl.com>
[Topic changed. If you respond to this, please drop unrelated mailing lists.] On Sat, 2003-02-22 at 14:54, Bill Manning wrote: > regarding the use of mapped addresses: > > draft-cmetz-v6ops-v4mapped-api-harmful-00.txt > > might be a useful ID to review before committing this draft to the > stds process. These issues are completely unrelated. The API issues are real but they are not something that can or should be considered in a protocol specification. [Sorry for the off-topicness of the following] I'm not too happy about RFC2553 myself in this respect, and I strongly support the "Alternative solution" (fully specify IPv4-mapped behaviour) in the above mentioned draft. I can attest from implementation experience that it is possible to create a hybrid IPv4/IPv6 stack implementation that uses around 80-90% shared code between IPv4 and IPv6. All IPv4 addresses are handled in IPv4-mapped format internally inside the stack. Our sockets API is (mostly) version agnostic. Most applications are not even aware which IP version they are using. The OS is not a unix derivative and did not have the legacy baggage of the BSD style sockets API. The API that was already defined for IPv4 yielded very easily to support IPv6. MikaL -------------------------------------------------------------------- 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 majordomo@sunroof.eng.sun.com --------------------------------------------------------------------
- IPv4-mapped API [Re: [dhcwg] Re: WG last call on … Mika Liljeberg