IETF Logo Mail Archive

Re: [v6ops] Please review the No IPv4 draft

Simon Perreault <simon.perreault@viagenie.ca> Tue, 15 April 2014 13:18 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B17811A0430 for <v6ops@ietfa.amsl.com>; Tue, 15 Apr 2014 06:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level:
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 VLbIB-cWxfW7 for <v6ops@ietfa.amsl.com>; Tue, 15 Apr 2014 06:18:23 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id C54F11A0499 for <v6ops@ietf.org>; Tue, 15 Apr 2014 06:18:23 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:2520:ef8a:477:622f]) by jazz.viagenie.ca (Postfix) with ESMTPSA id CEE51403E0; Tue, 15 Apr 2014 09:18:20 -0400 (EDT)
Message-ID: <534D319C.3030800@viagenie.ca>
Date: Tue, 15 Apr 2014 09:18:20 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <534BF5A5.5010609@viagenie.ca> <CAKD1Yr0j5+r6K8APoFageJz2RESKj5vkk10Ybom0p3Vec_G0YQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr0j5+r6K8APoFageJz2RESKj5vkk10Ybom0p3Vec_G0YQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/wHa1TbYXrTc4_oVRUD4B7X9gIFE
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Please review the No IPv4 draft
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 15 Apr 2014 13:18:29 -0000

Le 2014-04-15 00:20, Lorenzo Colitti a écrit :
>     In a nutshell, it defines DHCPv6 and RA options indicating to the host
>     that IPv4 is not available. Reviews from operations-minded people in
>     V6OPS would be of tremendous help.
> 
> I don't see a strong use case for this. It seems to me that the two
> scenarios in the introduction can be solved by simply configuring the
> DHCPv4 relay (or the server, if on-link) to drop all DHCPv4 requests.

DHCP clients do not interpret the absence of response as absence of IPv4
service. They will endlessly retry. It is this endless, periodic
retrying that causes the problems we list in section 3.

As an example, ISC dhclient retries every ~2 minutes or so by default.
(From my memory.)

> Am I missing something?

Basically we're trying to make DHCPv4 clients shut up.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

v2.23.0 | Report a Bug | By Email