Re: [6tisch] comments/thoughts/edits on 6tisch-architecture

"Pascal Thubert (pthubert)" <> Fri, 14 December 2018 02:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CEC68127598 for <>; Thu, 13 Dec 2018 18:46:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -15.959
X-Spam-Status: No, score=-15.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rzzmkW2vPA9Q for <>; Thu, 13 Dec 2018 18:46:10 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DF3D0130F7B for <>; Thu, 13 Dec 2018 18:46:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=4134; q=dns/txt; s=iport; t=1544755569; x=1545965169; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=09ptMEYGySZqLXUwJ9DKAaEnrEmY1eCZNPLjBAeOB2k=; b=TuUyLpfsR6/x6RJxbKbuKQvw2igKgxGpuUUWCCDX2KhYd2Oihq1zMxqd yuZBwwjfOPWzeDYErY72BxCpcQd2j7rg/I9iPtl/TYgBZfNO2QlgiO8Dh WKUlP4v8BrsO9hwIyDTc/GY0SSTzZabjMbwkYHSluVcn1eeEiZOsbDPw4 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.56,351,1539648000"; d="scan'208";a="277324110"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Dec 2018 02:45:52 +0000
Received: from ( []) by (8.15.2/8.15.2) with ESMTPS id wBE2jqV3016891 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 14 Dec 2018 02:45:52 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 13 Dec 2018 20:45:51 -0600
Received: from ([]) by ([]) with mapi id 15.00.1395.000; Thu, 13 Dec 2018 20:45:51 -0600
From: "Pascal Thubert (pthubert)" <>
To: Michael Richardson <>
CC: "" <>
Thread-Topic: [6tisch] comments/thoughts/edits on 6tisch-architecture
Thread-Index: AQHUkyYQuX+VAdd/Ckmz1zVLZjr9oKV9h/U0
Date: Fri, 14 Dec 2018 02:45:51 +0000
Message-ID: <>
References: <20849.1544734467@localhost>
In-Reply-To: <20849.1544734467@localhost>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [6tisch] comments/thoughts/edits on 6tisch-architecture
X-Mailman-Version: 2.1.29
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" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 14 Dec 2018 02:46:14 -0000

Hello Michael 

A great many thanks.

DetNet architecture can be a normative ref no problem there. We are concluding the WGLC changes in parallel, both docs will ship at roughly the same time.

I’ll act on all this today. I’ll be in a plane so I may not be able to push the result till your afternoon. If you change the xml please avoid the impacted areas till I do.

All the best!


> Le 14 déc. 2018 à 00:54, Michael Richardson <> a écrit :
> {I did a bunch of comments a few weeks ago on my phone, but it's
> a mess, and it lost a bunch of notes and I'm having to partially start over
> again}
> This is a summary of the changes I've suggested and/or committed:
> 1) ietf-detnet-use-cases is mentioned three times.
>   ietf-detnet-architecture is mentioned ten times.
>   They are Informational references.
>   I knew that things were related, but I didn't know that so much had
>   moved!  Since detnet-use-cases and detnet-architecture are in the IESG
>   queue, I think that maybe some could be a normative reference if
>   desired. I don't feel strongly here.
>   I have only scanned the ToC of the use-cases document and architecture.
>   If it's really informative, then that's all I should need to do,
>   right?
> 2) I don't like this sentence:
>   In order to enable the convergence of IT and OT in LLN environments,
>   6TiSCH ports the IETF suite of protocols that are defined for such
>   environments over the TSCH MAC.
> I have suggested:
>   In order to enable the convergence of IT and OT in LLN environments,
>   6TiSCH suports a subset of the IETF suite of protocols (IP) over the
> I've inserted "subset" to imply that one doesn't have to implement all the
> protocols.  Some might think they need to fit "finger" into their mote...
> 3) is: "domotics" a word I don't know, or a typo?
>   (section 1, last paragraph)
> 4) I fixed reference for IE registry to RFC8137.
> 5) I found the reference to "RPL applicability in industrial networks"
>   a poor reference.  The 6tisch WG replaces that document, and so I think
>   that we don't need further back references.
>   There is a second reference about cranes in section 3.2, which I think we
>   can live without.
> 6) I'd sure like to reference useofrplinfo in section 3.1, after:
>    "Header (SRH) in non-storing mode" + as explained in useofrplinfo..
>    but that would be a normative reference to a document that I can't
>    promise will get to the IESG publication queue soon.  Would this MISSREF
>    be acceptable?
> I am continuing to read/edit-for-grammar, but I thought I'd send this email
> to gather some feedback.
> --
> Michael Richardson <>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> _______________________________________________
> 6tisch mailing list