Re: [rtcweb] No Plan

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Fri, 31 May 2013 19:20 UTC

Return-Path: <fluffy@cisco.com>
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 16AF521F898B for <rtcweb@ietfa.amsl.com>; Fri, 31 May 2013 12:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 5+T6EH1cc7kA for <rtcweb@ietfa.amsl.com>; Fri, 31 May 2013 12:20:32 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 6E6C121F894E for <rtcweb@ietf.org>; Fri, 31 May 2013 12:20:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1108; q=dns/txt; s=iport; t=1370028032; x=1371237632; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=TtG74m1hJDDMtGdCXvXA/AYIvG+nvFuosfq6g7a+jBo=; b=mksTymDIhEAPEc9wla0FVoA/4usECbLK69lNN98uWviroJ64R0SEJXeo CrClLABFhnAKWBMim8L5K5yuD9qGaiMVuUdpNAz+uTrTh0p1wmexxj5Rw EPWmBlOxyE6R+AUrs6GqklHFyH2ry9wVgdckH2/CHlof3jzX12V8HKY09 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlIFAKz2qFGtJXHA/2dsb2JhbABZgwm/HoEDFnSCIwEBAQMBeQULAgEIDgoKJDIlAgQOBQiHfwa6MI5uAjEHgnZhA4hooBaDD4In
X-IronPort-AV: E=Sophos;i="4.87,780,1363132800"; d="scan'208";a="217377243"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-6.cisco.com with ESMTP; 31 May 2013 19:20:31 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r4VJKVqp002947 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 May 2013 19:20:31 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.36]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Fri, 31 May 2013 14:20:31 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Emil Ivov <emcho@jitsi.org>
Thread-Topic: [rtcweb] No Plan
Thread-Index: AQHOXiwEjuCu1hdg9k2txPBXuLNWSpkf/00A
Date: Fri, 31 May 2013 19:19:29 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB11352940B@xmb-aln-x02.cisco.com>
References: <51A65017.4090502@jitsi.org> <51A65DB8.9060702@alum.mit.edu> <51A880A7.7010908@jitsi.org> <C5E08FE080ACFD4DAE31E4BDBF944EB113528171@xmb-aln-x02.cisco.com> <51A8EAB7.8080206@jitsi.org>
In-Reply-To: <51A8EAB7.8080206@jitsi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <904A9D00A18F9B469C2D76E78682735C@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] 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: Fri, 31 May 2013 19:20:38 -0000

On May 31, 2013, at 12:23 PM, Emil Ivov <emcho@jitsi.org>
 wrote:

> On 31.05.13, 17:33, Cullen Jennings (fluffy) wrote:
>> 
>> On May 31, 2013, at 4:51 AM, Emil Ivov <emcho@jitsi.org> wrote:
>> 
>>> Having extra m= lines, particularly when using BUNDLE, is in many
>>> ways just extra signalling. If you'd like for that signalling to be
>>> in SDP, I don't see any problem with it. However it would be best
>>> for this extra layer of SDP signalling to appear at either the
>>> application layer or in a signalling gateway (that is going to be
>>> there anyway).
>>> 
>>> Does this make sense?
>> 
>> No. That does no make sense.
>> 
>> Can you please provide an specific example of what you think the SDP
>> would look like going across the JS API in the browser and then what
>> the SDP at the applications of signaling layer would look like and
>> how this would work with CLUE.
> 
> Certainly. Could you please post the SDP that you would like to see translated in a way that's compatible with "No Plan"?
> 
> Emil


We can start with the SDP in plan A