IETF Logo Mail Archive

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

Roy Marples <roy@marples.name> Thu, 05 December 2019 15:13 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 B30A012002E for <v6ops@ietfa.amsl.com>; Thu, 5 Dec 2019 07:13:40 -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=ham 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 w3IWDoLHfCTt for <v6ops@ietfa.amsl.com>; Thu, 5 Dec 2019 07:13:39 -0800 (PST)
Received: from relay2.marples.name (relay2.marples.name [IPv6:2a00:da00:1800:80d6::1]) (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 2CD02120025 for <v6ops@ietf.org>; Thu, 5 Dec 2019 07:13:39 -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 DC86879B for <v6ops@ietf.org>; Thu, 5 Dec 2019 15:13:37 +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 9E7821CD5DA; Thu, 5 Dec 2019 15:12:37 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marples.name; s=mail; t=1575558757; 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=UAbQFsqWJyu7j0Y+A1//kUarPhGp7u2W6VgOUEk+010=; b=QuQvxANNMdOdDXRP5Gf2RyxJVsLgxMfu9dJlTNKkWbJs9FZiHOf/ebTvQYU3vnLG6AIaPq WK8NctEaa3d0ObAJ4AnApImr7pBqwuC6OO9a+17Y3AeGh+jZ8Ew6lygXDFcYEW4noY9Vu9 MMr31QD4KzdExrH0uYT6NtwOAsGAcp4=
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Cc: "<mohamed.boucadair@orange.com>" <mohamed.boucadair@orange.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, V6 Ops List <v6ops@ietf.org>, Bjørn Mork <bjorn@mork.no>, "draft-link-dhc-v6only@ietf.org" <draft-link-dhc-v6only@ietf.org>
References: <CAFU7BAR1JLUZps=CAqJfeQtUf-xQ88RYvgYrPCP+QP0Ter7YFg@mail.gmail.com> <8736e0gqu2.fsf@miraculix.mork.no> <787AE7BB302AE849A7480A190F8B9330313E29BB@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAFU7BARiwGZohd5d-hqUUpH5jzjFerbLGcOBVc+S9BC3OYMFcw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B9330313E41EE@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAKD1Yr2ZuCXWvRGi-hTj3g0A24WHr=ept9CqFx6_mP3vKUcaqA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B9330313E429B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAKD1Yr0PKSyz3Ku6dw_-czqksB1tii_4Oc-9GqP9GG0HBzY+4Q@mail.gmail.com> <c246618e-3624-439c-79de-2ad15841eba7@marples.name> <CAKD1Yr2oQLTfviSQC+jeNmaYZROq31PXnQgoMHrL0DiGa6WWEQ@mail.gmail.com>
From: Roy Marples <roy@marples.name>
Message-ID: <4ebbee15-e3f6-356c-3bb7-53f005dbc162@marples.name>
Date: Thu, 05 Dec 2019 15:13:33 +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: <CAKD1Yr2oQLTfviSQC+jeNmaYZROq31PXnQgoMHrL0DiGa6WWEQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/dFSLA5SqCSA4x_Q2q1btsWnI17E>
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 15:13:41 -0000

On 05/12/2019 15:11, Lorenzo Colitti wrote:
> On Fri, Dec 6, 2019 at 12:01 AM Roy Marples 
> <roy=40marples.name@dmarc.ietf.org 
> <mailto:40marples.name@dmarc.ietf.org>> wrote:
> 
>     IPv4 has built in delays as well.. DHCP delay randomisation and DAD
>     timings via RFC 5227.
>     NetBSD has RFC 5227 in the kernel and works very nicely.
> 
> 
> True. Coincidentally, we've actually been finalizing an implementation 
> <https://android-review.googlesource.com/c/platform/packages/modules/NetworkStack/+/1095791> in 
> the last few weeks. The current client just sends a DISCOVER as soon as 
> it possibly can and takes the first offer it gets.
> 
>     I once saw a PDF that claimed Solaris does the same, although my hands
>     on experience says if it does work it uses timings different from
>     the RFC.
> 
> 
> IIRC we found the RFC timings to be way too long for mobile devices that 
> move between networks often, so we lowered them.

I would be supportive of an RFC to bring the timings/number of probes in 
line with IPv6 DAD as well.

Roy

v2.23.0 | Report a Bug | By Email