Re: [Roll] PLEASE Comment on draft-alexander-roll-mikey-lln-key-mgmt

Robert Cragie <robert.cragie@gridmerge.com> Thu, 08 September 2011 12:10 UTC

Return-Path: <robert.cragie@gmail.com>
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 5B65C21F8B73 for <roll@ietfa.amsl.com>; Thu, 8 Sep 2011 05:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.916
X-Spam-Level:
X-Spam-Status: No, score=-2.916 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 ti195mowt+NK for <roll@ietfa.amsl.com>; Thu, 8 Sep 2011 05:10:34 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 01C3121F8B6D for <roll@ietf.org>; Thu, 8 Sep 2011 05:10:33 -0700 (PDT)
Received: by vxi29 with SMTP id 29so684091vxi.31 for <roll@ietf.org>; Thu, 08 Sep 2011 05:12:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=EqBpiJ59XmjveyJWYdif7/y44zjQD+WJSxTfl68igcM=; b=GSc3K43aeUFRw+aOhm5Z+opzUkKFMqKD5KeXH32hB2icoaauOTvTS24hxm5nXvDglK 36WHoFPK31wXk29AlBFbiVJQmfRG4FmiE6pKhJupDOsgPF9ynJ+uSRqh85bOgHC9dPWg Jas8EJuOqjj5NKg1dasS1D6RyB1P4ArnNt3YM=
MIME-Version: 1.0
Received: by 10.220.9.132 with SMTP id l4mr158937vcl.185.1315483945789; Thu, 08 Sep 2011 05:12:25 -0700 (PDT)
Sender: robert.cragie@gmail.com
Received: by 10.220.187.202 with HTTP; Thu, 8 Sep 2011 05:12:25 -0700 (PDT)
In-Reply-To: <4E684FEF.8090102@toshiba.co.jp>
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> <4E684FEF.8090102@toshiba.co.jp>
Date: Thu, 08 Sep 2011 13:12:25 +0100
X-Google-Sender-Auth: RiFZdYglDDQB9L3YQw8_nsuW-tk
Message-ID: <CADrU+d+-FkRQ29BoAkcbKyZke7vazvaOBN8HBzz6bxMknDMThg@mail.gmail.com>
From: Robert Cragie <robert.cragie@gridmerge.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
Content-Type: multipart/alternative; boundary="0003255734da4be81704ac6cf9ec"
Cc: roll@ietf.org
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
Reply-To: robert.cragie@gridmerge.com
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 12:10:35 -0000

+1.

I can see the merit in attempting to propose a generic key management
protocol but the very fact that different mechanisms exist suggests that it
is probably an unattainable target due to the distinct properties of the
underlying system the key management is being applied to.

Also, I question whether roll *needs* a key management protocol. It needs a
key management proposal, which should probably focus on abstract key
management operations relevant to roll networks rather than mandating (a)
specific key management protocol(s). Or is the desire to be more specific to
provide better interoperability?

Robert

2011/9/8 Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>

> 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 mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>