Re: problem statement [was Re: New Version Notification for draft-hinden-ipv4flag-00.txt]

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 20 November 2017 14:33 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 57A3D129A9C for <ipv6@ietfa.amsl.com>; Mon, 20 Nov 2017 06:33:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 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] 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 Wb9rJX_9N5dw for <ipv6@ietfa.amsl.com>; Mon, 20 Nov 2017 06:33:08 -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 DCFDF126C0F for <ipv6@ietf.org>; Mon, 20 Nov 2017 06:33:07 -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 vAKEX6bb018531 for <ipv6@ietf.org>; Mon, 20 Nov 2017 15:33:06 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 43E1C208810 for <ipv6@ietf.org>; Mon, 20 Nov 2017 15:33:06 +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 31267201952 for <ipv6@ietf.org>; Mon, 20 Nov 2017 15:33:06 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vAKEX5Zc030760 for <ipv6@ietf.org>; Mon, 20 Nov 2017 15:33:06 +0100
Subject: Re: problem statement [was Re: New Version Notification for draft-hinden-ipv4flag-00.txt]
To: ipv6@ietf.org
References: <151090059151.22321.3357672601322845792.idtracker@ietfa.amsl.com> <E838C63E-7612-4AA4-9375-854C184D699E@gmail.com> <CAFU7BAQKoWPcEFQZgU3k_d0gUL4en6d2pyNq1V4RMNZ6HrSG8w@mail.gmail.com> <649be36e-5006-7688-448f-bc2794d6a39c@gmail.com> <CAKD1Yr3WC+vwL_=0PeiJ_D85NqFVTCkb8c83x-ZtGhAbSELGMA@mail.gmail.com> <5A119443.2030108@foobar.org> <CAFU7BASwgLfkO-4kk9-vba_P+jmcFHD5+Hy_7b3cnNkOSv30wg@mail.gmail.com> <CAKD1Yr3pKk22Hkxy4_8YMZYiA4Wwp=6JzdRDKFGdTY1gf=ntfA@mail.gmail.com> <alpine.DEB.2.20.1711200848390.32099@uplift.swm.pp.se>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <05ec66fb-e48f-b891-3c98-12fb5381bf35@gmail.com>
Date: Mon, 20 Nov 2017 15:33:05 +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: <alpine.DEB.2.20.1711200848390.32099@uplift.swm.pp.se>
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/49Bu-4Z0Hk6Nl4oDNv-GY_q1t14>
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: Mon, 20 Nov 2017 14:33:09 -0000


Le 20/11/2017 à 08:51, Mikael Abrahamsson a écrit :
> On Mon, 20 Nov 2017, Lorenzo Colitti wrote:
> 
>> Sure. But you wouldn't need complicated infrastructure for this - if 
>> all that's necessary is to respond to a DHCPv4 request with a canned 
>> "no DHCPv4 here" packet that is always the same, that's a lot easier 
>> to deploy than a full DHCPv4 infrastructure.
> 
> This functionality doesn't exist today in any access network I know of. 

That may not exist, but the counterpart functionality of blocking all 
that is _not_ IPv4 may exist.

On my enterprise IPv4-only network my laptop's RJ45 leds did not even 
blink this morning.  It was because I had unchecked IPv4 on my Windows, 
because I used in the Terminal Room at IETF, which was IPv6 only.

I suppose the switches on my enterprise network block all RJ45 that dont 
reply to IPv4, and block them hardly (RJ45 leds are off).

Same laptop connected to a dumb hub had the leds on.

Alex

[snip]