Re: [rtcweb] No Plan

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Fri, 31 May 2013 14:34 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 0F6A721F92E3 for <rtcweb@ietfa.amsl.com>; Fri, 31 May 2013 07:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.466
X-Spam-Level:
X-Spam-Status: No, score=-110.466 tagged_above=-999 required=5 tests=[AWL=0.133, 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 oT5Zw8aFiNgF for <rtcweb@ietfa.amsl.com>; Fri, 31 May 2013 07:34:34 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 570CC21F918C for <rtcweb@ietf.org>; Fri, 31 May 2013 07:34:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=747; q=dns/txt; s=iport; t=1370010874; x=1371220474; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ss2wWZ9VDQNM9Xp6htNOUJIC94XijrQQ61/8rdN/cGQ=; b=BLHaqB8RFhx34lWNY9ayeDNbf1J6ViURXxOCCgSKJfRpx3xYWOAv1Pb4 lD9ogXLSpHGHaib23Sr+deplrHzp3oqdKRxsVlZgcL74raxM5cmJZt/GF sFGkZi4qMbE+ndAmAuDpTAgq3NOwACvWpduwh9sW+/SxIYZwxPDSBhL6y k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvQFAOOyqFGtJXG9/2dsb2JhbABagwmDJbt1gQEWdIIjAQEBAwE6PwULAgEIDhQUEDIlAgQOBQiHfwa6Wo5pAjEHgnZhA6h+gw+CJw
X-IronPort-AV: E=Sophos;i="4.87,779,1363132800"; d="scan'208";a="217199648"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-2.cisco.com with ESMTP; 31 May 2013 14:34:34 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r4VEYX8d022927 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 May 2013 14:34:33 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.36]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Fri, 31 May 2013 09:34:33 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Emil Ivov <emcho@jitsi.org>
Thread-Topic: [rtcweb] No Plan
Thread-Index: AQHOXgv3C45MyLwwRkGGzRGA5mvi0A==
Date: Fri, 31 May 2013 14:33:32 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB113528171@xmb-aln-x02.cisco.com>
References: <51A65017.4090502@jitsi.org> <51A65DB8.9060702@alum.mit.edu> <51A880A7.7010908@jitsi.org>
In-Reply-To: <51A880A7.7010908@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="us-ascii"
Content-ID: <583931493C1C48469419A6D15044C06F@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 14:34:45 -0000

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.