Re: [sipcore] Proposal for a new SIP transport (WebSocket)

["Avasarala, Ranjit" <[e-mail]>]

Hi Victor

One comment - the proposal of SIP as a new WebSocket sub protocol is not very clear in ur draft. So you could add an example for it.
E.g.  Sec-WebSocket-Protocol: sip  (is this what you intend to propose?).

Also add a section on how SIP as a WebSocket sub protocol is negotiated as part of client/server handshake procedure.

Thanks

Regards
Ranjit

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Victor Pascual Avila
Sent: Tuesday, November 15, 2011 3:33 PM
To: SIPCORE (Session Initiation Protocol Core) WG
Subject: Re: [sipcore] Proposal for a new SIP transport (WebSocket)

FYI: We're planning to submit a new revision of the draft (addressing
the feedback received so far) during the next couple of weeks

-Victor

On Fri, Oct 28, 2011 at 2:42 PM, Iñaki Baz Castillo <[e-mail]> wrote:
> A draft describing a mechanism for usage of WebSocket protocol as a
> new transport between SIP entities was submitted to rtcweb WG on 13
> Sep 2011. However the discussions on that list seemed to conclude that
> the draft was interesting but outside the scope of rtcweb. Since the
> draft describes a new transport for SIP it makes more sense to propose
> it in SIPCORE WG. Therefore we ask the SIPCORE WG to discuss whether
> the proposed draft could fit well in this WG.
>
> There are some aspects of the draft that will be addressed in a new
> revision (as mandating Outbound support given the nature of the
> WebSocket protocol). The first revision of the draft can be found at:
>
> http://datatracker.ietf.org/doc/draft-ibc-rtcweb-sip-websocket/
>
> --------------------------------
> Abstract
>
>   This document specifies a WebSocket subprotocol for a new transport
>  in SIP (Session Initiation Protocol).  The WebSocket protocol enables
>  two-way realtime communication between clients (typically web-based
>  applications) and servers.  The main goal of this specification is to
>  integrate the SIP protocol within web
>  applications.
> ------------------------------
>
>
> This new SIP transport could fit well within a RTCweb architecture
> (since RTCweb does not mandate the in-the-wire protocol nor the format
> of the messages exchanged between RTCweb clients and servers). This is
> just a use case, a future revision of the draft could incorporate more
> use cases.
>
>
> A presentation of the proposed specification (including a video with
> running code) can be found at:
>
> http://sip-on-the-web.aliax.net/
>
> -------------------------------
> Introduction
>
>  The aim of this presentation is to show the SIP protocol working
>  within a web browser and interoperating with any SIP network.
>
>   After some slides describing the used technology there is a
>  signaling flowchart and a video showing a real implementation.
> -------------------------------
>
>
> Please let us know whether this draft would fit well in SIPCORE or may
> be we would do better by proposing it in DISPATCH.
>
> Thanks a lot.
>
>
> --
> Iñaki Baz Castillo
> <[e-mail]>
> _______________________________________________
> sipcore mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/sipcore
_______________________________________________
sipcore mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/sipcore