Re: [6tsch] Work item on security
Subir Das <subirdas21@gmail.com> Wed, 24 July 2013 13:20 UTC
Return-Path: <subirdas21@gmail.com>
X-Original-To: 6tsch@ietfa.amsl.com
Delivered-To: 6tsch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id 61A3721F99F6 for <6tsch@ietfa.amsl.com>;
Wed, 24 Jul 2013 06:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-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 Lvs1zsknz-8b for
<6tsch@ietfa.amsl.com>; Wed, 24 Jul 2013 06:20:10 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com
[IPv6:2607:f8b0:4003:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id
1A77C21F8447 for <6tsch@ietf.org>; Wed, 24 Jul 2013 06:20:10 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id wo10so460910obc.13 for
<6tsch@ietf.org>; Wed, 24 Jul 2013 06:20:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type; bh=0hcC/ZSBNMq0//FdOgxPINHtanhiCkU50DYtIHKWzYw=;
b=iS1nxAxPRlTwHl3eRCbIep0Gfpoe+zvgTkVsIST6UEk8Hyjd2cRV3N3lIbrGiUPHlK
v7rny1PR6nWqWW4BSdfA/bQ983e9jHdhjPipM82LmuCZOdgJv0JT9Fz0UEmvTt7SQI+4
rjb0ANFkGUvWV7JQPL3OoxNbL8GkBGv/U9WhBI9hcjjeHjp3RIOr5IfAz1tRMcoPFDzP
8zEty6MbacTJ/CQU6CqIM8KBGiuVp9CE7IZLH9iAhyd7aWkUPTgUqM1r8cimUSUIpoq8
H6E5wG3MyJzFihLUPhCg42tTkaCxYafd30m99wgxL2wxJAsoMej5C4qzCm11ocrkxbVi WwkQ==
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; bh=0hcC/ZSBNMq0//FdOgxPINHtanhiCkU50DYtIHKWzYw=;
b=kqWA6L7Jnf8BhP44R2th+wb3t6rwpNU9oE8FSrwYuXMgevE6oQrts8xgr+nnm6MXbB
U/4EnOzz6KA6VU9nM2R642J1s96sjgbx2WM0fBr1It9ASqrW3KF8+7mrjPfZwLgJHFDx
FwcuK+OSLlufr3nI1dg5JF8U2UJIsVFm14Q+jAc5JwHXWSiI6GEm/KCdgy8zEVDpu5mn
RffA9w9LpRiGuw7oznTPj+vR4gMehJX4RmdUQ8i2Wl8A3W1VDNnKP+MpAF26ZheHNURt
exfH18fU5ASsWXqYHI7AnjcDWh8kjA+uZEBFp5NIGQ8oEpMiQ4rj5QEsLW8ntq0mn84v SlsA==
MIME-Version: 1.0
X-Received: by 10.50.12.5 with SMTP id u5mr411830igb.58.1374672008559;
Wed, 24 Jul 2013 06:20:08 -0700 (PDT)
Received: by 10.42.29.72 with HTTP; Wed, 24 Jul 2013 06:20:08 -0700 (PDT)
In-Reply-To: <E045AECD98228444A58C61C200AE1BD8413A5DD0@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD8413A5DD0@xmb-rcd-x01.cisco.com>
Date: Wed, 24 Jul 2013 09:20:08 -0400
Message-ID: <CAFb8J8o0Do=S++-Py26y-o0kcx77fmY5UmH7VzSQ6tPqSznmJg@mail.gmail.com>
From: Subir Das <subirdas21@gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary=089e011616dac0c3e904e241c4f7
Cc: "Raghuram Sudhaakar \(rsudhaak\)" <rsudhaak@cisco.com>,
"6tsch@ietf.org" <6tsch@ietf.org>,
"Yoshihiro Ohba \(yoshihiro.ohba@toshiba.co.jp\)"
<yoshihiro.ohba@toshiba.co.jp>
Subject: Re: [6tsch] Work item on security
X-BeenThere: 6tsch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode
of IEEE 802.15.4e,
and impacts on RPL and 6LoWPAN such as resource allocation" <6tsch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tsch>,
<mailto:6tsch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6tsch>
List-Post: <mailto:6tsch@ietf.org>
List-Help: <mailto:6tsch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tsch>,
<mailto:6tsch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jul 2013 13:20:12 -0000
I would agree with Rene. Let's keep the text as it is and hear from folks during BoF session if there are other suggestions. We do need to develop a security architecture and requirements document and the charter text is clear. -Subir On Wed, Jul 24, 2013 at 6:09 AM, Pascal Thubert (pthubert) < pthubert@cisco.com> wrote: > Dear all :**** > > ** ** > > So far we have been pretty unclear on whether the security work would be > in charter, and what the scope of that work would be.**** > > Raghu unearthed the issue as he was working on the work item slides for > the BoF. **** > > ** ** > > I see the need for a security framework that describes commissioning, > provisioning, key exchange and link security for large 6TSCH networks.**** > > And that is exactly what Yoshi and the others have started with > draft-ohba-6tsch-security. **** > > ** ** > > Questions to the group:**** > > Could/should we make this a full work item? **** > > And if so, what scope exactly?**** > > ** ** > > Cheers,**** > > ** ** > > Pascal**** > > _______________________________________________ > 6tsch mailing list > 6tsch@ietf.org > https://www.ietf.org/mailman/listinfo/6tsch > >
- [6tsch] Work item on security Pascal Thubert (pthubert)
- Re: [6tsch] Work item on security Rene Struik
- Re: [6tsch] Work item on security Subir Das
- Re: [6tsch] Work item on security Pascal Thubert (pthubert)
- Re: [6tsch] Work item on security Thomas Watteyne
- Re: [6tsch] Work item on security Michael Richardson
- Re: [6tsch] Work item on security Subir Das