IETF Logo Mail Archive

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

Subir <subirdas21@gmail.com> Sun, 28 July 2013 07:56 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 3169221F9DC9 for <6tsch@ietfa.amsl.com>; Sun, 28 Jul 2013 00:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 X8LFHhDg+BtE for <6tsch@ietfa.amsl.com>; Sun, 28 Jul 2013 00:56:28 -0700 (PDT)
Received: from mail-ye0-x230.google.com (mail-ye0-x230.google.com [IPv6:2607:f8b0:4002:c04::230]) by ietfa.amsl.com (Postfix) with ESMTP id 308D321F9DC7 for <6tsch@ietf.org>; Sun, 28 Jul 2013 00:56:28 -0700 (PDT)
Received: by mail-ye0-f176.google.com with SMTP id q3so355842yen.35 for <6tsch@ietf.org>; Sun, 28 Jul 2013 00:56:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=7+CKKUvq9UUMnB21gE/k8iTs8h5TlziLVFaoloK3mLM=; b=aycxNKil10BghhM2SZj2+T/3+YGKX4kqjZGBZcTjGaQ9h57PI4W7zEoo9t2uPRV77R UXFxu9IckV6CZOR+1bSWv39HLq023xEkYHRx25nn3sZWK148DLSEfnZct3Q2MVcmjzuW KUQgn0XpWdduhUDPqHm96raab5VcCK2C02LA7pGGx5fFdLoJ1Wx5NU0TloR7YgufX1ER ctG4Rx6F59EI1DEwbEeNZDbtScw7ywk81Marea69V9IHtDuOK5CuRzExEuFv/a66i/HX Bf5Zrk3EAa+fO7l+Rfa1uatbOGgIR8At4SNBuFpIvIWn5KxuvPRf3xzsq+9EB5w8B8IB YmZw==
X-Received: by 10.236.71.229 with SMTP id r65mr3895306yhd.175.1374998187645; Sun, 28 Jul 2013 00:56:27 -0700 (PDT)
Received: from [166.144.174.73] (73.sub-166-144-174.myvzw.com. [166.144.174.73]) by mx.google.com with ESMTPSA id y70sm76233599yhe.15.2013.07.28.00.56.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Jul 2013 00:56:26 -0700 (PDT)
References: <CADJ9OA-itOKmPTu6s3VMc1BkwZbjC_y9Y7g5jjnS0p+HqjU5gg@mail.gmail.com> <CAFb8J8ofD9BtGzX2tzZkEq4H0jz66wdyvDUsR9fc963zquPQDg@mail.gmail.com> <CADJ9OA8uTBkN9qc8NctornQT-2NAvt8qmjjOPva4aXkJ8K0RkQ@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADJ9OA8uTBkN9qc8NctornQT-2NAvt8qmjjOPva4aXkJ8K0RkQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-B01597A3-E1B8-4EE9-AAA5-02706D3E8F6D
Content-Transfer-Encoding: 7bit
Message-Id: <5E518029-CF67-4DF4-A17A-DFBBCA063D56@gmail.com>
X-Mailer: iPhone Mail (10A523)
From: Subir <subirdas21@gmail.com>
Date: Sun, 28 Jul 2013 09:56:20 +0200
To: Thomas Watteyne <watteyne@eecs.berkeley.edu>
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: Sun, 28 Jul 2013 07:56:30 -0000

Thanks Thomas

Sent from my iPhone

On Jul 27, 2013, at 11:38 PM, Thomas Watteyne <watteyne@eecs.berkeley.edu> wrote:

> 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