[6tsch] work item 2: centralized route and track computation with PCE

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 23 July 2013 10:34 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 DDF2911E81D0 for <6tsch@ietfa.amsl.com>; Tue, 23 Jul 2013 03:34:34 -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=[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 C1TiPuWASU84 for <6tsch@ietfa.amsl.com>; Tue, 23 Jul 2013 03:34:29 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 1A94E11E818B for <6tsch@ietf.org>; Tue, 23 Jul 2013 03:34:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13491; q=dns/txt; s=iport; t=1374575669; x=1375785269; h=from:to:cc:subject:date:message-id:mime-version; bh=sWWsozwQAKnZcgyAkKkRYocbTZbFg+LbQFzWsF2oTXg=; b=OMpuBmuRfDv/DyZrujkbdrJzsot6JNffn3610BGDdFxLN7ucoZ5i6Pau GpoWw9/7wPrPe8vkCEeQplsaB7ZgZs/3RKu2lniTnBXfFVEn1SbbsZP8j M+XkA+C2sdJhqIZl/6YIn+bh6ppt02PZI3YiaZJF1cOhc+thuTHW9zNkH Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AioFAK5b7lGtJXG//2dsb2JhbABbDoI0RDVQwDmBERZ0giQBAQEELUwSARkBAwEBCx05FAMGCQEEAQ0FCIgIuHaOW4EHMQaDEW4DhUOOQ5UkglQ+gWhC
X-IronPort-AV: E=Sophos; i="4.89,726,1367971200"; d="scan'208,217"; a="238186712"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-2.cisco.com with ESMTP; 23 Jul 2013 10:34:27 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6NAYQsW010059 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 23 Jul 2013 10:34:26 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.35]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Tue, 23 Jul 2013 05:34:24 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Raghuram Sudhaakar (rsudhaak)" <rsudhaak@cisco.com>, "maria-rita.palattella@uni.lu" <maria-rita.palattella@uni.lu>, "Thomas Watteyne" <watteyne@eecs.berkeley.edu>
Thread-Topic: work item 2: centralized route and track computation with PCE
Thread-Index: Ac6HkBxqHDBpGaJmQ8OMT8IfC9cPIQ==
Date: Tue, 23 Jul 2013 10:34:24 +0000
Deferred-Delivery: Tue, 23 Jul 2013 10:34:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD841391C8B@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.216.93]
Content-Type: multipart/alternative; boundary="_000_E045AECD98228444A58C61C200AE1BD841391C8Bxmbrcdx01ciscoc_"
MIME-Version: 1.0
Cc: "6tsch@ietf.org" <6tsch@ietf.org>
Subject: [6tsch] work item 2: centralized route and track computation with PCE
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: Tue, 23 Jul 2013 10:34:35 -0000

Hello Raghu and all:

About item 2 6TSCH Centralized Management:

Since we wrote the charter a few months ago we have been digging and it appears that we are probably not ready for going standard track right away with a 6TSCH document.
- In one hand, we understand better that the PCE is the component we need for both centralized route AND track computation.
- OTOH, we realized that PCEP only covers a limited portion of the required standard work and we realize that we need to dig deeper in what needs to be done, in particular to locate the PCE(s), export topology and metrics to the PCE, and then install routes and tracks from the PCE.  We also understand that some of that work belongs to the PCE working group though it is unclear exactly how much that is.

Right now the charter has this:

2. Produce "6TSCH centralized management" to define the mechanism by which an
external Path Computation Element can communicate with the 6top protocol layer
of the different nodes in the network (1) to modify their TSCH schedule and
(2) to gather link quality statistics and data flow requirements.  The WG will
initially look at PCEP and CoAP.
Depending on the applicability of PCEP, this document will be targeted to
proposed standard.

In the light of our studies, I'd suggest this:
2. Produce requirements and an overall architecture for  "6TSCH centralized routes and tracks management"
describing the mechanism by which an external Path Computation Element (PCE) can communicate with
devices in a 6TSCH network in order to maintain routing and forwarding states. In detail, the WG will
consider operations (1) by the device routing layer for (i) sending topological information and routing
metrics to the PCE, and (ii) getting on-demand routing information; and (2) by the device 6top sublayer
for exporting neighboring and link quality statistics to the PCE and (2) requesting to (re)compute and
install a track that meets explicit flow requirements.

What do you guys think?


Pascal

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

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