Re: [Lln-futures] BoF Agenda
Ulrich Herberg <ulrich@herberg.name> Tue, 25 September 2012 16:30 UTC
Return-Path: <ulrich@herberg.name>
X-Original-To: lln-futures@ietfa.amsl.com
Delivered-To: lln-futures@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id 14C4121F8943 for <lln-futures@ietfa.amsl.com>;
Tue, 25 Sep 2012 09:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[AWL=-0.000,
BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1CBH0LVdkgMp for
<lln-futures@ietfa.amsl.com>; Tue, 25 Sep 2012 09:30:37 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com
[209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id CD2AB21F8940 for
<lln-futures@ietf.org>; Tue, 25 Sep 2012 09:30:36 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so8360264vbb.31 for
<lln-futures@ietf.org>; Tue, 25 Sep 2012 09:30:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type; bh=+xDsKsXAssDyB5ItbNApGNjQNUyKpza7Ujg9iGTtU1U=;
b=OoeQBdiYiT4hnpdBtHbyCenfiTMCkPA0t9PKAUgYPD6yurmPsJ4YNPxNubJxKxE86O
TH2aipHJ3Ll4ZLbRaHv7UJfCv7rMdCKd4JzJE5Wp8AumJwPWnBdomy+Y3QhDrxQ6kxEQ
CpGIsY5E8kU6O/Dk0742xejHByuxnzcoNbLTo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:x-gm-message-state;
bh=+xDsKsXAssDyB5ItbNApGNjQNUyKpza7Ujg9iGTtU1U=;
b=EwOzPn8Y1Z0Ye40yYC/4v8tFolgKJ3Q3CdrRgqCkvl4eTquAgoa5A1kpZQoAoiYmrR
j92MoPI/1C5M7o+6vFLyZicLGtfz1ir/8aPYGQ1DmEjkAgzWn3PERdRgEgTC287B3CBI
YG2ali+tO2WIexfuWcdMQgieUtERu/CBPYBuoUZUI/30I3CMAaYB+gxa9gUXWXa7UAZC
p0JQEXBfdShHhamMRBPbIN/arbL9ldJfmM4GbDKOH+bQwN9rrKBJeAzYROj2ZFQH9Nqo
Ny8zSjjC1CCoy2WsN77eb07LGJVJFhTGeIIjL/CCYs+mi1rT6a2fa+lzTAarTmzyO8Rl 5NOQ==
MIME-Version: 1.0
Received: by 10.221.2.76 with SMTP id nt12mr9502063vcb.12.1348590636319;
Tue, 25 Sep 2012 09:30:36 -0700 (PDT)
Received: by 10.58.102.102 with HTTP; Tue, 25 Sep 2012 09:30:36 -0700 (PDT)
In-Reply-To: <CAC8QAcdrhr+1bqnpZtgRz=qiXcKVE4GNmrrWLUVjGQx0tiky_w@mail.gmail.com>
References: <CAC8QAcdrhr+1bqnpZtgRz=qiXcKVE4GNmrrWLUVjGQx0tiky_w@mail.gmail.com>
Date: Tue, 25 Sep 2012 09:30:36 -0700
Message-ID: <CAK=bVC_W+tnBniE2KDYFwnSo_f4-0dT4Hknt5XrLDfqDQPqp4Q@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: sarikaya@ieee.org
Content-Type: multipart/alternative; boundary=bcaec54a377ad3442104ca89391b
X-Gm-Message-State: ALoCoQlQfvJjRiox+1sEcuFAFQLsXk5cNA26pS8FqC0s06mmj65AhKOPQ+qgqTBFcPsy1vbGym1c
Cc: "Keoh, Sye Loong" <sye.loong.keoh@philips.com>, lln-futures@ietf.org
Subject: Re: [Lln-futures] BoF Agenda
X-BeenThere: lln-futures@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <lln-futures.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lln-futures>,
<mailto:lln-futures-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lln-futures>
List-Post: <mailto:lln-futures@ietf.org>
List-Help: <mailto:lln-futures-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lln-futures>,
<mailto:lln-futures-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Sep 2012 16:30:38 -0000
Hi, that's great! I am also interested in security for LLNs. We have to be careful to clearly scope the work with respect to SOLACE (did SOLACE request a BOF as well? Or could there be a combined effort?) I think there are (at least) two parts that need work: bootstrapping security parameters (keys etc), which seems to be related to SOLACE. And then establishement of secure communcation during the operation of the network (confidentiality, integrity, authentication, as well as key revokation etc while the network is running). Best Ulrich On Tue, Sep 25, 2012 at 9:20 AM, Behcet Sarikaya <sarikaya2012@gmail.com>wrote;wrote: > Hi Geoff, all, > > I subscribed to lln-futures. Thanks for putting this up. > > I saw Sye's email on the archive and support it. > > I can contribute to the security presentation at the BoF. > > Regards, > > Behcet > > Dear all, > > I agree that having a formal BOF in Atlanta would be great to kick off > some discussion. Geoff, what do we need to prepare for a formal BOF in > IETF? > > Security for LLN is definitely one of the areas that we should > address. A common solution for key management, communication security, > security bootstrapping is beneficial as we can remove redundancies due > to the constraints of the devices. > > Cheers > Sye Loong > _______________________________________________ > Lln-futures mailing list > Lln-futures@ietf.org > https://www.ietf.org/mailman/listinfo/lln-futures >
- [Lln-futures] BoF Agenda Behcet Sarikaya
- Re: [Lln-futures] BoF Agenda Ulrich Herberg