[SIPForum-techwg] SIPconnect 1.1 baseline - IPv6
Elwell, John
john.elwell at siemens.com
Thu Aug 14 11:27:19 EDT 2008
> -----Original Message-----
> From: techwg-bounces at sipforum.org
> [mailto:techwg-bounces at sipforum.org] On Behalf Of Henning Schulzrinne
> Sent: 14 August 2008 14:43
> To: Spencer Dawkins
> Cc: techwg at sipforum.org
> Subject: Re: [SIPForum-techwg] SIPconnect 1.1 baseline - IPv6
>
> It might help the discussion if we distinguished between MUST
> implement and MUST use, just as we do for security
> mechanisms, such as
> TLS, or transport protocols, such as TCP, for SIP. Given that all
> mainstream server operating systems likely to be used for servers
> support IPv6, I see no problem with mandating IPv6 implementation.
> This really is not hard - we've done this in our server years
> ago, so
> I have some experience. Obviously, nobody is forced to run
> IPv6 or, as
> a service provider, offer IPv6 services. We're the not doing the
> industry a favor by pretending that we can just ignore the coming
> address crunch. The alternatives, such as yet more layers of NATing,
> are far worse than a few lines of socket code.
>
> Providing for both IPv6 and IPv4 does not prevent somebody,
> e.g., in a
> closed environment (say, IMS or the military) from running only IPv6
> if they so choose.
[JRE] But we aren't talking about a closed environment here, are we? We
are talking about between two environments - enterprise and service
provider.
John
More information about the techwg
mailing list