Re: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Mon, 22 October 2018 17:24 UTC

Return-Path: <pch-bCE2691D2@u-1.phicoh.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53468130EDF for <ipv6@ietfa.amsl.com>; Mon, 22 Oct 2018 10:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 dZ__iNtzu0nL for <ipv6@ietfa.amsl.com>; Mon, 22 Oct 2018 10:24:47 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2A67130E36 for <ipv6@ietf.org>; Mon, 22 Oct 2018 10:24:45 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1gEdwZ-0000FjC; Mon, 22 Oct 2018 19:24:43 +0200
Message-Id: <m1gEdwZ-0000FjC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-bCE2691D2@u-1.phicoh.com
References: <153973137181.9473.10666616544238076833@ietfa.amsl.com> <092346e1-6350-e54e-e711-9c5ee6dc4e6b@gmail.com> <4a883ed6-c0d7-5d3f-9657-3ba0476919e0@foobar.org> <6952EE88-B3D6-48BC-ACFF-C5248965EDC9@employees.org> <61706f85-cf3a-1a03-0371-30fe3eaaec6f@foobar.org> <2afa8333-fad3-3a26-0466-2ed3bd1e0c9c@gmail.com> <3F8BCD30-DEE4-44B8-BF45-CAB75F21B11A@jisc.ac.uk> <m1gEbZ3-0000IBC@stereo.hq.phicoh.net> <alpine.DEB.2.20.1810221800240.26856@uplift.swm.pp.se>
In-reply-to: Your message of "Mon, 22 Oct 2018 18:04:48 +0200 (CEST) ." <alpine.DEB.2.20.1810221800240.26856@uplift.swm.pp.se>
Date: Mon, 22 Oct 2018 19:24:41 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/tHS2464zbWloNN7OvkJIvyY2C7Y>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2018 17:24:55 -0000

>How many heard about this for the first time during that lightning talk 
>and had an informed idea about this? How many do even run IPv6 at all? On 
>wifi where this is most important probably?

This draft was also mentioned in the IPv6 WG. Typically there are quite a few
people going to IPv6 WG sessions, though of course it is hard to say
how many of them are actually running IPv6.

>What I would like to hear is from wifi experts, how much does the IPv4 
>broadcast traffic cause problems in large wifi deployments? Arena settings 
>for instance?

Maybe we can turn this around and ask the wifi experts to compare this draft
to the DHCPv4 option and ether type filtering to see if this draft actually
saves enough that mobile device vendors would actually implement it.

This draft contains the most vague hand waving: 
"It may result in an undesirable level [...]" What's the real number if
you employ ether type filtering?
"In particular, this may overload switches [...]" How is that ever going
to happen?

If this is a real operational problem, then maybe somebody can measure it,
write an article and a future draft can reference the article.

This draft is pointless if host operating systems ignore it. And right now,
ignoring this draft does seem to be the most sensible approach.