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

Brian E Carpenter <> Sun, 01 January 2017 19:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2B6BC1293E9 for <>; Sun, 1 Jan 2017 11:22:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eZG1M5titg0y for <>; Sun, 1 Jan 2017 11:22:46 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400e:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EACAF126B6D for <>; Sun, 1 Jan 2017 11:22:45 -0800 (PST)
Received: by with SMTP id f188so196705971pgc.3 for <>; Sun, 01 Jan 2017 11:22:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=HBi2HKxtnTe9p8OVrRgPQM/DgdxKfNY4JZgBMtXeQqo=; b=a/vcST13Ifn9dIaS983wCUNik2c+Gh7KyWPJjOMdMDpiZwHmSnHHssJE89mEGje24+ LNtwxGpSI74UJckLztDlODikPPSTHE3Pha92T0aE5mmzOFgqS90jrrOpj/jQmFtsOwe7 RAGhi3TJH1GrQiQufqpgSAlsLzrWPH3hOS8zWn3rZhMqc2Eiz6bFWWbygN0cbbL/t4Dk xbc15Lhj4Rb4vl2SyfOecmJPOolx9ZNlnRd+1nZotcDxJ3sxxP323LeLZeas/tMPEwY8 xYaPFyhaDbTNdVcU6rLpvr9GpKc0NPjoG3vxjCAH25F6lz88gd+vfOlMGXxXjFdvmyGC xTgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=HBi2HKxtnTe9p8OVrRgPQM/DgdxKfNY4JZgBMtXeQqo=; b=m/aQVjq4gUI37mLw95YQExUO4SU/U8X3qx3qw1fHW+QmIjr36qK46L+LyA1/n2qNNX oQs+sCQm4TgKbm8oC1k1ZfaHDyFC2e0k+65Iwn7i7sO441wdYDqwRtF0x1mj/CohNu99 x2Xkj/O7h3JXVPhVJk1iKRx9Vw7m2Zf0pSRDX+XEpcMQvhX7/eImUSCIrjUJakmPvLsX 4hvGr4uokQIP4i1lLT81Y/EaqXpNmtDFRIcXBnVb9d37ga7rCJ90sOnXzW0PSeZPNGCU Bm5frqVI4/tGFwqMmq4qsgdWMPzBh4SStTpIbMaQwjzc3Ulm6sveDAF0XHLhKL6ehREf 04XQ==
X-Gm-Message-State: AIkVDXJY2iCgbPzUTjyva7V8fK1RPTkruAXmHD72oyJe+Je5XDQfh4phlgiuMYYpp5YVpA==
X-Received: by with SMTP id u9mr96766932pgb.151.1483298565314; Sun, 01 Jan 2017 11:22:45 -0800 (PST)
Received: from ?IPv6:2406:e007:48a2:1:28cc:dc4c:9703:6781? ([2406:e007:48a2:1:28cc:dc4c:9703:6781]) by with ESMTPSA id s3sm94331138pfg.14.2017. for <> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Jan 2017 11:22:44 -0800 (PST)
Subject: Re: why v6 still isn't ready, was IPv10
References: <> <20161231231811.45008.qmail@ary.lan> <>
From: Brian E Carpenter <>
Organization: University of Auckland
Message-ID: <>
Date: Mon, 2 Jan 2017 08:22:40 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 01 Jan 2017 19:22:47 -0000

On 01/01/2017 17:45, Randy Bush wrote:
>> 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?
> you are confusing coincidence with causality

Indeed. In home networks, small office networks, many campus networks,
and in 3GPP deployment, DHCPv6 isn't a requirement. But in large corporate
networks, and many other campus networks, it is. Android BYOD devices won't
do too well in those. End users might not notice, because they will get 3GPP

I think (unlike Randy?) that having the choice between SLAAC and DHCPv6 is
a fine thing. But hampering DHCPv6 by not having a next-hop router option
is a self-inflicted wound. (And the discussion belongs here, because it
transcends WGs.)