Re: [6tsch] the first 30min
Qin Wang <qinwang@berkeley.edu> Thu, 18 July 2013 14:29 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 4AC8B11E8146 for <6tsch@ietfa.amsl.com>; Thu, 18 Jul 2013 07:29:02 -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 oYq338JDUfxU for <6tsch@ietfa.amsl.com>; Thu, 18 Jul 2013 07:28:58 -0700 (PDT)
Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) by ietfa.amsl.com (Postfix) with ESMTP id 5805111E80A2 for <6tsch@ietf.org>; Thu, 18 Jul 2013 07:28:55 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id x12so7025231ief.40 for <6tsch@ietf.org>; Thu, 18 Jul 2013 07:28:53 -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=Wszv1oEt3Q1jRDmrLihfktGxW29RjP6eGdxTlg02Lbo=; b=BkQeiTgn9rK5pyjl3kNLL50qlTS+unc+q/k6lZSQY2buyWgd9/3OHQbOtEYgrezVQw fNRaWpLkIJ/0LcX7UscAXJIAGRwr9XFVkg2YWDMqjApxQAzb1HddyImFF9g+QlMYE0/H 1mtbPU7Wp7wXy9l/rACjDh4UElEFrKb00TySzI9A7G2TPl1aU+IR1gnEdl1t9cBTX8OT RD+Ltw6LvL07Ud6LULYpw5zvRsbCOxATJNiooH+/2/FkMRbN9S9lHUQNXOdBKjofmUIW S+Rtz9ywGG7Qhni7CS3Tfuqd0cSarsKOrvkyo9qLr5X2V1bCl2eCVxiziLKbuwaqO0/b zoKw==
MIME-Version: 1.0
X-Received: by 10.50.126.36 with SMTP id mv4mr12411142igb.45.1374157733663; Thu, 18 Jul 2013 07:28:53 -0700 (PDT)
Received: by 10.64.54.233 with HTTP; Thu, 18 Jul 2013 07:28:52 -0700 (PDT)
In-Reply-To: <CADJ9OA-Rb2Mtj9mmJ-qrEXUFOi-hHJiGdXd-2M5QpSO-oEARyg@mail.gmail.com>
References: <CADJ9OA-b0ymStTstV2cv0vdGJGyy8HTx6RdXxVDkMTZcudz3xw@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD84137A1C2@xmb-rcd-x01.cisco.com> <CADJ9OA-Rb2Mtj9mmJ-qrEXUFOi-hHJiGdXd-2M5QpSO-oEARyg@mail.gmail.com>
Date: Thu, 18 Jul 2013 22:28:52 +0800
Message-ID: <CAAzoce6Dqsi6oyPOcAqr=ow+G7uW9c60NSe0Td+nK0C+9WRqMQ@mail.gmail.com>
From: Qin Wang <qinwang@berkeley.edu>
To: Thomas Watteyne <watteyne@eecs.berkeley.edu>
Content-Type: multipart/alternative; boundary="047d7b3a968494a7b604e1ca07e6"
X-Gm-Message-State: ALoCoQlNuQXjNMrsdnW1BYgok1wLCelrHaNCBhM2Hq8a+kXzw/f8kCPwMAGCmkoiZLC8ZcOxFh1L
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>, 6TSCH <6tsch@ietf.org>, "Ted Lemon (ted.lemon@nominum.com)" <ted.lemon@nominum.com>
Subject: Re: [6tsch] the first 30min
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: Thu, 18 Jul 2013 14:29:02 -0000
Hi Pascal, The three stages are very clear in logic. Just a comment on the sub-title of the second part. If the conclusion from Maria Rita talk is expected as "the crowd has a sense of a huge value for the real world, even for everyday life", the sub-title may need to be changed, e.g. "How it works?" or something else. Thought? Qin On Thu, Jul 18, 2013 at 8:50 PM, Thomas Watteyne <watteyne@eecs.berkeley.edu > wrote: > Pascal, > > Absolutely, I saw your attached e-mail, and I agree we're very close. I > was going through it when preparing this e-mail, after realizing we will > probably be moving thing around between Maria Rita's, Xavi's and my own > slides. > > I agree with your modification to the conclusion and the story you're > describing. > > Thomas > > > On Thu, Jul 18, 2013 at 2:26 PM, Pascal Thubert (pthubert) < > pthubert@cisco.com> wrote: > >> Hello Thomas**** >> >> ** ** >> >> I’d discuss the nutshells rather than the content (which is close to >> perfect; ) And I’d argue that the nutshells are also the conclusions.**** >> >> Did you see the thread attached? We’re mostly in line but it seems you >> went through it all again. I understand your logic, this is a nice story. >> **** >> >> My 2 centimes:**** >> >> ** ** >> >> - [5min] draft-watteyne-6tsch-tsch-lln-context-02 [Thomas]**** >> - *In a nutshell: IEEE802.15.4e TSCH is Deterministic Wirelessstandard >> ***** >> >> I expect that at this point the crowd understands that deterministic is a >> new and immensely powerful complex, enabling control loops and this key to >> OT/automation networks, and that we can actually achieve it on wireless.* >> *** >> >> - [10min] what is IEEE802.15.4e TSCH? [Maria Rita]**** >> - *In a nutshell: IEEE802.15.4e TSCH is a proven technology which >> opens up IT/OT/automation convergence if coupled with IPv6***** >> >> I expect that at this point the crowd has a sense of a huge value for the >> real world, even for everyday life. If ùy nutshell is Maria Rita’s >> conclusion then we have a great transition for Xavi (see my attached mail) >> **** >> >> - [15min] what is missing? [Xavi]**** >> - *In a nutshell: Some Blocks but mostly Glue are missing so 6TSCH >> is doable***** >> >> By then people must also be convinced that there is work to be done, >> understand what the scope of that work is, and that it is achievable within >> IETF classical operations.**** >> >> ** ** >> >> Works for you? **** >> >> ** ** >> >> Also, do you mind copyting the list or at least the other speakers and >> Ted and Marc?**** >> >> ** ** >> >> Pascal**** >> >> ** ** >> >> *From:* twatteyne@gmail.com [mailto:twatteyne@gmail.com] *On Behalf Of *Thomas >> Watteyne >> *Sent:* jeudi 18 juillet 2013 14:08 >> *To:* Maria Rita Palattella; Xavi Vilajosana; Pascal Thubert (pthubert) >> *Subject:* BoF: the first 30min**** >> >> ** ** >> >> Xavi, Maria Rita,**** >> >> ** ** >> >> [CC'ing Pascal]**** >> >> ** ** >> >> The first 30min at the BoF will be ours to convey the following messages: >> **** >> >> - IEEE802.15.4e TSCH is a powerful new standard**** >> - it's a proven technology**** >> - we want to fit an IETF IPv6 upper stack onto it**** >> - but pieces are missing**** >> >> We need to coordinate closely to avoid (1) that we repeat things and >> (2) that we follow the same stream of thought. From the slides that are now >> in the repo, I can see that we all are hesitant a bit about who says what. >> **** >> >> ** ** >> >> This e-mail is the start of the discussion we will have later today in >> our "private" webex.**** >> >> ** ** >> >> I believe that, high-level, we could separate our speaking time as >> follows:**** >> >> - [5min] draft-watteyne-6tsch-tsch-lln-context-02 [Thomas]**** >> >> >> - *In a nutshell: IEEE802.15.4e TSCH is new L2 standard***** >> - what we are presenting is the first draft generated by the >> group, and which highlights what IEEE802.15.4e TSCH is and what is missing. >> It's the document we used early on in the definition of the problem >> statement within the 6TSCH group, and we therefore present early on in the >> BoF.**** >> - IEEE802.15.4 is a double standard (PHY and MAC) for low-power >> wireless radio. It's a very well-known standard, used at the base of the >> 6LoWPAN, CORE and ROLL WGs.**** >> - IEEE802.15.4e is an amendment to its MAC protocol**** >> - one of the modes is Timeslotted Channel Hopping (TSCH)**** >> - TSCH allows low-power through synchronization, high reliability >> through channel hopping**** >> - nodes in the network follow the TSCH communication schedule**** >> - published IEEE standard, April 2012**** >> >> >> - [10min] what is IEEE802.15.4e TSCH? [Maria Rita]**** >> >> >> - *In a nutshell: IEEE802.15.4e TSCH is a proven technology which >> opens up new applications***** >> - playing with the schedule allows for a clean trade-off between >> throughout, latency, redundancy and power consumption**** >> - allows for a high level of determinism and traffic engineering*** >> * >> - opens up to new range of applications which require high >> reliability and low-power:**** >> >> >> - ** ** >> - Control loops in a wireless process control network, in which >> high reliability and a fully deterministic behavior are required. >> **** >> - Umbrella networks transporting data from different >> independent clients, and for which an operator needs flow isolation and >> traffic shaping.**** >> - Energy harvesting networks, which require an extremely low >> and predictable average power consumption.**** >> >> >> - an analogy of our work can be found in WirelessHART and >> ISA100.11a, although these standards don't use IETF building blocks. Those >> standards use a variant of Timeslotted Channel Hopping, but not >> IEEE802.15.4e.**** >> - we want to define how to run IPv6 on top of IEEE802.15.4e TSCH*** >> * >> - the IEEE802.15.4e standard only defines what nodes do once they >> have a schedule, NOT how to build and maintain that schedule**** >> >> >> - [15min] what is missing? [Xavi]**** >> >> >> - *In a nutshell: blocks are missing***** >> - some building blocks are missing to fit an IPv6 stack onto >> IEEE802.15.4e TSCH. Most of them already exist. We want to provide >> guidelines on how to glue them together.**** >> - the main blocks are:**** >> >> >> - (per draft-watteyne-6tsch-tsch-lln-context-02) guidelines to fully >> define the behavior of the network:**** >> >> >> - ** ** >> - network formation**** >> - election of timing parents needed for synchronization**** >> - network maintenance**** >> - security (mostly key management)**** >> >> >> - building and maintaining the communication schedule:**** >> >> >> - "the orchestra director"**** >> - Both centralized and distributed approaches are >> contemplating**** >> - protocols to coordinate nodes and distribute information*** >> * >> >> >> - multi-hop dataflow**** >> >> >> - integration with RPL (including feeding back metrics)**** >> - packet switching and tunneling**** >> >> >> - QoS and TE (includes different flow/packet priorities, traffic >> classes, and mapping to layer 2 resources)**** >> - ND and backbone architecture**** >> >> Thoughts? I ca go over this during the webex later today.**** >> >> ** ** >> >> Thomas**** >> > > > _______________________________________________ > 6tsch mailing list > 6tsch@ietf.org > https://www.ietf.org/mailman/listinfo/6tsch > >
- Re: [6tsch] the first 30min Thomas Watteyne
- Re: [6tsch] the first 30min Pascal Thubert (pthubert)
- Re: [6tsch] the first 30min Qin Wang
- Re: [6tsch] the first 30min Pascal Thubert (pthubert)
- Re: [6tsch] the first 30min Qin Wang
- Re: [6tsch] the first 30min Maria Rita PALATTELLA
- Re: [6tsch] the first 30min Pascal Thubert (pthubert)