Re: [6tsch] 1c "Why is this a problem? " BoF slides
Qin Wang <qinwang@berkeley.edu> Mon, 22 July 2013 15:34 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 68A9711E8121 for <6tsch@ietfa.amsl.com>;
Mon, 22 Jul 2013 08:34:36 -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 4ALxFSbwpgkV for
<6tsch@ietfa.amsl.com>; Mon, 22 Jul 2013 08:34:32 -0700 (PDT)
Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com
[209.85.223.173]) by ietfa.amsl.com (Postfix) with ESMTP id 1513521E80AF for
<6tsch@ietf.org>; Mon, 22 Jul 2013 08:34:31 -0700 (PDT)
Received: by mail-ie0-f173.google.com with SMTP id k13so15387360iea.4 for
<6tsch@ietf.org>; Mon, 22 Jul 2013 08:34:30 -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=sODOalY3t7XPav91YbvPRLhAS3jNeM6AKSuN0aGFqdI=;
b=WZuous4HKjQUngUraYTu4IsiAwvyOJzUTWKHnHqon1TNmi8hH60gY99SYPelos5T95
1HxjjLAjQoqJV4/GrxqlU1VT53W5xHhHqbxK8ZkL5NgeCIaJwfGCmlUN9JNxznDprwRv
kYYDlJHtZJMYLsgbRVIMdSvHbKDT0UECtm1wjNs5o8uxvmJ96fFHsQ9hKFdleChP7j27
hZxnIVPnbpcOfIrCE6VxVnAoi1PWS34hziVj0hDYe5LQ+/+7ujGP/+OSZCxM940AZRv3
ZtQWdPLaOyzCH0jPztipgoSDpchp48LLBtY99VrpTWl6OjgLK+gqfwjcppUdVngwGJXP a5Pw==
MIME-Version: 1.0
X-Received: by 10.50.67.43 with SMTP id k11mr10374762igt.26.1374507270588;
Mon, 22 Jul 2013 08:34:30 -0700 (PDT)
Received: by 10.64.171.82 with HTTP; Mon, 22 Jul 2013 08:34:30 -0700 (PDT)
In-Reply-To: <51ed4fe5.03210f0a.03c0.1e9d@mx.google.com>
References: <CADJ9OA9GpdK8BCONDVNZ-ay1d+4Jnr_ea3OKEK_X6pKubt2vEA@mail.gmail.com>
<CAAzoce5jHS16QsyE0Gs5CUQca6-oukOjLs6a1NZb=ckM7JfjOA@mail.gmail.com>
<CAM4EQiO47BeCj3ihs_j5CM4sU5NJjvJuvx7XsBQvGNadJjr6HA@mail.gmail.com>
<CAAzoce7AoLW14=BYpN5Fx4SLN_bmjiAxoOzJoRyxrPu5z_NOdw@mail.gmail.com>
<CAM4EQiM2mVGHSyk+C40q_WLf0zkrkxPxunXSBhDhntGqF5y=dg@mail.gmail.com>
<CAAzoce5RcroOMR6gmtYFXdkgZTiv2tfTXCJvd1gLMXxCo9+Pjg@mail.gmail.com>
<51ed2a92.84520f0a.3287.ffffe42d@mx.google.com>
<CAAzoce6u5sjiy9TPmEpsEx2tpi6ibOCSi2jLX1PC-UrTm_q4Hw@mail.gmail.com>
<51ed4fe5.03210f0a.03c0.1e9d@mx.google.com>
Date: Mon, 22 Jul 2013 23:34:30 +0800
Message-ID: <CAAzoce5=2JK-9Or_x6Sp76bpy7URUUwbsy4C05YJNm+MdLYtMw@mail.gmail.com>
From: Qin Wang <qinwang@berkeley.edu>
To: Alfredo Grieco <alfredo.grieco@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd76db09ad7e804e21b69e4
X-Gm-Message-State: ALoCoQkmSjMSR568mX/JOSDqfgLwMj0twyFz0aCwSwVw5pJJcG2zT8FQtis1ZTwoNOuPBh8IQS2X
Cc: 6TSCH <6tsch@ietf.org>
Subject: Re: [6tsch] 1c "Why is this a problem? " BoF slides
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:34:36 -0000
Alfredo, It may be too heavy to coordinate with WirelessHart and ISA100.11a. Should we commit it? I think we need to discuss the problem in ML. How do you think? Qin On Mon, Jul 22, 2013 at 11:29 PM, Alfredo Grieco <alfredo.grieco@gmail.com>wrote;wrote: > Hi Qin, > > There is also this further clarification in 6.1.2 > > “In that mode, the PCE may coordinate with a WirelessHART Network Manager > or > an ISA100.11a System Manager in order to specify the flows that are to be > transported transparently over the Track.” > > I was referring to this last one. > > What do you think ? > > Cheers and thanks > > Al > > Da: Qin Wang [mailto:qinwang@berkeley.edu] > Inviato: Monday, July 22, 2013 5:20 PM > A: Alfredo Grieco > Cc: 6TSCH > Oggetto: Re: [6tsch] 1c "Why is this a problem? " BoF slides > > Hi Alfredo, > > Thank you very much for finding it out, i.e. in section 6, > > "As a result, as long as the TSCH MAC (and Layer 2 security) accepts a > frame, that frame can be switched regardless of the protocol, whether this > is an IPv6 packet, a 6LoWPAN fragment, or a frame from an alternate > protocol > such as WirelessHART of ISA100.11a." > > But, from implementation point of view, it seems to me that the NW layer of > WirelessHART or ISA100.11a has to call the commands of 6top, instead of the > primitives of DL layer defined in WirelessHart and ISA100.11a. I'm not sure > if it works for WirelessHart and ISA100.11a. > > Thought? > Qin > > > > On Mon, Jul 22, 2013 at 8:50 PM, Alfredo Grieco <alfredo.grieco@gmail.com> > wrote: > Hi Qin, > > Sorry for the late reply. > > If you go to Sec. 6 of the architecture draft > (http://tools.ietf.org/html/draft-thubert-6tsch-architecture-02) we > explicitly say that ISA100.11a and WiHart could interoperate with a 6tsch > lln. > > In this sense, we move from competing to interoperating standards. > > Does it sound for you ? > > Thanks > > Alfredo > > > > > > Da: Qin Wang [mailto:qinwang@berkeley.edu] > Inviato: Friday, July 19, 2013 10:35 PM > A: Alfredo Grieco > Cc: Thomas Watteyne; 6TSCH; Pascal Thubert (pthubert) > Oggetto: Re: [6tsch] 1c "Why is this a problem? " BoF slides > > Alfredo, > > Thank you for clarifying. But, I'm still confused. Maybe I missed > something. > Can you tell me what you mean by "competing stds"? > > Thanks! > Qin > > On Sat, Jul 20, 2013 at 4:21 AM, Alfredo Grieco <alfredo.grieco@gmail.com> > wrote: > Qin, > > I was saying the opposite: 6top goes on top. > > There was a nice picture shown by Pascal in one of our weekly call several > weeks ago. > > Of course, the point you raise about ipv6 taking advantage from tsch is ok. > > Cheers > > Alfredo > > On Friday, July 19, 2013, Qin Wang wrote: > Hi Alfredo, > > I don't think WirelessHart and ISA100.11a can be added on top of 6top. The > reasons are: > > (1) They have their own and different protocol stacks. > (2) They use Timeslotted channel hopping technology, but not IEEE802.15.4e > TSCH. > > So, according to my understanding, the problem is how IPv6 protocol stack > can take advantage of TSCH, which has been proven good and standardized by > IEEE. > > Thought? > Qin > > > On Sat, Jul 20, 2013 at 3:33 AM, Alfredo Grieco <alfredo.grieco@gmail.com> > wrote: > Dear Qin, > > As far as I remember, it could be also possible to embrace other > technologies by adding on top of them 6top. No need to replace but include > other technologies. > > Cheers > > Alfredo > > > On Friday, July 19, 2013, Qin Wang wrote: > Hi Thomas and All, > > The first item of problems in the slide is: > > Customer dissatisfaction with competing stds > -> no device interop, double opex > -> lack of common network management > What does "competing stds" refer to? Referring to existing standards like > WirelessHart, ISA100.11a, or something else? From the statement, it may be > derived that 6TSCH WG wants to create a common standard to replace the > competing standards. It is not our objective, right? > Maybe I misunderstand something. Please point out. > Thanks > Qin > > > > > > On Sat, Jul 20, 2013 at 12:10 AM, Thomas Watteyne > <watteyne@eecs.berkeley.edu> wrote: > All, > > FYI, I pushed the 1c "Why is this a problem? " BoF slides we modified live > during the webex onto the repo. You'll find the latest version at > https://bitbucket.org/6tsch/meetings/src/master/130730_ietf-87_berlin > > Thomas > > _______________________________________________ > 6tsch mailing list > 6tsch@ietf.org > https://www.ietf.org/mailman/listinfo/6tsch > > > > > >
- [6tsch] 1c "Why is this a problem? " BoF slides Thomas Watteyne
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Qin Wang
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Alfredo Grieco
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Qin Wang
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Alfredo Grieco
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Qin Wang
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Alfredo Grieco
- [6tsch] R: 1c "Why is this a problem? " BoF slides Alfredo Grieco
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Qin Wang
- [6tsch] R: 1c "Why is this a problem? " BoF slides Alfredo Grieco
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Qin Wang
- [6tsch] R: 1c "Why is this a problem? " BoF slides Alfredo Grieco
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Pascal Thubert (pthubert)
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Qin Wang
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Pascal Thubert (pthubert)
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Qin Wang
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Kris Pister
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Pascal Thubert (pthubert)
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Kris Pister
- Re: [6tsch] 1c "Why is this a problem? " BoF slid… Pascal Thubert (pthubert)