Re: [smartpowerdir] Pushing IPv6

Fred Baker <fred@cisco.com> Sun, 14 February 2010 19:01 UTC

Return-Path: <fred@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 AF3C03A73D8 for <smartpowerdir@core3.amsl.com>; Sun, 14 Feb 2010 11:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 cNTyK048OfFv for <smartpowerdir@core3.amsl.com>; Sun, 14 Feb 2010 11:01:10 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 891633A7372 for <smartpowerdir@ietf.org>; Sun, 14 Feb 2010 11:01:10 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHbXd0urRN+J/2dsb2JhbACbHXSke5ZbhFsEgxQ
X-IronPort-AV: E=Sophos;i="4.49,472,1262563200"; d="scan'208";a="151295850"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 14 Feb 2010 19:02:37 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1EJ2aM3027553; Sun, 14 Feb 2010 19:02:36 GMT
Message-Id: <C2988B53-120C-406B-AC36-25D91730A799@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Vint Cerf <vint@google.com>
In-Reply-To: <38E62E00-85E1-45BA-9262-856C3E8A4DFD@google.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: Sun, 14 Feb 2010 11:02:35 -0800
References: <4B635A21.8080900@vigilsec.com> <E50529AC-817E-41AC-91E7-DDA8FA6DB8ED@cisco.com> <38E62E00-85E1-45BA-9262-856C3E8A4DFD@google.com>
X-Mailer: Apple Mail (2.936)
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: Sun, 14 Feb 2010 19:01:11 -0000

In my mind, "IP" is the "Internet Protocol", of which we have two  
versions. Various IEC standards tunnel one thing or another through  
UDP/IPv4 or TCP/IPv4; none of them use IPv6. That is two of the issues  
thta have to be handled - native, not tunnel, and permit IPv6.

"...even if they are up for general use of [some Internet Protocol]  
would like to use the [IPv4, which] they have deployed."

On Feb 14, 2010, at 6:08 AM, Vint Cerf wrote:

> Fred,
>
> In your note you use the acronym IP twice. Is the first use Internet  
> Protocol and the second Intellectual Property?
>
> I will make the point in the SGIPGB that if IP is going to be used,  
> it is foolish not to use IPv6 even if one needs to have a device in  
> the home that speaks IPv6 to all the appliances and sensors and IPv4  
> (and IPv6) to the outside world for convenience in the near term.
>
> vint
>
>
> On Feb 14, 2010, at 3:25 AM, Fred Baker wrote:
>
>> My understanding is that politics within the SGIP precluded them  
>> from saying that. One thing we should do is get a better handle on  
>> those politics; I suspect that the Enernex consultant is not  
>> completely unbiased (he champions the idea that the grid has  
>> "points of interoperability" aka gateways in it rather than general  
>> communications interoperability), and there are probably others who  
>> even if they are up for general use of IP would like to use the IP  
>> that they have deployed.
>>
>> On Jan 29, 2010, at 1: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
>>>
>>
>> http://www.ipinc.net/IPv4.GIF
>>
>

http://www.ipinc.net/IPv4.GIF