Re: [rtcweb] Fwd: New Version Notification for draft-ietf-rtcweb-overview-01.txt

Colin Perkins <csp@csperkins.org> Tue, 30 August 2011 15:38 UTC

Return-Path: <csp@csperkins.org>
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 ACFE621F8CDC for <rtcweb@ietfa.amsl.com>; Tue, 30 Aug 2011 08:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level:
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 HMe0R5wDvugQ for <rtcweb@ietfa.amsl.com>; Tue, 30 Aug 2011 08:38:11 -0700 (PDT)
Received: from lon1-msapost-2.mail.demon.net (lon1-msapost-2.mail.demon.net [195.173.77.181]) by ietfa.amsl.com (Postfix) with ESMTP id 8CCEA21F8CD7 for <rtcweb@ietf.org>; Tue, 30 Aug 2011 08:38:11 -0700 (PDT)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by lon1-post-2.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1QyQPZ-0000fe-cf; Tue, 30 Aug 2011 15:39:38 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-80--743355380
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <4E5513E8.3040902@alvestrand.no>
Date: Tue, 30 Aug 2011 16:39:37 +0100
Message-Id: <EC5069B1-1A33-4A69-AEA1-E62EFE177934@csperkins.org>
References: <4E5513E8.3040902@alvestrand.no>
To: Harald Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.1084)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Fwd: New Version Notification for draft-ietf-rtcweb-overview-01.txt
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: Tue, 30 Aug 2011 15:38:12 -0000

Harald,

This looks good. I just have two very minor comments regarding Section 5:

- The correct reference for SRTP is RFC3711, not RFC3550 (the security mechanism in RFC3550 is not compatible with SRTP).

- I agree with the sentiment that "SRTP is used for transport of all real-time media", however this leaves open the choice of RTP profile (there are several that use SRTP). It might be useful to reference draft-perkins-rtcweb-rtp-usage, since that addresses this question.

Cheers,
Colin



On 24 Aug 2011, at 16:08, Harald Alvestrand wrote:
> A few drawings, some more definitions, and a link to the W3C API spec.
> 
> If people are quick with comments, I can get another version done before our September 7 meeting; version numbers are cheap.
> 
>                Harald
> 
> -------- Original Message --------
> Subject:	New Version Notification for draft-ietf-rtcweb-overview-01.txt
> Date:	Wed, 24 Aug 2011 07:37:14 -0700
> From:	internet-drafts@ietf.org
> To:	harald@alvestrand.no
> CC:	harald@alvestrand.no
> 
> A new version of I-D, draft-ietf-rtcweb-overview-01.txt has been successfully submitted by Harald Alvestrand and posted to the IETF repository.
> 
> Filename:	 draft-ietf-rtcweb-overview
> Revision:	 01
> Title:		 Overview: Real Time Protocols for Brower-based Applications
> Creation date:	 2011-08-24
> WG ID:		 rtcweb
> Number of pages: 17
> 
> Abstract:
>    This document gives an overview and context of a protocol suite
>    intended for use with real-time applications that can be deployed in
>    browsers - &quot;real time communication on the Web&quot;.
> 
>    It intends to serve as a starting and coordination point to make sure
>    all the parts that are needed to achieve this goal are findable, and
>    that the parts that belong in the Internet protocol suite are fully
>    specified and on the right publication track.
> 
>    This work is an attempt to synthesize the input of many people, but
>    makes no claims to fully represent the views of any of them.  All
>    parts of the document should be regarded as open for discussion,
>    unless the RTCWEB chairs have declared consensus on an item.
> 
>    This document is a candidate to become a work item of the RTCWEB
>    working group.
> 
> 
>                                                                                   
> 
> 
> The IETF Secretariat
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb



-- 
Colin Perkins
http://csperkins.org/