Re: [smartpower-interest] Smart things in stupid networks

"Simpson, Robby (GE Energy Services)" <robby.simpson@ge.com> Thu, 28 July 2011 23:26 UTC

Return-Path: <robby.simpson@ge.com>
X-Original-To: smartpower-interest@ietfa.amsl.com
Delivered-To: smartpower-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8160C11E8165 for <smartpower-interest@ietfa.amsl.com>; Thu, 28 Jul 2011 16:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id texuC1YvcAgu for <smartpower-interest@ietfa.amsl.com>; Thu, 28 Jul 2011 16:26:26 -0700 (PDT)
Received: from exprod5og115.obsmtp.com (exprod5og115.obsmtp.com [64.18.0.246]) by ietfa.amsl.com (Postfix) with ESMTP id 704EF11E80A2 for <smartpower-interest@ietf.org>; Thu, 28 Jul 2011 16:26:25 -0700 (PDT)
Received: from Alpmlip05.e2k.ad.ge.com ([165.156.5.1]) (using TLSv1) by exprod5ob115.postini.com ([64.18.4.12]) with SMTP ID DSNKTjHwICzQ/Ruvl9nQAVAjQwEPLUj7n4vY@postini.com; Thu, 28 Jul 2011 16:26:25 PDT
Received: from unknown (HELO cinmlef12.e2k.ad.ge.com) ([3.159.213.59]) by Alpmlip05.e2k.ad.ge.com with ESMTP; 28 Jul 2011 19:26:24 -0400
Received: from ALPMLVEM04.e2k.ad.ge.com ([3.159.17.51]) by cinmlef12.e2k.ad.ge.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 28 Jul 2011 19:23:20 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 28 Jul 2011 19:26:27 -0400
Message-ID: <E3612E49CE74C64D94240A8AE70324C702E2CDA9@ALPMLVEM04.e2k.ad.ge.com>
In-Reply-To: <001101cc4d50$996b99f0$cc42cdd0$@yegin@yegin.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [smartpower-interest] Smart things in stupid networks
Thread-Index: AcxNFhoicjChTBo0QTWZTEAk6b/bHwAOULVAAAuHNlA=
References: <2607AB8B-3208-4935-B81D-EBA72D6B4E52@cisco.com> <001101cc4d50$996b99f0$cc42cdd0$@yegin@yegin.org>
From: "Simpson, Robby (GE Energy Services)" <robby.simpson@ge.com>
To: "Alper Yegin" <alper.yegin@yegin.org>, "Fred Baker" <fred@cisco.com>, <smartpower-interest@ietf.org>
X-OriginalArrivalTime: 28 Jul 2011 23:23:20.0790 (UTC) FILETIME=[56B5AF60:01CC4D7D]
X-Mailman-Approved-At: Sat, 30 Jul 2011 09:34:39 -0700
Cc: 6man-chairs@tools.ietf.org, tictoc-chairs@tools.ietf.org, core-chairs@tools.ietf.org, lwig-chairs@tools.ietf.org, eman-chairs@tools.ietf.org, opsawg-chairs@tools.ietf.org, homenet-chairs@tools.ietf.org, 6lowpan-chairs@tools.ietf.org, roll-chairs@tools.ietf.org, netconf-chairs@tools.ietf.org
Subject: Re: [smartpower-interest] Smart things in stupid networks
X-BeenThere: smartpower-interest@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Smart Power Interest <smartpower-interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smartpower-interest>, <mailto:smartpower-interest-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smartpower-interest>
List-Post: <mailto:smartpower-interest@ietf.org>
List-Help: <mailto:smartpower-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smartpower-interest>, <mailto:smartpower-interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 23:26:26 -0000

> PANA (RFC 5191) is adopted by Zigbee Alliance Smart Energy Profile 2.0
for
> authenticating devices for network access. PANA Relay introduces a
DHCP-
> like relay operation to PANA. This I-D is in RFC Editor's queue.

Hi Alper -- one clarification.

PANA is used by the ZigBee Alliance's ZigBee IP stack (a collection of
largely, if not exclusively IETF standards to allow IPv6 to work on
802.15.4).  This is different than the Smart Energy Profile 2.0, which
is link-layer agnostic and operates at the application layer.

- Robby