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

Iñaki Baz Castillo <ibc@aliax.net> Sun, 24 July 2011 18:28 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 E065921F8B06; Sun, 24 Jul 2011 11:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level:
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[AWL=0.029, 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 M01ws4Kjq9J9; Sun, 24 Jul 2011 11:28:50 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id B56C121F8B05; Sun, 24 Jul 2011 11:28:49 -0700 (PDT)
Received: by qyk9 with SMTP id 9so662065qyk.10 for <multiple recipients>; Sun, 24 Jul 2011 11:28:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.44.36 with SMTP id y36mr2768805qce.227.1311532129178; Sun, 24 Jul 2011 11:28:49 -0700 (PDT)
Received: by 10.229.185.195 with HTTP; Sun, 24 Jul 2011 11:28:49 -0700 (PDT)
In-Reply-To: <20110724121622.GS22405@1wt.eu>
References: <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> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com> <20110724121622.GS22405@1wt.eu>
Date: Sun, 24 Jul 2011 20:28:49 +0200
Message-ID: <CALiegfkzaMOHBz0-Sgj7HWtQX1jadczDu6t=5PoiNPMG69ZyVg@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Willy Tarreau <w@1wt.eu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
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: Sun, 24 Jul 2011 18:28:51 -0000

2011/7/24 Willy Tarreau <w@1wt.eu>eu>:
>> And I'm really tired of hearing the argument of the "latency" which
>> nobody demostrates (but just talks about it without replying me how
>> the same is not a problem in realtime protocols like SIP and XMPP).
>
> Because you have never worked in a mobile phone environment. You'd be
> amazed to see what end users are paying for ! Count 300-500 ms on average
> for a DNS request.

Well, mobile phone world is a pain due to GPRS/3G internet
connections. But those networks should be improved rather than
assuming that all the Internet must change to work on those infernal
environments (which IMHO are not yet ready for modern internet). All I
see in mobile networks are workarounds.




>> Could you explain me why DNS A is good but DNS SRV is bad in such
>> "anarchic" deployments?
>
> DNS is not mandatory for HTTP. It's not "DNS A" which makes it good, but
> "no mandatory DNS". This is a huge difference.

So, do you mean using URI's with IP rather than domain? (take into
account that TLS connection require the certificate to match the URI
domain, but anyhow it's also possible to use IP's within the
certificate).


Cheers.


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