Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard

Mark Andrews <marka@isc.org> Fri, 22 July 2011 12:41 UTC

Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D6F221F856A for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 05:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.606
X-Spam-Level:
X-Spam-Status: No, score=-2.606 tagged_above=-999 required=5 tests=[AWL=-0.007, 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 ntzBhSjo0Ohf for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 05:41:39 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA6C21F8513 for <ietf@ietf.org>; Fri, 22 Jul 2011 05:41:39 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id A1FA3C9424; Fri, 22 Jul 2011 12:41:28 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 36D8F216C7B; Fri, 22 Jul 2011 12:41:28 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id CF5F31217044; Fri, 22 Jul 2011 22:41:25 +1000 (EST)
To: Dave Cridland <dave@cridland.net>
From: Mark Andrews <marka@isc.org>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <CALiegfk0zVVRBbOP4ugsVXKmcLnryujP6DZqF6Bu_dC2C3PpeQ@mail.gmail.com> <9031.1311082001.631622@puncture> <CALiegfk_GLAhAf=yEe6hYw2bwtxEwg9aJN+f0Bm9he5QgsRavA@mail.gmail.com> <CAP992=Ft6NwG+rbcuWUP0npwVNHY_znHmXmznBQO_krMo3RT6g@mail.gmail.com> <CALiegfmTWMP3GhS1-k2aoHHXkUkB+eWqV=2+BufuWVR1s2Z-EA@mail.gmail.com> <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <4E28C035.6020009@necom830.hpcl.titech.ac.jp> <9031.1311328268.180517@puncture>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
In-reply-to: Your message of "Fri, 22 Jul 2011 10:51:08 +0100." <9031.1311328268.180517@puncture>
Date: Fri, 22 Jul 2011 22:41:25 +1000
Message-Id: <20110722124125.CF5F31217044@drugs.dv.isc.org>
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2011 12:41:40 -0000

In message <9031.1311328268.180517@puncture>, Dave Cridland writes:
> On Fri Jul 22 01:11:33 2011, Masataka Ohta wrote:
> > Dave Cridland wrote:
> > 
> > > It's proven impossible, despite effort, to retrofit SRV onto HTTP;
> > 
> > Where is a proof?
> 
> Sorry, I've a habit of using the word "proof" in the English (and  
> indeed Welsh) sense of "test" or "trial", rather than the  
> mathematical sense of the statement backed up by logic.
> 
> I should simply say that there have been attempts (I recall more than  
> one draft), but the situation is sufficiently entrenched that these  
> have gained no traction, in no small part because of the requirement  
> for something close to a flag day.

There is no need for a flag day.  If SRV support had been added
when first proposed there would be close to 100% by now.  Browsers
get regularly updated so there really is no reason to not add SRV
support.

The main reason to add SRV support is to provide indirection.

> 1) There are no SRV records.
> 
> 2) Therefore browsers do not support them.
> 
> 3) Therefore you'd need to allow for A-lookup as fallback for the  
> forseeable future.
> 
> 4) Therefore there's no incentive for browsers to support SRV.
>
> 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
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org