[SIPForum-techwg] SIPConnect 1.1 - Microsoft proposalandadditional requirements- TCP

[Hadriel Kaplan]

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.
>