[SIP] SCTP as transport for SIP

"Fairlie-Cuninghame, Robert" <rfairlie@nuera.com> Thu, 08 March 2001 14:45 UTC

Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA27967 for <sip-archive@odin.ietf.org>; Thu, 8 Mar 2001 09:45:14 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 2FBCB44368; Thu, 8 Mar 2001 09:45:10 -0500 (EST)
Delivered-To: sip@lists.bell-labs.com
Received: from exchange1.nuera.com (igate.nuera.com [204.216.240.98]) by lists.bell-labs.com (Postfix) with ESMTP id 865FF44367 for <sip@lists.bell-labs.com>; Thu, 8 Mar 2001 09:44:17 -0500 (EST)
Received: by exchange1.nuera.com with Internet Mail Service (5.5.2650.21) id <GN8V18KP>; Thu, 8 Mar 2001 06:43:29 -0800
Message-ID: <E79883AEA37FD411A58C00508BAC5F4B7102D3@exchange1.nuera.com>
From: "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>
To: "'schulzrinne@cs.columbia.edu'" <schulzrinne@cs.columbia.edu>, "'jdrosen@dynamicsoft.com'" <jdrosen@dynamicsoft.com>
Cc: "'sip@lists.bell-labs.com'" <sip@lists.bell-labs.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0A7DE.23C78330"
Subject: [SIP] SCTP as transport for SIP
Sender: sip-admin@lists.bell-labs.com
Errors-To: sip-admin@lists.bell-labs.com
X-BeenThere: sip@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:sip-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:sip@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/sip>, <mailto:sip-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SIP Mailing List <sip.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/sip>, <mailto:sip-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/sip/
Date: Thu, 08 Mar 2001 06:43:29 -0800

Hi there,

I have a query with your "SCTP as transport for SIP" draft
(http://www.cs.columbia.edu/~hgs/sip/drafts/draft-rosenberg-sip-sctp-00.txt)
,

For instance:

             If the transport is SCTP, the entity SHOULD look for
             exising open SCTP connections to the given IP address and
             port. The number of streams within the connection, and the
             mapping of SIP requests to streams, are at the discretion
             of the entity. However, it is RECOMMENDED that some kind of
             stateless hash be used so that requests for the same call
             all be mapped into the same stream. If no SCTP connection
             is established, one is opened and the request sent over it.

The draft says that the mapping of the SIP requests to streams is up to the
entity. How can this be? A SIP server would normally be only listening to
particular streams to receive SIP requests, the other streams may be unused
or used for some other purpose. The "lookup method" (SRV or whatever) must
surely specify an IP address, SCTP port and stream number to locate the SIP
service via SCTP?

What is more, due to the unidirectional nature of the SCTP streams, surely
the reverse stream must be specified to the endpoint in the Via (or
elsewhere). [I don't think a reverse DNS SRV lookup could be guaranteed -
the UAC may not even have a hostname.]

Does this not mean that we need to add an SCTP stream id URL parameter ?

For instance, some lookup yields a SIP URL (ie Request-URI) of 
sip:host.company.com;transport=sctp;sctp-stream=13 (or something else -
maybe "transport=sctp-13")

and then the Via: would similarly need to specify the reverse stream (which
may very easily be to a different stream or even to a different SCTP port).

I think there are quite a few consideration that SCTP raises above and
beyond other transport protocols (even when you ignore the issues related to
SCTP association establishment). I'll be interested to hear your opinions.

Regards, 

Robert.