Re: [smartpowerdir] Pushing IPv6

JP Vasseur <jvasseur@cisco.com> Mon, 01 February 2010 16:32 UTC

Return-Path: <jvasseur@cisco.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 9D84B3A68AF for <smartpowerdir@core3.amsl.com>; Mon, 1 Feb 2010 08:32:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.79
X-Spam-Level:
X-Spam-Status: No, score=-9.79 tagged_above=-999 required=5 tests=[AWL=0.809, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 6ue+GGCBz2GD for <smartpowerdir@core3.amsl.com>; Mon, 1 Feb 2010 08:32:16 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 2EC8C3A67E3 for <smartpowerdir@ietf.org>; Mon, 1 Feb 2010 08:32:16 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAM6QZkutJV2d/2dsb2JhbADDbpZ6hEUE
X-IronPort-AV: E=Sophos;i="4.49,384,1262563200"; d="scan'208";a="294587889"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by sj-iport-1.cisco.com with ESMTP; 01 Feb 2010 16:32:50 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id o11GWf32024144; Mon, 1 Feb 2010 16:32:50 GMT
Received: from xfe-ams-202.cisco.com ([144.254.231.96]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 1 Feb 2010 17:32:46 +0100
Received: from ams-jvasseur-8712.cisco.com ([10.55.201.131]) by xfe-ams-202.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 1 Feb 2010 17:32:46 +0100
Message-Id: <564A13D1-7E92-42F2-967D-2B3DAE686922@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4B635A21.8080900@vigilsec.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 1 Feb 2010 17:32:44 +0100
References: <4B635A21.8080900@vigilsec.com>
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 01 Feb 2010 16:32:46.0119 (UTC) FILETIME=[2F68B370:01CAA35C]
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: Mon, 01 Feb 2010 16:32:17 -0000

Hi Russ,

You raised a critical point. I think that we should collectively help  
make a clear statement in the direction of IPv6 for SG.
1) Number of addresses: definitely an important aspect, even if these  
networks are not connected to the public Internet. In most SG  
networks, the number of routers/hosts is in the order of millions  
(e.g. smart metering but also primary/secondary/poletop substation  
automation).
2) Autoconf and support of stateless autoconf with v6, ...
3) SGs are mostly made of smart objects ... and all protocols  
developed at the IETF for smart objects are IPv6 protocols ! 6LoWPAN (http://www.ietf.org/dyn/wg/charter/6lowpan-charter.html 
: IPv6 compression over 15.4, fragmentation and re-assembly, ...), RPL  
(http://www.ietf.org/dyn/wg/charter/roll-charter.html) for routing in  
smart object networks (again for smart metering and sub-station  
automation), ... are all IPv6 protocols.

As pointed out by Sam, the level of maturity of IPv6 is some area is  
not equivalent to IPv4 but the protocols are there, vendors are  
aggressively developing v6 applications and starting with v4 is most  
definitely not the right thing to do. We need to remember that the  
scale of these networks is such that the IPv4 would unavoidably  
require complex architectures ...

Cheers.

JP.

On Jan 29, 2010, at 10:58 PM, Russ Housley wrote:

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