[dhcwg] Iotdir last call review of draft-ietf-dhc-v6only-03

Pascal Thubert via Datatracker <noreply@ietf.org> Tue, 23 June 2020 09:55 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 53D103A182E; Tue, 23 Jun 2020 02:55:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pascal Thubert via Datatracker <noreply@ietf.org>
To: <iot-directorate@ietf.org>
Cc: dhcwg@ietf.org, draft-ietf-dhc-v6only.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.3.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <159290613429.20258.90107321879676135@ietfa.amsl.com>
Reply-To: Pascal Thubert <pthubert@cisco.com>
Date: Tue, 23 Jun 2020 02:55:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/lvYSi51Q66_lorscwUVo17nilgU>
Subject: [dhcwg] Iotdir last call review of draft-ietf-dhc-v6only-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Jun 2020 09:55:34 -0000

Reviewer: Pascal Thubert
Review result: Ready with Issues

draft-ietf-dhc-v6only-03 IOT-DIR review

   This document specifies a DHCPv4 option to indicate that a host
   supports an IPv6-only mode and willing to forgo obtaining an IPv4
   address if the network provides IPv6 connectivity. It is very readable
   and provides a clear justification of why the DHCP-based solution is
   well suited to address the problem.

                                             ... IPv6-only mode (either
   because the OS and all applications are IPv6-only capable or because
   the host has some form of 464XLAT [RFC6877] deployed),
   Do we have a good reference of what we mean by the v6-only mode of a host
   - or an interface for that matter ?

   Else it would help to define it before we use it. Note, the terminology
   defines a "IPv6-only capable host" but not the "mode".

   A DHCPv4 client SHOULD allow a device administrator to configure
   IPv6-only preferred mode
   and later
                                 In a typical deployment scenario, a
   network administrator would not configure the DHCPv4 server to return
   the IPv6-only Preferred option unless the network provides NAT64


   However it seems unlikely that any new transition technology would
   arise and be widely adopted in any foreseeable future.  Therefore
   adding support for non-existing technologies seems to be suboptimal
   and the proposed mechanism implies that NAT64 is used to facilitate
   connectivity between IPv6 and IPv4.

   I have a hard time with that one. Adding a byte or 2 of flags in the
   IPv6-Only Preferred option to indicate that the network supports NAT64
   and having the host request the address if it needs the service and it's not
   there does not seem to cost a lot and protects the future.