Re: [6tsch] work item 2 in the charter

Thomas Watteyne <watteyne@eecs.berkeley.edu> Fri, 19 July 2013 16:08 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 6B0A511E814E for <6tsch@ietfa.amsl.com>; Fri, 19 Jul 2013 09:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[AWL=0.057, 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 ACND7HK+aeJL for <6tsch@ietfa.amsl.com>; Fri, 19 Jul 2013 09:08:58 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id C669F21F99B0 for <6tsch@ietf.org>; Fri, 19 Jul 2013 09:08:36 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id lj1so4585634pab.31 for <6tsch@ietf.org>; Fri, 19 Jul 2013 09:08:36 -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:content-type; bh=aTpRUPPmapMIDcehr7Bk8Dkzpm8F9XcdGiof3OQy2XI=; b=sS5/SzWnANbWqOLWWmx9aho+LDnjKzCm1WZ23+U5sL1D2IKS0g44UNli0olIcRrH0O aqk9gi8/GMsCzLcZI4bBBvjYmcvEHsnmdg7Kdk5bjrsU10QJCxmw4R4NdVV8TRnJeXhx DG309WCeeU2imugMwtAu7lc5DrwkkLXHtCJToX/nsq3N5v91hAiqrZlAWGyAW3+/ukKk t0TpFHvnyoPFDkNUCsrLfoCmCT7IPlcWJTvMs7BrNypBKbh4ggkuJuQ39DkwDbLyQfwX duKfuT9jC9IPFsEyb2SeN+S1ZcOXyiMQ4sjAjk65nVUgh42VJ22Z8uLl9dnHBKUeV5Qi zyKQ==
X-Received: by 10.68.235.9 with SMTP id ui9mr18107917pbc.85.1374250116303; Fri, 19 Jul 2013 09:08:36 -0700 (PDT)
MIME-Version: 1.0
Sender: twatteyne@gmail.com
Received: by 10.66.147.228 with HTTP; Fri, 19 Jul 2013 09:08:16 -0700 (PDT)
In-Reply-To: <E045AECD98228444A58C61C200AE1BD84137DB02@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD84137DB02@xmb-rcd-x01.cisco.com>
From: Thomas Watteyne <watteyne@eecs.berkeley.edu>
Date: Fri, 19 Jul 2013 18:08:16 +0200
X-Google-Sender-Auth: FGcNbsOTRQZwHUqXqNvRm02LW_A
Message-ID: <CADJ9OA-SKc8ei+1M3PM2Qg-vCd3ofDrkzfJDL1yH3j9U=RknhQ@mail.gmail.com>
To: 6TSCH <6tsch@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8ff2436f03d15104e1df8a5f
Subject: Re: [6tsch] work item 2 in the charter
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: Fri, 19 Jul 2013 16:08:59 -0000

Pascal,
I agree that we should keep this at the level of requirements at this
point, since there is more work than we anticipated.
Thomas


On Fri, Jul 19, 2013 at 6:06 PM, Pascal Thubert (pthubert) <
pthubert@cisco.com> wrote:

>  Dear all:****
>
> ** **
>
> Please review the latest draft of the charter at
> https://bitbucket.org/6tsch/charter-ietf-6tsch/src ****
>
> Now is a good time to find the bugs! ****
>
> Work Item 2 in the charter (
> https://bitbucket.org/6tsch/charter-ietf-6tsch/) is still like this:****
>
> ** **
>
> “****
>
> 2. Produce "6TSCH centralized management" to define the mechanism by which
> an****
>
> external Path Computation Entity 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.****
>
> “****
>
> ** **
>
> Since the time we wrote this, we realized that there is a lot more to do
> than a simple increment to PCE/P.****
>
> ** **
>
> At the call we agreed that we should keep it to the level of requirements
> for this round. Do we all agree on this?****
>
> ** **
>
> If so we’ll need to revisit that text… Let us work on this early next
> week, this is probably the most urgent thing we have to do before the BoF.
> ****
>
> ** **
>
> Cheers,****
>
> ** **
>
> Pascal****
>
> ** **
>
> ** **
>
> _______________________________________________
> 6tsch mailing list
> 6tsch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tsch
>
>