Alternatives to the flag (Was:Confirmation to advance: draft-ietf-6man-ipv6only-flag-05)

David Farmer <farmer@umn.edu> Wed, 15 May 2019 13:28 UTC

Return-Path: <farmer@umn.edu>
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 3253A120312 for <ipv6@ietfa.amsl.com>; Wed, 15 May 2019 06:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 w2syypN7ZBD8 for <ipv6@ietfa.amsl.com>; Wed, 15 May 2019 06:27:58 -0700 (PDT)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (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 485F11202F8 for <ipv6@ietf.org>; Wed, 15 May 2019 06:27:58 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id 8D55CBB9 for <ipv6@ietf.org>; Wed, 15 May 2019 13:27:57 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id meprAcSN3oPu for <ipv6@ietf.org>; Wed, 15 May 2019 08:27:57 -0500 (CDT)
Received: from mail-vk1-f199.google.com (mail-vk1-f199.google.com [209.85.221.199]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id 33D3EB72 for <ipv6@ietf.org>; Wed, 15 May 2019 08:27:57 -0500 (CDT)
Received: by mail-vk1-f199.google.com with SMTP id y204so964869vkd.13 for <ipv6@ietf.org>; Wed, 15 May 2019 06:27:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XRSacZJLInjlh1uD2wuC/8GlI90tDX9xk5t6bjP/tr0=; b=UAd6VPxAiqdQDFK+fcd2ks9iLJCdKa+XpQGboL5gt00jD8L0UT74zJ3SqQ6+u/MCXt UFrCIMmA6hNg7hVH41cwbrZAdTNbtxdFWtFn8lSdRxzKsORPDtD/WNdZ4xGuvOQ4JmOn uzR/vYefbCkQHVj+jaqW35EN+iy+DSOsI/bsw5nN0ucjBol9V6BCQMOIp+VTcDJaK3xZ fdb2G5odX6WbZ/V582PNNs1UF5S9CsBi5YgyztYS9ZIt/gEC6LHcl6vnfa6McyWuPBgg 7KHxlKV7PN95amsuGr4PfUtaFIWdm1bF0hxqRk83uf2BZ0WyTRGCr/UlwakkV0s56Uy3 uDkw==
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=XRSacZJLInjlh1uD2wuC/8GlI90tDX9xk5t6bjP/tr0=; b=Rp2Uf7NX/38ngPLIoDsCMAG4jHKTtlba7cPUgitgvcYkfZErVL56mhHMgMH5jPi8ey nG2LvE5ll3mnlXto7vJ7SLwJZDWrxlXV7mXusIBYS+1S363jS1/ZAgN8N08VKW9LcHAe eboEiRXsIBs7RhL2SuGQAEQ08R3UygYw33pkpVjmZQoMNh6mCWHCFiJNUtSLtmTKxK64 67RkHh6hSkmbmrNIYVUm+dLWH38V316RONsqr1MLMZlUbitdECI4Dchc4gqNGC6yEMT4 BarK1fT8XcRhhVOqXcL04ElJfQl2P7jlVPj0bNcLVH6JYq4MRB5S3iveAHvkrWRuCUMV jCSw==
X-Gm-Message-State: APjAAAWAP1Tg3mfmwrEmSR1l8s4/AqtKgXmzsl/6yiPc9Tw851jShu97 A2k7aXB8d6hEgC/wakOx72y90MFrAnc0/68OplMUmR6VeBlBCQGcadtvM2pJJe/WM6Utl+P/b8u 5RgfRiHhNlb7o3NOjChimiOYl
X-Received: by 2002:a1f:8f0d:: with SMTP id r13mr18194909vkd.63.1557926876021; Wed, 15 May 2019 06:27:56 -0700 (PDT)
X-Google-Smtp-Source: APXvYqzu6InEIWPokVsFn0uvA9DQGwbLCLSy5Le+xxounyXQNCqesY5okkjTuUtJeHQo/XdhycelxK75fKRd7pmCYiw=
X-Received: by 2002:a1f:8f0d:: with SMTP id r13mr18194877vkd.63.1557926875509; Wed, 15 May 2019 06:27:55 -0700 (PDT)
MIME-Version: 1.0
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> <663F6C0B-7B8A-4088-B9C0-B2867B0C3EB8@gmail.com> <CAN-Dau3VJN7qNHAW-yStMrDRCa4vsDs2ObkAxswnYbcHde2t_w@mail.gmail.com> <m1hPqHO-0000J8C@stereo.hq.phicoh.net> <CAN-Dau3R=4JbcbK7tWkJKYzVjq7DvAAEjVsbCLbZdYYO8OJ0YA@mail.gmail.com> <m1hQ7Dm-0000M3C@stereo.hq.phicoh.net> <CAN-Dau040j6U+1CCn0QJiVMy2nVShHqqSFdCkM-FbMAH-2wjRA@mail.gmail.com> <m1hQCYr-0000KBC@stereo.hq.phicoh.net> <CAN-Dau3Lcv3qTBVtig36RfbQKuGpoqdTLfrM=eWfYxCCQRy5Sw@mail.gmail.com> <m1hQfSy-0000LTC@stereo.hq.phicoh.net>
In-Reply-To: <m1hQfSy-0000LTC@stereo.hq.phicoh.net>
From: David Farmer <farmer@umn.edu>
Date: Wed, 15 May 2019 08:27:39 -0500
Message-ID: <CAN-Dau3akjaZ-j16ucOY=-d0nabG4ZdFs6wrSD4EGr3NEh9Wsw@mail.gmail.com>
Subject: Alternatives to the flag (Was:Confirmation to advance: draft-ietf-6man-ipv6only-flag-05)
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Cc: 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000000492a0588ed1e98"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/13Ft0VmRwYYVzZbhm_5Gh-S_S9k>
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, 15 May 2019 13:28:04 -0000

On Tue, May 14, 2019 at 5:00 PM Philip Homburg <
pch-ipv6-ietf-6@u-1.phicoh.com> wrote:

>
> I'm saying that in the context of IPv6 connectivity, RFC 3927 is not needed
> unless explicitly enabled by the user.
>
> So the only change is that in the context of IPv6 it would be off by
> default.
>

Ok, I could live with that. But, when I've heard this kind of thing
discussed before there were serious objections to it. The objections I
remenber heraing were the change you propose effectivly breaks local
printing from a dual-stack host to an IPv4-Only printer if there are any
problems with the local DHCP server.

So, I'm not willing to drop what I think is a viable solution to the
problem unless other stakeholders are willing to buy into this kind of
change. In particular, I'm thinking the people maintaining mDNS in dnssd
wg. I can't see making the change proposed above without their buy-in.

In theory, an IPv4 stack could passively detect the filtering of Ethertype
0x0800 and 0x0806 by passively looking for other ARPs and/or IPv4 service
discovery traffic. However, both of these types of MAC layer broadcast
traffic are typically suppressed on most WiFi networks by the use of proxy
ARP and service discovery proxying or other forms of control or filtering
to limit MAC layer broadcast which is very inefficient on WiFi.  And,
battery-powered WiFi devices is where suppressing the futile IPv4 traffic
is most useful in this whole discussion.

So I think we either need the flag or disable RFC 3927 by default on
dual-stack hosts.

So my question to the WG chair and AD is how do we get input from other
stakeholders on the viability of alternatives to an IPv6-Only flag.

Thanks
-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================