Re: [hybi] -09: abstract and introduction

Iñaki Baz Castillo <ibc@aliax.net> Thu, 16 June 2011 11:18 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF33811E8243 for <hybi@ietfa.amsl.com>; Thu, 16 Jun 2011 04:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.664
X-Spam-Level:
X-Spam-Status: No, score=-2.664 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ooaQv09Q4yuR for <hybi@ietfa.amsl.com>; Thu, 16 Jun 2011 04:18:40 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id C55FC11E822C for <hybi@ietf.org>; Thu, 16 Jun 2011 04:18:39 -0700 (PDT)
Received: by qyk38 with SMTP id 38so267132qyk.10 for <hybi@ietf.org>; Thu, 16 Jun 2011 04:18:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.17.17 with SMTP id q17mr602739qca.154.1308223119030; Thu, 16 Jun 2011 04:18:39 -0700 (PDT)
Received: by 10.229.230.129 with HTTP; Thu, 16 Jun 2011 04:18:38 -0700 (PDT)
In-Reply-To: <op.vw51kblbidj3kv@simon-pieterss-macbook.local>
References: <4DF91FCA.8060403@stpeter.im> <op.vw51kblbidj3kv@simon-pieterss-macbook.local>
Date: Thu, 16 Jun 2011 13:18:38 +0200
Message-ID: <BANLkTin-PjMOGekGSBTiyFwxoyrcvQvK-A@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Simon Pieters <simonp@opera.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] -09: abstract and introduction
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Jun 2011 11:18:40 -0000

2011/6/16 Simon Pieters <simonp@opera.com>om>:
>> I know this has been discussed on the list, but how can an entity
>> discover if WebSocket is offered on ports other than 80/443? Would the
>> web server use a redirect to do that? Could it define SRV records?
>
> I don't think there's any discoverability. You can't know that WebSocket is
> offered on ports 80/443 either. I think the Web page that opens a WebSocket
> is supposed to know which port to use. (The WebSocket API doesn't allow
> redirects.)

Hummm, please, is it not clear that the WebSocket URI schema must be
provided in order to know which transport to use (TLS or TCP) and the
port to connect (80/443 depending the schema, in case no port is
explicitely given in the URI) ??



-- 
Iñaki Baz Castillo
<ibc@aliax.net>