[rtcweb] draft-ietf-rtcweb-jsep-08

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 04 November 2014 21:52 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id E01F31A0151 for <rtcweb@ietfa.amsl.com>; Tue, 4 Nov 2014 13:52:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Qv-TBvx-dh2G for <rtcweb@ietfa.amsl.com>; Tue, 4 Nov 2014 13:52:29 -0800 (PST)
Received: from resqmta-po-03v.sys.comcast.net (resqmta-po-03v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:162]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F00C11A014F for <rtcweb@ietf.org>; Tue, 4 Nov 2014 13:52:28 -0800 (PST)
Received: from resomta-po-13v.sys.comcast.net ([]) by resqmta-po-03v.sys.comcast.net with comcast id BZro1p00457bBgG01ZsUSL; Tue, 04 Nov 2014 21:52:28 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([]) by resomta-po-13v.sys.comcast.net with comcast id BZsT1p00L3Ge9ey01ZsUCS; Tue, 04 Nov 2014 21:52:28 +0000
Message-ID: <54594A9B.9090703@alum.mit.edu>
Date: Tue, 04 Nov 2014 16:52:27 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1415137948; bh=PXdHf+vfthRvbrCVLL5R8H4TQC4ZWfq0i23fNpE/5Dg=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=gt1lz0boiFinnTMijIm1dlYh6ZFz3svpDV6NXbLgNGdDZQ7Xs8RJyie7XQWx4aLeS henN2BWtDIqzrU7VseL97zWoIfvxm2sSMjCogvcArB1aXlGtNc0oDebHq2RD+Rurbw D+aHDl5q9wCcChKN4umh4di+gdaVcHKNsiIhyo7P4ANdTmbsgMqs11os9jJUSAu64i qf1zQYtqiptV+1DQFGKbBXixk+LcTWWkd2lAWbk724wgIyRAdQwM7yi9Jzqgd5fUHV 6q3YAoP36zd0ywss90UDwPmbmODzZV4HIuxluh4Ej11Mk8FyOKzdf3pGkfZkEGI7gM 6XduvdwO8JCEg==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/2cKSLYOXTmvfdiGmYnlrJdKa5yA
Subject: [rtcweb] draft-ietf-rtcweb-jsep-08
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 04 Nov 2014 21:52:30 -0000

I have a few related comments on jsep-08:

Section 4.1.1 defines the BUNDLE policy values. It certainly appears 
that when you are using the default "balanced" policy there will be 
*separate* bundle groups for audio and video, and that the SCTP m-line 
will not be bundled.

However section 5.2.1 says:

    Once all m= sections have been generated, a session-level "a=group"
    attribute MUST be added as specified in [RFC5888].  This attribute
    MUST have semantics "BUNDLE", and MUST include the mid identifiers of
    each m= section.  The effect of this is that the browser offers all
    m= sections as one BUNDLE group.  However, whether the m= sections
    are bundle-only or not depends on the BUNDLE policy.

This doesn't deal with bundle policy - this rule seems to apply only to 
max-compat policy.

Section 7.1 says that both Alice and Bob are using the "balanced" 
policy, which should lead to separate bundles for audio and video, but 
the example shows a single bundle - consistent with a "max-bundle" 
policy. There are no examples that show more than one bundle group.