Re: [rtcweb] Comments on draft-ietf-rtcweb-overview-05

Harald Alvestrand <harald@alvestrand.no> Thu, 31 January 2013 15:08 UTC

Return-Path: <harald@alvestrand.no>
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 A972121F8586 for <rtcweb@ietfa.amsl.com>; Thu, 31 Jan 2013 07:08:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.499
X-Spam-Level:
X-Spam-Status: No, score=-110.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TXWe1z7vBE6b for <rtcweb@ietfa.amsl.com>; Thu, 31 Jan 2013 07:08:01 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 5F37921F857E for <rtcweb@ietf.org>; Thu, 31 Jan 2013 07:08:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6DF3B39E1BE for <rtcweb@ietf.org>; Thu, 31 Jan 2013 16:08:00 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxwfngoOY+30 for <rtcweb@ietf.org>; Thu, 31 Jan 2013 16:07:58 +0100 (CET)
Received: from hta-dell.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:be30:5bff:fede:bcdc]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id A252939E1B7 for <rtcweb@ietf.org>; Thu, 31 Jan 2013 16:07:58 +0100 (CET)
Message-ID: <510A88CD.9090602@alvestrand.no>
Date: Thu, 31 Jan 2013 16:07:57 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <i82ig8pdnb81tlbbbe79u6q7v4acmp67e3@hive.bjoern.hoehrmann.de>
In-Reply-To: <i82ig8pdnb81tlbbbe79u6q7v4acmp67e3@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Comments on draft-ietf-rtcweb-overview-05
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, 31 Jan 2013 15:08:02 -0000

On 01/30/2013 01:23 PM, Bjoern Hoehrmann wrote:
> Hi,
>
>    http://tools.ietf.org/html/draft-ietf-rtcweb-overview-05 claims that
> it is an "overview" in title and abstract, but it also references RFC
> 2119 and uses RFC 2119 keywords and has normative references making the
> role of the document unclear. Either the RFC 2119 reference and keywords
> have to be removed, or Abstract and perhaps title have to be changed to
> make it clear who or what would conform to this specification.

The original intent was that an application that claims conformance to 
the RTCWEB specification could specify only that it conforms to this 
document, pulling the normative references in by reference.

It is up to the chairs to determine if this purpose is a) desirable and 
b) achievable.

>
> I understand the Chairs are already aware some of the references need to
> be updated. The `[getusermedia]` reference should point to some proper
> publication of the W3C, under `http://www.w3.org/TR/` most likely.

(speaking with W3C WG chair hat on) These documents are not finished.
It is up to the IETF whether it wishes to refer to them as 
work-in-progress or hold publication until publications exist.

>
> There are various parts that have placeholder text, e.g. section 9 has
> "<whatever dB metrics makes sense here - most important that we have one
> only>" and '<WORKING GROUP DRAFT "MEDIA PROCESSING">', and Appendix A
> has 'The draft referred to as "transport and middle boxes" in Section 4
> has not been written yet.' That seems to indicate that the draft is not
> ready for publication yet.

Noted. These are important to get right.

>
> In section 12 is a typo "ad to" which should probably be "and to".
>
> Also in section 12, "The number of people who have taken part in the
> discussions surrounding this draft are too numerous to list". Ordinarily
> people would not be acknowledged simply for having taken part in some
> discussion surrounding a document, and it's usually not true that there
> have been "too many to list"; I think it would be better to remove the
> quoted text.
>
> As noted in http://www.w3.org/2001/06/manual/#Translations the document
> should not use "we" as that is hard to translate and usually it's not
> very clear who the pronoun refers to (authors, editors, working group,
> the IETF at large, or someone else).

Seven occurences found, five of them in appendix A, which the text says 
should be moved to a different document, and one in the change log.
>
> There seem to be many phrases used in the document that are not very
> suitable for a general audience, examples are "communications event",
> "communications partnership", and "a strong changer of the marketplace
> of deployment". (Two of the phrases there come from the last paragraph
> in 2.3. which as a whole is not very comprehensible and probably needs
> to be re-written).

While the readers of this document are not a "general" audience, this 
paragraph was not easy to write, and does seem hard to read. Alternative 
suggestions are welcome.

>
> regards,