[Stox] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
Ralph Meijer <ralphm@ik.nu> Mon, 22 July 2013 15:06 UTC
Return-Path: <ralphm@ik.nu>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5E7E21E80B6; Mon, 22 Jul 2013 08:06:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hB--a1FzGdpT; Mon, 22 Jul 2013 08:06:08 -0700 (PDT)
Received: from mag.ik.nu (mag.ik.nu [IPv6:2001:16f8:4::61]) by ietfa.amsl.com (Postfix) with ESMTP id 7341B11E80F2; Mon, 22 Jul 2013 08:06:08 -0700 (PDT)
Received: from mag.ik.nu (localhost [127.0.0.1]) by mag.ik.nu (Postfix) with ESMTP id D664FA1047; Mon, 22 Jul 2013 17:06:05 +0200 (CEST)
X-Virus-Scanned: amavisd-new at ik.nu
Received: from mag.ik.nu ([127.0.0.1]) by mag.ik.nu (mag.ik.nu [127.0.0.1]) (amavisd-new, port 10024) with SMTP id IcMi5T779wHw; Mon, 22 Jul 2013 17:05:43 +0200 (CEST)
Received: from [192.168.3.215] (s53751670.adsl.online.nl [83.117.22.112]) by mag.ik.nu (Postfix) with ESMTPSA id E3E6DA1021; Mon, 22 Jul 2013 17:05:42 +0200 (CEST)
Message-ID: <51ED4A45.9000703@ik.nu>
Date: Mon, 22 Jul 2013 17:05:41 +0200
From: Ralph Meijer <ralphm@ik.nu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: public-webrtc@w3.org, rtcweb@ietf.org
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: stox@ietf.org, XMPP Jingle <jingle@xmpp.org>
Subject: [Stox] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jul 2013 15:06:13 -0000
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>
- [Stox] Proposed message to send to the IETF rtcwe… Ralph Meijer
- [Stox] XSF Jingle Special Interest Group. Ralph Meijer
- Re: [Stox] [rtcweb] Proposed message to send to t… Iñaki Baz Castillo
- Re: [Stox] [rtcweb] Proposed message to send to t… Iñaki Baz Castillo
- Re: [Stox] XSF Jingle Special Interest Group. Iñaki Baz Castillo
- Re: [Stox] [rtcweb] Proposed message to send to t… Daniel-Constantin Mierla
- Re: [Stox] [rtcweb] Proposed message to send to t… Daniel-Constantin Mierla
- Re: [Stox] [rtcweb] Proposed message to send to t… Emil Ivov
- Re: [Stox] [rtcweb] Proposed message to send to t… tim panton
- Re: [Stox] Proposed message to send to the IETF r… Philipp Hancke