Re: IPv4 traffic on "ietf-v6ONLY"

Warren Kumari <warren@kumari.net> Wed, 15 November 2017 11:31 UTC

Return-Path: <warren@kumari.net>
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 7EFBA126B6E for <ipv6@ietfa.amsl.com>; Wed, 15 Nov 2017 03:31:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 XZ7_BNmjXpiv for <ipv6@ietfa.amsl.com>; Wed, 15 Nov 2017 03:31:15 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 BE50D1200FC for <ipv6@ietf.org>; Wed, 15 Nov 2017 03:31:14 -0800 (PST)
Received: by mail-wm0-x230.google.com with SMTP id g141so2307949wmg.2 for <ipv6@ietf.org>; Wed, 15 Nov 2017 03:31:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=z2FhKLR9uscdiReKL2nj0INiWTy4llaSqjYRhAGOuOE=; b=rqUAn1BN27xxiDsz3Sb3dqpw3zQUkXZWM+AcIFMfKlxJ0c9i3JMZFrYAGjsD73nOx+ k3N+cU2bS4uOvYYMko4DlIra0IOYhOMEDdxDlh74E4XdQT9uRvK7JXjWMyiupcWNwK9J vLBYZlsL1COG/rJi41DqJ/vLS/QfIwpzpZmq5Uu6y1NXeilGzP6xL/73RyxCdvJu0qSo XVgvG5vTnwuqPZ6qne8ryaOet4mF/jYs9FYEeKoofcag5PxMJ1iCInZ7ZkiyfYERWYYC 0A84A+mfIGs3rfmN35OQ3umAcn7R7Ie0vfv7yoZqkTJtsgGb/owaMMx/ypoBND+YdPwX 3Wfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=z2FhKLR9uscdiReKL2nj0INiWTy4llaSqjYRhAGOuOE=; b=mPWD+YpA1IFbkd+c4lBX/01BrdveKIKZYFge+XyU7h+IIYTZyxVuCDsVMVJudtaaKm XVPbU+tgDyiqgsFWztoEcHJEBHxRwfVTD0DLvFbM952gElH8dKazIgb33BSIQzZ9SUyP 4OFbB5m4JaRrGxnalZuHMql9OzgiG7djo7p68wYVb5ne5gCnBeKcERAAsUqjWZdhAA0C 8Hz4JeJkDVGBRjGE6xI7oKqFt9UFsNGH+bK2UjlcNzEBwqjvS9KaYfMoRWW9JNNzW2Oy sItFPfQUie4TxNn671NNp2ol6rHsvZrZ522qkBUR84s3lSnhgDo30i7jIcRdjsp29yXV hKQw==
X-Gm-Message-State: AJaThX446fEE/2jfXhYLuMg8q1MI44zHr+mCNrsbvLe+mZ7X1akmW0Ib XplJjSyUqUuzPrsZrWH/XQrpfkot45p9gfw8yPQAQg==
X-Google-Smtp-Source: AGs4zMabU4X3WP1xmA8f8CfbQnlgmx9ebuYpnIQKa72WNgFbYemwjdBPj4gPOyQEtOkIyA0fxDxXp46WT9E2DknRLD4=
X-Received: by 10.28.191.80 with SMTP id p77mr12561392wmf.85.1510745472914; Wed, 15 Nov 2017 03:31:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.160.149 with HTTP; Wed, 15 Nov 2017 03:30:32 -0800 (PST)
In-Reply-To: <5655992F-737A-4223-A917-63CAD6DF7A1D@cisco.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>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 15 Nov 2017 19:30:32 +0800
Message-ID: <CAHw9_iKb8oUP_XzPPCJp1cgBHZeE1aRpGB6UTZS8qvy80KVMig@mail.gmail.com>
Subject: Re: IPv4 traffic on "ietf-v6ONLY"
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
Cc: Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>, "Andrew Yourtchenko (ayourtch)" <ayourtch@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/IP-KlLALxgChdD1Yer-zXhsY7F0>
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:31:16 -0000

On Wed, Nov 15, 2017 at 7:02 PM, Rajiv Asati (rajiva) <rajiva@cisco.com> wrote:
>
> Of course, a DHCPv4 option conflicts with the goal of some people to have
> no IPv4 related infrastructure at all.
>
>
>  Perhaps, define a DHCPv6 option to convey v6-only, for which the client
> interpretation should be to suppress v4.


Can someone remind me what problem we are trying to solve?
W

>
> 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.
>
> We have to remember that allowing this would continue to hurt WLAN (not
> wired LAN) for obvious reasons - radio bandwidth.
>
> During one of ciscolive conferences, i recall having observed lots of
> useless v4 traffic (e.g. discovery) on WLAN.  Andrew (cced) may remember
> more details.
>
> Cheers,
> Rajiv
>
> On Nov 15, 2017, at 5:48 AM, Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>
> wrote:
>
> Does that return us to the question of how to tell hosts that IPv4
>
> doesnt live here, and to stop trying?
>
>
> The safest option to do that is a DHCPv4 option that says 'no IPv4 service
> here, go away'.
>
> Any network that has IPv4 production traffic already has to protect against
> rogue DHCPv4 servers.
>
> Of course, a DHCPv4 option conflicts with the goal of some people to have
> no IPv4 related infrastructure at all.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf