Re: [rtcweb] Proposed new milestones for RTCWEB

Salvatore Loreto <salvatore.loreto@ericsson.com> Fri, 27 July 2012 13:20 UTC

Return-Path: <salvatore.loreto@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F6C321F85DB for <rtcweb@ietfa.amsl.com>; Fri, 27 Jul 2012 06:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.416
X-Spam-Level:
X-Spam-Status: No, score=-106.416 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, 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 ZEwGg5isj1eF for <rtcweb@ietfa.amsl.com>; Fri, 27 Jul 2012 06:20:01 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 0E62421F841D for <rtcweb@ietf.org>; Fri, 27 Jul 2012 06:20:00 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f6c6d000001cc5-a3-5012957f1df3
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 32.DB.07365.F7592105; Fri, 27 Jul 2012 15:19:59 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.264.0; Fri, 27 Jul 2012 15:19:59 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 2401D2478 for <rtcweb@ietf.org>; Fri, 27 Jul 2012 16:19:59 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id A382B533E4 for <rtcweb@ietf.org>; Fri, 27 Jul 2012 16:19:59 +0300 (EEST)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 5BD8F533D8 for <rtcweb@ietf.org>; Fri, 27 Jul 2012 16:19:59 +0300 (EEST)
Message-ID: <5012957E.2060405@ericsson.com>
Date: Fri, 27 Jul 2012 16:19:58 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CA+9kkMCqAL+Mi1FV-rkNa5Hd67pg7+_8Ztns8j7O6cxtECo8Gw@mail.gmail.com> <5007F6AB.5000705@ericsson.com>
In-Reply-To: <5007F6AB.5000705@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFLMWRmVeSWpSXmKPExsUyM+JvrW79VKEAg10XNS3W/mtnd2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxp5VM1kLZkpUrJw+kamBcb1QFyMnh4SAicT7huNsELaYxIV7 64FsLg4hgVOMEjvnz2eCcDYwSnzrvMkK4VxklHi35gIrSIuQwBFGiZUznSDss4wSR94pgNi8 AtoSP7/vZO5i5OBgEVCV2HlLHCTMJmAm8fzhFrCwqECyxN//6RDVghInZz5hAbFFBIQltr7q ZQKxhQUsJBpff2WCmF4gMe/GGbAaTgEdiUnzL4LZzAK2EhfmXIey5SW2v53DDPGMmsTVc5uY IXq1JHrPdjJNYBSZhWTdLCTts5C0L2BkXsUonJuYmZNebqiXWpSZXFycn6dXnLqJERjeB7f8 1t3BeOqcyCFGaQ4WJXFerqT9/kIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYJ9/4U1YkZKCo Ju1buW9xy0Gj1TwbvV6dXqquWFr5surYHYObJ/VDN3KHNc9mag96w/RT71zMt8rb+9cv7LV8 O+ub0f7AhS/WpJ41DTWS/1GQduiH9ftN2nr22jGvmJUENH4Kmq87ZqZU02K1Zq8Ji1vy2/6q L55bfH9OT06JqI7Qem3Ecj5TiaU4I9FQi7moOBEAqg954T0CAAA=
Subject: Re: [rtcweb] Proposed new milestones for RTCWEB
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 13:20:02 -0000

I agree with Stefan,
I would suggest March 2013 or even earlier as timeline for the Data



On 7/19/12 2:59 PM, Stefan Hakansson LK wrote:
> This looks reasonable to me. The possible exception would be: I think
> the data parts could be earlier (given that the media stuff can be
> delivered as proposed - 4 months extra for the data seems a bit much).
>
> Stefan
>
> On 07/18/2012 09:08 PM, Ted Hardie wrote:
>> As folks know, we are behind on our milestones.  The following
>> milestones represent a proposal from me and Magnus, based on some text
>> from Cullen.  Please review in light of our deliverable list:
>>
>>       1.  Define the communication model in detail, including how session
>>           management is to occur within the model.
>>
>>       2.  Define a security model that describes the security and privacy
>>           goals and specifies the security protocol mechanisms necessary
>>           to achieve those goals.
>>
>>       3.  Define the solution - protocols and API requirements - for
>>           firewall and NAT traversal.
>>
>>       4.  Define which media functions and extensions shall be supported in
>>           the client and their usage for real-time media, including media
>>           adaptation to ensure congestion safe usage.
>>
>>       5.  Define what functionalities in the solution, such as media codecs,
>>           security algorithms, etc., can be extended and how the
>>           extensibility mechanisms works.
>>
>>       6.  Define a set of media formats that must or should be supported by
>>           a client to improve interoperability.
>>
>>       7.  Define how non media data is transported between clients in a
>>           secure and congestion safe way.
>>
>>       8.  Provide W3C input for the APIs that comes from the communication
>>           model and the selected components and protocols that are part of
>>           the solution.
>>
>>       9.  The group will consider options for interworking with legacy VoIP
>>           equipment.
>>
>> Timeline:
>>
>> Sep 2012 - Send Use Cases document to IESG for publication as Informational
>> Sep 2012 - Complete Overview (and hold for dependency resolution)
>> Sep 2012 - Send Security and Privacy Problem Statement to IESG for
>> publication as Informational
>>
>> Jan 2013 - Send Signalling Negotiation and NAT Traversal to IESG for
>> publication as Proposed Standard
>> Jan 2013 - Send Security Solution to IESG for publication as Proposed Standard
>> Jan 2013 - Send Media Transport, Media Processing, and Codecs to
>> IESG for publication as Proposed Standard
>>
>> May 2013 - Send Data Stream Transport for non-media data to IESG for
>> publication as Proposed Standard
>>
>> Comments, please!
>>
>> Ted
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb