IETF Logo Mail Archive

Re: [dhcwg] Alvaro Retana's No Objection on draft-ietf-dhc-v6only-06: (with COMMENT)

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 11 August 2020 21:21 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 72B193A0CF2; Tue, 11 Aug 2020 14:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 fyAQOGdt77YO; Tue, 11 Aug 2020 14:21:14 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F7F63A0C82; Tue, 11 Aug 2020 14:21:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id A15F7389AF; Tue, 11 Aug 2020 17:00:27 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 33My7N70LwhK; Tue, 11 Aug 2020 17:00:26 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id AC2B9389A2; Tue, 11 Aug 2020 17:00:26 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 54C18430; Tue, 11 Aug 2020 17:21:11 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alvaro Retana <aretana.ietf@gmail.com>, The IESG <iesg@ietf.org>, draft-ietf-dhc-v6only@ietf.org, dhcwg@ietf.org, dhc-chairs@ietf.org
In-Reply-To: <CAFU7BASdBLDJu95SEHko=Euih5+zrPKrfwdSn+P99sdS5KPQNQ@mail.gmail.com>
References: <159709259716.21004.16588247748099066521@ietfa.amsl.com> <CAFU7BASdBLDJu95SEHko=Euih5+zrPKrfwdSn+P99sdS5KPQNQ@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 11 Aug 2020 17:21:11 -0400
Message-ID: <12638.1597180871@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/rwvmA8FKIGoydEe-t7EvW5i3N98>
Subject: Re: [dhcwg] Alvaro Retana's No Objection on draft-ietf-dhc-v6only-06: (with COMMENT)
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: Tue, 11 Aug 2020 21:21:17 -0000

Jen Linkova <furry13@gmail.com> wrote:
    > Long-term it would be much cleaner and more desirable for the server
    > to respond with 0.0.0.0 - therefore SHOULD here.
    > However there are two issues with this:
    > - it would require the server change. I can not deploy this option
    > until my DHCP server code is updated - which would delay the adoption
    > significantly. If we allow the server to return a normal IPv4 address
    > - I can deploy it right now (well, I'm in process actually).

    > - there is evidence that some intermediate devices are not happy with
    > 0.0.0.0 in the DHCPOFFER. While it's a bug - it would block the
    > adoption.

Specifically, that it DHC relays built-in to switching and routing products
are inspecting this return value and doing stuff like linking L2 and L3
addresses together, or other special sauce.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email