Re: [rtcweb] Revision of bundling proposal/analysis

Randell Jesup <randell-ietf@jesup.org> Sun, 24 March 2013 05:18 UTC

Return-Path: <randell-ietf@jesup.org>
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 77FB321F8C5D for <rtcweb@ietfa.amsl.com>; Sat, 23 Mar 2013 22:18:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 385Hb4PT0pmb for <rtcweb@ietfa.amsl.com>; Sat, 23 Mar 2013 22:18:53 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 0B02F21F861B for <rtcweb@ietf.org>; Sat, 23 Mar 2013 22:18:52 -0700 (PDT)
Received: from pool-98-111-140-34.phlapa.fios.verizon.net ([98.111.140.34]:1250 helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <randell-ietf@jesup.org>) id 1UJdKV-0009mg-M4 for rtcweb@ietf.org; Sun, 24 Mar 2013 00:18:52 -0500
Message-ID: <514E8C6A.6040304@jesup.org>
Date: Sun, 24 Mar 2013 01:17:30 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <201303111600.r2BG0K16222765@shell01.TheWorld.com>
In-Reply-To: <201303111600.r2BG0K16222765@shell01.TheWorld.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
Subject: Re: [rtcweb] Revision of bundling proposal/analysis
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: Sun, 24 Mar 2013 05:18:53 -0000

On 3/11/2013 12:00 PM, Dale R. Worley wrote:
> I've just submitted draft-worley-sdp-bundle-05, which is an SDP
> bundling proposal along with a bunch of analysis and comparison to
> other bundling proposals.
>
> The biggest change is adding a detailed analysis of alternatives for
> the address/port combinations to be used when offering constituent
> media descriptions (m= lines) so as to get all the mechanics to work
> as we'd like.  It is from this analysis I noticed that we don't have a
> good method to *answer* a constituent media description.  (I've sent
> e-mail about that to MMUSIC.)
>
> I've added an example containing two SCTP media descriptions, which
> will be a common case on WebRTC.

Actually, we nominally support only a single DataChannel connection per 
PeerConnection (at the W3 level), so you'll never have the example given 
in WebRTC.

Using BUNDLE outside of WebRTC would change that.

I also was surprised at encapsulating SRTP packets *inside* DTLS (and 
DTLS packets *inside* DTLS).

-- 
Randell Jesup
randell-ietf@jesup.org