Re: Do we need two ways of identifying m-lines?

• From: Eric Rescorla <ekr@rtfm.com>
• Date: Sun, 19 Aug 2012 17:06:58 -0700
• To: Harald Alvestrand <harald@alvestrand.no>
• Cc: public-webrtc@w3.org
• Message-ID: <CABcZeBPGWYS+o471mnbRQrYugf2OfU2DDPnhWFZ9umbya+Q3-w@mail.gmail.com>

On Sun, Aug 19, 2012 at 12:29 PM, Harald Alvestrand
<harald@alvestrand.no> wrote:
> On 08/19/2012 05:46 PM, Eric Rescorla wrote:
>>
>> The current RTCIceCandidate type has two ways of identifying the m-line,
>> an m-line index (sdpMLineIndex) and an sdpMid, corresponding
>> to the RFC 3388 media stream identification value.
>
> The reason for the index is that we can't guarantee that a remote offer will
> have unique labels on all its M-lines.
>
> For offers produced by WebRTC, we can choose to make them all have mid
> values (and they have to, if we use BUNDLE).

Hmm...

It sounds to me like index will always work but that label won't, so why
not just always use index? What am I missing?

-Ekr

Received on Monday, 20 August 2012 00:08:07 UTC