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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 07 May 2019 23:24 UTC

Return-Path: <brian.e.carpenter@gmail.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 5DFF2120103 for <ipv6@ietfa.amsl.com>; Tue, 7 May 2019 16:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 qipgTSdkwAOh for <ipv6@ietfa.amsl.com>; Tue, 7 May 2019 16:24:02 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 D00BD120098 for <ipv6@ietf.org>; Tue, 7 May 2019 16:24:02 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id j26so9073380pgl.5 for <ipv6@ietf.org>; Tue, 07 May 2019 16:24:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=h1JqzGgP4zFRcZPWX5T4zFeCGLgbk8VM65Z2kz7elTs=; b=HigiE6EjnqL55RnrGRdU00QCVZQhcNIg+Ipm5moUaPUODacFmD3r1nnQodGENz04ce KxD6X8ydkYnaySQZlAyMvinVibeSo1/2L6D7j4hvj3WWaKyl7GcpPBfBbbKUI2pux/99 YT8sWbTYyAQ5yFPZvJJCU0f1zRa7cV4vVrfodpkUu+b9N5blAyjcnEksSSnh8BDz9KYq O+a+MQ9xgzILHfInP6tNsUE34MW0vpVhuVqs42s3f//QV8ltC4wDcHnsTit32i+UhgHX P9aPFHd6MF3zJyLltDyypZKjBn7xzOfndnjcvFJIkmywlztZ3nrPt95drSVPBz6gXQEu ez8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=h1JqzGgP4zFRcZPWX5T4zFeCGLgbk8VM65Z2kz7elTs=; b=saaigkMEgn4MKLmBa6o7LRvSy6RKVAoqOiuO8t0g1Ayev9gtsjojbQKXyGTmKAA/Hz 9nK0oypKmO0dTdvzpmm8nHyNBUqRN2FVJ8n0Lbrg2ZgPjnnnvOiFsrmm9X5VOVNv9iV6 +acP0opp3kHUcsjo/x+R/pL8L3oQhijI6fEK+OGBDD3hVRxxnDG3AeUBiO6w6JzegPwP GJvJUkPd4d/bZjKgOtK7yv/N3EwkN7FFS13zeKMSFx+KhqaS0LjKH8oQGcDT76/IVQFN rUb5ossuNAe09j5Ge99Vt7bV+nsOvaNcHiBGMX1z93lgwbVnfKKsDLmi3hyM4zPHxkhC zOdw==
X-Gm-Message-State: APjAAAWeqE1pnnywhW0uGRKYUuJBn3XQWZtuB9zk/jlimLM1n58KMo4F kLPTAi2NARM8viQDGeNYUz46qNYm
X-Google-Smtp-Source: APXvYqxFOQxUwyNjRsKNm5dl+lRUQ1xJWm5WSvUwKaYy09IBrDa9BPo6HYMCQkS/1H8BqveUOUdpEA==
X-Received: by 2002:a63:d04b:: with SMTP id s11mr35520540pgi.187.1557271441971; Tue, 07 May 2019 16:24:01 -0700 (PDT)
Received: from [130.216.36.6] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.36.6]) by smtp.gmail.com with ESMTPSA id p20sm19167024pgh.83.2019.05.07.16.23.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 May 2019 16:24:01 -0700 (PDT)
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
To: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>, David Farmer <farmer@umn.edu>, 6man WG <ipv6@ietf.org>
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <alpine.DEB.2.20.1905070846120.1824@uplift.swm.pp.se> <5bf11ff3fb3b4ba88c33c23521d931e8@boeing.com> <CAN-Dau3BtudB5HM=1u72BExu_64teEDeO7i+aQXhk28Qc2u2vA@mail.gmail.com> <CAN-Dau0Rv3YKg+rmwMK2yDOD0iDi-=bG0uGq0yNMTkLH7nAGBw@mail.gmail.com> <2afb858d1d9e43ffbf8dbef3cf4739f7@boeing.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <0647a519-1c4e-88bd-4254-6fc69f2447b3@gmail.com>
Date: Wed, 08 May 2019 11:23:56 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <2afb858d1d9e43ffbf8dbef3cf4739f7@boeing.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/BfWrWk_EBwzlRZTMVeu52vMQUIY>
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: Tue, 07 May 2019 23:24:05 -0000

> And quite frankly, who cares? In most networks, managed or unmanaged, no one should care.

We've always said that the aim was to save battery (and spectrum) that would otherwise be consumed by useless IPv4 packets, including multicasts. It's certainly a judgment call whether anybody cares.

Regards
   Brian

On 08-May-19 10:49, Manfredi (US), Albert E wrote:
> From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of David Farmer
> 
>> The two alternatives to this flag I've heard discussed are;
>>
>> 1. Layer 2 filtering of Etherthypes 0x0800 and 0x0806
>> 2. RFC2563 to signal host to not use Link-local IPv4
> 
> And/or, do not return A records after DNS queries, switch off DHCPv4 entirely, do not make servers reachable even with statically configured IPv4 addresses, do not allow routers to respond to ARP queries. Let the hosts decide for themselves, how long and hard they want to keep trying to use IPv4. Anyone worried about battery power can certainly take those hints! Those not worried, no problem.
> 
> The intention of this flag, from those who thought it was important, has always been to prevent *all IPv4 traffic*. And yet, that remains unachievable anyway. You, the user, even if on a well-managed enterprise network, in your office or in your lab, can always install your own IPv4-only peripheral device, to reach with your own dual-stack host. So flag or no flag, you won't necessarily achieve this strict IPv6-only goal.
> 
> And quite frankly, who cares? In most networks, managed or unmanaged, no one should care. If you manage an enterprise network, the best you can do is only set up enterprise hosts, servers, and routers, for only IPv6. Employ the measures listed above, and you're as close to being done as you'll ever be. And no new flag needed.
> 
> Hey, whether you create a new flag or not, you will require updated logic in hosts, to save battery power. Let the hosts which care about this update themselves, without needing any new flag, and leave the others be.
> 
> Bert
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>