Re: [hybi] -09: abstract and introduction

Iñaki Baz Castillo <ibc@aliax.net> Wed, 15 June 2011 23:16 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 676CC11E80A0 for <hybi@ietfa.amsl.com>; Wed, 15 Jun 2011 16:16:10 -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 9cLE70GJAlJm for <hybi@ietfa.amsl.com>; Wed, 15 Jun 2011 16:16:09 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 77F0111E8080 for <hybi@ietf.org>; Wed, 15 Jun 2011 16:16:09 -0700 (PDT)
Received: by qwc23 with SMTP id 23so679449qwc.31 for <hybi@ietf.org>; Wed, 15 Jun 2011 16:16:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.90.83 with SMTP id h19mr163002qcm.268.1308179767656; Wed, 15 Jun 2011 16:16:07 -0700 (PDT)
Received: by 10.229.230.129 with HTTP; Wed, 15 Jun 2011 16:16:07 -0700 (PDT)
In-Reply-To: <4DF93B86.7050704@stpeter.im>
References: <4DF91FCA.8060403@stpeter.im> <BANLkTinBEprfvY7oRu6_ZeiX4ei0rS5GjA@mail.gmail.com> <4DF93B86.7050704@stpeter.im>
Date: Thu, 16 Jun 2011 01:16:07 +0200
Message-ID: <BANLkTinWNrjdA9sx3Kx7NX_h7OC8k0e_cg@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:16:10 -0000

2011/6/16 Peter Saint-Andre <stpeter@stpeter.im>im>:
> I want to point a client to the WebSocket service at example.com. I
> can't assume that it's served on port 80 or port 443. How does my client
> figure out which port to use?

You have not enough data. A WebSocket service is not just identified
by a host and optional port, it also requires an URI schema (ws for
plain TCP or wss for TLS over TCP). So you need a WebSocket URI (like
"ws://1.2.3.4[:999]).

In your example above, if you want to point a client to the WebSocket
service at example.com, how do you know wheter to use TLS or not? you
need to know the URI schema for that.

Of course, in the case of using SRV records things change a bit (since
the server IP and port) must be determined by performing SRV
procedures and more than one valid destinations can be retrieved in
the DNS response.

PS: If I want to point a http client to the HTTP service at
example.com, how does my client figure out which port to use? Same
response as abobe, I need the URI scheme (http or https).  ;)

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