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

Alexandre Petrescu <alexandru.petrescu@gmail.com> Tue, 21 November 2017 20:40 UTC

Return-Path: <alexandru.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 07D41129BCD for <ipv6@ietfa.amsl.com>; Tue, 21 Nov 2017 12:40:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 FBtbarDUOnuI for <ipv6@ietfa.amsl.com>; Tue, 21 Nov 2017 12:40:03 -0800 (PST)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (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 D877B1204DA for <ipv6@ietf.org>; Tue, 21 Nov 2017 12:40:02 -0800 (PST)
Received: by mail-wm0-x22a.google.com with SMTP id l188so4310325wma.1 for <ipv6@ietf.org>; Tue, 21 Nov 2017 12:40:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=b19hNQuxu4iBh/4LWIcRtsE/LUcslqcVvsXR423Pem0=; b=WfSPAI0ufLaHg2Cg7jp12zbt/d/KK0LPY/JsPbQ5n9W4wmifhu8LBh43o/wjiRPkLU aN0c4MPqMD8kOO97p+kEyEc/qIYLPBnZEUjV15muPPGiMQRKMflst2cj/nhbeu5QLOG8 DcxRU97X6VOcxIqNujgsBZm0eHh/Wad/xQAprOQvMjDnRfUlmCGcjgnyHTWgNf56nmJw hFYDMeLd4fVQSXXdg3l1DFsr1mWZ4nI01pk50BXDSD0JvxykO36zcepu4uhMCiiDaTWv Ot50oj3xsnjt6dvbABiDOs+QZP7z1s+V8sh6NLJzAC2bWLa8nOJvasl1NJzilhoTyYz8 Se/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=b19hNQuxu4iBh/4LWIcRtsE/LUcslqcVvsXR423Pem0=; b=BEiuF45zQlkthmwjUI6h0F/lHDrJw3p++doKB8MqdzXS8sje8UNXe4BHU+uIf1xXtr oKAC5ILKOr/Foq8FN+/+P3/xDPsM/AZayk2Vl1foTbg2OKHSimkMdPSRmcWgfepu5TpH b3S7BJJUERzr8Ddalj3TSnpk5QP6fGk9RiErqzDMNaki8Bd2TzGj0x7tv6c8zimeA8ZN HOhKE10biHLC6vXnwMsEYrtplLqyyx+RUz/TEtmThv5aB2ZqgcFwYV9N2ImPmfcwItlJ UEsH+K/+q/Z5uS6MGt71JCF9YLjwu30Jbr6c7mcrwAJUuHg5aaZ3bUvHj3UCEp2VcSyk 7l6w==
X-Gm-Message-State: AJaThX766fuBLHrCTCNekbldj7HxMgFmUEZaIb7lPYjWy+m1jJelFIyW WTWROCKJP5v2q6wxtL9h2x+DzQ==
X-Google-Smtp-Source: AGs4zMbvqpYo+6w+m68aHN1ZVN5ZR8NiVRdz7+CrBIuH12wV7rDXdi6gPEul5U0DUREoW2fWd60WfA==
X-Received: by 10.80.182.35 with SMTP id b32mr26821753ede.205.1511296801237; Tue, 21 Nov 2017 12:40:01 -0800 (PST)
Received: from [192.168.1.206] (150.241-136-217.adsl-static.isp.belgacom.be. [217.136.241.150]) by smtp.gmail.com with ESMTPSA id g45sm9690993eda.88.2017.11.21.12.38.49 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Nov 2017 12:40:00 -0800 (PST)
From: Alexandre Petrescu <alexandru.petrescu@gmail.com>
X-Google-Original-From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
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> <5A12FBE4.9030101@foobar.org> <alpine.DEB.2.20.1711210647151.32099@uplift.swm.pp.se> <B8EC63CA-CCD7-4124-A9A5-1A12C65D70F8@employees.org>
Message-ID: <c1cc6d92-e36a-cf8a-4cc9-e5416bd5e158@gmail.com>
Date: Tue, 21 Nov 2017 21:38:32 +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: <B8EC63CA-CCD7-4124-A9A5-1A12C65D70F8@employees.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/CyxTegaZVi-CDAh9ynjl6OfK5Q0>
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: Tue, 21 Nov 2017 20:40:05 -0000

Le 21/11/2017 à 12:39, Ole Troan a écrit :
> We might consider disabling IPv4 on a network in the same fashion
> that we did it for AppleTalk, Apollo Domain, Banyan VINES, DECNet,
> CLNS, XNS, IPX...
> 
> This isn't a new problem.

Let me remember.
When I switched a PC AT 286 from IPX to TCP/IP it was because the latter
gave access to remote servers and persons rather than just big disk on a
local LAN.  Sunsite.doc.ic.ac.uk was important because, among other
things, gave access to RFCs, which IPX LAN server wouldnt.

This would translate today into putting the RFCs and I-Ds on IPv6 only.
(datatracker, tools.ietf.org, etc)  Or the email lists, or the other
services.

Alex

> 
> Ole
> 
>> On 21 Nov 2017, at 06:49, Mikael Abrahamsson <swmike@swm.pp.se>;
>> wrote:
>> 
>> On Mon, 20 Nov 2017, Nick Hilliard wrote:
>> 
>>> It comes down where in your stack you want to put your hacks.  A
>>> sentry
>> 
>> Indeed. And I'd rather put this hack in IPv6, as it requires adding
>> code to configure and send an additional RA option compared to
>> requiring a complete IPv4 stack and DHCPv4 code to send some option
>> there.
>> 
>> In 5-10 years, I might not want an IPv4 stack in a lot of network
>> equipment.
>> 
>> -- Mikael Abrahamsson    email: swmike@swm.pp.se
>> 
>> --------------------------------------------------------------------
>>
>> 
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 
> --------------------------------------------------------------------
>