[hybi] New issue: SRV record lookup

Dave Cridland <dave@cridland.net> Mon, 16 August 2010 15:00 UTC

Return-Path: <dave@cridland.net>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05C723A63C9 for <hybi@core3.amsl.com>; Mon, 16 Aug 2010 08:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level:
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id usnw68UYKFrM for <hybi@core3.amsl.com>; Mon, 16 Aug 2010 08:00:31 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id 83A9A3A692C for <hybi@ietf.org>; Mon, 16 Aug 2010 08:00:31 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 25C78116809F for <hybi@ietf.org>; Mon, 16 Aug 2010 16:01:07 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (localhost.localdomain [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQItQPSYngRb for <hybi@ietf.org>; Mon, 16 Aug 2010 16:01:06 +0100 (BST)
Received: from puncture (puncture [217.155.137.60]) by peirce.dave.cridland.net (Postfix) with ESMTPA id 051C7116809E for <hybi@ietf.org>; Mon, 16 Aug 2010 16:01:06 +0100 (BST)
MIME-Version: 1.0
Message-Id: <4931.1281970866.019884@puncture>
Date: Mon, 16 Aug 2010 16:01:06 +0100
From: Dave Cridland <dave@cridland.net>
To: Server-Initiated HTTP <hybi@ietf.org>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
Subject: [hybi] New issue: SRV record lookup
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 16 Aug 2010 15:00:33 -0000

I have a nagging feeling I've mentioned this before buried somewhere  
deep, but...

Our current protocol description piggybacks on HTTP, and is intended  
to be served from (or via) the existing HTTP infrastructure.

This is fine and good, but in practise, I believe we'll see an  
advantage in mid-size deployments to move websocketry off the HTTP  
server entirely. (Huge deployments, like Google, presumably do this  
in infrastructure relatively painlessly).

If we mandate that browsers need to perform SRV lookup with an A  
record fallback, then I believe we'll allow this to happen quite  
easily.

Are there any objections to - at the least - raising this as a new  
issue?

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade