Re: [smartpowerdir] Pushing IPv6

Sam Hartman <hartmans@painless-security.com> Sat, 30 January 2010 16:48 UTC

Return-Path: <hartmans@painless-security.com>
X-Original-To: smartpowerdir@core3.amsl.com
Delivered-To: smartpowerdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 945D53A68B0 for <smartpowerdir@core3.amsl.com>; Sat, 30 Jan 2010 08:48:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level:
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KTnFUlndTEGf for <smartpowerdir@core3.amsl.com>; Sat, 30 Jan 2010 08:48:13 -0800 (PST)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id CE5B73A67A6 for <smartpowerdir@ietf.org>; Sat, 30 Jan 2010 08:48:13 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 1587D201C9; Sat, 30 Jan 2010 11:48:40 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3EDE34924; Sat, 30 Jan 2010 11:48:37 -0500 (EST)
From: Sam Hartman <hartmans@painless-security.com>
To: Russ Housley <housley@vigilsec.com>
References: <4B635A21.8080900@vigilsec.com>
Date: Sat, 30 Jan 2010 11:48:37 -0500
In-Reply-To: <4B635A21.8080900@vigilsec.com> (Russ Housley's message of "Fri, 29 Jan 2010 16:58:57 -0500")
Message-ID: <tslmxzv7d3u.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF SmartPower Directorate <smartpowerdir@ietf.org>
Subject: Re: [smartpowerdir] Pushing IPv6
X-BeenThere: smartpowerdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Members of the Smart Power Directorate <smartpowerdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smartpowerdir>, <mailto:smartpowerdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smartpowerdir>
List-Post: <mailto:smartpowerdir@ietf.org>
List-Help: <mailto:smartpowerdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smartpowerdir>, <mailto:smartpowerdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jan 2010 16:48:14 -0000

>>>>> "Russ" == Russ Housley <housley@vigilsec.com> writes:

    Russ> ARIN has sent NIST a message saying that it is not possible to
    Russ> get enough IPv4 addresses to support SmartGrid.  However, the
    Russ> NIST document does not include a statement of preference for
    Russ> IPv6.  How can we make that happen

There's probably a part of this that is political.  However, I've often
found that even when there is a political part to something like this
there is also a part that has to do with uncertainty and fear of the
new.  We've all at some point in our lives pitched some technology that
was not mature enough and we've definitely all received proposals to use
some research technology when we need a production solution today.

I don't have the personal background to address the political aspects of
this, but addressing fear of the unknown seems like something we should
be very good at.

I'll admit that even I'm not 100% convinced that V6 is the answer.  It
seems like you have two potential options: use IPv4 but not the
Internet--accept that to some lesser or greater extent your addressing
plan will overlap with the Internet's and that you'll have a lot of NAT.
Alternatively, use IPv6.  Obviously, the long-term story is better with
V6.  however, there are areas where v6 does not shine today.  I've been
looking at firewall and network management products for one of my
clients, and the v6 story there is not great.

So, an area where we can give technical input and perhaps use our
technical input as a way to get a voice in the political discussion
follows.  We understand what the needs of SG applications are and put
together realistic comments on how well v6 can deal with that today and
how feasible it would be to correct any gaps in the deployment time
line.