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

[Christer Holmberg <[e-mail]>]

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.

Regards,

Christer