IETF Logo Mail Archive

Re: [6tsch] charter: new language security work item

Thomas Watteyne <watteyne@eecs.berkeley.edu> Sat, 27 July 2013 21:39 UTC

Return-Path: <twatteyne@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 0EA5B11E8115 for <6tsch@ietfa.amsl.com>; Sat, 27 Jul 2013 14:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 F0IKQbRVm+Ro for <6tsch@ietfa.amsl.com>; Sat, 27 Jul 2013 14:39:21 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 62D9611E8113 for <6tsch@ietf.org>; Sat, 27 Jul 2013 14:39:06 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un1so3267784pbc.29 for <6tsch@ietf.org>; Sat, 27 Jul 2013 14:39:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=a8xcBcX+3/3COC5Xb2SkX36lAYLMXEkFEDyfDruLfIo=; b=xqrrFlORsCfDJ0nOqRmPgO4UvljKt+bloekB2BQfjdUyszReDCBrLFhGXX3aguJesY FXxd0iuLz8wnTT6LphY/gZSZNaIWXhKzQ14F+YRUp+enY01KmtP4g6hTp3QgpQNVXSDT 6Es2AvEjGZYtEMu2JctAu2jeQbjPKvz/xhW/911kwaUHz7L3qu1crjTcYFx1Wf96WKD+ dP3KH2rLjpVO6GAvDu50L3ycvEZ9OHhVjfoDO3mIk0HZiWFsvUvOe4zpysgg3cWUX9bi EMV5316KIo/yTatxU9ouO38+W9LqlB95fTuj9kTkFkygiWKVj6dA8ddzplTEDyeP3+GY XUrg==
X-Received: by 10.68.103.131 with SMTP id fw3mr60158879pbb.65.1374961145528; Sat, 27 Jul 2013 14:39:05 -0700 (PDT)
MIME-Version: 1.0
Sender: twatteyne@gmail.com
Received: by 10.66.147.193 with HTTP; Sat, 27 Jul 2013 14:38:45 -0700 (PDT)
In-Reply-To: <CAFb8J8ofD9BtGzX2tzZkEq4H0jz66wdyvDUsR9fc963zquPQDg@mail.gmail.com>
References: <CADJ9OA-itOKmPTu6s3VMc1BkwZbjC_y9Y7g5jjnS0p+HqjU5gg@mail.gmail.com> <CAFb8J8ofD9BtGzX2tzZkEq4H0jz66wdyvDUsR9fc963zquPQDg@mail.gmail.com>
From: Thomas Watteyne <watteyne@eecs.berkeley.edu>
Date: Sat, 27 Jul 2013 23:38:45 +0200
X-Google-Sender-Auth: DQNWaANjGuzPTjG-_ZbyTkvGWLk
Message-ID: <CADJ9OA8uTBkN9qc8NctornQT-2NAvt8qmjjOPva4aXkJ8K0RkQ@mail.gmail.com>
To: Subir Das <subirdas21@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b5d99e1a8cbc604e285165b
Cc: 6TSCH <6tsch@ietf.org>
Subject: Re: [6tsch] charter: new language security work item
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: Sat, 27 Jul 2013 21:39:23 -0000

Subir,

I see how this language can lead to confusion. As you correctly point out,
it's the "6TSCH Security architecture and requirements" document which aims
at Informational, not the document describing the actual solution if/when
we decide to create it.

I've updated the charter text and slides. You'll find the latest version at
[1]. The language now reads:

7. Produce "6TSCH Security architecture and requirements", and depending on
the security requirements identified in the document, the group may work on
a security solution and ask for security area review.
The "6TSCH Security architecture and requirements" document will aim at
Informational.

Thanks for spotting the potentially confusing text.

Thomas

[1] https://bitbucket.org/6tsch/charter-ietf-6tsch/src



On Sat, Jul 27, 2013 at 5:15 PM, Subir Das <subirdas21@gmail.com> wrote:

> Hi Thomas,
> Sorry I was not able to join the call yesterday. I assume the sentence "This
> document will aim at Informational." implies to the requirements and
> architecture document not the solution document if the group wants to
> develop it. So it would be good if we clarify it. So my suggestion would be
> to change the sentence as  "The security architecture and
> requirements document will aim at an Informational document."
>
> Thanks,
> _Subir
>
>
> On Sat, Jul 27, 2013 at 3:50 AM, Thomas Watteyne <
> watteyne@eecs.berkeley.edu> wrote:
>
>> All,
>>
>> Per the discussion on the mailing list, and during yesterday's call, we
>> slightly modified the language for the security work item.
>>
>> That section now reads:
>>
>> 7. Produce "6TSCH Security architecture and requirements", and depending
>> on the security requirements identified in the document, the group may work
>> on a security solution and ask for security area review.
>> This document will aim at Informational.
>>
>> This change was pushed to the charter's repository at
>> https://bitbucket.org/6tsch/charter-ietf-6tsch/src/
>>
>> Thomas
>>
>> _______________________________________________
>> 6tsch mailing list
>> 6tsch@ietf.org
>> https://www.ietf.org/mailman/listinfo/6tsch
>>
>>
>

v2.8.7 | Report a Bug | By Email