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

Another requirement - not HAN specific, is support for a low-latency
mechanism to send a message to a large number of HAN devices from a backend
system. An example use case is a Load management system sending a
'load-shed' message to a large subset of its customers for immediate grid
reliability needs. This implies some sort of efficient broadcast/multicast
mechanism.

Not sure if this requirement really belongs here, just wanted to bring this
point up ..

-john

On 10/19/09 1:00 PM, "zach@sensinode.com" <zach@sensinode.com> wrote:

> On Mon, 19 Oct 2009 11:53:51 -0700, John Mani <jmani@comverge.com> wrote:
>> Thanks Don.
>> 
>> Would it be possible to address (and access) an ipv6 end-node over the
>> Internet? Or is there some proxying/address-translation needed at the
>> 'ESP'?
>> I'm just not familiar with how this all can be achieved technically.
> 
> Yes, all IPv6 nodes (also 6LoWPAN ones) can be addressed and accessed. I
> interpret this requirement to mean that you should tunnel IPv6-in-IPv4 over
> 
> whatever IPv4-only parts of the Internet you come across. There are
> probably 
> half a dozen other alternatives as well but that is the most
> straight-forward 
> from my experience.
> 
>> The requirement - as stated currently, might be confusing? When it states
>> "across both back-end systems and embedded networks", I take it to
> include
>> the 'access side of the meter' as well ...
> 
> You are right, should be clearer.
> 
> Zach
>  
>> -john
>> 
>> 
>> On 10/19/09 11:44 AM, "Don Sturek" <d.sturek@att.net> wrote:
>> 
>>> 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
>>> 
>> 
>> _______________________________________________
>> 6lowapp mailing list
>> 6lowapp@ietf.org
>> https://www.ietf.org/mailman/listinfo/6lowapp