[dhcwg] Martin Duke's Discuss on draft-ietf-dhc-v6only-05: (with DISCUSS and COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Wed, 29 July 2020 23:01 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 09ECD3A094F; Wed, 29 Jul 2020 16:01:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dhc-v6only@ietf.org, dhc-chairs@ietf.org, dhcwg@ietf.org, Bernie Volz <volz@cisco.com>, volz@cisco.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.12.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <159606370302.11342.6386305944714261698@ietfa.amsl.com>
Date: Wed, 29 Jul 2020 16:01:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/TxBx8Y67bGkRTWH1zlSUsO9Pitw>
Subject: [dhcwg] Martin Duke's Discuss on draft-ietf-dhc-v6only-05: (with DISCUSS and COMMENT)
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: Wed, 29 Jul 2020 23:01:43 -0000

Martin Duke has entered the following ballot position for
draft-ietf-dhc-v6only-05: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dhc-v6only/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Not so much an objection, but a question:

What would happen if, in response to a DHCPDISCOVER with the IPv6-only offer,
an attacker spoofed a DHCPOFFER with this option and a V6ONLY_WAIT value of
UINT32_MAX, when in fact there was no NAT64, or v6 capability, at all? Would
the very long timeout amplify existing DoS attacks on DHCP?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

This seems like an important stepping stone to v6 adoption, so thanks.

Sec 3.1 In client-generated messages, what is in the "Value field"? I presume
this is one of those "client MUST set to zero and server MUST ignore" cases?

Sec 3.3
"If the client then
   issues a DHCPREQUEST for the address, the server MUST process it per
   [RFC2131], including replying with a DHCPACK for the address if in
   the meantime it has not been committed to another client."

What if it HAS been committed to another client? What then?