MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37E9EA74@ESESSMB209.ericsson.se>
References: <CALiegfm7Rb4e5DFGycr=EsdigE1XFCUiqNL6+GpRSyrGe=_RWg@mail.gmail.com>
 <56DED735.1000101@ericsson.com>
 <CALiegf=G77JOcoR6DORnPsMx4OCgy=_dYQ_r8KfjMy_33vn89A@mail.gmail.com>
 <7594FB04B1934943A5C02806D1A2204B37E9EA74@ESESSMB209.ericsson.se>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Wed, 9 Mar 2016 00:34:09 +0100
Message-ID: <CALiegf=F4z9r+oCO1DMW_nXq7TBJjf-n3N1r6yr5tLoksXtUqg@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/GT5oAtfB29wU4CC-gA1W0fXyhuI>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
 "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE: no reason por payload type to be unique within
 bundled m= lines
Precedence: list

2016-03-08 20:05 GMT+01:00 Christer Holmberg <christer.holmberg@ericsson.co=
m>:
> When we discussed payload type mappings and RTP sessions, it was said tha=
t, in a sendonly m- line, the payload type values are simply "place holders=
", the remote endpoint will tell you what values it want to receive.
>
> So, in your case, you can't say "I am going to send you with PT 100". The=
 answerer is going to say what it wants to receive, so in your case it may =
e.g. chose 98 for alice-audio and 99 for bob-audio.

So I tell you that I will send N codecs with SSRC 1234 and you tell me
which payload I should use. This makes no sense IMHO. SDP was designed
for 1-to-1 symmetric (audio) streams. When it comes to multi-stream (I
send my audio and video and receive multiple audio and video streams
from others) SDP becomes a nightmare.


--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>