IETF Logo Mail Archive

Re: [hybi] I-D Action: draft-ietf-hybi-thewebsocketprotocol-13.txt

"Len Holgate" <len.holgate@gmail.com> Wed, 07 September 2011 08:51 UTC

Return-Path: <len.holgate@gmail.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 7894921F8B1F for <hybi@ietfa.amsl.com>; Wed, 7 Sep 2011 01:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 eLFFCQ101qnh for <hybi@ietfa.amsl.com>; Wed, 7 Sep 2011 01:51:06 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id BB74621F84FC for <hybi@ietf.org>; Wed, 7 Sep 2011 01:51:05 -0700 (PDT)
Received: by wwf5 with SMTP id 5so4709320wwf.13 for <hybi@ietf.org>; Wed, 07 Sep 2011 01:52:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:in-reply-to :thread-index:x-mimeole; bh=mO35Li6NqtM1XOX/N7f1hVpRXRpG7LlPRT7dv3WF6HE=; b=mohkuGAp8uSO1kmIW82q5h8d4gHGjfTl8TfDNVZBbryklZzlDF7D+zfkWXDgXQg8ZX oPyxmBwdLNQ5PQiFXchC1Xs5zjlTtcfWU48FrrrOwB6PY+/eqCJQcO7u//XIhKVUBMWn PfaEFYBqRHZlCby0wzl87MGZPCaxyBvJiLiSc=
Received: by 10.227.200.146 with SMTP id ew18mr6278676wbb.16.1315385572768; Wed, 07 Sep 2011 01:52:52 -0700 (PDT)
Received: from Venus (cpc6-glfd6-2-0-cust182.6-2.cable.virginmedia.com [80.5.71.183]) by mx.google.com with ESMTPS id p19sm2892521wbm.16.2011.09.07.01.52.51 (version=SSLv3 cipher=OTHER); Wed, 07 Sep 2011 01:52:51 -0700 (PDT)
From: Len Holgate <len.holgate@gmail.com>
To: 'Willy Tarreau' <w@1wt.eu>
References: <20110831184207.1514.64093.idtracker@ietfa.amsl.com> <0fc901cc6878$1681eec0$0a00a8c0@Venus> <CAH9hSJb2rH+fX0AnekYxsEkHKzb15aHrg_hDQw1baWLiWBF-3w@mail.gmail.com> <17b501cc6d31$3016d6d0$0a00a8c0@Venus> <CAH9hSJYhLpcXrOtS-nzLt2YW9QbngEsfdcNF+0TadyVA6rrK1A@mail.gmail.com> <17ef01cc6d39$3575ae50$0a00a8c0@Venus> <20110907085128.GA19144@1wt.eu>
Date: Wed, 07 Sep 2011 09:52:38 +0100
Message-ID: <17fc01cc6d3b$7f561df0$0a00a8c0@Venus>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <20110907085128.GA19144@1wt.eu>
Thread-Index: AcxtO1j3LE0P298sTqq6GHe5Z1I2FgAAAsXA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
Cc: hybi@ietf.org
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-thewebsocketprotocol-13.txt
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: Wed, 07 Sep 2011 08:51:06 -0000

In which case it should be MAY...

The current wording is broken and will lead to broken implementations.

Someone pick one or the other. 

> -----Original Message-----
> From: Willy Tarreau [mailto:w@1wt.eu] 
> Sent: 07 September 2011 09:51
> To: Len Holgate
> Cc: 'Takeshi Yoshino'; sh@defuze.org; hybi@ietf.org
> Subject: Re: [hybi] I-D Action: 
> draft-ietf-hybi-thewebsocketprotocol-13.txt
> 
> On Wed, Sep 07, 2011 at 09:36:14AM +0100, Len Holgate wrote:
> > Fair enough.
> > 
> > So, will server to client masking become MUST NOT in the 
> next draft? 
> 
> Adding "MUST NOT" in a spec always causes issues in implementations
> because the receivers expect that the case never happens and generally
> don't handle the situation gracefully. Basically, the on-wire protocol
> makes it possible to enable or disable masking so we don't need to put
> specific conditions on the cases we're not interested in.
> 
> Regards,
> Willy
> 
>

v2.23.0 | Report a Bug | By Email