MIME-Version: 1.0
In-Reply-To: <51ED53E6.10400@ik.nu>
References: <51ED4A45.9000703@ik.nu>
 <CALiegfk1kUuezLSOqfLRnFC7gNWXgjerv9Q_mPKrR01zp3mdqQ@mail.gmail.com>
 <51ED53E6.10400@ik.nu>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Mon, 22 Jul 2013 17:54:59 +0200
Message-ID: <CALiegfn0Ye-SmbiVyfB=_Viy0KNaJ=keOuM9mL34ui5hNOhMhw@mail.gmail.com>
To: Ralph Meijer <ralphm@ik.nu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: stox@ietf.org, XMPP Jingle <jingle@xmpp.org>,
 "rtcweb@ietf.org" <rtcweb@ietf.org>,
 "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] XSF Jingle Special Interest Group.
Precedence: list

2013/7/22 Ralph Meijer <ralphm@ik.nu>:
> Hi I=C3=B1aki,
>
> I have been following the recent discussions for a while now, and think I
> understand the various stand points, including yours.
>
> As I mentioned in my announcement, mapping SDP to Jingle's negotiation
> parameters is indeed one of the concerns we are going to look into.
> Philipp's work on his WebRTC plugin for Strophe.js [1], which uses Jingle
> signalling, has shown that it indeed takes quite some effort to map and
> mangle SDP to get things going. The spreadsheet questionnaire that Peter
> Thatcher asked people to fill in (thanks!) also has several comments to t=
hat
> effect. During our discussions on the Jingle mailing list and the meeting
> last week, more of such comments were made.
>
> I want to stress, again, that Jingle's negotiation parameters should not =
be
> referred to as a flavor of SDP expressed in XML. This is misleading, as i=
t
> is not managed by MMUSIC, and actually weakens your point of not wanting =
SDP
> as an API surface. I can understand that looking at the current
> specification could give that impression, though. The Jingle examples are
> currently interleaved by SDP examples to show the mapping, and we are
> looking into making the distinction clearer, maybe even as a document
> separate from this one.

Thanks for the clarification. So Jingle's session description is not
just a plain-to-XML mapping of a common SDP. Good to know.

However, wouldn't you prefer to have a pure JS Object with all the
media and transport information you require to build your Jingle
XML-SDP instead of having to parse a plain SDP string blob?

Thanks a lot.


--
I=C3=B1aki Baz Castillo
<ibc@aliax.net>