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

"Benjamin A. Rolfe" <ben@blindcreek.com> Thu, 29 September 2011 22:15 UTC

Return-Path: <ben@blindcreek.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 A33DB21F8B3F for <6lowpan@ietfa.amsl.com>; Thu, 29 Sep 2011 15:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.653
X-Spam-Level:
X-Spam-Status: No, score=-1.653 tagged_above=-999 required=5 tests=[AWL=-0.946, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, MISSING_HEADERS=1.292]
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 FQgE5EjXGuqb for <6lowpan@ietfa.amsl.com>; Thu, 29 Sep 2011 15:15:01 -0700 (PDT)
Received: from wilson.nswebhost.com (wilson.nswebhost.com [209.217.228.58]) by ietfa.amsl.com (Postfix) with ESMTP id 73FB221F8B59 for <6lowpan@ietf.org>; Thu, 29 Sep 2011 15:15:01 -0700 (PDT)
Received: from [64.74.213.174] (port=49521 helo=[192.168.250.11]) by wilson.nswebhost.com with esmtpa (Exim 4.69) (envelope-from <ben@blindcreek.com>) id 1R9OvL-0006FS-Lg for 6lowpan@ietf.org; Thu, 29 Sep 2011 17:17:48 -0500
Message-ID: <4E84EE8F.8000708@blindcreek.com>
Date: Thu, 29 Sep 2011 15:17:51 -0700
From: "Benjamin A. Rolfe" <ben@blindcreek.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.20) Gecko/20110804 Lightning/1.0b2 Thunderbird/3.1.12
MIME-Version: 1.0
CC: 6lowpan@ietf.org
References: <4E7CC30C.10305@htt-consult.com> <9F3F4978-B966-4074-B96A-A2C2ED879F6A@yegin.org> <4E83C7A6.4020008@blindcreek.com> <709DC625-A433-4DDC-9505-D9DD7180B93E@yegin.org>
In-Reply-To: <709DC625-A433-4DDC-9505-D9DD7180B93E@yegin.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - wilson.nswebhost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - blindcreek.com
X-Source:
X-Source-Args:
X-Source-Dir:
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
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: Thu, 29 Sep 2011 22:15:02 -0000

I can summarize the 802.15 family; Bob will have to speak specifically 
to the KMP RP and which it will apply to.  Each consists of a distinct 
MAC sub-layer specification and one or more PHY specifications (usually 
more).

802.15.1 - you will probably know it as Bluetooth (802.15.1 where the 
"personal" comes from in WPAN); short range, moderate data rate, small 
networks in both radio SOI and number of devices. Current revision 2005.

802.15.3 - high rate WPAN. The current standard includes a common MAC 
and multiple PHY layers, including a 2.4GHz PHY operating up to 55Mbps, 
and a very high rate (up to 5Gbps) PHYs operating in the 60 GHz (mmWave) 
band.  Also small ROI and modest number of devices.  The very high rate 
is being used in consumer applications such as video transport.   
Initial standard 2003 with amendment 3b published 2005 and amendment 3c 
published 2009.

802.15.4 - LR-WPAN, first publication in 2003 with a simple MAC and 2 
PHYs, one 2.4GHz (OQPSK) and one for the 868 MHz and 915 MHz (BPSK) 
bands. This is the version called out in ZigBee.  Since 2003 there has 
been a major revision that made significant changes to the MAC and two 
new PHYs operating in the 868 and 915 bands: OQPSK and ASK.  Amendment 
4a adds two more PHYs, a UWB PHY in 3 to 10 GHz band, and a CSS PHY in 
2.4GHz; Amendment 4c adds PHYs for operating in the 780MHz band in 
China; Amendment 4d adds a GFSK PHY operating in the 950MHz band in 
Japan. The current revision is P802.15.4-2011 which includes all of the 
above amendments on the 2006 revision.  Currently there are 3 new 
amendments nearing completion:  Task Group (TG) 4e is adding new 
features to the MAC; TG4g is adding three new PHYs and a plethora of 
bands around the world, and is already being used for smart grid and M2M 
applications; TG4f adds 2 new PHYs for RFID applications.   Additional 
TGs are underway defining even more new PHYs expanding the usefulness of 
15.4 even further.  Quite a bit has happened since 2003!

802.15.6 - Body Area Networks (or as I like to call it, very personal 
area networks), with yet another distinct MAC (including security). 
Currently there are 3 PHYs in the draft.   Balloting in progress.

802.15.7 - Visible Light Communications.   Approved in 2011.



-B

> Thank you.
>
> I think it'd be useful for IETF community to understand what those 5/6 distinct standards, and if the KMP being sought would be a generic solution or specific to each one of them. PANA being used for one of them already, I wonder whether it applies to the others or not. Any ideas on that?
>
>
>
>
>
>
>
>
> On Sep 29, 2011, at 4: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
>