asterisk users - Jan 2004 - AW: IPv6 support

In the setup I'm looking now there are IPv4-only and IPv6-only SIP-clients
(or UA's) but the
Proxies (or servers) are v4 and v6 dual-stacked (to make things a bit easier). 
I think there will be a lot of IPv6-only SIP-clients  (e.g. mobile clients and
all the existing IPv4-NAT'ed
networks) and a lot of IPv4-only "old legacy" SIP-clients. We have to
find ways to deal with such
setups. 
 
There are ways with IPv4/IPv6 NAT-PT but I think this is not the right way (a
lot of DNS-problems).
There seems to be a way with RTP-Proxies (thanks Olle for the link) but even
this (if it works) seems
not the right solution for the problem (it's still a kind of NAT who breaks
the end-to-end idea).
What do you think about a back-to-back-server between the IPv4 and the IPv6
world?
 
Regards
Armin
 
 

	-----Urspr?ngliche Nachricht----- 
	Von: asterisk-users-admin@lists.digium.com im Auftrag von Nicolas Bougues 
	Gesendet: Do 08.01.2004 21:53 
	An: asterisk-users@lists.digium.com 
	Cc: 
	Betreff: Re: [Asterisk-Users] IPv6 support
	
	

	On Thu, Jan 08, 2004 at 11:19:48AM +0100, Olle E. Johansson wrote:
	> >
	> >There is no real "design issue" with IPV6. No more NAT,
that's all.
	> Oh, there is a lot of design issues if you consider a dual-IP network.
	>
	> * If you dial me from an IPv4 network and I'm on IPv6, we have to
force
	> media proxy
	>   (Like NAT today)
	>
	> * If you're on a IPv4 only network, dialling me and get an IPv6
address to
	> my SIP proxy
	>   - what do you do?
	> * If you're dialing through a SIp proxy and your SDP is IPv6 and your
SIP
	> contact is IPv4,
	>   what do we do?
	>
	
	Well, usually right now :
	- machines have both v4 and v6 stacks
	- machines have both v4 and v6 addresses
	
	In this setup, there wouldn't be any change for v4 stuff. And v6 stuff
	is not much more complicated (although there still might be problems,
	like, for instance, some VoIP protocol having syntax problems with v6
	addresses).
	
	The idea of a v4 client and v6 server (or proxy, or whatever) looks a
	little bit odd to me. If such a thing was easy to do, the world would
	have embraced ipv6 quite some time ago.
	
	IPv4 machines can only talk to IPv4.
	
	IPv6 maps IPv4 addresses. So a machine with an IPv6 only stack could
	theoritically reach a v4 client through some gateway. And I agree,
	this would be quite a mess from the voip protocol stand point.
	
	But hopefully, either :
	- v6 hosts are fully v4 enabled as well
	- v6 only hosts will only talk to v6 peers
	
	--
	Nicolas Bougues
	Axialys Interactive
	_______________________________________________
	Asterisk-Users mailing list
	Asterisk-Users@lists.digium.com
	http://lists.digium.com/mailman/listinfo/asterisk-users

Brunner, Armin wrote:
> In the setup I'm looking now there are IPv4-only and IPv6-only
SIP-clients (or UA's) but the
> Proxies (or servers) are v4 and v6 dual-stacked (to make things a bit
easier).
> I think there will be a lot of IPv6-only SIP-clients  (e.g. mobile clients
and all the existing IPv4-NAT'ed
> networks) and a lot of IPv4-only "old legacy" SIP-clients. We
have to find ways to deal with such
> setups. 
>  
> There are ways with IPv4/IPv6 NAT-PT but I think this is not the right way
(a lot of DNS-problems).
> There seems to be a way with RTP-Proxies (thanks Olle for the link) but
even this (if it works) seems
> not the right solution for the problem (it's still a kind of NAT who
breaks the end-to-end idea).
> What do you think about a back-to-back-server between the IPv4 and the IPv6
world?
IPv6-enabled Asterisk fits right in.

I think the missing piece is how IPv4 clients now when to use a proxy or not.
But with Asterisk,
you can (like NAT today) force the media stream through Asterisk and let
asterisk make the decision
if it's possible to let the media stream bypass (SIP re-invite) asterisk.

Also, you could configure this is SER, so SER forwards calls from
"mixed" networks to ASterisk.

Again, I would like to see someone looking into what it takes to IPv6 enable
asterisk, both
coding (making sure we have space for 128 bits IP address and mask) and
configuration,
(accepting IP addresses with : instead of . ).

/O