Where to for Samba4? - Native IPv6

[Andrew Bartlett]

On Thu, 2007-09-06 at 16:10 +0100, davidholder at erion.co.uk wrote:
> Andrew,
> 
> I think it is important that Samba4 should be native IPv6. This is going
> to be necessary as the world moves to IPv6. Particularly next year, with
> the release of Windows Server 2008 and with the requirement for IPv6
> support in Federal agencies in the US.
> 
> IMHO it is worth considering dropping support for the historic IPv4 socket
> API and only supporting the IPv6 socket API. Use of IPv6 within the Samba4
> internals would allow you to use one set of function calls for IPv4 and
> IPv6. Essetially, if you code for IPv6 then you get IPv4 for free (this is
> little bit of a simplification).
> 
> This would bring you into line with Vista and Windows Server 2008 and with
> many other platforms and products that are now IPv6 native.
> 
> Whether you take this approach or not, IPv6 support should be high on the
> list. There are many organisations that have been holding off implementing
> IPv6 due to lack of full support in AD, with the release of Windows Server
> 2008 this will change. Some may drop Samba as a result.
> 
> I'm on holiday at present, so I may be slow to reply to any comments! I'll
> do my best!

Jelmer recently merged the IPv4 and IPv6 socket layers, so this may be
closer to a reality.  I'll let jelmer comment further, he really
understands this area better than I.

Andrew Bartlett

-- 
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
Samba Developer, Red Hat Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba-technical/attachments/20070907/b9fcba52/attachment.bin