[6tsch] R: 1c "Why is this a problem? " BoF slides

"Alfredo Grieco" <alfredo.grieco@gmail.com> Mon, 22 July 2013 15:30 UTC

Return-Path: <alfredo.grieco@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 4380C21E808A for <6tsch@ietfa.amsl.com>; Mon, 22 Jul 2013 08:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 B0OF7UG9uEMt for <6tsch@ietfa.amsl.com>; Mon, 22 Jul 2013 08:30:11 -0700 (PDT)
Received: from mail-ee0-x234.google.com (mail-ee0-x234.google.com [IPv6:2a00:1450:4013:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 20AF621E808D for <6tsch@ietf.org>; Mon, 22 Jul 2013 08:29:47 -0700 (PDT)
Received: by mail-ee0-f52.google.com with SMTP id c50so3967134eek.11 for <6tsch@ietf.org>; Mon, 22 Jul 2013 08:29:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=mAs26yMwrqeid4kjrHbcUj0s+P/Aj/DTV+v9fok83/Y=; b=Mpwv8P9KvpRWLCC8+2iGvRgMvQyoFyOLol+74GjcEqlBuZXMAf+LhQOhOIUiGsrdZw gTzx8FoFyYCcR9/txuDAK1CDe2o3v+g/wYoN4ZotLUvl1c7i2fwFxt5oihOxYvrrmxSb KQJXiwiOHIDLBEOdusPhwUc8Iy9iNPiOAGCETQrUNti/l7GTdCFzR9KpBQ5thY1ScizZ +7bhlQqC4LlBBnTuYVcCmr2AR3KqBUEcMv6r6D0vl7+/Ji6pCDsv5RyoKwIzQX3dUmit JzHOoh9N9BzMo0Rjy3qZbPN305P2PatjuXLqz6Wf0RFvgpcU4E6BAp8hfcag8tx4ODaG 6q4Q==
X-Received: by 10.14.173.130 with SMTP id v2mr28483272eel.29.1374506982479; Mon, 22 Jul 2013 08:29:42 -0700 (PDT)
Received: from GriecoPC (deecom23.poliba.it. [193.204.59.55]) by mx.google.com with ESMTPSA id b3sm51545794eev.10.2013.07.22.08.29.41 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 22 Jul 2013 08:29:41 -0700 (PDT)
From: "Alfredo Grieco" <alfredo.grieco@gmail.com>
To: "'Qin Wang'" <qinwang@berkeley.edu>
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>
In-Reply-To: <CAAzoce6u5sjiy9TPmEpsEx2tpi6ibOCSi2jLX1PC-UrTm_q4Hw@mail.gmail.com>
Date: Mon, 22 Jul 2013 17:29:39 +0200
Message-ID: <51ed4fe5.03210f0a.03c0.1e9d@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac6G7vFc02b/sQtgRsOV+avucpWEHQAAS11Q
Content-Language: en-us
Cc: '6TSCH' <6tsch@ietf.org>
Subject: [6tsch] R: 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:30:13 -0000

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