IETF Logo Mail Archive

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

Willy Tarreau <w@1wt.eu> Wed, 07 September 2011 08:49 UTC

Return-Path: <w@1wt.eu>
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 7936021F8A7B for <hybi@ietfa.amsl.com>; Wed, 7 Sep 2011 01:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.98
X-Spam-Level:
X-Spam-Status: No, score=-3.98 tagged_above=-999 required=5 tests=[AWL=-1.937, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 Gs3D77yUaaHP for <hybi@ietfa.amsl.com>; Wed, 7 Sep 2011 01:49:49 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA2121F8A67 for <hybi@ietf.org>; Wed, 7 Sep 2011 01:49:48 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p878pSLJ019316; Wed, 7 Sep 2011 10:51:28 +0200
Date: Wed, 07 Sep 2011 10:51:28 +0200
From: Willy Tarreau <w@1wt.eu>
To: Len Holgate <len.holgate@gmail.com>
Message-ID: <20110907085128.GA19144@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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <17ef01cc6d39$3575ae50$0a00a8c0@Venus>
User-Agent: Mutt/1.4.2.3i
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:49:49 -0000

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