[Serdev] Concept for a SIP cluster implementation

[Greger V. Teigre]

>> >It also won't have an impact on scenarios where no Path is used, so...
>>
>> Ah! I see, I didn't get that you wanted the code directly into head,
>> without going into experimental.  That I will not have an opinion on :-)
>> But AFAI can see, implementing Path is something that would strengthen
>> SER's capabilities as long as the RFC (and 3GPP) specs are followed.
>
>  Following 3GPP does not make much sense to me. In my opinion the 3GPP
>  architecture does not solve any issues of real-world SIP setups, it
>  can only work in walled gardens. In my opinion we should only make it
>  work in the public internet where the adminstrators of SIP servers do
>  not control the network. This is the most challenging environment.
>  Everything else (such as walled gardens of mobile operators) is
>  easier.

I won't take a stand in the 3GPP walled garden vs. "real-word" SIP setups 
;-)
I just want to make sure that the path module keeps it's original purpose 
when moving the functionality.  If the functionality is already there (I 
don't know, I'm not a 3GPP expert), it should be straight-forward to keep 
it. That's why I suggested a chat with Dragos.
g-)