Re: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)

Simon Hobson <linux@thehobsons.co.uk> Wed, 31 October 2018 15:54 UTC

Return-Path: <linux@thehobsons.co.uk>
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 B3EAD130E34 for <ipv6@ietfa.amsl.com>; Wed, 31 Oct 2018 08:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=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 9LT1LNMhfXk3 for <ipv6@ietfa.amsl.com>; Wed, 31 Oct 2018 08:54:56 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AA45130DDF for <ipv6@ietf.org>; Wed, 31 Oct 2018 08:54:56 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from simons-macbookpro.thehobsons.co.uk (Simons-MacBookPro.thehobsons.co.uk [192.168.137.111]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 3DB0B1BC41 for <ipv6@ietf.org>; Wed, 31 Oct 2018 15:54:51 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <20181031154737.3errng2ifcmmzcve@faui48f.informatik.uni-erlangen.de>
Date: Wed, 31 Oct 2018 15:54:50 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AA151D6-E8C6-40FB-BF2C-C4610C260400@thehobsons.co.uk>
References: <9A4368D6-E4B1-474C-9838-B584AF6D70C8@thehobsons.co.uk> <m1gHUMI-0000I6C@stereo.hq.phicoh.net> <acb0984ec73b40c9a350a0d144b23835@boeing.com> <20181030183416.wfv47m63w5xk3cqe@faui48f.informatik.uni-erlangen.de> <143d790e624d498c91fbf69b070da007@boeing.com> <20181030210020.66dppz77jeowp722@faui48f.informatik.uni-erlangen.de> <87651dfca4694f599e67abbc593f1787@boeing.com> <7FFB03B9-2629-47D1-A3D1-E4FDD6937BC3@thehobsons.co.uk> <CAO42Z2xeqJN3_MSx8Z5cY_kmVDfm-4C7oWKPbnecbC2Fww6UJw@mail.gmail.com> <E74C0E26-87B6-403E-8052-BD6533C1D79B@thehobsons.co.uk> <20181031154737.3errng2ifcmmzcve@faui48f.informatik.uni-erlangen.de>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Wd4H6tf6JVuyFecGnbDPGIO08B4>
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, 31 Oct 2018 15:54:59 -0000

Toerless Eckert <tte@cs.fau.de> wrote:

> I am asserting that routers can can assert whether there are 
> any IPv4 only hosts on the LAN and only when there are none,
> and if the router itself is also not configured to route IPv4
> would it automatically set the v6only flag.

There are TWO really big and in practical terms insurmountable problems there.

Firstly, wanting to deprecate IPv4 (in as far as this flag assists it) is an administrative function. it is not a case of whether there are any IPv4 only devices on the network - as has been mentioned several times, there may well be legacy devices still operating but for most devices "we don't care about being able to talk to them".
If you make this (no IPv4 devices) a pre-condition of setting the flag then it's highly unlikely that you'll ever set it given how many of them there are.

Secondly, an IPv6 only router won't know if there are any IPv4 devices there.