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

Scott Schmit <i.grok@comcast.net> Fri, 22 July 2011 18:26 UTC

Return-Path: <i.grok@comcast.net>
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 B0EFA21F8B27 for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 11:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level:
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hJld3UkNpt6n for <ietf@ietfa.amsl.com>; Fri, 22 Jul 2011 11:26:51 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by ietfa.amsl.com (Postfix) with ESMTP id 1A9DB21F84BF for <ietf@ietf.org>; Fri, 22 Jul 2011 11:26:51 -0700 (PDT)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta02.westchester.pa.mail.comcast.net with comcast id B5xn1h0030Fqzac526Srim; Fri, 22 Jul 2011 18:26:51 +0000
Received: from odin.ulthar.us ([68.33.77.0]) by omta08.westchester.pa.mail.comcast.net with comcast id B6Sa1h01N00PQ6U3U6Sjhz; Fri, 22 Jul 2011 18:26:50 +0000
Received: from odin.ulthar.us (localhost [127.0.0.1]) by odin.ulthar.us (8.14.4/8.14.3) with ESMTP id p6MIQVvA019725 for <ietf@ietf.org>; Fri, 22 Jul 2011 14:26:31 -0400
Received: (from draco@localhost) by odin.ulthar.us (8.14.4/8.14.4/Submit) id p6MIQVqx019724 for ietf@ietf.org; Fri, 22 Jul 2011 14:26:31 -0400
Date: Fri, 22 Jul 2011 14:26:31 -0400
From: Scott Schmit <i.grok@comcast.net>
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
Message-ID: <20110722182631.GB6562@odin.ulthar.us>
Mail-Followup-To: ietf@ietf.org
References: <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> <4E295249.5060700@necom830.hpcl.titech.ac.jp> <20110722123114.GA6562@odin.ulthar.us> <4E298ADA.2060209@necom830.hpcl.titech.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4E298ADA.2060209@necom830.hpcl.titech.ac.jp>
User-Agent: Mutt/1.5.21 (2010-09-15)
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 18:26:51 -0000

On Fri, Jul 22, 2011 at 11:36:10PM +0900, Masataka Ohta wrote:
> Scott Schmit wrote:
> 
> > _http._tcp.example.com. SRV 0 99 80 www.example.com.
> > _http._tcp.example.com. SRV 0 1 80 www-ds.example.com.
> > www.example.com. A 198.0.2.1
> > www-ds.example.com. A 198.0.2.2
> > www-ds.example.com. AAAA 2001:db8::2
> > 
> > I.e., content providers could control/measure their probability of
> > failure.
> 
> Are you saying content providers will actively control their probability
> of failure from 99.99%> to 99% or 99.1% (assuming 10% IPv6 deployment)
> only to promote IPv6?

I'm saying that they can be IPv6-ready without affecting their bottom
line (at least, as they perceive it). Whether they will or not--as you
point out--is another thing altogether, but at least it takes away an
often-used excuse.

Also, I've seen comments along the lines of "I want to phase in the IPv6
traffic" this allows that to happen.

-- 
Scott Schmit