Message-ID: <BLU403-EAS336A4AA94CDB5E97170F9A5939F0@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
References: <20130530185619.4124.56395.idtracker@ietfa.amsl.com>
 <51A87F91.2080500@jitsi.org> <51AEA08D.8090103@cisco.com>
From: Bernard Aboba <bernard_aboba@hotmail.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <51AEA08D.8090103@cisco.com>
Date: Tue, 4 Jun 2013 19:41:17 -0700
To: Flemming Andreasen <fandreas@cisco.com>
Cc: Ari Keranen <ari.keranen@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] MMUSIC Working Group Virtual Interim Meeting, June 17,
 2013
Precedence: list

Yes, you are missing something. No plan analyzes issues with both Plan A and=
 Plan B and describes how to fix them. As they stand, both Plan A nor Plan B=
 result in O/A exchanges that aren't needed and will break congestion contro=
l. Also, neither satisfies the requirements of the RTP usage doc or is compa=
tible with a number of legacy implementations. No  plan offers a solution to=
 these and other issues.=20

On Jun 4, 2013, at 7:29 PM, "Flemming Andreasen" <fandreas@cisco.com> wrote:=


>=20
> On 5/31/13 6:46 AM, Emil Ivov wrote:
>> Dear chairs,
>>=20
>> Could you please also consider the following draft for the interim meetin=
g agenda:
>>=20
>> http://tools.ietf.org/html/draft-ivov-rtcweb-noplan
> Sure, however I could use some clarification here. On one hand, the draft f=
alls squarely in the middle of the overall "Plan" discussion we have and hen=
ce is highly relevant, but at the same time, if I understand correctly, the d=
raft is not asking MMUSIC to do anything in terms of protocol development. R=
ather, if this approach is adopted, it would be more of an RTCWeb usage docu=
ment specifying how one could use several different mechanisms (and possibly=
 WebRTC APIs) to implement signaling. There doesn't seem to be a "mandatory t=
o implement" mechanism for guaranteeing interoperability (in contrast to Pla=
n A/B), but rather there are references to "app specific signalling" mechani=
sms, etc. Am I missing something here ?
>=20
>=20
>> I apologise if not stating this earlier has introduced any confusion.
> No worries.
>=20
> Thanks
>=20
> -- Flemming
>=20
>> Regards,
>> Emil
>>=20
>> On 30.05.13, 21:56, IESG Secretary wrote:
>>> Greetings,
>>>=20
>>> This is to announce a(nother) virtual interim meeting for the MMUSIC
>>> Working Group to take place on Monday, June 17, from 7:00 am - 10:00 am
>>> Pacific Time. The goal of this meeting is to come to a resolution on the=

>>> so-called "Plan A" or "Plan B" approach related to SDP signaling needed
>>> by RTCWeb, CLUE, etc. (i.e. do we have potentially lots of "m=3D" lines o=
r
>>> very few "m=3D" lines and to what extent is there sub-negotation and
>>> signaling at the SSRC level).
>>>=20
>>> A more detailed agenda and logistics will be sent out separately on the
>>> MMUSIC mailing list. For now, people should take a close look at the
>>> following two drafts:
>>>=20
>>> http://www.ietf.org/id/draft-roach-rtcweb-plan-a-00.txt
>>>=20
>>> http://www.ietf.org/internet-drafts/draft-uberti-rtcweb-plan-00.txt
>>>=20
>>> You may also want to look at
>>> http://www.ietf.org/id/draft-roach-rtcweb-glareless-add-00.txt
>>>=20
>>>=20
>>> Thanks
>>>=20
>>> -- Ari & Flemming (MMUSIC co-chairs)
>>>=20
>>>=20
>>> PS: Per our previous interim meeting announcement, we tried to schedule
>>> a longer and in-person physical interim meeting, however it has proven
>>> impossible to find a set of dates where we could get critical mass for
>>> such a meeting. Scheduling even a virtual interim before the Berlin IETF
>>> has been surprisingly difficult with the above date being the only
>>> viable option at this point.
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic