Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05

Nick Hilliard <nick@foobar.org> Wed, 08 May 2019 10:19 UTC

Return-Path: <nick@foobar.org>
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 3B8C4120172 for <ipv6@ietfa.amsl.com>; Wed, 8 May 2019 03:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 tnoyGgsj2w3t for <ipv6@ietfa.amsl.com>; Wed, 8 May 2019 03:19:42 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67F5612003E for <ipv6@ietf.org>; Wed, 8 May 2019 03:19:42 -0700 (PDT)
X-Envelope-To: ipv6@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id x48AJdJW030620 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 May 2019 11:19:39 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: ipv6@ietf.org
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <a2465e81-a17f-ab48-efda-20fe12a70077@foobar.org> <30239E0C-C444-4A7E-8342-AEE47BF8A2BB@employees.org> <20190505200449.GB7546@vurt.meerval.net> <80073906-c3c0-1f22-9e7f-c2b349063936@gmail.com> <CAO42Z2xzVW3m0mN7jEn8SYyYCYhrufVnkfp3rBjJcijBkvucNQ@mail.gmail.com> <CACWOCC-35yVYXSRR0sRL-MBMHyOFZtJx9E9h14G8qqVh5T7qGA@mail.gmail.com> <232c1a43-0fd9-4eae-737b-260a3906f72a@gmail.com> <51F2BD2A-A590-4AF1-B8C1-FE62C9416340@steffann.nl> <8C63324F-FEF6-40BD-B918-B413CDEF9186@gmail.com> <478d5dc5-af00-4ab0-d8ef-75e41cd501d4@foobar.org> <9eb009ba-234f-ea62-779b-469255543f91@gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <2ac6e5ef-42aa-c6c5-b1b6-73b0a2a9ddec@foobar.org>
Date: Wed, 08 May 2019 11:19:37 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 PostboxApp/6.1.15
MIME-Version: 1.0
In-Reply-To: <9eb009ba-234f-ea62-779b-469255543f91@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/qCp4IEvPy786XGT06D8SPDV_MM8>
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: Wed, 08 May 2019 10:19:45 -0000

Brian E Carpenter wrote on 08/05/2019 00:18:
> Nick, excuse top posting but it seems to me that you are
> assuming that in a managed network, the hosts are all
> managed too.

erm, didn't say this. Didn't even imply it!  :-(

>               That's certainly a false assumption in my
> experienced: managed routers and access points with
> BYOD hosts is a very common scenario.

If you're running a BYOD network which is large enough that you actually 
care about whether people are attempting ipv4, then it probably falls 
into the gigantic l2 domain category, and you should be using the 
management capabilities of the APs to block ethertypes 0x0800 and 
0x0806.  If your APs don't support this functionality, then this is a 
mixture case of using kit which is unfit for purpose and pretending that 
you're running a "managed network" when the reality is that you aren't 
(and no, having a mess of unmanaged l2 behind a competently provisioned 
layer 3 device is not "managed" in any meaningful sense).  If it's not 
large enough to matter, then the flag isn't really relevant anyway.

Nick