Re: [smartpowerdir] Pushing IPv6

Vint Cerf <vint@google.com> Sun, 14 February 2010 19:02 UTC

Return-Path: <vint@google.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 756EE3A7372 for <smartpowerdir@core3.amsl.com>; Sun, 14 Feb 2010 11:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.099
X-Spam-Level:
X-Spam-Status: No, score=-106.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 H4CJKNpL11ZE for <smartpowerdir@core3.amsl.com>; Sun, 14 Feb 2010 11:02:51 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id BA3883A68AC for <smartpowerdir@ietf.org>; Sun, 14 Feb 2010 11:02:50 -0800 (PST)
Received: from kpbe18.cbf.corp.google.com (kpbe18.cbf.corp.google.com [172.25.105.82]) by smtp-out.google.com with ESMTP id o1EJ4HbN008884 for <smartpowerdir@ietf.org>; Sun, 14 Feb 2010 11:04:17 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1266174257; bh=xt1Um2/M+gMuGtFb/2aFXkMz914=; h=Cc:Message-Id:From:To:In-Reply-To:Content-Type: Content-Transfer-Encoding:Mime-Version:Subject:Date:References; b=FRCLGuhXDQ8sKVm0r7YEY05M6KyhwySWy54cvf73qpz4KG5MITTXXidbRxwnI47r9 V4YzFLprL+Sf6kZpjqTEg==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=cc:message-id:from:to:in-reply-to:content-type: content-transfer-encoding:mime-version:subject:date:references:x-mailer:x-system-of-record; b=i2G21O/qyGYYztz88k/13AEEarUbhBBDAJdfd1l/3LPE8n8sIfoOgc9FtDaRxll0T qCcja8TpqQ9j3Ql1ZFr7g==
Received: from iwn5 (iwn5.prod.google.com [10.241.68.69]) by kpbe18.cbf.corp.google.com with ESMTP id o1EJ4FNW017756 for <smartpowerdir@ietf.org>; Sun, 14 Feb 2010 11:04:16 -0800
Received: by iwn5 with SMTP id 5so1101383iwn.9 for <smartpowerdir@ietf.org>; Sun, 14 Feb 2010 11:04:15 -0800 (PST)
Received: by 10.231.152.75 with SMTP id f11mr1938896ibw.50.1266174254696; Sun, 14 Feb 2010 11:04:14 -0800 (PST)
Received: from ?10.0.1.3? (ip68-111-76-185.oc.oc.cox.net [68.111.76.185]) by mx.google.com with ESMTPS id 21sm5498387iwn.14.2010.02.14.11.04.13 (version=SSLv3 cipher=RC4-MD5); Sun, 14 Feb 2010 11:04:13 -0800 (PST)
Message-Id: <C11D8B2F-9DB8-4CC2-BC86-4BB11634E244@google.com>
From: Vint Cerf <vint@google.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <C2988B53-120C-406B-AC36-25D91730A799@cisco.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 14:04:12 -0500
References: <4B635A21.8080900@vigilsec.com> <E50529AC-817E-41AC-91E7-DDA8FA6DB8ED@cisco.com> <38E62E00-85E1-45BA-9262-856C3E8A4DFD@google.com> <C2988B53-120C-406B-AC36-25D91730A799@cisco.com>
X-Mailer: Apple Mail (2.936)
X-System-Of-Record: true
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:02:56 -0000

ack and agree.

v

On Feb 14, 2010, at 2:02 PM, Fred Baker wrote:

> 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
>