[SIPForum-techwg] TCP vs. UDP (actually, SIPconnect does *not* change SIP)

[Eric Burger]

[as a participant]
UDP vs. TCP: SIPconnect can safely mandate *only* TCP.  If a device is  
SIP (RFC 3261) compliant, it will support UDP, because RFC 3261  
requires UDP support.  However, SIPconnect can feel free to MANDATE  
TCP, as TCP support is a feature of SIP (RFC 3261).

A device manufacturer will look stupid if they say they are SIPconnect  
compliant but not SIP compliant. Conversely, SIPconnect testing will  
be a factor of two easier if we do not have to test both TCP and UDP  
scenarios.

Just a thought.


On May 16, 2008, at 1:53 PM, Hadriel Kaplan wrote:

>
> Actually I think we need to do both, to some degree.  There *are*  
> interop issues in "existing practice", because there are no common  
> profiles documented in any standard I know of which are specific  
> enough to avoid some of the interop issues.  Today that means a lot  
> of configuration may be needed between the service provider and  
> enterprise, and testing, which is delaying bring-up quite a bit.   
> Even for the SIP-Connect 1.0, we've found different "interpretations".
>
> And ultimately we'll want SIP requests from a SIP-Connect 1.1  
> interface to be successfully routable everywhere.  That won't impact  
> UDP vs. TCP obviously, but for example if someone were to say "we  
> should support S/MIME", I think we'd have to take existing practice  
> into account. ;)
>
> BTW, we should actually specify some details about TCP usage,  
> because even for that there is a disparity in implementations for  
> some details. (e.g., connect-reuse behavior, keep-alive mechanism,  
> failure handling)
>
> -hadriel
>
>> -----Original Message-----
>> From: techwg-bounces at sipforum.org [mailto:techwg- 
>> bounces at sipforum.org] On
>> Behalf Of Francois Audet
>>
>> Again, our goal is not to document existing practice. There is no  
>> point
>> in doing this.
>>
>> There are a number of well-known reasons why we should be encouraging
>> people to use
>> TCP.
>>
>> TCP cannot be a MAY.
>>
>
> _______________________________________________
> techwg mailing list
> Send mail to: techwg at sipforum.org
> Unsubscribe or edit options at:  http://sipforum.org/mailman/listinfo/techwg