Re: [hybi] [tsv-area] Fwd: I-D Action:draft-hixie-thewebsocketprotocol-35.txt

<L.Wood@surrey.ac.uk> Mon, 17 August 2009 14:58 UTC

Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA1F4B.23AA2242"
Date: Mon, 17 Aug 2009 15:58:11 +0100
Message-ID: <4835AFD53A246A40A3B8DA85D658C4BE01368948@EVS-EC1-NODE4.surrey.ac.uk>
Thread-Topic: [tsv-area] Fwd: I-D Action:draft-hixie-thewebsocketprotocol-35.txt
Thread-Index: AcofIpf0PjdBkNr+TlqhEVBsPnP6wAAJ8qRY
References: <20090816093001.319053A692F@core3.amsl.com> <015CC5B3-A697-46D5-B76D-3BC609A4E13D@nokia.com>
From: L.Wood@surrey.ac.uk
To: lars.eggert@nokia.com, hybi@ietf.org
Subject: Re: [hybi] [tsv-area] Fwd: I-D Action:draft-hixie-thewebsocketprotocol-35.txt
Precedence: list

I don't see the reason for Connection: upgrade / Upgrade: WebSocket
as the handshake mechanism.

Surely a Content-* header (say: Content-Upgrade: WebSocket) is better, as 
it will be explicitly dropped and 501'd by proxies or by sources
not supporting web sockets? (per section 9.6 of RFC2616.) That
way, you know when the handshake has failed...

thanks,

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@surrey.ac.uk>



-----Original Message-----
From: tsv-area-bounces@ietf.org on behalf of Lars Eggert
Sent: Mon 2009-08-17 11:07
To: TSV Area
Subject: [tsv-area] Fwd: I-D Action:draft-hixie-thewebsocketprotocol-35.txt
 
Transport folks will want to give this a read. Comment on hybi@ietf.org.

Lars

Begin forwarded message:

> From: "Internet-Drafts@ietf.org" <Internet-Drafts@ietf.org>
> Date: August 16, 2009 11:30:01 GMT+02:00
> To: "i-d-announce@ietf.org" <i-d-announce@ietf.org>
> Subject: I-D Action:draft-hixie-thewebsocketprotocol-35.txt
> Reply-To: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>
> A New Internet-Draft is available from the on-line Internet-Drafts  
> directories.
>
> 	Title           : The Web Socket protocol
> 	Author(s)       : I. Hickson
> 	Filename        : draft-hixie-thewebsocketprotocol-35.txt
> 	Pages           : 31
> 	Date            : 2009-08-16
>
> This protocol enables two-way communication between a user agent
> running untrusted code running in a controlled environment to a
> remote host that understands the protocol.  It is intended to fail to
> communicate with servers of pre-existing protocols like SMTP or HTTP,
> while allowing HTTP servers to opt-in to supporting this protocol if
> desired.  It is designed to be easy to implement on the server
> side.Author's note
>
> This document is automatically generated from the same source
> document as the HTML5 specification.  [HTML5]
>
> Please send feedback to either the hybi@ietf.org list or the
> whatwg@whatwg.org list.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-hixie-thewebsocketprotocol-35.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> [InternetShortcut]
> URL=ftp://ftp.ietf.org/internet-drafts/draft-hixie-thewebsocketprotocol-35.txt

Re: [hybi] I-D Action:draft-hixie-thewebsocketpro… L.Wood
Re: [hybi] I-D Action:draft-hixie-thewebsocketpro… Mark Nottingham
Re: [hybi] [tsv-area] Fwd: I-D Action:draft-hixie… L.Wood
Re: [hybi] [tsv-area] Fwd: I-D Action:draft-hixie… Ian Hickson
Re: [hybi] [tsv-area] Fwd: I-D Action:draft-hixie… Jamie Lokier