[hybi] Moving forward: SHOULD use SRV?

Bruce Atherton <bruce@callenish.com> Wed, 27 July 2011 23:56 UTC

Return-Path: <bruce@callenish.com>
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 4D66A21F8B09 for <hybi@ietfa.amsl.com>; Wed, 27 Jul 2011 16:56:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 v1-+oup2NlwD for <hybi@ietfa.amsl.com>; Wed, 27 Jul 2011 16:56:55 -0700 (PDT)
Received: from biz82.inmotionhosting.com (biz82.inmotionhosting.com [173.247.251.126]) by ietfa.amsl.com (Postfix) with ESMTP id DC7AD21F8B08 for <hybi@ietf.org>; Wed, 27 Jul 2011 16:56:55 -0700 (PDT)
Received: from [24.108.144.160] (helo=[192.168.145.10]) by biz82.inmotionhosting.com with esmtpa (Exim 4.69) (envelope-from <bruce@callenish.com>) id 1QmDy0-0000Z7-AS; Wed, 27 Jul 2011 16:56:44 -0700
Message-ID: <4E30A5C6.1070009@callenish.com>
Date: Wed, 27 Jul 2011 16:56:54 -0700
From: Bruce Atherton <bruce@callenish.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz82.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - callenish.com
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: [hybi] Moving forward: SHOULD use SRV?
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, 27 Jul 2011 23:56:56 -0000

> Guys, it feels like you're playing ping-pong here. It's fun for us to
> watch the ball go back and forth, but we're not moving forward. Can you
> see a way to make progress toward consensus?

My read of the situation is that we have established that requiring SRV 
lookups from Websockets clients with the use of MUST is out of the 
question. At least one browser vendor has said they will not implement 
it, and in addition there are the HTTP proxy and connection reuse 
issues. It looks to me like most of the advocates of that position are 
(reluctantly) accepting that it will not be adopted.

OTOH, a number of voices have been raised in support or acceptance of 
recommending the use of SRV records to resolve hostnames in Websocket 
URLs as a best practice through the use of the SHOULD keyword. Others 
(particularly on the ietf mailing list) have said that unless it is a 
MUST you shouldn't bother doing it at all.

Perhaps consensus (or lack of it) on this idea could be looked for at 
the meeting tomorrow.