Re: [6tsch] slides for work items

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 22 July 2013 15:12 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 CDF5D11E811D for <6tsch@ietfa.amsl.com>; Mon, 22 Jul 2013 08:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.545
X-Spam-Level:
X-Spam-Status: No, score=-10.545 tagged_above=-999 required=5 tests=[AWL=0.053, 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 VY4lfqP5Cqph for <6tsch@ietfa.amsl.com>; Mon, 22 Jul 2013 08:12:51 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 0B0D911E80F6 for <6tsch@ietf.org>; Mon, 22 Jul 2013 08:12:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12270; q=dns/txt; s=iport; t=1374505957; x=1375715557; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Qan6bcmyzH56Io/PIsRzJsQiMeDx6eA+S8Oxc/8o9Ac=; b=W7D5tQ1wAdBikdaKFl44tTeVG/4RjO1YDtQ3vvqJTsSbxfRgBkYlHtWj x5Si4IQvm8NSgQG01ccsPlxt3mjaK0/2ctwTDo4DXqP0itoYTzCL8Pro6 0YkG3ZBPV3Z5LPfDxuzjZHv5XTPNSDaGwUsSZYIrAQ4w28mji/Xb/hSMJ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjYFAIxK7VGtJV2c/2dsb2JhbABaDoI0RDVQwDGBFBZ0giQBAQEEAQEBJAZBCxACAQgRAQMBAQsdBycLFAMGCAIEAQ0FCBOHdQy3XgSPZS0EBgGDEG4DhUOOQ5UkglQ+gio
X-IronPort-AV: E=Sophos; i="4.89,719,1367971200"; d="scan'208,217"; a="237834566"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-7.cisco.com with ESMTP; 22 Jul 2013 15:12:35 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r6MFCZaP008171 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 22 Jul 2013 15:12:35 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.35]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Mon, 22 Jul 2013 10:12:34 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Thomas Watteyne <watteyne@eecs.berkeley.edu>, "Raghuram Sudhaakar (rsudhaak)" <rsudhaak@cisco.com>
Thread-Topic: [6tsch] slides for work items
Thread-Index: AQHOhuscWxlLjqJGpkyYx8mnaBxWsJlwyU/g
Date: Mon, 22 Jul 2013 15:12:34 +0000
Deferred-Delivery: Mon, 22 Jul 2013 15:12:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD841380619@xmb-rcd-x01.cisco.com>
References: <2C3A8CAFDCAFCA41B8BF705CD9471C5B184DBECC@xmb-rcd-x04.cisco.com> <CADJ9OA-o6w0Vf7Yat6XQ4Za5v-mQCeEU8d-x58S2TYBTWEH0ag@mail.gmail.com>
In-Reply-To: <CADJ9OA-o6w0Vf7Yat6XQ4Za5v-mQCeEU8d-x58S2TYBTWEH0ag@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.108.224]
Content-Type: multipart/alternative; boundary="_000_E045AECD98228444A58C61C200AE1BD841380619xmbrcdx01ciscoc_"
MIME-Version: 1.0
Cc: "6tsch@ietf.org" <6tsch@ietf.org>
Subject: Re: [6tsch] slides for work items
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: Mon, 22 Jul 2013 15:12:56 -0000

Hi Raghu and Thomas:

I made a slight update 6TOP -> 6top since apparently we are using lowercase here.

For security, I'd be OK to revisit the charter and promote the work considering that we have a very serious draft and some identified issues (e.g. securing the beacons or not, scalability). Can we take that to the list separately?

The other item that we need to conclude on is the PCE interaction. The charter (and the slides) miss the fact that we need to define what topological / metric information gets passed to the PCE, how we locate the PCE, how we make available and scale the PCE, and which protocol we use for all this. The chartered piece, working on PCEP, is only the visible part of that iceberg.

We need to conclude on the thread, which is stalled. Should I propose text?

Pascal

From: 6tsch-bounces@ietf.org [mailto:6tsch-bounces@ietf.org] On Behalf Of Thomas Watteyne
Sent: lundi 22 juillet 2013 16:50
To: Raghuram Sudhaakar (rsudhaak)
Cc: 6tsch@ietf.org
Subject: Re: [6tsch] slides for work items

Raghuram,

Thanks! I uploaded the slides into the repo and updated the links in the wiki.

I believe we want to stick as closely as possible to the charter.

We have elected to treat security not as a explicit work item in the charter, since it can end up being a requirements document followed by a security draft, or something which is scattered in different drafts.

The charter text now is:
"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."

Unless we decide to change the charter text, I would keep the same "logic" in the presentation, and therefore not give the security work a work item number.

A couple of remarks:
- please change from 6TOP to 6top throughout.
- [2] I would put the work items in the order they appear in the charter.
- please note that work item 2 might change in the next couple of days, so you might have to adapt the slides.

Thomas

On Mon, Jul 22, 2013 at 7:25 AM, Raghuram Sudhaakar (rsudhaak) <rsudhaak@cisco.com<mailto:rsudhaak@cisco.com>> wrote:
All,
Attached are the slides for the work items. Please provide your comments.

Specifically, please provide feedback on whether we must have the security framework as a work item.

-raghuram

_______________________________________________
6tsch mailing list
6tsch@ietf.org<mailto:6tsch@ietf.org>
https://www.ietf.org/mailman/listinfo/6tsch