Re: [hybi] -09: abstract and introduction

Peter Saint-Andre <stpeter@stpeter.im> Wed, 15 June 2011 23:08 UTC

Return-Path: <stpeter@stpeter.im>
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 0334D11E8178 for <hybi@ietfa.amsl.com>; Wed, 15 Jun 2011 16:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level:
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 vEEkJaOt86Uy for <hybi@ietfa.amsl.com>; Wed, 15 Jun 2011 16:08:57 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 644E611E80A0 for <hybi@ietf.org>; Wed, 15 Jun 2011 16:08:57 -0700 (PDT)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 95631400A5; Wed, 15 Jun 2011 17:09:19 -0600 (MDT)
Message-ID: <4DF93B86.7050704@stpeter.im>
Date: Wed, 15 Jun 2011 17:08:54 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
References: <4DF91FCA.8060403@stpeter.im> <BANLkTinBEprfvY7oRu6_ZeiX4ei0rS5GjA@mail.gmail.com>
In-Reply-To: <BANLkTinBEprfvY7oRu6_ZeiX4ei0rS5GjA@mail.gmail.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030002040103030105040808"
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:08:58 -0000

On 6/15/11 5:03 PM, Iñaki Baz Castillo wrote:
> 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?

Not if you wrote that SRV spec!

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?

Peter

-- 
Peter Saint-Andre
https://stpeter.im/