Re: [rtcweb] XSF Jingle Special Interest Group.

Iñaki Baz Castillo <> Mon, 22 July 2013 15:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6650611E8113 for <>; Mon, 22 Jul 2013 08:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JnAtvI1P0Jda for <>; Mon, 22 Jul 2013 08:55:25 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D9BBB11E80EF for <>; Mon, 22 Jul 2013 08:55:21 -0700 (PDT)
Received: by with SMTP id bq6so883215qab.18 for <>; Mon, 22 Jul 2013 08:55:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=IcXN3skJLTWZTHMpoZhv869xvUwIdlddARQUv3Eb+/A=; b=I30WtN7XKK2ss9tDqYGFtbVL0+GJI62TSn6HnOVDCYj9Ig47Wdkb/4/632cl6VMSdd qYtpYE95WTx2jinwq2KocwhBwwdOSg6teWOKiXE+VjyauP5TO9f94oCDp062OyfSeCCE GxMWfrUe2nVUE1+W4pPdrbI3AZ0DE8djHBxcdFcdLR+Ilbou9ap8kRmZnxAhN/dkfabl JJFV2LsbDCC0qtBw7n1YmKisJ2znYrLYooLOiNIbGA7zL5UQCqM6rYkhq53wZDc3/m/e fjK5EO8ktnY6311+6p3cI8+Na3anMomCyWqepwxa/0wtuNUSMFFNeel1C6jkLt0HvVvS V1nA==
X-Received: by with SMTP id cb15mr34885234qab.48.1374508519821; Mon, 22 Jul 2013 08:55:19 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Mon, 22 Jul 2013 08:54:59 -0700 (PDT)
In-Reply-To: <>
References: <> <> <>
From: Iñaki Baz Castillo <>
Date: Mon, 22 Jul 2013 17:54:59 +0200
Message-ID: <>
To: Ralph Meijer <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlOHT7Oa3EyOcMDgVK9/3MzMrbik7UaRoi4hoPB3NXKYY42rFnyeuK6m/wZnwKDUklqtl8F
Cc:, XMPP Jingle <>, "" <>, "" <>
Subject: Re: [rtcweb] XSF Jingle Special Interest Group.
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 22 Jul 2013 15:55:30 -0000

2013/7/22 Ralph Meijer <>:
> Hi Iñaki,
> 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 that
> 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 it
> 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ñaki Baz Castillo