IETF Logo Mail Archive

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

<mohamed.boucadair@orange.com> Thu, 05 December 2019 13:24 UTC

Return-Path: <mohamed.boucadair@orange.com>
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 414BD120858; Thu, 5 Dec 2019 05:24:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 Klsol1T01THv; Thu, 5 Dec 2019 05:24:42 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29EA1120170; Thu, 5 Dec 2019 05:24:42 -0800 (PST)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 47TGfH5B7Bz1ydH; Thu, 5 Dec 2019 14:24:39 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.20]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 47TGfH26t7zFpX7; Thu, 5 Dec 2019 14:24:39 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBMA1.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0468.000; Thu, 5 Dec 2019 14:24:39 +0100
From: mohamed.boucadair@orange.com
To: Lorenzo Colitti <lorenzo@google.com>
CC: Jen Linkova <furry13@gmail.com>, Bjørn Mork <bjorn@mork.no>, "dhcwg@ietf.org" <dhcwg@ietf.org>, V6 Ops List <v6ops@ietf.org>, "draft-link-dhc-v6only@ietf.org" <draft-link-dhc-v6only@ietf.org>
Thread-Topic: [dhcwg] IPv6-Only Preferred DHCPv4 option
Thread-Index: AQHVq0wM0EzcIgM90k+qjQhPGFF0raerWiog
Date: Thu, 05 Dec 2019 13:24:38 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330313E4587@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
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>
In-Reply-To: <CAKD1Yr0PKSyz3Ku6dw_-czqksB1tii_4Oc-9GqP9GG0HBzY+4Q@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B9330313E4587OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/NCZ67VnTZb-xFLoOGoLsk93nUsk>
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 13:24:44 -0000

Re-,

Please see inline.

Cheers,
Med

De : Lorenzo Colitti [mailto:lorenzo@google.com]
Envoyé : jeudi 5 décembre 2019 10:12
À : BOUCADAIR Mohamed TGI/OLN
Cc : Jen Linkova; Bjørn Mork; dhcwg@ietf.org; V6 Ops List; draft-link-dhc-v6only@ietf.org
Objet : Re: [dhcwg] IPv6-Only Preferred DHCPv4 option

On Thu, Dec 5, 2019 at 5:58 PM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
IMO, a host will need to “pause” the v4 configuration for xxx ms to make sure the configuration (v4/v6) is consistent.

Hosts do not do this today, and I don't think they will start doing so. The reason is that they cannot tell whether another protocol will start working. If they wait xxx ms to make sure the other protocol comes up, they are slowing down all connections to single-stack networks by xxx ms, making their users unhappy.

[Med] Do you mean that clients that receive the signal to release IPv4 configuration will make the users unhappy anyway because they will need to wait for the pref64 to properly work?

Note that IPv6 has built-in delays in the protocol itself (DAD for the link-local address; various randomized delays) that make it very difficult to get anything done before at least 1-2 seconds have passed. Hosts that know that 70% of networks are IPv4-only will not want to wait 1-2 seconds to connect to those networks.

[Med] In that case, what is the benefit for the host to indicate its ipv6-only mode support?

v2.23.0 | Report a Bug | By Email