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

Randy Turner <rturner@amalfisystems.com> Wed, 29 November 2017 13:29 UTC

Return-Path: <rturner@amalfisystems.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 113A6127369 for <6tisch@ietfa.amsl.com>; Wed, 29 Nov 2017 05:29:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.389
X-Spam-Level:
X-Spam-Status: No, score=-5.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
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 2Hjg3ggYQFHp for <6tisch@ietfa.amsl.com>; Wed, 29 Nov 2017 05:29:09 -0800 (PST)
Received: from atl4mhob05.registeredsite.com (atl4mhob05.registeredsite.com [209.17.115.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB581120724 for <6tisch@ietf.org>; Wed, 29 Nov 2017 05:29:08 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.209]) by atl4mhob05.registeredsite.com (8.14.4/8.14.4) with ESMTP id vATDT5Cg001174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <6tisch@ietf.org>; Wed, 29 Nov 2017 08:29:05 -0500
Received: (qmail 24578 invoked by uid 0); 29 Nov 2017 13:29:05 -0000
X-TCPREMOTEIP: 24.30.117.47
X-Authenticated-UID: rturner@amalfisystems.com
Received: from unknown (HELO ?10.0.1.30?) (rturner@amalfisystems.com@24.30.117.47) by 0 with ESMTPA; 29 Nov 2017 13:29:05 -0000
From: Randy Turner <rturner@amalfisystems.com>
Message-Id: <FDEC3B3D-0B33-481D-BB7D-C5F31F4B6E45@amalfisystems.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_49FD470B-A898-4DDB-A3E3-8E651B813363"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 29 Nov 2017 08:28:00 -0500
In-Reply-To: <276a968c507c49319bf01eb82f582536@XCH-RCD-001.cisco.com>
Cc: Yasuyuki Tanaka <yatch1.tanaka@toshiba.co.jp>, "6tisch@ietf.org" <6tisch@ietf.org>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
References: <c196a45d-da0b-e296-e93a-53b9e95e2627@toshiba.co.jp> <276a968c507c49319bf01eb82f582536@XCH-RCD-001.cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/26EjDdpJOxDI8xz7nJsGMtVNCmE>
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 13:29:11 -0000

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> 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 <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 <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 <https://www.ietf.org/mailman/listinfo/6tisch>