Return-Path: <rgm@labs.htt-consult.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 9A2431F0CAA for <6lowpan@ietfa.amsl.com>;
 Mon, 14 Nov 2011 08:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 NtxjekwBPG64 for
 <6lowpan@ietfa.amsl.com>; Mon, 14 Nov 2011 08:47:48 -0800 (PST)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149])
 by ietfa.amsl.com (Postfix) with ESMTP id 6A3A11F0C73 for <6lowpan@ietf.org>;
 Mon, 14 Nov 2011 08:47:48 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com
 (Postfix) with ESMTP id 866C662ACE; Mon, 14 Nov 2011 16:47:10 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost
 (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id
 6zmaM545ksur; Mon, 14 Nov 2011 11:46:59 -0500 (EST)
Received: from nc2400.htt-consult.com (unknown [203.69.99.17]) (Authenticated
 sender: rgm@labs.htt-consult.com) by klovia.htt-consult.com (Postfix) with
 ESMTPA id BFDF562ABE; Mon, 14 Nov 2011 11:46:58 -0500 (EST)
Message-ID: <4EC145FC.4030601@labs.htt-consult.com>
Date: Tue, 15 Nov 2011 00:46:52 +0800
From: Robert Moskowitz <rgm@labs.htt-consult.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.23) Gecko/20110928 Fedora/3.1.15-1.fc14 Thunderbird/3.1.15
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
References: <4EBD7EC9.4090705@labs.htt-consult.com>
 <7122CCCC-BF56-4A67-B255-DF126BEA495D@yegin.org>
In-Reply-To: <7122CCCC-BF56-4A67-B255-DF126BEA495D@yegin.org>
Content-Type: multipart/alternative;
 boundary="------------050507020807020108020803"
Cc: 6lowpan@ietf.org
Subject: Re: [6lowpan] IEEE 802.15.9 KMP over 802.15.4 and 802.15.7 approved
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: Mon, 14 Nov 2011 16:47:52 -0000

This is a multi-part message in MIME format.
--------------050507020807020108020803
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 11/14/2011 03:17 PM, Alper Yegin wrote:
>
>  Hi Bob,
>
>  This PAR document still does not refer to IETF's PANA (IETF RFC that
>  is already adopted by the Zigbee IP spec.) I'm hoping the PAR changes
>  you are referring are already addressing that. Please let us know.

It was a procedural question as to what is 'wanted' here.  Strictly IEEE 
standards or broader interpretation?  The 802EC clearified that a 
broader inclusion was desired so words have been added to point out that 
Zibgee IP has addressed this within their upper layer.  A 'literal' 
interpretation was that 802.1X does not work over 802.15.4 or 15.7 so 
there was no comparable standard.

Also 802.1 pointed out the need to include the potential need of an 
Registry Authority (6.1b) and that too was added.  The final posted PAR 
will reflect these two changes.

>
>  Thanks.
>
>  Alper
>
>
>  On Nov 11, 2011, at 10:00 PM, Robert Moskowitz wrote:
>
> > The IEEE 802ec approved the PAR this afternoon. The PAR documents
> > are at:
> >
> > 
https://mentor.ieee.org/802.15/dcn/11/15-11-0613-05-0kmp-key-management-protocol-par.doc
> >
> >
https://mentor.ieee.org/802.15/dcn/11/15-11-0665-05-0kmp-kmp-5c-draft.doc
> >
> > We did agree to two procedural changes in the PAR, so there will be
> > a rev 6 posted sometime soon.
> >
> >
> > _______________________________________________ 6lowpan mailing
> > list 6lowpan@ietf.org
> > https://www.ietf.org/mailman/listinfo/6lowpan
>
>


--------------050507020807020108020803
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    On 11/14/2011 03:17 PM, Alper Yegin wrote:<br>
    <span style="white-space: pre;">&gt; <br>
      &gt; Hi Bob,<br>
      &gt; <br>
      &gt; This PAR document still does not refer to IETF's PANA (IETF
      RFC that<br>
      &gt; is already adopted by the Zigbee IP spec.) I'm hoping the PAR
      changes<br>
      &gt; you are referring are already addressing that. Please let us
      know.</span><br>
    <br>
    It was a procedural question as to what is 'wanted' here.&nbsp; Strictly
    IEEE standards or broader interpretation?&nbsp; The 802EC clearified that
    a broader inclusion was desired so words have been added to point
    out that Zibgee IP has addressed this within their upper layer.&nbsp; A
    'literal' interpretation was that 802.1X does not work over 802.15.4
    or 15.7 so there was no comparable standard.<br>
    <br>
    Also 802.1 pointed out the need to include the potential need of an
    Registry Authority (6.1b) and that too was added.&nbsp; The final posted
    PAR will reflect these two changes.<br>
    <br>
    <span style="white-space: pre;">&gt; <br>
      &gt; Thanks.<br>
      &gt; <br>
      &gt; Alper<br>
      &gt; <br>
      &gt; <br>
      &gt; On Nov 11, 2011, at 10:00 PM, Robert Moskowitz wrote:<br>
      &gt; <br>
      &gt;&gt; The IEEE 802ec approved the PAR this afternoon. The PAR
      documents<br>
      &gt;&gt; are at:<br>
      &gt;&gt; <br>
      &gt;&gt;
<a class="moz-txt-link-freetext" href="https://mentor.ieee.org/802.15/dcn/11/15-11-0613-05-0kmp-key-management-protocol-par.doc">https://mentor.ieee.org/802.15/dcn/11/15-11-0613-05-0kmp-key-management-protocol-par.doc</a><br>
      &gt;&gt;<br>
      &gt;&gt; </span><br>
<a class="moz-txt-link-freetext" href="https://mentor.ieee.org/802.15/dcn/11/15-11-0665-05-0kmp-kmp-5c-draft.doc">https://mentor.ieee.org/802.15/dcn/11/15-11-0665-05-0kmp-kmp-5c-draft.doc</a><br>
    <span style="white-space: pre;">&gt;&gt; <br>
      &gt;&gt; We did agree to two procedural changes in the PAR, so
      there will be<br>
      &gt;&gt; a rev 6 posted sometime soon.<br>
      &gt;&gt; <br>
      &gt;&gt; <br>
      &gt;&gt; _______________________________________________ 6lowpan
      mailing<br>
      &gt;&gt; list <a class="moz-txt-link-abbreviated" href="mailto:6lowpan@ietf.org">6lowpan@ietf.org</a> <br>
      &gt;&gt; <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/6lowpan">https://www.ietf.org/mailman/listinfo/6lowpan</a><br>
      &gt; <br>
      &gt; </span><br>
    <br>
  </body>
</html>

--------------050507020807020108020803--
