Re: [v6ops] [dhcwg] IPv6-Only Preferred DHCPv4 option

Roy Marples <roy@marples.name> Thu, 05 December 2019 01:37 UTC

Return-Path: <roy@marples.name>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 364BC120058 for <v6ops@ietfa.amsl.com>; Wed, 4 Dec 2019 17:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=marples.name
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 fZiXUhUw94wL for <v6ops@ietfa.amsl.com>; Wed, 4 Dec 2019 17:37:01 -0800 (PST)
Received: from relay2.marples.name (relay2.marples.name [77.68.23.143]) (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 B6F26120809 for <v6ops@ietf.org>; Wed, 4 Dec 2019 17:37:01 -0800 (PST)
Received: from mail.marples.name (cpc115040-bour7-2-0-cust370.15-1.cable.virginm.net [81.108.15.115]) by relay2.marples.name (Postfix) with ESMTPS id 4E3C8796 for <v6ops@ietf.org>; Thu, 5 Dec 2019 01:37:00 +0000 (UTC)
Received: from [10.73.1.30] (unknown [10.73.1.30]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.marples.name (Postfix) with ESMTPSA id 6CEF81CD619; Thu, 5 Dec 2019 01:36:03 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marples.name; s=mail; t=1575509763; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2Kx9+dAvmmDll0Rca+VkEIXQS6R9yjXWl43q+reJYoo=; b=kQsIyUEvxWZCKzVzuYbk08P7L9vR/4Q20eBjzdVccFOJLnMRXIKCAvJtpp5jDXWKQRix/7 5yCO49AXegM2eOBA9pqtYhDhXBGp8GRbS24MoTKn9hKY86qxiYtx/qcGB/irR611DDDaVF AoiV89JYV+3qPZzuqyE6wMupWz5aJx4=
To: Mark Smith <markzzzsmith@gmail.com>
Cc: dhcwg@ietf.org, V6 Ops List <v6ops@ietf.org>, draft-link-dhc-v6only@ietf.org
References: <CAFU7BAR1JLUZps=CAqJfeQtUf-xQ88RYvgYrPCP+QP0Ter7YFg@mail.gmail.com> <da078a21-b606-f0d9-3833-d66b20410853@marples.name> <CAO42Z2ySBsazGTE-RqwgLO8SAVzttqaFKQU3d5ttFL8+7te6mg@mail.gmail.com>
From: Roy Marples <roy@marples.name>
Message-ID: <6f8f4dbc-2f61-3aa9-16e9-cc6e6b11d246@marples.name>
Date: Thu, 05 Dec 2019 01:36:57 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAO42Z2ySBsazGTE-RqwgLO8SAVzttqaFKQU3d5ttFL8+7te6mg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/rfgc4JanDRGnBzQbDGHFEebfolI>
Subject: Re: [v6ops] [dhcwg] IPv6-Only Preferred DHCPv4 option
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Dec 2019 01:37:04 -0000

On 05/12/2019 01:19, Mark Smith wrote:
> Going by the now almost entire lack of existence of Appletalk, IPX,
> DECNET, XNS, VINES (I haven't seen or heard of any of them in a
> network since 1999),  it's likely IPv6 will be the single network
> layer protocol in the future. Running a single network layer protocol
> is cheaper and easier, which is why those others have gone away (that
> also explains why nearly all links use or emulate (Wifi) Ethernet
> framing, unless they specifically can't).
> 
> IPv6 will have a life, just as IPv4 has had a life, and those other
> past protocols have had a lives. IPv6 is designed to last for much
> longer than almost any of them, centuries most likely, so I don't
> think we shouldn't be worrying about accommodating "IPv8" now at the
> cost of making IPv4 easier to move away from. We don't have any idea
> what "IPv8"'s transition requirements are or what it will even look
> like.

And this affects the wording and intent of my proposal how?

1 client sends DISCOVER with I CAN WORK WITHOUT DHCP ADDRESS option
2 server sends I HAVE NO DHCP ADDRESS option with T2 timer
3 client reads this and will retry in T2 seconds

This satisfies the use case the OP put forward and makes no mention of 
any other protocol than DHCP AND makes things much simpler to actually 
implement.
What did I miss?

Roy