Re: [rtcweb] Translating Plan A into No Plan (Was: No Plan)

Iñaki Baz Castillo <ibc@aliax.net> Mon, 03 June 2013 18:26 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26ED921F91B8 for <rtcweb@ietfa.amsl.com>; Mon, 3 Jun 2013 11:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
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 FnlfuOFxX3ny for <rtcweb@ietfa.amsl.com>; Mon, 3 Jun 2013 11:26:34 -0700 (PDT)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD6621F8667 for <rtcweb@ietf.org>; Mon, 3 Jun 2013 11:26:34 -0700 (PDT)
Received: by mail-qc0-f170.google.com with SMTP id s11so2385106qcw.15 for <rtcweb@ietf.org>; Mon, 03 Jun 2013 11:26:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; 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=5ZI0FCfZF8QuRgc9TY0femXepTtKDmgjHwwcmT1yxcA=; b=lvSD45Xjp16w2Y7mMkhOger9HjAajgCyZ9EW3ND5W/LGgpvS2mBFfaHedSidhL1x56 Yc21HfHBh9P6C78Sg7HcoZ0s21uyYseyK6DfbdvMAWEBsKCR8S78roLK8hXFMEEYkXqq JzIT8qQrt2FbSfWCGKwA7fstzj+AsF5+9Jzq0YQL7V8La0kRG+Tw0/hd7dY8HGSg6aI1 w0ogOOyu/VrpYo9pqOt0Fgwqc3wgGqIfZ0BfQ2tMgTJv6yZ4ATSFjCLmQCSZ2bGLPdVn BpvUEd5nti3FDURAmqG804tazzT5GL3wUV4vhiVYZpjYoULkyksN+ZcGVnyE3GCU7RSR Zjwg==
X-Received: by 10.224.4.74 with SMTP id 10mr20519035qaq.38.1370283993825; Mon, 03 Jun 2013 11:26:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.26.103 with HTTP; Mon, 3 Jun 2013 11:26:13 -0700 (PDT)
In-Reply-To: <51ACD224.8080100@jitsi.org>
References: <51A65017.4090502@jitsi.org> <51A65DB8.9060702@alum.mit.edu> <51A880A7.7010908@jitsi.org> <C5E08FE080ACFD4DAE31E4BDBF944EB113528171@xmb-aln-x02.cisco.com> <51A8EAB7.8080206@jitsi.org> <C5E08FE080ACFD4DAE31E4BDBF944EB11352940B@xmb-aln-x02.cisco.com> <51ACD224.8080100@jitsi.org>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Mon, 3 Jun 2013 20:26:13 +0200
Message-ID: <CALiegfnYkVPfuXsd36tOHC8vOC7kn9cXd9F5nya+LuCVc=J7yw@mail.gmail.com>
To: Emil Ivov <emcho@jitsi.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkEsgJGPqTkLPI6HE3XRVR+kp7bAQ3BdG+ViTniYpKkuCvlu5yuykIKwq56b3N8pzRL2EEI
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Translating Plan A into No Plan (Was: No Plan)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2013 18:26:53 -0000

2013/6/3 Emil Ivov <emcho@jitsi.org>rg>:
> If you need to talk to a Plan A endpoint you basically have the following
> options:
>
> 1. You use JavaScript to prettify the "No Plan" SDP and turn it into
> something that looks like "Plan A". Not my favourite option, but I am sure
> some would like to use it. Maybe vendors of Plan A equipment would even
> distribute JS libs that do this. It would basically all come down to
> generating one ssrc attribute and two additional m=lines and appending this
> to the existing SDP string.

HI, I would really prefer something that does not require SDP mangling
via JS. That is dangerous. SDP is too much flexible and we never know
how a SDP will look, so artificial mangling at JS level seems
unfeasible IMHO.


--
Iñaki Baz Castillo
<ibc@aliax.net>