[6tsch] Work item on security

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 24 July 2013 10:09 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 549AA11E8156 for <6tsch@ietfa.amsl.com>; Wed, 24 Jul 2013 03:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 N9SPfMN4hkne for <6tsch@ietfa.amsl.com>; Wed, 24 Jul 2013 03:09:16 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id A6E3411E839B for <6tsch@ietf.org>; Wed, 24 Jul 2013 03:09:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4209; q=dns/txt; s=iport; t=1374660556; x=1375870156; h=from:to:cc:subject:date:message-id:mime-version; bh=mRNjs5KI+oy7NNh08iAy0OxStIrP+ycyDa2bkpOQNOM=; b=jVe10kABNRRQ+2pDlTDNHJ3Bz9iQH/a184oitpkZ00RfvX5LT7yROJJ4 JTrLe7D1ktZIFkWgQ3wK+MwzrYoRbCgs7qrf58HHZBO/MwIh+5fkot88m igQjRFhUIbKvnVaYs+oS05FyXCZtJkC6kLaMkXrSnMPXusKgagSkf9+ax 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAOam71GtJV2c/2dsb2JhbABbgkJENVDBAIEWFnSCJgEELUwSAQweViYBBAENDYgIuRKPSTGDGW4DqSyDFIIq
X-IronPort-AV: E=Sophos; i="4.89,734,1367971200"; d="scan'208,217"; a="238718321"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP; 24 Jul 2013 10:09:14 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r6OA9EIp032278 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 24 Jul 2013 10:09:14 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.94]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Wed, 24 Jul 2013 05:09:13 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Raghuram Sudhaakar (rsudhaak)" <rsudhaak@cisco.com>, "Yoshihiro Ohba (yoshihiro.ohba@toshiba.co.jp)" <yoshihiro.ohba@toshiba.co.jp>
Thread-Topic: Work item on security
Thread-Index: Ac6IVZGwDZfxq3CLRRyw9+ditzXuXw==
Date: Wed, 24 Jul 2013 10:09:13 +0000
Deferred-Delivery: Wed, 24 Jul 2013 10:08:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD8413A5DD0@xmb-rcd-x01.cisco.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.218]
Content-Type: multipart/alternative; boundary="_000_E045AECD98228444A58C61C200AE1BD8413A5DD0xmbrcdx01ciscoc_"
MIME-Version: 1.0
Cc: "6tsch@ietf.org" <6tsch@ietf.org>
Subject: [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 10:09:22 -0000

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