IETF Logo Mail Archive

[hybi] Websocket and TLS activation after connection setup

Francis Brosnan Blazquez <francis@aspl.es> Thu, 03 December 2009 12:45 UTC

Return-Path: <francis@aspl.es>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0D5C3A6A2D for <hybi@core3.amsl.com>; Thu, 3 Dec 2009 04:45:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.698
X-Spam-Level: ****
X-Spam-Status: No, score=4.698 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, FH_HOST_ALMOST_IP=1.889, HOST_EQ_STATIC=1.172, HOST_EQ_STATICIP=1.511, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IobWX8ynv-wa for <hybi@core3.amsl.com>; Thu, 3 Dec 2009 04:45:23 -0800 (PST)
Received: from dolphin.aspl.es (196.Red-212-170-101.staticIP.rima-tde.net [212.170.101.196]) by core3.amsl.com (Postfix) with ESMTP id C61B13A688E for <hybi@ietf.org>; Thu, 3 Dec 2009 04:45:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by dolphin.aspl.es (Postfix) with ESMTP id AF58CFCC07D for <hybi@ietf.org>; Thu, 3 Dec 2009 13:45:05 +0100 (CET)
X-Virus-Scanned: amavisd-new at dolphin.aspl.es
Received: from dolphin.aspl.es ([127.0.0.1]) by localhost (dolphin.aspl.es [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TlJDVgcmnMFw for <hybi@ietf.org>; Thu, 3 Dec 2009 13:45:04 +0100 (CET)
Received: from [192.168.0.132] (barracuda [10.0.0.4]) by dolphin.aspl.es (Postfix) with ESMTP id 6ADA7FCC07B for <hybi@ietf.org>; Thu, 3 Dec 2009 13:45:04 +0100 (CET)
From: Francis Brosnan Blazquez <francis@aspl.es>
To: Hybi <hybi@ietf.org>
Content-Type: text/plain
Organization: ASPL
Date: Thu, 03 Dec 2009 13:45:05 +0100
Message-Id: <1259844305.18230.2791.camel@vulcan.aspl.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3
Content-Transfer-Encoding: 7bit
Subject: [hybi] Websocket and TLS activation after connection setup
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 03 Dec 2009 12:45:23 -0000

Hi,

It seems current WebSocket API do not allows an user to first connect
and then negotiate TLS (SSL) to secure its session. Is there any plan to
include such feature in the API and the websocket protocol?

Cheers!
-- 
Francis Brosnan Blazquez <francis@aspl.es>
ASPL

v2.23.0 | Report a Bug | By Email