IETF Logo Mail Archive

Re: IPv4 traffic on "ietf-v6ONLY"

Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com> Wed, 15 November 2017 11:21 UTC

Return-Path: <pch-bCE2691D2@u-1.phicoh.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 9D771124205 for <ipv6@ietfa.amsl.com>; Wed, 15 Nov 2017 03:21:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 GAx0Q0cgxDuS for <ipv6@ietfa.amsl.com>; Wed, 15 Nov 2017 03:21:26 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (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 7AA831200FC for <ipv6@ietf.org>; Wed, 15 Nov 2017 03:21:26 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1eEvku-0000F7C; Wed, 15 Nov 2017 12:21:20 +0100
Message-Id: <m1eEvku-0000F7C@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: IPv4 traffic on "ietf-v6ONLY"
From: Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>
Sender: pch-bCE2691D2@u-1.phicoh.com
References: <f9805855-68cf-a3e8-a13f-c6ac31b09058@gmail.com> <bbd4e1d2-047f-6758-76f8-fd591c51dad7@gmail.com> <D631CE54.8C0F5%lee@asgard.org> , <m1eEvEP-0000G3C@stereo.hq.phicoh.net> <5655992F-737A-4223-A917-63CAD6DF7A1D@cisco.com>
In-reply-to: Your message of "Wed, 15 Nov 2017 11:02:01 +0000 ." <5655992F-737A-4223-A917-63CAD6DF7A1D@cisco.com>
Date: Wed, 15 Nov 2017 12:21:19 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/AqzId_So0iaQxGOPKtnUSq7YAvA>
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: Wed, 15 Nov 2017 11:21:27 -0000

>     Perhaps, define a DHCPv6 option to convey v6-only, for which
>     the client interpretation should be to suppress v4.  Although
>    this will be at the cross road with allowing client's wishes to
>    use v4 LL for whatever useless/useful traffic, it would be a
>    reasonable deployment policy to enforce.

The problem with a DHCPv6 option is that an IPv4-only network may not be
prepared to defend against rogue DHCPv6 servers.

So anyone who starts such a server can kick everybody else of the IPv4 network.

Great option for an overcrowded hotel or conference network.

v2.23.0 | Report a Bug | By Email