Re: [v6ops] Please review the No IPv4 draft

Simon Perreault <simon.perreault@viagenie.ca> Tue, 15 April 2014 13:20 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 826A61A0499 for <v6ops@ietfa.amsl.com>; Tue, 15 Apr 2014 06:20:00 -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 0qj0cHjz-NFW for <v6ops@ietfa.amsl.com>; Tue, 15 Apr 2014 06:19:55 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 860651A01F1 for <v6ops@ietf.org>; Tue, 15 Apr 2014 06:19:55 -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 8AF0F403E0; Tue, 15 Apr 2014 09:19:52 -0400 (EDT)
Message-ID: <534D31F8.6060902@viagenie.ca>
Date: Tue, 15 Apr 2014 09:19:52 -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: Niall O'Reilly <niall.oreilly@ucd.ie>, Lorenzo Colitti <lorenzo@google.com>
References: <534BF5A5.5010609@viagenie.ca> <CAKD1Yr0j5+r6K8APoFageJz2RESKj5vkk10Ybom0p3Vec_G0YQ@mail.gmail.com> <m2k3argftt.wl%Niall.oReilly@ucd.ie>
In-Reply-To: <m2k3argftt.wl%Niall.oReilly@ucd.ie>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/xNfLwYWGHa-rLa_frdGe64oGBC8
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:20:00 -0000

Le 2014-04-15 04:25, Niall O'Reilly a écrit :
>> 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.
> 
>   Why go even that far?  What's wrong with the minimalist solution of
>   just not providing any DHCPv4 service,

...which, from the point of view of the client, is exactly the same as
Lorenzo's suggestion of dropping requests.

>   and leaving the client to
>   pick a link-local IPv4 address?

The host will do that in some cases, but in general DHCPv4 clients will
not simply shut up. They will retry endlessly.

>   Is the noise/signal (stet!) ratio in client-generated traffic already
>   so low that a few DHCPDISCOVERs per client would be noticeable?

Yes. Please see the issues this creates that are listed in section 3 of
our draft.

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