Re: [hybi] Opera's Pre-Last Call review of websocket -06

"Simon Pieters" <simonp@opera.com> Tue, 26 April 2011 09:21 UTC

Return-Path: <simonp@opera.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD44BE0709 for <hybi@ietfa.amsl.com>; Tue, 26 Apr 2011 02:21:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 XrLjltPIkINk for <hybi@ietfa.amsl.com>; Tue, 26 Apr 2011 02:21:03 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by ietfa.amsl.com (Postfix) with ESMTP id 010C6E0727 for <hybi@ietf.org>; Tue, 26 Apr 2011 02:21:02 -0700 (PDT)
Received: from simon-pieterss-macbook.local (c-039ee355.410-6-64736c14.cust.bredbandsbolaget.se [85.227.158.3]) (authenticated bits=0) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p3Q9Klh1006408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Apr 2011 09:20:48 GMT
Content-Type: text/plain; charset="utf-8"; format="flowed"; delsp="yes"
To: ifette@google.com, Julian Reschke <julian.reschke@gmx.de>
References: <op.vs9bponnidj3kv@simon-pieterss-macbook.local> <op.vs9li6der4mipi@emoller-pc.gothenburg.osa> <op.vteywfw6idj3kv@simon-pieterss-macbook.local> <BANLkTimTC2nf13eCrOZ0E_ZBPueFMxwpmA@mail.gmail.com> <4DB3D418.1010005@gmx.de>
Date: Tue, 26 Apr 2011 11:20:59 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
From: Simon Pieters <simonp@opera.com>
Message-ID: <op.vujf89h3idj3kv@simon-pieterss-macbook.local>
In-Reply-To: <4DB3D418.1010005@gmx.de>
User-Agent: Opera Mail/11.10 (MacIntel)
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Opera's Pre-Last Call review of websocket -06
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Apr 2011 09:21:03 -0000

On Sun, 24 Apr 2011 09:41:12 +0200, Julian Reschke <julian.reschke@gmx.de>  
wrote:

> On 22.04.2011 03:45, Ian Fette (イアンフェッティ) wrote:
>> On Mon, Apr 4, 2011 at 5:42 AM, Simon Pieters <simonp@opera.com
>> <mailto:simonp@opera.com>> wrote:
>>
>>     Hi,
>>
>>     We have reviewed
>>     http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-06
>>
>>     The introduction section is non-normative but has a number of MUSTs.
>>     Please don't have any requirements in the introduction.
>>
>>
>> I have ensured that normative requirements are now consistently upper
>> case. There are no upper case MUSTs left in the non-normative
>> introduction in the draf that will be 07.
>> ...
>
> But note that RFC 2119 says:
>
>     In many standards track documents several words are used to signify
>     the requirements in the specification.  These words are often
>     capitalized.  This document defines these words as they should be
>     interpreted in IETF documents.  Authors who follow these guidelines
>     should incorporate this phrase near the beginning of their document:
>
> ...so the magic lies in the keyword, not in the uppercasing.

Indeed. Words such as 'could' and 'will' can be used instead in  
non-normative contexts.

-- 
Simon Pieters
Opera Software