Re: [Stox] [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
Emil Ivov <emcho@jitsi.org> Mon, 22 July 2013 16:28 UTC
Return-Path: <emil@sip-communicator.org>
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 5245321F9E88 for <stox@ietfa.amsl.com>; Mon, 22 Jul 2013 09:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level:
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 Pe+8kutJ8lhE for <stox@ietfa.amsl.com>; Mon, 22 Jul 2013 09:27:30 -0700 (PDT)
Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) by ietfa.amsl.com (Postfix) with ESMTP id C85D811E8127 for <stox@ietf.org>; Mon, 22 Jul 2013 09:26:48 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id a12so6299894wgh.16 for <stox@ietf.org>; Mon, 22 Jul 2013 09:26:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=sBLwGr2RRxUfZuqqDAVE8oOAeHqmr63o16Hab11zz+U=; b=BevPedp+MT/zWkZBmtPnCHmTYCjLLLNg72WpDObmnNmsyIAiB5IbD6FvQdpX0BuJov oZtONJFgpfV1Q9o+6mUx0cWHoIKw6iAq5UbSEinLg3BOLDRfOe49Ogoxshv3TNW1b9YB U4ohD1UV2G4yFo52RVGnPCChS8OLfi57tHq5hrd/2rygdUXkhfkp9kAbZes0LSELe+pU ABQEmO8lxQYQN9y5IixkeMViLDGRqin30o9gEr9xo+v78MliAkRcZzHYpL3ZMrHjRNd4 rIQQOE/vnNgN5b8ap1oSrHZGFUiTitFbWqcOrJXgpQowj8eFVvV5GwzgyWAXBjRDpPA6 ck5A==
X-Received: by 10.180.38.37 with SMTP id d5mr26810867wik.37.1374510369217; Mon, 22 Jul 2013 09:26:09 -0700 (PDT)
Received: from camionet.local ([2a01:e35:2e2c:f600:cc7b:5fa5:6ef9:f634]) by mx.google.com with ESMTPSA id l2sm5763200wif.8.2013.07.22.09.26.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Jul 2013 09:26:08 -0700 (PDT)
Message-ID: <51ED5D1E.1020000@jitsi.org>
Date: Mon, 22 Jul 2013 18:26:06 +0200
From: Emil Ivov <emcho@jitsi.org>
Organization: Jitsi
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Iñaki Baz Castillo <ibc@aliax.net>
References: <51ED4A45.9000703@ik.nu> <CALiegfk1kUuezLSOqfLRnFC7gNWXgjerv9Q_mPKrR01zp3mdqQ@mail.gmail.com> <51ED4FA2.8070603@gmail.com> <CALiegf=FR9sw3Pt=4iRkeu9S3zy3tpVt+5s+tu_n+gWjS8b8Wg@mail.gmail.com>
In-Reply-To: <CALiegf=FR9sw3Pt=4iRkeu9S3zy3tpVt+5s+tu_n+gWjS8b8Wg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQk6wztnDm5yXzaeYO7Sda28BbJ3MCSBBfNvZqGmkYKhzWKgzjYanVIfGpebuz/gbuQnXsU/
Cc: Daniel-Constantin Mierla <miconda@gmail.com>, stox <stox@ietf.org>, XMPP Jingle <jingle@xmpp.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>, Ralph Meijer <ralphm@ik.nu>
Subject: Re: [Stox] [rtcweb] 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 16:28:07 -0000
On 22.07.13, 17:44, Iñaki Baz Castillo wrote: > 2013/7/22 Daniel-Constantin Mierla <miconda@gmail.com>: >> On 7/22/13 5:14 PM, Iñaki Baz Castillo wrote: >>> >>> 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. >> >> You are obviously misinforming here. SIP is the signaling protocol and a SIP >> server has really little to deal with SDP -- I'm sure you know that. > > I was talking about a SIP device also implementing WebRTC in the media > plane. Current WebRTC spec mandates plain-SDP usage in the wire to > signal your media description and transport/ICE information to the > peer. I don't think this is true. You can very well translate the SDP to Jingle in the browser and then only send XML on the wire. I completely agree that this would be a pain, but there is nothing that "mandates" against it. Emil -- https://jitsi.org
- [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