IETF Logo Mail Archive

Re: why v6 still isn't ready, was IPv10

"John Levine" <johnl@taugh.com> Sat, 31 December 2016 23:18 UTC

Return-Path: <johnl@taugh.com>
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 EA4001295C1 for <ietf@ietfa.amsl.com>; Sat, 31 Dec 2016 15:18:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WDI_jswJiWRX for <ietf@ietfa.amsl.com>; Sat, 31 Dec 2016 15:18:35 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC56E129444 for <ietf@ietf.org>; Sat, 31 Dec 2016 15:18:34 -0800 (PST)
Received: (qmail 63211 invoked from network); 31 Dec 2016 23:18:33 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 31 Dec 2016 23:18:33 -0000
Date: Sat, 31 Dec 2016 23:18:11 -0000
Message-ID: <20161231231811.45008.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: why v6 still isn't ready, was IPv10
In-Reply-To: <eb7127f9-4f29-325b-11cb-9accdf300b4c@gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JYnAo5i2yECZsjVn3448YQMBSvc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 31 Dec 2016 23:18:36 -0000

>>> It isn't. So what? If that's your requirement, run DHCPv6. Your
>>> Android users can complain to whoever it is that supports Android.
>> 
>> for some silly reason, my customers don't think they pay me for
>> blame shifting.  they just want things to work.
>
>Yes. So not implementing DHCPv6 might be a self-defeating decision
>by an operating system developer, don't you think?

Hmmn, let's take a look at smartphone OS market share (per IDC for
3Q2016)

Windows Phone  0.3%
Apple iOS     12.5%
Android       86.8%

It appears that not implementing DHCPv6 is the key to world
domination.  Next question, please?

R's,
John

v2.23.0 | Report a Bug | By Email