Re: [dhcwg] I-D Action: draft-ietf-dhc-v6only-08.txt

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 17 August 2020 12:40 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78E9A3A1514 for <dhcwg@ietfa.amsl.com>; Mon, 17 Aug 2020 05:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.278
X-Spam-Level:
X-Spam-Status: No, score=-0.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.949, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 JVN8Dho4awM5 for <dhcwg@ietfa.amsl.com>; Mon, 17 Aug 2020 05:40:05 -0700 (PDT)
Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) (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 01BD53A1506 for <dhcwg@ietf.org>; Mon, 17 Aug 2020 05:40:04 -0700 (PDT)
Received: from [IPv6:2a01:e35:2e59:ce10::da3d:a356] (unknown [IPv6:2a01:e35:2e59:ce10::da3d:a356]) by smtp4-g21.free.fr (Postfix) with ESMTP id 1E0EE19F5AB for <dhcwg@ietf.org>; Mon, 17 Aug 2020 14:40:02 +0200 (CEST)
To: dhcwg@ietf.org
References: <159736181150.2650.7599523170218973622@ietfa.amsl.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <690bfa0c-0f82-d668-a7da-f85532630492@gmail.com>
Date: Mon, 17 Aug 2020 14:40:02 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <159736181150.2650.7599523170218973622@ietfa.amsl.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/dhcwg/s3KQ7OAEOe59FTA_WCEvKAaInOo>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-v6only-08.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2020 12:40:07 -0000

Hi,

The draft says:
> IPv6-only mode: a mode of operation when a host acts as an IPv6-only 
> capable host and does not have IPv4 addresses assigned (except that 
> IPv4 link-local addresses [RFC3927] may have been configured).

I disagree with this definition, because of the exception it allows, and
because of using only the term Host.

There is no exception in IPv6-only.  There is no IPv4 address in an
IPv6-only computer, be it link-local or loopback.

In an IPv6-only computer the IPv4 stack is removed altogether from the
running space.  It my reside in a file on the disk, but not in RAM and
not swapped either.  Maybe some IPv4 address might still be present in
'hosts' file but that is on disk too, not in memory.

For example, in Windows, uncheck the IPv4 box from interface properties.
  In BSD remove the IPv4 kernel module.  (in linux it's still impossible
to remove it, and from android too; that makes it that one cant get an
IPv6-only linux-based computer, but that's the way it is today).

I propose the following definition:

IPv6-only mode: a mode of operation of a computer whose IPv4 stack has
been removed from the running space and where IPv6 stack is active.

Alex




Le 14/08/2020 à 01:36, internet-drafts@ietf.org a écrit :
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Dynamic Host
> Configuration WG of the IETF.
> 
> Title           : IPv6-Only-Preferred Option for DHCPv4 Authors
> : Lorenzo Colitti Jen Linkova Michael C. Richardson Tomek Mrugalski 
> Filename        : draft-ietf-dhc-v6only-08.txt Pages           : 14 
> Date            : 2020-08-13
> 
> Abstract: This document specifies a DHCPv4 option to indicate that a
> host supports an IPv6-only mode and is willing to forgo obtaining an
> IPv4 address if the network provides IPv6 connectivity.  It also
> updates RFC2563 to specify the DHCPv4 server behavior when the
> server receives a DHCPDISCOVER not containing the Auto-Configure
> option but containing the new option defined in this document.
> 
> 
> The IETF datatracker status page for this draft is: 
> https://datatracker.ietf.org/doc/draft-ietf-dhc-v6only/
> 
> There are also htmlized versions available at: 
> https://tools.ietf.org/html/draft-ietf-dhc-v6only-08 
> https://datatracker.ietf.org/doc/html/draft-ietf-dhc-v6only-08
> 
> A diff from the previous version is available at: 
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-v6only-08
> 
> 
> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at
> tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at: 
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________ dhcwg mailing list 
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>