Re: [hybi] About authentication mechanism

Iñaki Baz Castillo <ibc@aliax.net> Thu, 30 June 2011 11:50 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 13D6221F8762 for <hybi@ietfa.amsl.com>; Thu, 30 Jun 2011 04:50:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level:
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[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 z+8sOa4rTKIm for <hybi@ietfa.amsl.com>; Thu, 30 Jun 2011 04:50:10 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 867D721F875C for <hybi@ietf.org>; Thu, 30 Jun 2011 04:50:10 -0700 (PDT)
Received: by qyk29 with SMTP id 29so1584041qyk.10 for <hybi@ietf.org>; Thu, 30 Jun 2011 04:50:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.224.75 with SMTP id in11mr1427979qcb.211.1309434608422; Thu, 30 Jun 2011 04:50:08 -0700 (PDT)
Received: by 10.229.240.15 with HTTP; Thu, 30 Jun 2011 04:50:08 -0700 (PDT)
In-Reply-To: <CAF4kx8fsyrkdJ7TX2+hkMcb=M-TPtbPiLup1OWoxpvKf=FZDOA@mail.gmail.com>
References: <BANLkTinerv=Ua4d-ma+uPVJjF95U1U5iXg@mail.gmail.com> <BANLkTin4mWJgQm+pfyYRs_RhRkdMBfY_Og@mail.gmail.com> <BANLkTiksptqmTWftg7Ur98QQnp22QV7OLA@mail.gmail.com> <BANLkTimw8T4pZieBeCjaPQJ8oYWfbTjkmg@mail.gmail.com> <BANLkTikOzzHF1dGz-2-UwTC0kb2ZQd_0Jw@mail.gmail.com> <BANLkTimCTTCU4UFA7JFuBvDZSFv++UyGCA@mail.gmail.com> <BANLkTinWnTxkCh9BM_utX0=pxzE02DypuA@mail.gmail.com> <BANLkTi=LEOyhagpGZF9gTyLxGuqv5U64wmO_afwaw=eR=pVcPw@mail.gmail.com> <BANLkTinGb38bLyH20Q-QaP2jeDCfgYvENw@mail.gmail.com> <CABLsOLD-EWb=pQ33c9FSU3cu0JTGS5mc2-e5-oq-skfp7rzQhA@mail.gmail.com> <CALiegfnfWwqtWqHZ5GUCWMNdWODnV+fHNhn+fxpL49KQ=Fs8Fw@mail.gmail.com> <BANLkTi=CHoqCaTpBUyjokotR6F6tcfajcNedwQg0_ge0JRUYNQ@mail.gmail.com> <CALiegf=Y-kWG7piRnbDtKeh7Edj11OtQqHVCUq4N2_D1pXG8Qw@mail.gmail.com> <BANLkTim++ywp3fCM8YXuRkH41pUOLqbJZt1JhVdpdUcbJkaVmQ@mail.gmail.com> <CALiegfm8aCsnav51DC=h4DmH+F0DAJUk69D4bbv_0GtvDjw3tw@mail.gmail.com> <CAF4kx8fsyrkdJ7TX2+hkMcb=M-TPtbPiLup1OWoxpvKf=FZDOA@mail.gmail.com>
Date: Thu, 30 Jun 2011 13:50:08 +0200
Message-ID: <CALiegfnDTgq2B1G+qDmsG+Vv1=bcKedhcn-UJbcNHv__JRHSjg@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: ifette@google.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: hybi@ietf.org, Greg Wilkins <gregw@intalio.com>
Subject: Re: [hybi] About authentication mechanism
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: Thu, 30 Jun 2011 11:50:11 -0000

2011/6/30 Ian Fette (イアンフェッティ) <ifette@google.com>om>:
> As for loadbalancing / failover beyond what basic DNS provides, again, this
> isn't required for a base protocol but could easily be specified as an
> extension should the need arise / people wish to do so. HTTP and TCP weren't
> built in a day either.

Hi Ian. DNS SRV does exist but however HTTP makes no usage of it, why?
because HTTP was previous to SRV and because at this time, it's
impossible to expect that all HTTP clients would implement SRV.

If WebSocket protocol is published without mandating DNS SRV
resolution in client side, then adding it into a late extension will
never succeed (as there will be clients not supporting it, so a server
could never rely on SRV resolution from clients).

In other protocols much more complex than WebSocket (as SIP or XMPP),
DNS SRV is defined/mandated in the core protocol, it's not an
extension, so things work.

BTW: http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02

Cheers.



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