Re: [6tsch] Work item on security

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 24 July 2013 13:56 UTC

Return-Path: <pthubert@cisco.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 E1E5D11E821A for <6tsch@ietfa.amsl.com>; Wed, 24 Jul 2013 06:56:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.501
X-Spam-Level:
X-Spam-Status: No, score=-10.501 tagged_above=-999 required=5 tests=[AWL=0.097, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 EGqreiaukvmK for <6tsch@ietfa.amsl.com>; Wed, 24 Jul 2013 06:56:55 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 338A911E8210 for <6tsch@ietf.org>; Wed, 24 Jul 2013 06:56:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11825; q=dns/txt; s=iport; t=1374674213; x=1375883813; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=GxTuXm2A+h7gon5bC8F4drNFPHGa6Dc9kMxp1XlyR8U=; b=mE3qmOe0DjeoFs9PM/cyPXkvpCQVCwCLKGXId5oShOe+eHIM1xHsMJrg cbK31KSxr6B8/Mi19W/jxEPDfzypYqkw0In8LPTmHk5pkMWU/xrA8+PQS 4JvzqfPgxaTSjx60jhiEUwF+I/Le2pLJdTGzKpZrMb0RYX10sa7uy29QO E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoYFAMzb71GtJV2a/2dsb2JhbABbgkJENVDBAoEWFnSCJAEBAQQBAQEqQQsQAgEIEQEDAQELHQcnCxQDBggBAQQOBQgRAod1DLlABI9MLQQGAYMSbgOFRIMuoDqDFIIq
X-IronPort-AV: E=Sophos; i="4.89,735,1367971200"; d="scan'208,217"; a="235798546"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-9.cisco.com with ESMTP; 24 Jul 2013 13:56:14 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6ODuEIK028422 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 24 Jul 2013 13:56:14 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.94]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Wed, 24 Jul 2013 08:56:14 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Subir Das <subirdas21@gmail.com>
Thread-Topic: [6tsch] Work item on security
Thread-Index: Ac6IVZGwDZfxq3CLRRyw9+ditzXuXwARNuUAAAl5gKA=
Date: Wed, 24 Jul 2013 13:56:13 +0000
Deferred-Delivery: Wed, 24 Jul 2013 13:55:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD8413A65FD@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD8413A5DD0@xmb-rcd-x01.cisco.com> <CAFb8J8o0Do=S++-Py26y-o0kcx77fmY5UmH7VzSQ6tPqSznmJg@mail.gmail.com>
In-Reply-To: <CAFb8J8o0Do=S++-Py26y-o0kcx77fmY5UmH7VzSQ6tPqSznmJg@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.86.254]
Content-Type: multipart/alternative; boundary="_000_E045AECD98228444A58C61C200AE1BD8413A65FDxmbrcdx01ciscoc_"
MIME-Version: 1.0
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:57:00 -0000

Hi Subir and René:

The current draft charter lists only 6 work items, and then has an unnumbered paragraph as follows:
"
A document on the security architecture and requirements for 6TSCH will be
developed, and depending on the security requirements identified in the
document, the group may work on a security solution and ask for security area
review.
"

My suggestion is not to add standard track work now but to:
1) add the item above as item 7 with a sentence that is more homogeneous with 1 .. 6 and eventually
2) add words like commissioning, provisioning, key life cycle management or network / node bootstrap to indicate that these items are in scope.

What do you think?

Pascal

From: 6tsch-bounces@ietf.org [mailto:6tsch-bounces@ietf.org] On Behalf Of Subir Das
Sent: mercredi 24 juillet 2013 15:20
To: Pascal Thubert (pthubert)
Cc: Raghuram Sudhaakar (rsudhaak); 6tsch@ietf.org; Yoshihiro Ohba (yoshihiro.ohba@toshiba.co.jp)
Subject: Re: [6tsch] Work item on security

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<mailto: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<mailto:6tsch@ietf.org>
https://www.ietf.org/mailman/listinfo/6tsch