Re: New Version Notification for draft-hinden-ipv4flag-00.txt

Lorenzo Colitti <lorenzo@google.com> Sat, 18 November 2017 12:52 UTC

Return-Path: <lorenzo@google.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 03B8F126DED for <ipv6@ietfa.amsl.com>; Sat, 18 Nov 2017 04:52:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level:
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 8jqz0_MHstTg for <ipv6@ietfa.amsl.com>; Sat, 18 Nov 2017 04:52:01 -0800 (PST)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 697741200E5 for <ipv6@ietf.org>; Sat, 18 Nov 2017 04:52:01 -0800 (PST)
Received: by mail-io0-x22c.google.com with SMTP id g73so11402350ioj.8 for <ipv6@ietf.org>; Sat, 18 Nov 2017 04:52:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AHjut/L7WKmBEZWdxYSgvYnuA+B4rvXU2QSReEZSD8I=; b=SalRL9V0pKfTy5lT9WXGooI7+U2+jhb9PHSAMulNBulwi4rUMeo3Y5l/OmFlGRXCYK Bho0TLUHeJYKsBuAs0Dys+V4lcH8SwwrAAVOuwrufoe9FnRrxFCNCm0MKsXUrEmx+0hm cLFZepuX/N3Z3sCKaSUflEkHulx1U6KSx8SV4IyuinXPQAMkIIfCnW4Rst9HdqUGmICQ FJY7mxTxG5geOz9Ubc5Ge1F1rsKeJrpFXmhhP/qj9loSmaxP9LBxm51LyPpHaQA35LWF dES1vlcKGzQCQ07ic5z3bzN4k8IB5PC+SDtG/77Efaxhnw6yAJvzKvTJTyt2Vj9WmK2u wl9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AHjut/L7WKmBEZWdxYSgvYnuA+B4rvXU2QSReEZSD8I=; b=VtrMLuQkMq6Ac3LbibDjI1nGmU/iu7/HJTQuDQbBetMVQHdm2E+u6P3FMrLUG5ZgcA 7v6crIRcc8nPSMyTqbIYlplG3DnHAoQbUycDWYAO9/Jl4vaPvV69Cg4wWBQ5lPqoxzyJ 2ZxGjoowg3SaAVNjaYaaVrSmg+XIQsnJUyi+CCq59MPSIiyw55a32Idvx/HG9DCI09Yn vr8UBBHigmRWxPfSEAyd4ERYv/p1Pwua62LGla78YgdX5qOM+ZESfxBGyjC++JyX/QuY xmHrvE97ZlfGNvtTgPDWqpOax2xnqC0KANRDpCg4+valLOiva6Mqh5qQSUWvRxccI/yH 9Xyg==
X-Gm-Message-State: AJaThX4Xu/QtjD9uEodLDBnI9GMFFz4uGbwIkeVf4Mrfk2Cl5ZOFXlEs MOAlBnWaVOWWwk3qzx6VgqWK1KPsgINeF9nBvZlmHCPE
X-Google-Smtp-Source: AGs4zMZaSO4nSNDHJYQi9ezDJw7ais1V/31P4KIGE96t+7sIwpmNBdRaW3HMGCL6kz414ix8hNbX3VXMmZbfN8ty7qg=
X-Received: by 10.107.53.42 with SMTP id c42mr6962241ioa.254.1511009520118; Sat, 18 Nov 2017 04:52:00 -0800 (PST)
MIME-Version: 1.0
References: <151090059151.22321.3357672601322845792.idtracker@ietfa.amsl.com> <E838C63E-7612-4AA4-9375-854C184D699E@gmail.com> <4393db44-6427-5905-c3b4-60a546f88807@gont.com.ar> <0F60023D-9EDA-4C5D-9ABB-27BEAD294780@gmail.com> <5CFC106B-E118-4576-9D0C-F9A59289A7E1@google.com> <05978309-F55F-4E1E-BDCE-B14352FC654E@gmail.com> <79680F90-1F77-4934-9A1A-2B0DE9B43525@google.com> <CAKD1Yr3vqJB9_virMp7+uH2zOYLDM+XNf=L1OihN0DdXzCNobA@mail.gmail.com> <82D69638-7AD1-41B8-A2AD-EE94EAEB5106@thehobsons.co.uk>
In-Reply-To: <82D69638-7AD1-41B8-A2AD-EE94EAEB5106@thehobsons.co.uk>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 18 Nov 2017 12:51:49 +0000
Message-ID: <CAKD1Yr1Ogg9h3YLS=4ivJGrmguEzpe6oWF8+9SRYMfwzSaA4zQ@mail.gmail.com>
Subject: Re: New Version Notification for draft-hinden-ipv4flag-00.txt
To: Simon Hobson <linux@thehobsons.co.uk>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="001a11449a44b366b6055e4151a5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/RcgiI_v36EXawRAGC9zqa3BRA4Y>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 18 Nov 2017 12:52:03 -0000

On Sat, 18 Nov 2017, 20:10 Simon Hobson, <linux@thehobsons.co.uk>; wrote:

> > What about an option that signified there was no IPv4 on the network? If
> the option is sent by any of the routers on the link, then hosts would not
> attempt IPv4 configuration.
>
> Doesn't that come with exactly the same problem as described ? If *ANY*
> router on the network provides IPv6 only, then it'll signal that there's no
> IPv4 on the network even though there may well be.
>

It would be up to the administrator to ensure that no router sent the
option unless the network were truly IPv4-only. So the situation you
describe would be a configuration error.

That would mean that the option could only be used in managed networks.

Not great, I agree.

>