Re: IPv4 traffic on "ietf-v6ONLY"

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 15 November 2017 13:29 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 516EC126DCA for <ipv6@ietfa.amsl.com>; Wed, 15 Nov 2017 05:29:48 -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 plGtLD53KX-i for <ipv6@ietfa.amsl.com>; Wed, 15 Nov 2017 05:29:46 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 37DF6124B17 for <ipv6@ietf.org>; Wed, 15 Nov 2017 05:29:46 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id vAFDTi6q018535 for <ipv6@ietf.org>; Wed, 15 Nov 2017 14:29:44 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7BF10203A89 for <ipv6@ietf.org>; Wed, 15 Nov 2017 14:29:44 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 72037201D7B for <ipv6@ietf.org>; Wed, 15 Nov 2017 14:29:44 +0100 (CET)
Received: from [132.166.84.19] ([132.166.84.19]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vAFDTfwP026763 for <ipv6@ietf.org>; Wed, 15 Nov 2017 14:29:43 +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> <m1eEvEP-0000G3C@stereo.hq.phicoh.net> <5655992F-737A-4223-A917-63CAD6DF7A1D@cisco.com> <CAHw9_iKb8oUP_XzPPCJp1cgBHZeE1aRpGB6UTZS8qvy80KVMig@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <bcebb0db-9092-6147-0a94-1c5c23d71e5d@gmail.com>
Date: Wed, 15 Nov 2017 14:29:40 +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: <CAHw9_iKb8oUP_XzPPCJp1cgBHZeE1aRpGB6UTZS8qvy80KVMig@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/bm1ILpdPcHpBwUurk1oX8zL_Ttk>
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 13:29:48 -0000


Le 15/11/2017 à 12:30, Warren Kumari a écrit :
> 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?

To me, the problem comes mainly from the impossibility to say "IPv6-only".

It's not just a terminology problem.  There are bad side-effects of 
abusing the term "IPv6-only".  Some people claim that IPv6 is there 
already, because there are "IPv6-only" networks.  But there are no 
"IPv6-only" networks at all.  (except in some very rare cases that are 
not visible at IETF nor at mobile network operators.)

Another problem can be related to that wireless network efficiency (too 
many useless IPv4 packets on the air of "ietf-v6ONLY").

The 'noise' problem is symmetric - valid in IPv4 too.  The person at the 
IETF ticketing system tells me I have to go meet them to manually remove 
the DNS Server IPv6 address that the "ietf" SSID has put on my Windows 
and that stays there forever.  That DNS IPv6 address makes noise on my 
corporate IPv4-only network.  I suppose the person does not want me to 
go there at each IETF for that manual operation.  That's a speculation 
of a problem too.  Maybe he has some magic means (a protocol?) that 
makes that the DNS IPv6 address has a lifetime, or so.

Alex

> 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
>> --------------------------------------------------------------------
>>
> 
> 
>