Re: [6lowapp] Fwd: New Version Notification for draft-sturek-6lowapp-smartenergy-00
"zach@sensinode.com" <zach@sensinode.com> Mon, 19 October 2009 20:01 UTC
Return-Path: <zach@sensinode.com>
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 2BBDB3A68BB for <6lowapp@core3.amsl.com>;
Mon, 19 Oct 2009 13:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599]
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 G9tADwZlmBy8 for
<6lowapp@core3.amsl.com>; Mon, 19 Oct 2009 13:01:24 -0700 (PDT)
Received: from smtp-68.nebula.fi (smtp-68.nebula.fi [83.145.220.68]) by
core3.amsl.com (Postfix) with ESMTP id A75153A6825 for <6lowapp@ietf.org>;
Mon, 19 Oct 2009 13:00:48 -0700 (PDT)
Received: from webmail3.nebula.fi (webmail3.nebula.fi [83.145.246.137]) by
smtp-68.nebula.fi (Postfix) with ESMTP id ABAFE43F09AE;
Mon, 19 Oct 2009 23:00:53 +0300 (EEST)
MIME-Version: 1.0
Date: Mon, 19 Oct 2009 23:00:53 +0300
From: "zach@sensinode.com" <zach@sensinode.com>
To: John Mani <jmani@comverge.com>
In-Reply-To: <C70203CF.A67F%jmani@comverge.com>
References: <C70203CF.A67F%jmani@comverge.com>
Message-ID: <426cf1a24e6c6c226668bbda939e6ad9@mailserver13.nebula.fi>
X-Sender: zach@sensinode.com
User-Agent: Nebula Webmail
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="UTF-8"
Cc: 6lowapp@ietf.org
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
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 20:01:25 -0000
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
- [6lowapp] Fwd: New Version Notification for draft… Zach Shelby
- Re: [6lowapp] Fwd: New Version Notification for d… John Mani
- Re: [6lowapp] Fwd: New Version Notification for d… Don Sturek
- Re: [6lowapp] Fwd: New Version Notification for d… John Mani
- Re: [6lowapp] Fwd: New Version Notification for d… zach@sensinode.com
- Re: [6lowapp] Fwd: New Version Notification for d… John Mani
- Re: [6lowapp] Fwd: New Version Notification for d… Hamid Mukhtar