Re: [6tisch] 6TiSCH Protocol Stack in draft-ietf-6tisch-architecture-12

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 29 November 2017 16:07 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A35A1271DF for <6tisch@ietfa.amsl.com>; Wed, 29 Nov 2017 08:07:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hLN3z5XIJ2Iu for <6tisch@ietfa.amsl.com>; Wed, 29 Nov 2017 08:07:51 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E735B120727 for <6tisch@ietf.org>; Wed, 29 Nov 2017 08:07:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=52088; q=dns/txt; s=iport; t=1511971670; x=1513181270; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=au74eOJ0CiXVVTKmq3Cmzk9oqvfupeP5zCj+JwASKeo=; b=MIc0NtH5GqG4XPRnudkF93FYpKeufSTgWT3oJn/gv6UludPvUUKFBEZ9 KJXipr0WRDyUTS9byYrk1GhyB409rndQ/n3dMlmfD9sl3ZnRvJNuZGy3k 49mKIyyFepokVYoqN0PxaRSjD8o8PlCmT1eJTHXiVS+XyVRYib0qPqBpF E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C7AQDx2R5a/4MNJK1bGQEBAQEBAQEBAQEBAQcBAQEBAYJKcmZuJweDeJkQgX2WdIIOAwoYAQyER08CGoR6QBcBAQEBAQEBAQFrKIUfAQEBAQMBASEKQQsMBAIBCA4DAQMBASEBBgMCAgIlCxQDBggCBA4FCIk2ZBCnEoInimcBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYNBggmBVoFpgh2BDoMygiSCX4JjBYo6BY5riSMCh3KNEZNajHmJHAIRGQGBOQEhATaBUW8VOoIpglIcgWd3AYhigRQBAQE
X-IronPort-AV: E=Sophos; i="5.44,474,1505779200"; d="scan'208,217"; a="38104842"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Nov 2017 16:07:50 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id vATG7oZb022080 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 Nov 2017 16:07:50 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 29 Nov 2017 10:07:49 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1320.000; Wed, 29 Nov 2017 10:07:49 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Randy Turner <rturner@amalfisystems.com>
CC: Yasuyuki Tanaka <yatch1.tanaka@toshiba.co.jp>, "6tisch@ietf.org" <6tisch@ietf.org>
Thread-Topic: [6tisch] 6TiSCH Protocol Stack in draft-ietf-6tisch-architecture-12
Thread-Index: AQHTaNOG4q/cGgc4v0uua79mwLFK3qMrBVSggAC5WgD//8cUgA==
Date: Wed, 29 Nov 2017 16:07:41 +0000
Deferred-Delivery: Wed, 29 Nov 2017 16:06:39 +0000
Message-ID: <16e908d3289743d0b68d2ef97d25fc3c@XCH-RCD-001.cisco.com>
References: <c196a45d-da0b-e296-e93a-53b9e95e2627@toshiba.co.jp> <276a968c507c49319bf01eb82f582536@XCH-RCD-001.cisco.com> <FDEC3B3D-0B33-481D-BB7D-C5F31F4B6E45@amalfisystems.com>
In-Reply-To: <FDEC3B3D-0B33-481D-BB7D-C5F31F4B6E45@amalfisystems.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.22.5]
Content-Type: multipart/alternative; boundary="_000_16e908d3289743d0b68d2ef97d25fc3cXCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/eMrTRJy7cqhDP5tQdURlWobw9tY>
Subject: Re: [6tisch] 6TiSCH Protocol Stack in draft-ietf-6tisch-architecture-12
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.22
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" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Nov 2017 16:07:53 -0000

Hello Randy

The SF actually triggers 6top messages for bandwidth allocation and the messages can carry opaque (to 6P) SF chat. So no it is not entirely internal algorithms.

Cheers,

Pascal

From: Randy Turner [mailto:rturner@amalfisystems.com]
Sent: mercredi 29 novembre 2017 14:28
To: Pascal Thubert (pthubert) <pthubert@cisco.com>
Cc: Yasuyuki Tanaka <yatch1.tanaka@toshiba.co.jp>; 6tisch@ietf.org
Subject: Re: [6tisch] 6TiSCH Protocol Stack in draft-ietf-6tisch-architecture-12

