optionality of SIP over websocket support
- From: "Lewis, Keith" <
- To: jsr359-experts <
- Subject: optionality of SIP over websocket support
- Date: Fri, 5 Apr 2013 09:52:18 +0100
It will be important to indicate which of the new material in the JSR359 spec is mandatory for a SIP container to support. In particular we should make it clear that support for Sip Outbound and Sip Over WebSockets is optional.
I suggest that we should add the following text to section 13.
Support for use of WebSocket transports by a SIP container is optional. Containers with this capability must include the string "RFCxxx" in the list of supported rfcs available to applications via the ServletContext. see 3.3 RFCs supported.
Once SIP over WebSockets becomes an official RFC we can substitute the appropriate number in the text above.
Similar text can be included in the section on SIP outbound.
The text above is modelled on what is said in 5.7.1 regarding support for Reliable Provisional Responses.
Regarding the client capabilities specified in draft-ietf-sipcore-sip-websocket-08. I understand that this is seen as lower priority and so is not currently in scope. On the other hand it does not look difficult to implement. I suggest that containers that support the RFC should provide both the client and server functions. This makes it easier for applications to interpret the javax.servlet.sip.supportedRfcs parameter in the ServletContext - inclusion of the RFC means support for all parts of the spec. I note that we chose to implement both sides of the Sip Outbound spec, given that they will often be used together it seems strange not to also do both sides of Sip over WebSockets.
Note: The information contained in this message may be privileged and confidential
and protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Thrupoint, Inc.