Re: [rtcweb] Proposed new milestones for RTCWEB

Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com> Thu, 19 July 2012 11:58 UTC

Return-Path: <stefan.lk.hakansson@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 31ADF21F871E for <rtcweb@ietfa.amsl.com>; Thu, 19 Jul 2012 04:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.006
X-Spam-Level:
X-Spam-Status: No, score=-6.006 tagged_above=-999 required=5 tests=[AWL=0.243, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 ZAhn-MCiWtPB for <rtcweb@ietfa.amsl.com>; Thu, 19 Jul 2012 04:58:49 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 23CF621F871C for <rtcweb@ietf.org>; Thu, 19 Jul 2012 04:58:48 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f6c6d000001cc5-02-5007f6ac42ed
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id E9.B0.07365.CA6F7005; Thu, 19 Jul 2012 13:59:41 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.264.0; Thu, 19 Jul 2012 13:59:40 +0200
Message-ID: <5007F6AB.5000705@ericsson.com>
Date: Thu, 19 Jul 2012 13:59:39 +0200
From: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CA+9kkMCqAL+Mi1FV-rkNa5Hd67pg7+_8Ztns8j7O6cxtECo8Gw@mail.gmail.com>
In-Reply-To: <CA+9kkMCqAL+Mi1FV-rkNa5Hd67pg7+_8Ztns8j7O6cxtECo8Gw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFJMWRmVeSWpSXmKPExsUyM+Jvre7ab+wBBmtnsVus/dfO7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujMMTD7IXLBCtuLrwKmMD43/+LkZODgkBE4lnO24xQ9hiEhfu rWfrYuTiEBI4xShxfsF6FghnOaPE4TVb2UGqeAW0Je5tXcQEYrMIqEpMWXmFDcRmE7CRWNs9 BSwuKhAisebbFEaIekGJkzOfsIDYIgLCEltf9YLVCAtYSDS+/gpmCwkESMx4PgXoCg4OToFA iUcvJEHCzAK2EhfmXGeBsOUltr+dwwxRrivx7vU91gmMArOQbJiFpGUWkpYFjMyrGIVzEzNz 0ssN9VKLMpOLi/Pz9IpTNzECw+/glt+6OxhPnRM5xCjNwaIkzsuVtN9fSCA9sSQ1OzW1ILUo vqg0J7X4ECMTB6dUA2PYFK6tP1yrp0k8WLKMMWrx6/8n9fVOnWr71+acfZ9hr/+d9Ldm/M3H q/dfCPsxwefdgcOLN27cMTPfPcht9WFjqzufKo1bPqf4XJq/WPRQhRRbdsp3rTX7fHW/B9w4 t+9aOU9hgPm/h/4/F3EqnVw5YX3i8+9bzz0rYUqenfJPYgb3zBNHj2yfpcRSnJFoqMVcVJwI ANxtv/cNAgAA
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: Thu, 19 Jul 2012 11:58:50 -0000

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
>