Re: [hybi] -09: abstract and introduction

Iñaki Baz Castillo <ibc@aliax.net> Wed, 15 June 2011 23:03 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 D8F1021F847D for <hybi@ietfa.amsl.com>; Wed, 15 Jun 2011 16:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.663
X-Spam-Level:
X-Spam-Status: No, score=-2.663 tagged_above=-999 required=5 tests=[AWL=0.014, 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 XzMNTavcURPC for <hybi@ietfa.amsl.com>; Wed, 15 Jun 2011 16:03:03 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 3F79921F8472 for <hybi@ietf.org>; Wed, 15 Jun 2011 16:03:03 -0700 (PDT)
Received: by qyk7 with SMTP id 7so644714qyk.10 for <hybi@ietf.org>; Wed, 15 Jun 2011 16:03:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.7.212 with SMTP id e20mr180153qce.192.1308178981176; Wed, 15 Jun 2011 16:03:01 -0700 (PDT)
Received: by 10.229.230.129 with HTTP; Wed, 15 Jun 2011 16:03:01 -0700 (PDT)
In-Reply-To: <4DF91FCA.8060403@stpeter.im>
References: <4DF91FCA.8060403@stpeter.im>
Date: Thu, 16 Jun 2011 01:03:01 +0200
Message-ID: <BANLkTinBEprfvY7oRu6_ZeiX4ei0rS5GjA@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Peter Saint-Andre <stpeter@stpeter.im>
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: Wed, 15 Jun 2011 23:03:04 -0000

2011/6/15 Peter Saint-Andre <stpeter@stpeter.im>im>:
> Section 1.7 says:
>
>   By default the WebSocket protocol uses port 80 for regular WebSocket
>   connections and port 443 for WebSocket connections tunneled over TLS
>   [RFC2818].
>
> 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?

I don't understand the question. The WebSocket URI is provided by the
webserver (most probably) and it can contain a port or not. If it does
not contain a port then default port should be used (80/443 depending
on URI schema). Do I miss something?


> Would the
> web server use a redirect to do that? Could it define SRV records?

I wrote a draft for including SRV records in WebSocket:

  http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02

...but got not too much interest, nothing in fact (I assume that since
HTTP just uses DNS A records, no more DNS stuff exists).




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