Hi Guys,

I think this stack diagram looks ok — the “Scheduling Functions” block does not add a protocol encapsulation (on the wire) as the other blocks do, correct? It’s just an internal set of algorithms ?

If so, you could probably leave this off as “internal APIs” or non  on-the-wire functionality would not fit with the rest of the diagram - if non on-the-wire functionality is included then some type of visual cue would be
needed by RPL to indicate that RPL does not only utilize ICMPv6 for its’ functionality but also probably needs connectivity with the “IPv6” block for routing table access, or connectivity down to the TSCH block for neighbor table state changes, etc.

However, all that being said, it’s not a big deal, I’m interpreting this stack as an “on the wire” layering showing where protocol headers are encapsulated/deencapsulated, and I’m assuming there’s a scheduling function somewhere, but it’s really not a protocol layer.  Am I interpreting this correctly?

Thx,
Randy


On Nov 29, 2017, at 3:31 AM, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:

Hello Yatch:

Great point. You’ll note that 6P runs at the top of the MAC and below 6LoWPAN and IP, so I’d rather not group it as you suggest.

What about the following:

   +-----+-----+
   |    COMI   |
   +-----+-----+-----+------+-------+-----+
   | CoAP/EDHOC/COSE |  6LoWPAN ND  | RPL |
   +-----+-----+-----+------+-------+-----+
   |       UDP       |      ICMPv6        |
   +-----+-----+-----+-----+-------+------+
   |                 IPv6                 |
   +--------------------------------------+----------------------+
   |     6LoWPAN HC   /   6LoRH HC        | Scheduling Functions |
   +--------------------------------------+----------------------+
   |     6top (to be IEEE Std 802.15.12) inc. 6top protocol (6P) |
   +-------------------------------------------------------------+
   |                 IEEE Std 802.15.4 TSCH                      |
   +-------------------------------------------------------------+

?

Pascal
-----Original Message-----
From: Yasuyuki Tanaka [mailto:yatch1.tanaka@toshiba.co.jp]
Sent: mercredi 29 novembre 2017 06:33
To: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>
Cc: 6tisch@ietf.org<mailto:6tisch@ietf.org>
Subject: 6TiSCH Protocol Stack in draft-ietf-6tisch-architecture-12

Hello Pascal,

I have one minor comment on Figure 1 of the draft;

   https://tools.ietf.org/html/draft-ietf-6tisch-architecture-12#section-3.1

My suggestion is to put "6LoWPAN HC / 6LoRH" directly on "IEEE Std
802.15.4 TSCH" and to add one box labeled with "Scheduling Functions".
It would look like...

(suggested version)

       +-----+-----+
       |    COMI   |
       +-----+-----+-----+------+-------+-----+
       | CoAP/EDHOC/COSE |  6LoWPAN ND  | RPL |
       +-----+-----+-----+------+-------+-----+
       |       UDP       |        ICMPv6      |
       +-----+-----+-----+-----+-------+------+------------------------+
       |                 IPv6                 |  Scheduling Functions  |
       +--------------------------------------+------------------------+
       |        6LoWPAN HC   /   6LoRH        |      6top protocol     |
       +--------------------------------------+------------------------+
       |                     IEEE Std 802.15.4 TSCH                    |
       +---------------------------------------------------------------+

(current version)

       +-----+-----+
       |    COMI   |
       +-----+-----+-----+------+-------+-----+
       | CoAP/EDHOC/COSE |  6LoWPAN ND  | RPL |
       +-----+-----+-----+------+-------+-----+
       |       UDP       |          ICMP      |
       +-----+-----+-----+-----+-------+------+----+
       |                 IPv6                      |
       +-------------------------------------------+
      |             6LoWPAN HC   /   6LoRH        |
       +-------------------------------------------+
       |                   6top                    |
       +-------------------------------------------+
       |             IEEE Std 802.15.4 TSCH        |
       +-------------------------------------------+

"ICMP" is replaced with "ICMPv6" as well.

Thanks!

Best,
Yatch

_______________________________________________
6tisch mailing list
6tisch@ietf.org<mailto:6tisch@ietf.org>
https://www.ietf.org/mailman/listinfo/6tisch