W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 22 Jul 2013 17:14:36 +0200
Message-ID: <CALiegfk1kUuezLSOqfLRnFC7gNWXgjerv9Q_mPKrR01zp3mdqQ@mail.gmail.com>
To: Ralph Meijer <ralphm@ik.nu>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, stox@ietf.org, XMPP Jingle <jingle@xmpp.org>
Great. First thing you should complain about is the fact that current
WebRTC specification makes unfeasible for a browser to use SDP-XML as
defined by XEP-0167. So if you have a SIP server you will be able to
directly connect from the browser, but if you have a Jingle server you
will need a gateway.

2013/7/22 Ralph Meijer <ralphm@ik.nu>:
> Hi all,
>
> I would like to inform the group of the recent formation [1] of the Jingle
> Special Interest Group (SIG) at the XMPP Standards Foundation (XSF). The
> recent increase of activity in the WebRTC and rtcweb working groups and
> related high-profile product developments and announcements were reasons for
> the XMPP Council to decide to concentrate efforts around Jingle in a SIG.
>
> Jingle [2] is a general framework for managing media sessions between XMPP
> Sessions, including, but not limited to, audio/video streams, file transfer
> and application sharing. There are several documents describing applications
> of Jingle and the used transports, most linked from the overall framework
> specification [3].
>
> The specification of Jingle RTP Sessions [4], most relevant to these working
> groups, defines a Jingle application type for negotiating RTP sessions. It
> has been designed such that interoperability with SIP-based systems is
> possible. This includes mapping negotiation parameters to and from SDP,
> while remaining a signaling protocol in its own right (not merely SDP in
> angle brackets).
>
> The following work items were defined in the kick-off meeting last
> Wednesday, July 17 [5, raw log 6]:
>
>  * Re-examining the state of the various Jingle proposals.
>  * Polishing Jingle File Transfer.
>  * Updating the SDP mapping in [4], including BUNDLE and Trickle-ICE
>    improvements.
>  * Documenting and communicating the value proposition of Jingle/XMPP.
>
> This SIG already includes a number of people participating in discussions on
> the WebRTC and rtcweb mailing lists and is lead by Dave Cridland (chair),
> Philipp Hancke, Lance Stout and myself. It is open to anyone, and we are
> looking forward to cooperate with the WebRTC and rtcweb working groups to
> improve both WebRTC and Jingle.
>
> The discussion venues are the Jingle mailing list [7] and the Jingle XMPP
> multi-user chat room [8]. Our next meeting in the MUC room is Wednesday July
> 24 at 15:30 UTC. This group's experience and input would be highly
> appreciated, and your participation in both the meeting and the on-going
> discussion would be most welcome.
>
> Thanks,
>
> Ralph Meijer
>
> [1] <http://mail.jabber.org/pipermail/jingle/2013-June/001933.html>
> [2] <http://xmpp.org/about-xmpp/technology-overview/jingle/>
> [3] <http://xmpp.org/extensions/xep-0166.html>
> [4] <http://xmpp.org/extensions/xep-0167.html>
> [5] <http://mail.jabber.org/pipermail/jingle/2013-July/001956.html>
> [6] <http://logs.xmpp.org/jingle/130717/>
> [7] <http://mail.jabber.org/mailman/listinfo/jingle>
> [8] <xmpp:jingle@muc.xmpp.org?join>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb



-- 
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Monday, 22 July 2013 15:15:28 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:35 UTC