Re: [secdir] Review of draft-ietf-hybi-thewebsocketprotocol-10

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 09 August 2011 13:50 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C3F321F8A30 for <secdir@ietfa.amsl.com>; Tue, 9 Aug 2011 06:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level:
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, 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 Fp2dHrOsvLgD for <secdir@ietfa.amsl.com>; Tue, 9 Aug 2011 06:50:39 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 87CDF21F8B7B for <secdir@ietf.org>; Tue, 9 Aug 2011 06:50:38 -0700 (PDT)
Received: from [188.28.117.11] (188.28.117.11.threembb.co.uk [188.28.117.11]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TkE7RQALhAOr@rufus.isode.com>; Tue, 9 Aug 2011 14:51:04 +0100
Message-ID: <4E413B4D.9090309@isode.com>
Date: Tue, 09 Aug 2011 14:51:09 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090303 SeaMonkey/1.1.15
To: kathleen.moriarty@emc.com
References: <AE31510960917D478171C79369B660FA0E05485F1E@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E05485F1E@MX06A.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-hybi-thewebsocketprotocol.all@tools.ietf.org, ifette+ietf@google.com, secdir@ietf.org
Subject: Re: [secdir] Review of draft-ietf-hybi-thewebsocketprotocol-10
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 13:50:40 -0000

Hi Kathleen,
Thank you for the review.
 
kathleen.moriarty@emc.com wrote:
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> security area directors.  Document editors and WG chairs should treat
> these comments just like any other last call comments.
>
> Description: The WebSocket protocol consists of an opening
>    handshake followed by basic message framing, layered over TCP.  The
>    goal of this technology is to provide a mechanism for browser-based
>    applications that need two-way communication with servers that does
>    not rely on opening multiple HTTP connections (e.g. using
>    XMLHttpRequest or <iframe>s and long polling).
>
>
> This document is ready once the security considerations identified in the Gen-ART review are addressed.
>
> Note: The Gen-ART review covered some security and protocol semantics already, thank you Richard.  Richard identified some subtle security issues and developed the "masking" concept in the draft.  It looks like his review from Gen-ART is also on version 10, so I am not certain if his considerations were addressed fully yet.
>   
The purpose of masking will be clarified, hopefully in -11.

I think the WG either agreed to Richard's issues, or agreed to disagree. 
They were discussed in details in the HYBI WG meeting in Quebec.
> There are a few 'catch all' paragraphs in the security section to enforce the need for secure coding - making sure the server only accepts what it is supposed to accept (but just at a high level).  They also hit upon the use of proxies and what can happen in the middle.
>
>
> Best regards,
> Kathleen
>
>