Skip to main content

Re: Meeting Notes

  • From: "Lewis, Keith" < >
  • To: jsr359-experts < >
  • Subject: Re: Meeting Notes
  • Date: Thu, 4 Apr 2013 11:48:19 +0100
  • List-id: <>


this is a good summary of our discussion except for the second bullet.
  • The further comment on this, was, can this implicit association usecases be handle in a generic way for other transports too.

Perhaps the following wording would be clearer.

  • Some members suggested that the use cases described in 13.2.1 could be implemented using generic mechanisms that are independent of the transport. They therefore wondered whether the getInitiatingWebSession() method was really needed.

On Thu, Apr 4, 2013 at 10:49 AM, Binod < " target="_blank"> > wrote:
Attendees:   Dan, Nitzan, Jean, Eric, George, Keith, Tom, Binod (Sorry, if I missed anyone).

[My phone was a bit bad to listen yesterday. Hope I understood everyone correctly].

- We discussed sip/websocket draft. Here are the comments and decisions.
    o The association between websession and sip messages are not bound to life-cycle
       of any sessions. It is simply returning the http session of the converged web application
       just like returning the URL with which the connection was established.
    o The further comment on this, was, can this implicit association usecases be handled
       in a generic way for other transports too.
    o Then there was a question of whether an application written for websocket transport
       can be portably switched to another transport or not. That switched our discussion to
       creating initial requests from a SIP application. The rfc draft does not mandate the use
       of sip outbound spec for identifying the ws connection but mention it only as one
       possible way. So, for those applications that does not use sip outbound need to have a
       way to specify the websocket connection to send messages. Binod took an action item
       to discuss this with sip/websocket rfc editor.
    o For EDR, this section will be restructured to explain the usage of Flow interfaces. It will
       then indicate that this require the feedback from the community.
    o Then the discussion was about closing the websocket connection  from the application.
       Again, the main concern was, wouldn't other transports face the same usecases. Jean
       mentioned that mobicents community had requests for the same for TCP transport
       as well. He will send the details of that to the group. We will again request feedback
       from community on this.
    o On the application composition, the new TargetedRequestType may be counter productive
       since that stops sip/ws from using any other kind of request targeting. We will remove that.
  - Jean will update the outbound draft with the comments. We will include that in the EDR.
    However, we will leave the application composition on the outbound draft outside of EDR.
  - EDR draft will be frozen by end of next week to allow sufficient time for submitting to JCP.

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.

Meeting Notes

Binod 04/04/2013

Re: Meeting Notes

Lewis, Keith 04/04/2013

<Possible follow-up(s)>

Meeting Notes

Binod 04/25/2013
Please Confirm