IETF Logo Mail Archive

Re: [v6ops] Please review the No IPv4 draft

Simon Perreault <simon.perreault@viagenie.ca> Tue, 15 April 2014 13:36 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 51DCE1A046C for <v6ops@ietfa.amsl.com>; Tue, 15 Apr 2014 06:36:55 -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 LDOGv6IoMPPL for <v6ops@ietfa.amsl.com>; Tue, 15 Apr 2014 06:36:50 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 316031A0430 for <v6ops@ietf.org>; Tue, 15 Apr 2014 06:36:50 -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 44431403E0 for <v6ops@ietf.org>; Tue, 15 Apr 2014 09:36:47 -0400 (EDT)
Message-ID: <534D35EE.3060705@viagenie.ca>
Date: Tue, 15 Apr 2014 09:36:46 -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: v6ops@ietf.org
References: <534BF5A5.5010609@viagenie.ca> <534BFA08.3030404@foobar.org> <49EA8AC9-D5C5-4FE5-9A10-0CD574782F0F@nominum.com> <534C07FC.8000907@foobar.org> <F08AF14D-22C6-4F4C-9388-670EB4CD8453@nominum.com> <F2A0EC2F-6B41-4560-88BA-CEBF3E921B61@delong.com> <091F7BAB-2AAC-41B3-A67C-540482323E71@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1AFE3163@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AFE3163@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/pecXU2H5ZwXolCWQCztG2dkh7LQ
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:36:55 -0000

Le 2014-04-14 16:44, Bernie Volz (volz) a écrit :
> BTW: How significant is the problem anyway? Has this been analyzed by anyone?
> 
> Sure, the clients broadcast these packets but this is the "good" direction in Wifi - the Wifi 'switch' can be told to drop them. Other switches can to?
> 
> Seems to me that this would be far better to leave to the networking infrastructure to just 'block' the DHCPv4 packets if IPv4 isn't enabled?

This doesn't work when the L2 link is shared with clients to which you
do want to provide IPv4 service.

> I suspect many access networks (i.e. DOCSIS - the IP Provisioning Mode TLV) already provide some information about whether v4, v6, or both are available?

That is true, but there's no way to propagate this information to more
hosts in the home. So you end up with DHCP requests eating battery life
in the home. Our draft describes how to propagate the No-IPv4 knowledge
inside the home.

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