Re: [Roll] PLEASE Comment on draft-alexander-roll-mikey-lln-key-mgmt
Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp> Thu, 08 September 2011 05:16 UTC
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 132CF21F8B2A for <roll@ietfa.amsl.com>; Wed, 7 Sep 2011 22:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level:
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=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 ROBnE8hT1M4X for <roll@ietfa.amsl.com>; Wed, 7 Sep 2011 22:16:03 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by ietfa.amsl.com (Postfix) with ESMTP id 3478D21F8B18 for <roll@ietf.org>; Wed, 7 Sep 2011 22:16:02 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp with ESMTP id p885HqtP021549 for <roll@ietf.org>; Thu, 8 Sep 2011 14:17:52 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp id p885Hqpc017628 for roll@ietf.org; Thu, 8 Sep 2011 14:17:52 +0900 (JST)
Received: from unknown [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id QAA17627; Thu, 8 Sep 2011 14:17:52 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id p885Hq18029941 for <roll@ietf.org>; Thu, 8 Sep 2011 14:17:52 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id p885Hp60008174; Thu, 8 Sep 2011 14:17:51 +0900 (JST)
Received: from [133.196.16.130] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0LR6001UBUPR3C80@mail.po.toshiba.co.jp> for roll@ietf.org; Thu, 08 Sep 2011 14:17:51 +0900 (JST)
Date: Thu, 08 Sep 2011 14:17:35 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <5DAFCC5E-1D44-4DFB-B47A-8BBD708C2C2C@cisco.com>
To: roll@ietf.org
Message-id: <4E684FEF.8090102@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-2022-JP"
Content-transfer-encoding: 7bit
References: <79860D3D-A86D-474B-BA0B-D4ADDC6977D9@cisco.com> <683511D7-32EE-49F1-AA67-C8599C8775BA@cisco.com> <BB7753E4-8A10-4CAA-975C-631BE1199263@thomasclausen.org> <F6236DB9-2480-4522-A65D-7B4D8F686CAF@cisco.com> <D17D7ADC-CC10-4C9B-BAED-ACEAB8C71F4B@thomasclausen.org> <5DAFCC5E-1D44-4DFB-B47A-8BBD708C2C2C@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
Subject: Re: [Roll] PLEASE Comment on draft-alexander-roll-mikey-lln-key-mgmt
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Sep 2011 05:16:04 -0000
Hello, I think a cross-layer key management approach is important for resource-constrained devices. On the other hand, there are similar approaches proposed in other IETF WG: http://tools.ietf.org/id/draft-arkko-core-security-arch-00.txt http://tools.ietf.org/id/draft-garcia-core-security-02.txt http://tools.ietf.org/id/draft-sarikaya-core-sbootstrapping-02.txt http://tools.ietf.org/id/draft-ohba-core-eap-based-bootstrapping-00.txt (and I am a co-author of the last two ones.) MIKEY-based cross-layer key management (such as described in draft-alexander) can be an alternative, and similar solutions can be defined using other key management protocols such as PANA, TLS, IKEv2, GDOI and maybe HIP. I am not trying to compare them here, but I just want to point out that there are multiple approaches in this area. Regards, Yoshihiro Ohba (2011/09/06 1:36), JP Vasseur wrote: > Thanks Thomas for your feed-back. > > Still, I would encourage people to read and comment; the issue of key > management has been raised by several > ADs and in the security framework, so we may want to make some > progress and address IESG's requests. > > On Sep 5, 2011, at 6:07 PM, Thomas Heide Clausen wrote: > >> Dear JP, >> >> Thanks. I have read the specification a couple of times, but as I am >> not a key-management-expert, I have not (yet) formed any real >> opinions on the technical content. I am still working on that bit ;) >> >> However as you message was cryptic, I wanted to make sure that I did >> not miss any last-review-before-wg-document deadline. I understand >> that there's no immediate deadline so I would suggest that the WG >> gets to consider that when a determination has been made on the >> other ongoing issues currently being discussed >> >> [Not to belittle this document; I, for one, like most LLN routers >> just have limited bandwidth and processing power….trying to make >> sure that they are being used appropriately] >> >> Respectfully yours, >> >> Thomas >> >> >> >> On Sep 5, 2011, at 16:53 , JP Vasseur wrote: >> >>> Hi Thomas, >>> >>> On Sep 5, 2011, at 4:47 PM, Thomas Heide Clausen wrote: >>> >>>> Dear JP, >>>> >>>> I am not sure I completely understand the question……is this the WG >>>> chair polling the group for adaptation as WG document? >>>> >>>> If yes, when do you plan on making a decision (so as to give a >>>> target as to before when an opinion should have been formed?) >>>> >>> >>> I was polling the WG to get some comment since we did not get a >>> chance to discuss it during the WG meeting, >>> that was not yet a poll for WG adoption. >>> >>> Any opinion to share of this document ? >>> >>> Thanks. >>> >>> JP. >>> >>> >>>> Thomas >>>> >>>> On Aug 31, 2011, at 14:55 , JP Vasseur wrote: >>>> >>>>> Any comment ? >>>>> >>>>> Thanks. >>>>> >>>>> JP. >>>>> >>>>> Begin forwarded message: >>>>> >>>>>> *From: *JP Vasseur <jpv@cisco.com <mailto:jpv@cisco.com>> >>>>>> *Subject: **[Roll] PLEASE Comment on >>>>>> draft-alexander-roll-mikey-lln-key-mgmt* >>>>>> *Date: *August 26, 2011 9:17:42 AM GMT+02:00 >>>>>> *To: *roll WG <roll@ietf.org <mailto:roll@ietf.org>> >>>>>> >>>>>> Dear all, >>>>>> >>>>>> Several of you expressed some interest in >>>>>> draft-alexander-roll-mikey-lln-key-mgmt. That said, could you >>>>>> please comment on this I-D as soon as possible ? We need a key >>>>>> management protocol and if it turns >>>>>> out that the WG wants to adopt this ID, I'll poll the WG to make >>>>>> it a WG … Please comment. >>>>>> >>>>>> Thanks. >>>>>> >>>>>> JP. >>>>>> _______________________________________________ >>>>>> Roll mailing list >>>>>> Roll@ietf.org <mailto:Roll@ietf.org> >>>>>> https://www.ietf.org/mailman/listinfo/roll >>>>> >>>>> _______________________________________________ >>>>> Roll mailing list >>>>> Roll@ietf.org <mailto:Roll@ietf.org> >>>>> https://www.ietf.org/mailman/listinfo/roll >>>> >>> >> > > > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll
- [Roll] PLEASE Comment on draft-alexander-roll-mik… JP Vasseur
- [Roll] Fwd: PLEASE Comment on draft-alexander-rol… JP Vasseur
- Re: [Roll] PLEASE Comment on draft-alexander-roll… Thomas Heide Clausen
- Re: [Roll] PLEASE Comment on draft-alexander-roll… JP Vasseur
- Re: [Roll] PLEASE Comment on draft-alexander-roll… Thomas Heide Clausen
- Re: [Roll] PLEASE Comment on draft-alexander-roll… JP Vasseur
- Re: [Roll] PLEASE Comment on draft-alexander-roll… Yoshihiro Ohba
- Re: [Roll] PLEASE Comment on draft-alexander-roll… Robert Cragie