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

Christer Holmberg <> Fri, 14 February 2014 14:22 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 03F9C1A0289 for <>; Fri, 14 Feb 2014 06:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id E0v9UlUxJl0F for <>; Fri, 14 Feb 2014 06:22:51 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 8BB491A025C for <>; Fri, 14 Feb 2014 06:22:49 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-47-52fe26b7f624
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id E2.F2.04249.7B62EF25; Fri, 14 Feb 2014 15:22:47 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.02.0387.000; Fri, 14 Feb 2014 15:22:46 +0100
From: Christer Holmberg <>
To: "" <>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-jsep-06.txt - PeerConnection BUNDLE policy
Thread-Index: Ac8pjtnjzyDELOBDTjiX88M43xAyxw==
Date: Fri, 14 Feb 2014 14:22:46 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPLMWRmVeSWpSXmKPExsUyM+Jvje52tX9BBsvvSFms/dfO7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujEf7DjIVvGOr+NCxna2BcS1rFyMnh4SAicTJRy1sELaYxIV7 64FsLg4hgSOMEkf2vWCCcBYzStx/PJ+li5GDg03AQqL7nzZIg4iAusTlhxfYQWxhgQSJNffX MELEEyVe/+5gg7D1JE4eXgpmswioSuxcdJ8FxOYV8JU4c7MBrJcRaPH3U2uYQGxmAXGJW0/m M0EcJCCxZM95ZghbVOLl439QRytJ/NhwiQWiXkdiwe5PbBC2tsSyha+ZIeYLSpyc+YRlAqPw LCRjZyFpmYWkZRaSlgWMLKsYOYpTi5Ny040MNjECA/nglt8WOxgv/7U5xCjNwaIkzvvxrXOQ kEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsa9fWs3KEfFHJtmP6NObn+J/KzGlprAONeonZHq mn5pZ+LVJr31ksjKiP1Z9fbvbbd/iRUMN7TYvxf+8XL5OXfO/K5jM6pNt+XsipiX8HWvwy9t ibJP3cE7/c0jXFTqzdZcE7vqsZGnqMymzD7zinSHlFN4aEdai9XqNn+pDzfXP7x7NO5hsxJL cUaioRZzUXEiAAPq0yIyAgAA
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-jsep-06.txt - PeerConnection BUNDLE policy
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 14 Feb 2014 14:22:53 -0000


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.