[astridevcon-2007] Agenda Planning: Phase 1

[Marc Blanchet]

Le 07-04-14 à 11:58, Olle E Johansson a écrit :
>
> 14 apr 2007 kl. 17.54 skrev Marc Blanchet:
>
>> Le 07-04-14 à 09:05, Tilghman Lesher a écrit :
>>
>>> On Saturday 14 April 2007, Dinesh Nair wrote:
>>>> On Fri, 13 Apr 2007 06:32:33 -0400, Marc Blanchet wrote:
>>>>> - IPv6 support
>>>>
>>>> hear, hear.
>>>
>>> Is there a design issue that needs to be addressed that would  
>>> benefit from
>>> the wide number of developers present?
>>
>> well, fine by me: let's put the v6 code into the trunk.  Kevin?
>>
>>> I'm agreed that IPv6 support in
>>> Asterisk would be a good thing, but I'm not aware of the issues.
>>
>> in a nutshell:
>> - to support ipv6, you need to support multiple (listening)  
>> sockets. not supported now in -trunk even in v4. supported in the  
>> v6 branch. this would benefit users and developers, but need to be  
>> put back on -trunk
>> - url parsing: v6 adds [] to addresses.
>> - media transport negotiation: which transport (v4 or v6) will you  
>> use
>> - related to v6: stun/ice/anat/...
>> - every current network call has to be modified. are developers  
>> ready?
>>
>> Have you looked at the v6 branch?
>
> Marc,
> Is there a step-by-step way of integrating this, so we can test in  
> modules?

there is a README-IPV6.txt file in the v6 branch which attempts to  
discuss that.
- right now, I have separate netsock, rtp and udptl routines/ 
objects/....  then chan_sip is modified to use the new routines.
- netsock, rtp and udptl new routines have a different namespace so  
the non-modified channels are not using that new code in any form.
- the new routines are IP version independent: they handle both v4  
and v6, which is the right way to convert an application to v6: you  
make it version independent.  (the new namespace adds "vi" to the  
routines names: vi stands for version independent, not for your  
favorite editor ;-))
- therefore, it is structured right now to handle merging  
"incrementally": channel by channel.

- still, it is pretty significant changes in the code...

> The socket issue certainly seems to be a separate module, and then we
> could go step by step and review/merge.
>
> stun is available in the google talk/jingle channel today, but not  
> in SIP yet.

will look. but as you know, there is a need to handle NAT and IPv6 in  
a coherent way, so looking at the overall picture is the right thing  
to do, before it becomes tooo messy.

Marc.

>
> /O_______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> AstriDevCon-2007 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/astridevcon-2007

-----
IPv6 book: Migrating to IPv6, Wiley, 2006, http://www.ipv6book.ca