Re: [6lowapp] Fwd: New Version Notification for draft-sturek-6lowapp-smartenergy-00

"Don Sturek" <d.sturek@att.net> Mon, 19 October 2009 18:44 UTC

Return-Path: <d.sturek@att.net>
X-Original-To: 6lowapp@core3.amsl.com
Delivered-To: 6lowapp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EACD28C10E for <6lowapp@core3.amsl.com>; Mon, 19 Oct 2009 11:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level:
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
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 s1PD5liTq4BO for <6lowapp@core3.amsl.com>; Mon, 19 Oct 2009 11:44:17 -0700 (PDT)
Received: from smtp103.sbc.mail.mud.yahoo.com (smtp103.sbc.mail.mud.yahoo.com [68.142.198.202]) by core3.amsl.com (Postfix) with SMTP id 67BF928C0FC for <6lowapp@ietf.org>; Mon, 19 Oct 2009 11:44:17 -0700 (PDT)
Received: (qmail 22591 invoked from network); 19 Oct 2009 18:44:24 -0000
Received: from unknown (HELO Studio) (d.sturek@65.42.208.133 with login) by smtp103.sbc.mail.mud.yahoo.com with SMTP; 19 Oct 2009 18:44:24 -0000
X-YMail-OSG: dWqePTsVM1m2D.GCC5MdlfUPpAkxrJK4jf5HFKQOPCAqMG9l8796HSCx0eY4D_oP0gV0mJS.ZOgvg9kIZ6t60Q0bMRjm74MqgVJhXNNdZCF.xK2_Yw1afZfApY4WpVJ7uBl7u5aW7SjTCgB5DvvdSPEPw59BUyi460LTjvlJwFSAUHpBc7et88.FGPO7TAB_Wq6WX.dOpzOxEVL6.ehcPFrp152o9_cWzIngxj41xvKTU2yFZlLAokE3lMLWecRu_qD7h9xmiBzzZzBpagdwmPA4DvB74F4ix1au5UWgPy8ORv3C81y.J3ZlPzrtNX6XL7_BWyWNG2VEWTlkbr0E8wk.0PTOeYdMypYFIplmjR7rOdGCcg--
X-Yahoo-Newman-Property: ymail-3
From: "Don Sturek" <d.sturek@att.net>
To: "'John Mani'" <jmani@comverge.com>, "'Zach Shelby'" <zach@sensinode.com>, <6lowapp@ietf.org>
References: <4A16D036-F76D-4244-9AF8-0E56AB0075F6@sensinode.com> <C702002E.A675%jmani@comverge.com>
In-Reply-To: <C702002E.A675%jmani@comverge.com>
Date: Mon, 19 Oct 2009 11:44:19 -0700
Message-ID: <012101ca50ec$2b3380e0$819a82a0$@sturek@att.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcpQ61XFC/ebeNAhsUGcjtUChK1LFwAAJp9w
Content-Language: en-us
Subject: Re: [6lowapp] Fwd: New Version Notification for draft-sturek-6lowapp-smartenergy-00
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: d.sturek@att.net
List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowapp>
List-Post: <mailto:6lowapp@ietf.org>
List-Help: <mailto:6lowapp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 18:44:18 -0000

Hi John,

I don't think we should make such a requirement for the access side of the
meter.  I agree with you that using public ISPs will likely mean using IPv4
in many cases.

However, for the HAN we are expecting to use just IPv6 due to the critical
limitation on IPv4 addresses and the desire to do direct addressing.

Don


-----Original Message-----
From: 6lowapp-bounces@ietf.org [mailto:6lowapp-bounces@ietf.org] On Behalf
Of John Mani
Sent: Monday, October 19, 2009 11:38 AM
To: Zach Shelby; 6lowapp@ietf.org
Subject: Re: [6lowapp] Fwd: New Version Notification for
draft-sturek-6lowapp-smartenergy-00

Re: requirement-1 in section 2.1, states that "end-2-end IPv6" is required
across both back-end systems and embedded networks in Smart Energy.

I'm curious if this requirement can be met for an AMI deployment over the
public Internet (not all ISPs support v6 yet ..)

-john


On 10/19/09 6:06 AM, "Zach Shelby" <zach@sensinode.com> wrote:

> Hi,
> 
> We have posted a 6lowapp draft summarizing Smart Energy 2.0 with
> requirements identified for the new working group effort along with
> possible future work. This is just a first draft, and will surely
> still evolve during and after Hiroshima.
> 
> http://www.ietf.org/id/draft-sturek-6lowapp-smartenergy-00.txt
> 
> Zach (on behalf of Don)
> 
> Begin forwarded message:
> 
>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>> Date: October 19, 2009 16:03:50 GMT+03:00
>> To: zach@sensinode.com
>> Cc:  
>>
d.sturek@att.net,Daniel.Lohman@itron.com,Michael.Stuber@itron.com,skip.ashto
n
>> @ember.com
>> Subject: New Version Notification for draft-sturek-6lowapp-
>> smartenergy-00
>> 
>> 
>> A new version of I-D, draft-sturek-6lowapp-smartenergy-00.txt has
>> been successfuly submitted by Zach Shelby and posted to the IETF
>> repository.
>> 
>> Filename:  draft-sturek-6lowapp-smartenergy
>> Revision:  00
>> Title:   Smart Energy Requiements for 6LowApp
>> Creation_date:  2009-10-19
>> WG ID:   Independent Submission
>> Number_of_pages: 12
>> 
>> Abstract:
>> The new Smart Energy (SE) Version 2 (SE 2) is aimed at providing end-
>> to-end connectivity between energy providers, energy consumers, and
>> their respective equipment.  This effort has been recognized as part
>> of the Smart Grid roadmap by the US National Institute of Standards
>> and Technology (NIST).  Whereas SE 1 was based on a proprietary
>> ZigBee stack, SE 2 will is based on IPv6 with support for IEEE
>> 802.15.4, HomePlug and use across the Internet.  The work in 6LowApp
>> on application protocols and commissioning is an important component
>> of SE 2.  This document introduces SE 2 along with requirements
>> identified for 6LowApp and considerations for future work.
>> 
>> 
>> 
>> The IETF Secretariat.
>> 
>> 

_______________________________________________
6lowapp mailing list
6lowapp@ietf.org
https://www.ietf.org/mailman/listinfo/6lowapp