Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)

"Cullen Jennings (fluffy)" <> Wed, 03 July 2013 19:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6255F21F9D4E for <>; Wed, 3 Jul 2013 12:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.487
X-Spam-Status: No, score=-110.487 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id koG3KDcWJRB0 for <>; Wed, 3 Jul 2013 12:16:35 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id B35A921F9D2D for <>; Wed, 3 Jul 2013 12:16:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=768; q=dns/txt; s=iport; t=1372878995; x=1374088595; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=pfuWdSE7B+ybsq9iJPQlXUVnfCaVyWRP4zFWznsacY0=; b=nCrAmUE+uLOJJpUCZD+TPqJZdqVEK3tvJUgjcH0Xd+oinOs+rtuPe95U EEIYa/x0xmofwUy/gu6ROA9RA87dUbOIc/9d49UboGoM+yCxvRB7IgPQo wWv1kuEkTderSg/w6jcZVF4Sred8ZyLojLD4eCNSY+hdBFjW7dncX171k 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al4FAFh31FGtJV2c/2dsb2JhbABagwl7gkG9doEGFnSCIwEBAQMBeQULAgEIIhkLMiUCBA4FCIgBBroijzgCMQeDBGkDiGugI4FYgTmCKA
X-IronPort-AV: E=Sophos;i="4.87,990,1363132800"; d="scan'208";a="230692445"
Received: from ([]) by with ESMTP; 03 Jul 2013 19:16:35 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id r63JGZiI018945 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Jul 2013 19:16:35 GMT
Received: from ([]) by ([]) with mapi id 14.02.0318.004; Wed, 3 Jul 2013 14:16:34 -0500
From: "Cullen Jennings (fluffy)" <>
To: Robin Raymond <>
Thread-Topic: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)
Thread-Index: AQHOdJEmOvnZG+z+f0Kk7cl3DKmS85lNmqUUgAYTtAA=
Date: Wed, 3 Jul 2013 19:16:34 +0000
Message-ID: <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<>" <>
Subject: Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)
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: Wed, 03 Jul 2013 19:16:41 -0000

On Jun 29, 2013, at 8:28 PM, Robin Raymond <> wrote:

> Versus this SDP blob that many of us must parse/mangle/generate from our code if we want to go beyond a basic demo:

My assertion has always been we should avoid any JS app needing to touch the SDP. Every example I have heard of why people are doing (with exception of one) it is ones that there has been discussion of providing an API to do that and/or to fix a bug in browsers. (Just as FYI, the one exception is Kaufrman's use of ICE to put things in what is usual done as a MPLS tunnel. There are probably other common ways to solve that problem). 

I like Peter's idea of trying to capture what are the reason people think they need to look at the SDP.