Re: [rtcweb] I-D Action: draft-ietf-rtcweb-jsep-06.txt - PeerConnection BUNDLE policy

Justin Uberti <juberti@google.com> Wed, 19 February 2014 07:27 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 B93091A037D for <rtcweb@ietfa.amsl.com>; Tue, 18 Feb 2014 23:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.926
X-Spam-Level:
X-Spam-Status: No, score=-1.926 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.548, 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 tmCenHbJd9wq for <rtcweb@ietfa.amsl.com>; Tue, 18 Feb 2014 23:27:33 -0800 (PST)
Received: from mail-ve0-x22e.google.com (mail-ve0-x22e.google.com [IPv6:2607:f8b0:400c:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 0C16B1A0366 for <rtcweb@ietf.org>; Tue, 18 Feb 2014 23:27:32 -0800 (PST)
Received: by mail-ve0-f174.google.com with SMTP id pa12so14303veb.5 for <rtcweb@ietf.org>; Tue, 18 Feb 2014 23:27:29 -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=nUGqVTq5xZyn90m1FJWHyUbMnlNEetP1ti33BWOpzBg=; b=fKlmYROBdwZu0kkcr2O1jnGLM0c2raCHME7ORED9URdzvsMJK0DeImtMs6cuQ4ttxQ eJY5ESZWzJG2bVerPJ20qyu11tunb1fuW/iduJLej6fvF5WECGZjPSO1egcqk6Gn0LR/ XgxqwwYueSqXdGTScoM8MpmmoNSF+T7k72sdNxF6K+TNSm9wZ+1/sAq/d1/CCd9nPwa4 SCMBN8hrMH+PyXeSrCg1qUkzxFMsqIuor1HFawfwWxtKezra8nfDVsF6vn7qBDatAzCB oXvI5/GQTfHEgnkU8A2k+ns5MwqG+G/ai35V6ymUru+PJz9Wn0l1EeDyVWSy4U4Pq8p/ z66Q==
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=nUGqVTq5xZyn90m1FJWHyUbMnlNEetP1ti33BWOpzBg=; b=gALnCduQxYP+I4O/Km6c9PFW2Ri87XLjpMOyzDflsPE16R4HIzftpjFwAuQq3KYN7u 6vpR92uljfK2d1PnTf0pINA1MLfc9PxcyY+0uSgAokqcMkUiYhiLgmGMp8iTw8+NgfZQ GGKxXbKk8jRkX+DOygbyc/3pO7P0YBWfyQGBZNsAt4ktWbVjP10GnpiXIJ2qvCPS9wDd ayxZ3c2tOkZZrFrL5Z1JoPUql/TuxlSatVNgmZVnM22d1mytjov4S999L6WQfz7e3jAN +aReS47kXZyBVyirmx1a6mMhOVknJjCNz+u2AWdhlj5+nxvxuEXNxYOkVIrM5Ql+yTci JPug==
X-Gm-Message-State: ALoCoQmz/PE5lY2K8ghizXQuBExZ5p+cNk0+kQBNVVUWqmi9I6YGXM2Z7jgafQi69+KXc6/XSbHc+jC3t3/OcjD3/6Zu6inJhCgqK1kIhFw+2RWIQYYB0RI0+xhnXhU+WCkGa1Wfndaur7qL41rXwWSLfakX5grPQjcwXnopUFvZWh5QQZvdxaCvu1QG46jNthCrfA3Pus5q
X-Received: by 10.52.236.132 with SMTP id uu4mr323754vdc.47.1392794849605; Tue, 18 Feb 2014 23:27:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.89.170 with HTTP; Tue, 18 Feb 2014 23:27:09 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1730E7@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1730E7@ESESSMB209.ericsson.se>
From: Justin Uberti <juberti@google.com>
Date: Tue, 18 Feb 2014 23:27:09 -0800
Message-ID: <CAOJ7v-2ecnurvXs426-TsZwwjpwiVQNPNWqw8=0+bsEHCcDeoA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="089e01183eb4419ce804f2bd52a2"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/VKmkm1b9remDA7e3weFwQLvrTZU
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-jsep-06.txt - PeerConnection BUNDLE policy
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, 19 Feb 2014 07:27:36 -0000

On Fri, Feb 14, 2014 at 6:22 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> Section 4.1.1. defines, for the PeerConnection constructor, the
> possibility to specify BUNDLE policy.
>
> However, I am missing the possibility to indicate whether, within a BUNDLE
> group, the same port number shall be used or not.
>
> Section 5.2.1 does say:
>
>         "o  The port value is set to the port of the default ICE candidate
> for
>         this m= section; if this m= section is not being bundled into
>         another m= section, the port value MUST be unique."
>
> ...but, it doesn't talk about the case when the port IS being bundled into
> another m= section. Normally, in the initial Offer, the port value will be
> unique also in that case, but if the PeerConnection is created due to
> forking, and it is known that the remote peer supports BUNDLE, then
> identical port values can be used already in the initial offer.
>

If a m= section is being bundled into another m= section, then the port
number must be the same, as indicated in the BUNDLE WG draft.

I did not include a policy option to force use of the same port; the
closest thing would be to use a policy of "all", which will mark all lines
except the first as bundle-only and achieve basically the same result,
although it would require a second offer to update the bundle-only ports.
If this is a problem we could consider adding another policy value.