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

Justin Uberti <juberti@google.com> Wed, 05 November 2014 00:58 UTC

Return-Path: <juberti@google.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EA211A1AB7 for <rtcweb@ietfa.amsl.com>; Tue, 4 Nov 2014 16:58:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.972
X-Spam-Level:
X-Spam-Status: No, score=-1.972 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id owzv0APHLxaL for <rtcweb@ietfa.amsl.com>; Tue, 4 Nov 2014 16:58:43 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F24661A1AA6 for <rtcweb@ietf.org>; Tue, 4 Nov 2014 16:58:42 -0800 (PST)
Received: by mail-ob0-f173.google.com with SMTP id wn1so11786354obc.18 for <rtcweb@ietf.org>; Tue, 04 Nov 2014 16:58:42 -0800 (PST)
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; bh=yseesXzUPenkbjIB/6l2lSwwUoavvA3WETuefmj1QHQ=; b=ZDItVdIsQThgb2yfr1VeNoisYgoFSH9ma00MOAftRxGQEp6fd9rkN1wKTwsODj4LIu 6imi03n9t6lEuwRUXLJA83LbM2ivjmSYf0Ek13XZ6m2ijcYFDkmZdyka/YpqYRvdWe2/ 7hz/u2Wm3L/qzg1ZyfTu/NFct3yHeRSHIl3+eWey+XpfY/chbN1ngf/UDyMh5cDvZtwi ARst0IoCg6anA1618xAmd+3TUyMkBhFOQR+iEZ9IPTIuJzfA0On94SQQrHu60ZAm5eud UBtc1xZ/RvVr2yVzNEqHcoVjATLOKEBPYx9lyHK7mJsULJRb7P+rNYgVYZMedd8J8y1K xd2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=yseesXzUPenkbjIB/6l2lSwwUoavvA3WETuefmj1QHQ=; b=hhXvo2bg+KQyp0MBkR/K6D8gPwaia9vYA82aBG6iLJ/xl6ImnU4baQ6EjYAalIy6yq kU37OMqG1Y4GD6pX5/qjwrP5aL0MPlTIBdsPPCeYUqjrxVzp21L3FMxiAu8wr3USYhVb IdqHw3xMWM8xWlR4Z5HBENfDy7rS+ouXKNgPdfv5sQjqjXd+RN4xkvOlInwVfIkdew8I n4KvPcI9FiiWr7PXAELvBaW2EZ5CmsP5KlDC63kJs7KpUc/fA/m5T1VYmpmQp+Dknz2J rnsJ4YQ9P3VFDPXaIrbueAZRqBVPJAmbngVkuklwTmdHR7q+jVIqI2X3+EiRV/4i7C2n G7qA==
X-Gm-Message-State: ALoCoQlkJl1MRHrwQflWRn0sCUp86jqz0WDIIDQlLxWgrJeP+JBAhdsJS4RgYLpR9K/moJgxv1Tn
X-Received: by 10.182.46.168 with SMTP id w8mr4948359obm.56.1415149122128; Tue, 04 Nov 2014 16:58:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.248.170 with HTTP; Tue, 4 Nov 2014 16:58:20 -0800 (PST)
In-Reply-To: <54594A9B.9090703@alum.mit.edu>
References: <54594A9B.9090703@alum.mit.edu>
From: Justin Uberti <juberti@google.com>
Date: Tue, 04 Nov 2014 16:58:20 -0800
Message-ID: <CAOJ7v-3zgw1BByRm+AY74_AfD1DbiTKoR2YJ_7ojotY5D8XjHw@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary="047d7bfeaf70baac6e0507121470"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/VduLtsaIHt7AYVQH6qIdyhuflxU
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [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: Wed, 05 Nov 2014 00:58:47 -0000

On Tue, Nov 4, 2014 at 1:52 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> 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.
>

This is not correct. Rather, the m= lines for these groups will not be
marked as a=bundle-only.

>
> 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.
>
>
Right. JSEP endpoints always try to BUNDLE (and rtcp-mux). Legacy endpoints
can of course reject this.