[hybi] Communications usage for the Web Socket Protocol

Henry Sinnreich <henry.sinnreich@gmail.com> Tue, 25 May 2010 14:47 UTC

Return-Path: <henry.sinnreich@gmail.com>
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 EE8CB3A6B5B for <hybi@core3.amsl.com>; Tue, 25 May 2010 07:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.398
X-Spam-Level: *
X-Spam-Status: No, score=1.398 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 fxmDERfJ+r6M for <hybi@core3.amsl.com>; Tue, 25 May 2010 07:47:07 -0700 (PDT)
Received: from mail-gx0-f226.google.com (mail-gx0-f226.google.com [209.85.217.226]) by core3.amsl.com (Postfix) with ESMTP id B16993A6B3B for <hybi@ietf.org>; Tue, 25 May 2010 07:47:07 -0700 (PDT)
Received: by gxk26 with SMTP id 26so2408673gxk.13 for <hybi@ietf.org>; Tue, 25 May 2010 07:46:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:mime-version :content-type; bh=tvHJKpFk0alWe+LNHvV7zKHRJrRQOltj4CRdaA8584g=; b=cAJD1mZkODttQczE8ToJzArvUcgHM4CbSaNwJLCV6AiqVuFOV6hx2MLNxsjMFnu4CS eviBRA128DxcFw5Xhs54aPHxukuiSrtwM0o5/Yk6vXNjOqobsq5hM21vs61zgiT70W3y pxBTYFI1m4GGkGuJOaBosff0+acMuJ2GYjrI8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:mime-version:content-type; b=x0on4jeDZoTMZFD1k/eJjlBo7Zn73XGGKtbz2wpY+cHxPNNtAybDJr+k2ADF4yXPGU W1geo0EuuwJqLMpSheTq8GeiYPH96UtGwTi7CMJ0HzyIjv+fSAyiz09kBHfZE3aPZ7RF XDC70NwcqdjFztY0UKQNI2FroV13YmhoDxcLg=
Received: by 10.150.188.15 with SMTP id l15mr8063357ybf.120.1274798816224; Tue, 25 May 2010 07:46:56 -0700 (PDT)
Received: from [192.168.0.35] (cpe-76-184-229-173.tx.res.rr.com [76.184.229.173]) by mx.google.com with ESMTPS id p5sm57666333ybe.0.2010.05.25.07.46.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 25 May 2010 07:46:55 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Tue, 25 May 2010 09:46:53 -0500
From: Henry Sinnreich <henry.sinnreich@gmail.com>
To: hybi@ietf.org, whatwg@whatwg.org, ian@hixie.ch
Message-ID: <C8214D0D.102B9%henry.sinnreich@gmail.com>
Thread-Topic: Communications usage for the Web Socket Protocol
Thread-Index: Acr8GR1VHHC7JHxzMUy+lthlAxwBwA==
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3357625615_19710273"
X-Mailman-Approved-At: Thu, 03 Jun 2010 22:26:09 -0700
Cc: Alan Johnston <alan.b.johnston@gmail.com>
Subject: [hybi] Communications usage for the Web Socket Protocol
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: Tue, 25 May 2010 14:47:11 -0000

The Web Socket Protocol is far more general and useful than modestly
described in the latest I-D version

http://www.whatwg.org/specs/web-socket-protocol/

The sections 1. Introduction and 1.1. Background could also mention some of
these facts:

Many new network application protocols were standardized in the IETF staring
in the mid Œ90s.
The concept then was new applications require new network protocols.
Examples include: The SIP/SDP family of protocols, RTSP, XMPP, MEGACO, MSRP,
etc. for communications and media control applications, not to mention other
non-IETF network application protocols such as H.323 or IAX.

The web development 15 years later has shown however that HTTP can support
literally countless Internet applications.
Actually any application that requires only a data communication channel
between the UA and the Web feature server.
This certainly includes IM as in the section 1.1. Background, but also web
conferencing, blogs, wikis, social networks, etc.

The data communications for SIP signaling over symmetric HTTP are described
in 
³SIP APIs for Communications on the Web²
http://www.ietf.org/id/draft-sinnreich-sip-web-apis-00.txt

What do you think?

Thanks, Henry