Return-Path: X-Original-To: mmusic@ietfa.amsl.com Delivered-To: mmusic@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E47A21F905F; Tue, 7 May 2013 15:02:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q8VzJSP47cD9; Tue, 7 May 2013 15:02:11 -0700 (PDT) Received: from blu0-omc1-s25.blu0.hotmail.com (blu0-omc1-s25.blu0.hotmail.com [65.55.116.36]) by ietfa.amsl.com (Postfix) with ESMTP id 8D49121F86F0; Tue, 7 May 2013 15:02:11 -0700 (PDT) Received: from BLU169-W108 ([65.55.116.9]) by blu0-omc1-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 7 May 2013 15:02:09 -0700 X-EIP: [z+ikBbIH0mZ0gFFuDSFbCAnQhucye7spSp/gk4LOp2Y=] X-Originating-Email: [bernard_aboba@hotmail.com] Message-ID: Content-Type: multipart/alternative; boundary="_f739abbd-a421-4394-b155-2762a690f704_" From: Bernard Aboba To: Harald Alvestrand , Roni Even Date: Tue, 7 May 2013 15:02:09 -0700 Importance: Normal In-Reply-To: <518900CF.6050403@alvestrand.no> References: <20130503054601.4639.64651.idtracker@ietfa.amsl.com> , , <008701ce4b21$a0997aa0$e1cc6fe0$@gmail.com>, <518900CF.6050403@alvestrand.no> MIME-Version: 1.0 X-OriginalArrivalTime: 07 May 2013 22:02:09.0543 (UTC) FILETIME=[85502170:01CE4B6E] Cc: "rtcweb@ietf.org" , "mmusic@ietf.org" Subject: Re: [MMUSIC] [rtcweb] Fwd: New Version Notification for draft-uberti-rtcweb-plan-00.txt X-BeenThere: mmusic@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiparty Multimedia Session Control Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 May 2013 22:02:17 -0000 --_f739abbd-a421-4394-b155-2762a690f704_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Roni said:=20 I=0A= think that plan B is the right direction. I am wondering if=0A= this should be discussed in RTCWEB or MMUSIC=0A= =0A= =0A= =20 =0A= To the extent that the proposals are attempts to "profile" existing RFC= s or MMUSIC work in progress for use in WebRTC=2C it seems to me like the d= iscussion belongs in RTCWEB. One advantage of that approach is that the sol= ution need not necessarily apply to "all uses of SDP for any scenario for a= ll time"=2C just to the WebRTC use cases.=20 To the extent that NEW SDP functionality is needed=2C MMUSIC discussion wou= ld be appropriate. But until the general direction is decided=2C it won't = be clear what the required new functionality is (if any). =20 =0A= =20 =0A= =0A= =0A= =20 = --_f739abbd-a421-4394-b155-2762a690f704_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Roni said:

I=0A= think that plan B is the right direction. I am wondering if=0A= this should be discussed in RTCWEB or MMUSIC

=0A=
=0A= =0A=
=0A= To the extent that the proposals are attempts to "profile" existing RFC= s or MMUSIC work in progress for use in WebRTC=2C it seems to me like the d= iscussion belongs in RTCWEB. One advantage of that approach is that the sol= ution need not necessarily apply to "all uses of SDP for any scenario for a= ll time"=2C just to the WebRTC use cases.

To the extent that NEW SD= P functionality is needed=2C MMUSIC discussion would be appropriate. = =3B But until the general direction is decided=2C it won't be clear what th= e required new functionality is (if any). =3B
=0A=
=0A=
=0A=
=0A=


= --_f739abbd-a421-4394-b155-2762a690f704_--