IETF Logo Mail Archive

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

Qin Wang <qinwang@berkeley.edu> Sun, 21 July 2013 13:46 UTC

Return-Path: <qinwang@berkeley.edu>
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 65E7E21F9F13 for <6tsch@ietfa.amsl.com>; Sun, 21 Jul 2013 06:46:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 TAcSseXr-IkL for <6tsch@ietfa.amsl.com>; Sun, 21 Jul 2013 06:45:57 -0700 (PDT)
Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE4621F9E12 for <6tsch@ietf.org>; Sun, 21 Jul 2013 06:45:57 -0700 (PDT)
Received: by mail-ie0-f179.google.com with SMTP id c10so13372971ieb.10 for <6tsch@ietf.org>; Sun, 21 Jul 2013 06:45:56 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=iyeL3QNhUpJgJQvZTjZynjbgs9J04lvo0Z2vwagYbpg=; b=WTHyLrmYMkoSGadBixX97SMaRquyDq5U9HDkG55bnLu6+KwRXJeZZMOpbqsiQmO3+D P4q83QNGHFXxNpWj+4OvWOzVyim6OTekn25Fvx1d47ZCDoYHdndJ8viU+Kw6v3RgUedT BzzpFvFNN+z83o706JHUOC6nC2EZlK5apWN/FMGYgoGQuv6nQCkAxCMrlvDd0ygAP7aS tHpp8wktiBHvcOHstRl5G+HC1YD3nE5lLSysEXk032TsfcFP1KRcjol5SSEWddpVjosK edgOns78PY3dvWdbcBy6GMeAsuNgnqfq4W7gvppqBNnji+ye9EvC7k6PF7enkibfV56I UirA==
MIME-Version: 1.0
X-Received: by 10.42.11.211 with SMTP id v19mr14648600icv.29.1374414356240; Sun, 21 Jul 2013 06:45:56 -0700 (PDT)
Received: by 10.64.51.8 with HTTP; Sun, 21 Jul 2013 06:45:56 -0700 (PDT)
In-Reply-To: <E045AECD98228444A58C61C200AE1BD84137E60E@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD84137DB02@xmb-rcd-x01.cisco.com> <CAAzoce7GEpnviwKkqC61hWx2Bkx8Y1f72UBq3c03PV6FfPgEKw@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD84137E60E@xmb-rcd-x01.cisco.com>
Date: Sun, 21 Jul 2013 21:45:56 +0800
Message-ID: <CAAzoce514e=PouvHNuvJy5Wn+gWb4=XC-5p4r9aGs7qE-96aNA@mail.gmail.com>
From: Qin Wang <qinwang@berkeley.edu>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary=20cf301d3e607a74e504e205c724
X-Gm-Message-State: ALoCoQlRyqcwp7sMYrRhk3PkbLmzTZ7xdAYPpcHs5Vsd8Luzz+khx1TIEuXmkctActDdUu/+fU3k
Cc: "6tsch@ietf.org" <6tsch@ietf.org>
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: Sun, 21 Jul 2013 13:46:01 -0000

Pascal,

Yes, I think we can add "mobility" in the first paragraph of "Description
of Working Group [2/5]".

Thanks
Qin


On Sat, Jul 20, 2013 at 2:55 PM, Pascal Thubert (pthubert) <
pthubert@cisco.com> wrote:

>  Dear Qin:****
>
> ** **
>
> I’m a bit out of sync.****
>
> ** **
>
> 1) I agree we shoud have mobility somewhrere****
>
> 2) slide 8 in the charter slides on the repo is this “ Description of
> Working Group [2/5]”****
>
> ** **
>
> Is that where you’d like to see mobility mentioned?****
>
> ** **
>
> Cheers,****
>
> ** **
>
> Pascal****
>
> ** **
>
> *From:* Qin Wang [mailto:qinwang@berkeley.edu]
> *Sent:* vendredi 19 juillet 2013 21:12
> *To:* Pascal Thubert (pthubert)
> *Cc:* 6tsch@ietf.org
> *Subject:* Re: [6tsch] work item 2 in the charter****
>
> ** **
>
> Hi Pascal,****
>
> ** **
>
> The slides are pretty good. Just a comment on slide-8. Should we add
> "mobility" as one of criteria?****
>
> ** **
>
> Thanks****
>
> Qin****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On Sat, Jul 20, 2013 at 12:06 AM, 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****
>
> ** **
>

v2.8.7 | Report a Bug | By Email