Re: [hybi] New port and Tunneling?

"Shelby Moore" <shelby@coolpage.com> Wed, 18 August 2010 09:07 UTC

Return-Path: <shelby@coolpage.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 829E33A6A51 for <hybi@core3.amsl.com>; Wed, 18 Aug 2010 02:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[AWL=0.679, BAYES_00=-2.599]
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 5KxkrrwqbjTj for <hybi@core3.amsl.com>; Wed, 18 Aug 2010 02:07:29 -0700 (PDT)
Received: from www5.webmail.pair.com (www5.webmail.pair.com [66.39.3.83]) by core3.amsl.com (Postfix) with SMTP id CD69D3A68E1 for <hybi@ietf.org>; Wed, 18 Aug 2010 02:07:28 -0700 (PDT)
Received: (qmail 19244 invoked by uid 65534); 18 Aug 2010 09:08:04 -0000
Received: from 121.97.54.174 ([121.97.54.174]) (SquirrelMail authenticated user shelby@coolpage.com) by sm.webmail.pair.com with HTTP; Wed, 18 Aug 2010 05:08:04 -0400
Message-ID: <948240ae68778daedf01f136342ab039.squirrel@sm.webmail.pair.com>
In-Reply-To: <2276.1282119618.010687@puncture>
References: <9e3c9de9b6d6278aa26921f4b22963ad.squirrel@sm.webmail.pair.com> <b5f838a87561f318ae6c3958a058b057.squirrel@sm.webmail.pair.com> <657f148a719e31c1699dccfe3e6e63c4.squirrel@sm.webmail.pair.com> <AANLkTimV77PKU3pTAgfBMu5XvzKX7ovHdE6xBCh9o-dx@mail.gmail.com> <340466c936045003a3930a65610df597.squirrel@sm.webmail.pair.com> <19abc4caa904ecc7371926db9a711cdb.squirrel@sm.webmail.pair.com> <2276.1282119618.010687@puncture>
Date: Wed, 18 Aug 2010 05:08:04 -0400
From: Shelby Moore <shelby@coolpage.com>
To: Dave Cridland <dave@cridland.net>
User-Agent: SquirrelMail/1.4.20
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: Server-Initiated HTTP <hybi@ietf.org>
Subject: Re: [hybi] New port and Tunneling?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: shelby@coolpage.com
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: Wed, 18 Aug 2010 09:07:30 -0000

> On Wed Aug 18 09:14:09 2010, Shelby Moore wrote:
>> > After sending this email, I am going to take some time to read
>> some of
>> > your publications, so I can understand better your expertise.
>>
>> Thank you for providing public copies of your research papers.
>>
>> Now I am going to teach you (arrogant? maybe, but not desired, just
>> the
>> way it is[1]).
>
> Is this really the best forum for this?

I don't know.  Is this the best forum for the following?

http://www6.ietf.org/mail-archive/web/hybi/current/msg02400.html

I raised the security issue specifically with respect to SOP on network
requests, because it applies to whether we could enable P2P with this
proposed WS over new port + tunnel, and whether we must apply SOP to
Websockets in any case.

And I don't know where to have that very narrow security discussion else
where amongst motivated participants?

Then again, maybe it is simply a punt for this WG and just specify that
the implementation must decide?  That way as the future understanding
morphs on SOP, then WebSockets standard won't be voided.  I had read a
little bit of HTML5 and seems to be conflating itself with the security
and forcing certain SOP paradigms?