Re: [6lowpan] [saag] Follow up on IEEE 802.15 Key Management

Robert Cragie <robert.cragie@gridmerge.com> Fri, 30 September 2011 12:27 UTC

Return-Path: <robert.cragie@gridmerge.com>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E67F521F8A57 for <6lowpan@ietfa.amsl.com>; Fri, 30 Sep 2011 05:27:58 -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=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zIumFnW6R+4D for <6lowpan@ietfa.amsl.com>; Fri, 30 Sep 2011 05:27:58 -0700 (PDT)
Received: from mail78.extendcp.co.uk (mail78.extendcp.co.uk [79.170.40.78]) by ietfa.amsl.com (Postfix) with ESMTP id CB40C21F8B20 for <6lowpan@ietf.org>; Fri, 30 Sep 2011 05:27:53 -0700 (PDT)
Received: from client-82-26-192-102.pete.adsl.virginmedia.com ([82.26.192.102] helo=[192.168.1.80]) by mail78.extendcp.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) id 1R9cEj-0001U0-32 for 6lowpan@ietf.org; Fri, 30 Sep 2011 13:30:41 +0100
Message-ID: <4E85B6F9.4020908@gridmerge.com>
Date: Fri, 30 Sep 2011 13:32:57 +0100
From: Robert Cragie <robert.cragie@gridmerge.com>
Organization: Gridmerge Ltd.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: 6lowpan@ietf.org
References: <4E7CC30C.10305@htt-consult.com> <9F3F4978-B966-4074-B96A-A2C2ED879F6A@yegin.org> <4E83C7A6.4020008@blindcreek.com>
In-Reply-To: <4E83C7A6.4020008@blindcreek.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms050609070705010702060807"
X-Authenticated-As: robert.cragie@gridmerge.com
Subject: Re: [6lowpan] [saag] Follow up on IEEE 802.15 Key Management
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert.cragie@gridmerge.com
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2011 12:27:59 -0000

Actually, the ZigBee Alliance has adopted PANA/EAP for the ZigBee IP 
stack, which is a specification of an IPv6 stack using 6lowpan over 
802.15.4-2006 (not 2003) based on IETF standards. This is independent 
from the SEP 2.0 application profile, which incidentally uses TLS.

At the time of development, there was no EAP transport specified for any 
802.15 standard. The most expedient route for us at the time was to use 
PANA (RFC 5191), which uses UDP datagrams which are accommodated easily 
in 6lowpan without requiring any changes. With addition of the PANA 
relay (RFC 6345), it provides an effective EAP transport, especially 
where the authentication server is not in direct contact with the 
joining node. Any EAP transport for 802.15 networks also needs to take 
this into consideration given the topologies formed in 802.15 networks 
(well, at least 802.15.4)

Robert


On 29/09/2011 2:19 AM, Benjamin A. Rolfe wrote:
> There is an obvious difference in scope:  The scope of the ZigBee SEP 
> profile is specifically Demand
> Response and Load Management applications. ZigBee uses IEEE 
> P802.15.4-2003.  The scope of the referenced PAR includes all current 
> members of the 802.15 family of standards, which includes 5 distinct 
> MAC and PHY standards (soon to be 6).
>
> I'm sure Bob can elaborate further.
>
> Hope that helps.
>
> Regards
>
> -Ben
>
>
>
>
>> Hi Bob,
>>
>> As you know, Zigbee Alliance has already adopted EAP/PANA for network 
>> access authentication and key agreement for Smart Energy Profile 2.0.
>>
>> Is the problem you are seeking to solve the same problem, or a 
>> different one?
>>
>> Thanks.
>>
>> Alper
>>
>>
>>
>>
>>
>> On Sep 23, 2011, at 8:34 PM, Robert Moskowitz wrote:
>>
>>> This week the PAR for KMP passed within 802.15:
>>>
>>> https://mentor.ieee.org/802.15/dcn/11/15-11-0613-03-0kmp-key-management-protocol-par.doc 
>>>
>>> https://mentor.ieee.org/802.15/dcn/11/15-11-0665-03-0kmp-kmp-5c-draft.doc 
>>>
>>>
>>> In the PAR we are requesting the creation of a Recommended Practice 
>>> that will be identified as 802.15.8.
>>>
>>> Next step is to get IEEE 802 approval which will be at the Atlanta 
>>> meeting week prior to IETF.
>>>
>>> For all the current documents for the KMPIG:
>>>
>>> https://mentor.ieee.org/802.15/documents?is_group=0kmp
>>>
>>> In particular
>>>
>>> https://mentor.ieee.org/802.15/dcn/11/15-11-0650-00-0kmp-kmp-for-802-15.ppt 
>>>
>>>
>>> GIves the latest thoughts on how the shim will work and how the 
>>> document will be structured.
>>>
>>> _______________________________________________
>>> saag mailing list
>>> saag@ietf.org
>>> https://www.ietf.org/mailman/listinfo/saag
>> _______________________________________________
>> 6lowpan mailing list
>> 6lowpan@ietf.org
>> https://www.ietf.org/mailman/listinfo/6lowpan
>>
>
> _______________________________________________
> 6lowpan mailing list
> 6lowpan@ietf.org
> https://www.ietf.org/mailman/listinfo/6lowpan
>