Re: [v6ops] Please review the No IPv4 draft

"Dale W. Carder" <dwcarder@wisc.edu> Thu, 17 April 2014 14:01 UTC

Return-Path: <dwcarder@wisc.edu>
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 E77E31A02E7 for <v6ops@ietfa.amsl.com>; Thu, 17 Apr 2014 07:01:56 -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 gPZlXj6Z_HFs for <v6ops@ietfa.amsl.com>; Thu, 17 Apr 2014 07:01:52 -0700 (PDT)
Received: from smtpauth2.wiscmail.wisc.edu (wmauth2.doit.wisc.edu [144.92.197.222]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4751A0171 for <v6ops@ietf.org>; Thu, 17 Apr 2014 07:01:51 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 8bit
Content-disposition: inline
Content-type: text/plain; charset="utf-8"
Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0N4600B00H4G3H00@smtpauth2.wiscmail.wisc.edu> for v6ops@ietf.org; Thu, 17 Apr 2014 09:01:48 -0500 (CDT)
X-Spam-PmxInfo: Server=avs-2, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.4.17.135119, SenderIP=0.0.0.0
Received: from ricotta.doit.wisc.edu (ricotta.doit.wisc.edu [144.92.67.161]) by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0N4600K6GHMYQX20@smtpauth2.wiscmail.wisc.edu>; Thu, 17 Apr 2014 09:01:48 -0500 (CDT)
Date: Thu, 17 Apr 2014 09:01:46 -0500
From: "Dale W. Carder" <dwcarder@wisc.edu>
To: "George, Wes" <wesley.george@twcable.com>
Message-id: <20140417140145.GF66237@ricotta.doit.wisc.edu>
References: <534BF5A5.5010609@viagenie.ca> <20140415142103.GA50776@ricotta.doit.wisc.edu> <534D4D32.7080001@viagenie.ca> <489D13FBFA9B3E41812EA89F188F018E1AFE5ACB@xmb-rcd-x04.cisco.com> <CF72FB46.18429%wesley.george@twcable.com> <20140416144528.GA62773@ricotta.doit.wisc.edu> <CF75418B.1878F%wesley.george@twcable.com>
In-reply-to: <CF75418B.1878F%wesley.george@twcable.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/vSml6svTzllZnIh1l0GaA7SRnVI
Cc: "v6ops@ietf.org" <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: Thu, 17 Apr 2014 14:01:57 -0000

Thus spake George, Wes (wesley.george@twcable.com) on Thu, Apr 17, 2014 at 08:41:52AM -0400:
> On 4/16/14, 10:45 AM, "Dale W. Carder" <dwcarder@wisc.edu> wrote:
> 
> >Modern enterprise wireless controller
> >networks are way, way more sophisticated than their wired counterparts
> >due to the management of scarce RF time.  So, I don't buy any argument
> >in this draft that there is a problem in this direction.
> 
> A fair point, but this extends beyond simply enterprise networks, and I’m
> not willing to assume that all wireless networks will have a controller,
> modern or otherwise. There are plenty of small and midsize networks that
> are simply one or more APs all strung together on the same LAN. 

It's also worth pointing out that these will be the same networks that 
will be significantly vulnerable to the attack vector opened up by this
draft.  If they are not filtering packets for RF performance, I would
fear that they are not filtering for rogue dhcp packets either.

Dale