Re: IPv4 traffic on "ietf-v6ONLY"

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 15 November 2017 11:23 UTC

Return-Path: <alexandre.petrescu@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 F037A124BE8 for <ipv6@ietfa.amsl.com>; Wed, 15 Nov 2017 03:23:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] 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 Ybs7MmDehFGh for <ipv6@ietfa.amsl.com>; Wed, 15 Nov 2017 03:23:23 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 7F2B51200FC for <ipv6@ietf.org>; Wed, 15 Nov 2017 03:23:23 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id vAFBNLvv025987 for <ipv6@ietf.org>; Wed, 15 Nov 2017 12:23:21 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AA6B420374C for <ipv6@ietf.org>; Wed, 15 Nov 2017 12:23:21 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A10F320370B for <ipv6@ietf.org>; Wed, 15 Nov 2017 12:23:21 +0100 (CET)
Received: from [132.166.84.214] ([132.166.84.214]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vAFBNKxu005368 for <ipv6@ietf.org>; Wed, 15 Nov 2017 12:23:21 +0100
Subject: Re: IPv4 traffic on "ietf-v6ONLY"
To: ipv6@ietf.org
References: <f9805855-68cf-a3e8-a13f-c6ac31b09058@gmail.com> <bbd4e1d2-047f-6758-76f8-fd591c51dad7@gmail.com> <D631CE54.8C0F5%lee@asgard.org> <CAFU7BARq033wQ7Uh6_DxiXJ4BR_O7v=jz5yHmNmsjpxsxhOMVg@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <ba6e9127-0e5d-b954-dd4c-5c4d32f45965@gmail.com>
Date: Wed, 15 Nov 2017 12:23:15 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAFU7BARq033wQ7Uh6_DxiXJ4BR_O7v=jz5yHmNmsjpxsxhOMVg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/oN3_dRoAWClSvmxIoxE_YlyTPnY>
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:23:26 -0000


Le 15/11/2017 à 04:08, Jen Linkova a écrit :
> On Wed, Nov 15, 2017 at 1:59 PM, Lee Howard <lee@asgard.org> wrote:
>>>> There is much IPv4 traffic on the "ietf-v6ONLY" ESSID.
>>>
>>> Also on the DNS64 network. But it is all one-way, you
>>> will notice. No replies as far as I can see. Most of them
>>> are sourced from 169.254.*.*, but there are some oddities such as
>>> 31.130.227.98  224.0.0.1       IGMPv2  42      Membership Query, general
>>
>>
>> Does that return us to the question of how to tell hosts that IPv4 doesn’t
>> live here, and to stop trying?
> 
> I do not believe we should be doing this. How do you tell the hosts
> 'Ipv4[] does not live here, stop trying' and why would you
> be doing this when I can just get hosts talk to each other on link
> using IPv6 LLAs?

You could do that with DHCPv4: it has some mechanism to not respod to 
DHCPv4 Request, or to reduce the lifetime, or reply negatively altogether.

You could also invent an ICMPv4 message send by the Router to the 
IPv6-only Host that says: I only do IPv6.

But to avoid the IPv4 LL-addressed traffic I dont know.

Alex

> Or that...I don't know, DECNET, Appletalk or MPLS does not live here?
> 
> 
>>
>>>
>>> I have a couple of Wireshark capture files if anyone cares.
>>>
>>>    Brian
>>>
>>> --------------------------------------------------------------------
>>> 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
>> --------------------------------------------------------------------
> 
> 
>