[MMUSIC] POF/PAN: Length of mid values

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 22 October 2013 18:12 UTC

From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: POF/PAN: Length of mid values
Thread-Index: Ac7PUkEvfSSwviXnTPSLJog1JkUgBQ==
Content-Class: urn:content-classes:message
Date: Tue, 22 Oct 2013 18:12:22 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C4EBB9C@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C4EBB9CESESSMB209erics_"
MIME-Version: 1.0
Subject: [MMUSIC] POF/PAN: Length of mid values
Precedence: list

Hi,



The draft currently says that the length of the mid value must be at least 32 randomly chosen characters. AFAIK, the only reason is to prevent that two endpoints would choose the same mid value.



However, as I indicated in another reply, there might be cases where e.g. a BUNDLE group contains LOTS of m- lines (read: mid values), which means we could end up with really long SDP message bodies - just because of the mid values.



Wouldn't it be possible to simply assign e.g. a 1 character mid value prefix to the Offerer and the Answerer? That would ensure that they don't assign the same mid value to an m- line, because at least the prefix would always be different.



Regards,



Christer

[MMUSIC] POF/PAN: Length of mid values Christer Holmberg
Re: [MMUSIC] POF/PAN: Length of mid values Martin Thomson
Re: [MMUSIC] POF/PAN: Length of mid values Paul Kyzivat
Re: [MMUSIC] POF/PAN: Length of mid values Christer Holmberg