IETF Logo Mail Archive

Re: [hybi] DNS SRV for WebSocket

Greg Wilkins <gregw@intalio.com> Sun, 27 March 2011 23:37 UTC

Return-Path: <gregw@intalio.com>
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 8EB863A6986 for <hybi@core3.amsl.com>; Sun, 27 Mar 2011 16:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level:
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[AWL=-0.335, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
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 JmsNnGawB0MU for <hybi@core3.amsl.com>; Sun, 27 Mar 2011 16:37:43 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 623EA3A697E for <hybi@ietf.org>; Sun, 27 Mar 2011 16:37:43 -0700 (PDT)
Received: by vxg33 with SMTP id 33so2203738vxg.31 for <hybi@ietf.org>; Sun, 27 Mar 2011 16:39:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.18.6 with SMTP id s6mr4637825vdd.144.1301269149282; Sun, 27 Mar 2011 16:39:09 -0700 (PDT)
Received: by 10.52.155.71 with HTTP; Sun, 27 Mar 2011 16:39:09 -0700 (PDT)
In-Reply-To: <BANLkTi=G6bc=FquLM8agKWojmDkD9FohxA@mail.gmail.com>
References: <BANLkTi=G6bc=FquLM8agKWojmDkD9FohxA@mail.gmail.com>
Date: Mon, 28 Mar 2011 10:39:09 +1100
Message-ID: <AANLkTikiiAMfS-zU=cEgNBh0E7MmyixtSuAOyZ5-OkAV@mail.gmail.com>
From: Greg Wilkins <gregw@intalio.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] DNS SRV for WebSocket
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: Sun, 27 Mar 2011 23:37:44 -0000

I agree it would be good to have websockets somehow support DNS loadbalancing.

However, I do know that we have been very concerned to reduce the
latency needed to establish a WS connection and I'd be concerned if
every normal WS connection would now be delayed by an extra DNS lookup
time.   I'd also not like to make it mandatory that clients have to
support it.

Would it be practicable to only support this if the client used
_ws._tcp.mydomain.org as the hostname in the WS connection?  If they
used www.mydomain.org, then normal DNS processing would take place?

cheers

v2.23.0 | Report a Bug | By Email