Re: [6tisch] WGLC for https://www.ietf.org/id/draft-ietf-6tisch-architecture-17.txt

Simon Duquennoy <simon.duquennoy@ri.se> Thu, 22 November 2018 12:31 UTC

Return-Path: <simon.duquennoy@ri.se>
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 4F5A0129AB8; Thu, 22 Nov 2018 04:31:47 -0800 (PST)
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=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 WrzKH7YMZhcp; Thu, 22 Nov 2018 04:31:42 -0800 (PST)
Received: from smtp-out11.electric.net (smtp-out11.electric.net [185.38.181.40]) (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 9C8C812D4E8; Thu, 22 Nov 2018 04:31:41 -0800 (PST)
Received: from 1gPo8x-000E1J-TG by out11a.electric.net with emc1-ok (Exim 4.90_1) (envelope-from <simon.duquennoy@ri.se>) id 1gPo8x-000E3K-Uj; Thu, 22 Nov 2018 04:31:39 -0800
Received: by emcmailer; Thu, 22 Nov 2018 04:31:39 -0800
Received: from [194.218.146.197] (helo=sp-mail-2.sp.se) by out11a.electric.net with esmtps (TLSv1.2:ECDHE-RSA-AES128-SHA256:128) (Exim 4.90_1) (envelope-from <simon.duquennoy@ri.se>) id 1gPo8x-000E1J-TG; Thu, 22 Nov 2018 04:31:39 -0800
Received: from mail-wm1-f44.google.com (10.116.0.226) by sp-mail-2.sp.se (10.100.0.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1531.3; Thu, 22 Nov 2018 13:31:39 +0100
Received: by mail-wm1-f44.google.com with SMTP id c126so8931819wmh.0; Thu, 22 Nov 2018 04:31:38 -0800 (PST)
X-Gm-Message-State: AA+aEWa/4l1BmwKjPe5fP2n4SRqyPVMQZhXE1VXsuuLkXHXrdeMnRuPl 2kJv2yt6Ab17P+paf6nZGWxWU5tFSvz+1j7XkX8=
X-Google-Smtp-Source: AFSGD/UwEkdo48wefVZEQP+sITrxNqn4L5yULiuicGq1nA/vDU/9X5wwluM12V0gY2CCfgI+3HaeuGLC4xBEirEu3L0=
X-Received: by 2002:a7b:ca53:: with SMTP id m19mr6792718wml.102.1542889893216; Thu, 22 Nov 2018 04:31:33 -0800 (PST)
MIME-Version: 1.0
References: <eaeba2a200c644738778e865a5f539b2@XCH-RCD-001.cisco.com> <CAMxvJtLgaEKCuNmSi-LW8his=et1e=9hBtT0P7Y5pD5FWcpwuA@mail.gmail.com> <68e645171a5249d8bf60ea7237a73fe7@XCH-RCD-001.cisco.com>
In-Reply-To: <68e645171a5249d8bf60ea7237a73fe7@XCH-RCD-001.cisco.com>
From: Simon Duquennoy <simon.duquennoy@ri.se>
Date: Thu, 22 Nov 2018 13:31:23 +0100
X-Gmail-Original-Message-ID: <CAMxvJtK4jrfCxB_CPJOCTkE2EQAgcZcZ4jrEo2LTT7A5-Fjm3Q@mail.gmail.com>
Message-ID: <CAMxvJtK4jrfCxB_CPJOCTkE2EQAgcZcZ4jrEo2LTT7A5-Fjm3Q@mail.gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
CC: 6tisch <6tisch@ietf.org>, 6tisch-ads@ietf.org, 6tisch-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000349a6057b400cc6"
X-Originating-IP: [10.116.0.226]
X-ClientProxiedBy: sp-mail-3.sp.se (10.100.0.163) To sp-mail-2.sp.se (10.100.0.162)
X-Outbound-IP: 194.218.146.197
X-Env-From: simon.duquennoy@ri.se
X-Proto: esmtps
X-Revdns:
X-HELO: sp-mail-2.sp.se
X-TLS: TLSv1.2:ECDHE-RSA-AES128-SHA256:128
X-Authenticated_ID:
X-PolicySMART: 14510320
X-Virus-Status: Scanned by VirusSMART (c)
X-Virus-Status: Scanned by VirusSMART (s)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/zKzhgXf-11QvaEdGPKcy0KpX5vg>
Subject: Re: [6tisch] WGLC for https://www.ietf.org/id/draft-ietf-6tisch-architecture-17.txt
X-BeenThere: 6tisch@ietf.org
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" <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: Thu, 22 Nov 2018 12:31:47 -0000

Thanks a lot, Pascal!
Simon


On Thu, Nov 22, 2018 at 1:08 PM Pascal Thubert (pthubert) <
pthubert@cisco.com> wrote:

> Hello Simon
>
>
>
> I added the following on your behalf
>
>
>
>           <xref target="I-D.ietf-6tisch-msf">MSF</xref> is one of the
> possible
>
>            scheduling functions. MSF uses the rendez-vous slot from
>
>            <xref target="RFC8180"/> for network discovery, neighbor
> discovery,
>
>            and any other broadcast.
>
>            For basic unicast communication with any neighbor, each node
> uses a
>
>            receive cell at a well-known slotOffset/channelOffset, derived
> from
>
>            a hash of their own MAC address.
>
>            Nodes can reach any neighbor by installing a transmit (shared)
> cell
>
>            with slotOffset/channelOffset derived from the neighbor's MAC
> address.
>
>            For child-parent links, MSF continuously monitors the load
> to/from
>
>            parents and children. It then uses 6P to install/remove unicast
> cells
>
>            whenever the current schedule appears to be under-/over-
> provisioned.
>
>
>
> Please note this makes you contributor. I also added your name in the
> contributor section if you do not mind.
>
>
>
> Take care,
>
>
>
> Pascal
>
>
>
> *From:* Simon Duquennoy <simon.duquennoy@ri.se>
> *Sent:* jeudi 22 novembre 2018 09:50
> *To:* Pascal Thubert (pthubert) <pthubert@cisco.com>
> *Cc:* 6tisch <6tisch@ietf.org>; 6tisch-ads@ietf.org;
> 6tisch-chairs@ietf.org
> *Subject:* Re: [6tisch] WGLC for
> https://www.ietf.org/id/draft-ietf-6tisch-architecture-17.txt
>
>
>
> Hi Pascal, WG,
>
>
>
> I drafted a summary of MSF for potential inclusion in 4.4.2.
>
>
>
> The proposal is to:
>
> (1) Remove MSF mention in "An optional Scheduling Function (SF) such as
> MSF [I-D.ietf-6tisch-msf] is used to"
>
> ->  "An optional Scheduling Function (SF) is used to"
>
> (2) Add the following paragraph at the end of the section:
>
> ========
>
> As an example SF, we briefly introduce MSF [I-D.ietf-6tisch-msf].
>
> MSF uses the rendez-vous slot from [RFC8180] for network discovery,
> neighbor discovery, and any other broadcast.
>
> For basic unicast communication with any neighbor, each node has a receive
> cells at a well-known slotOffset/channelOffset, derived from a hash of
> their own MAC address.
>
> Nodes can reach any neighbor by installing a transmit (shared) cell with
> slotOffset/channelOffset derived from the neighbor's MAC address.
>
> For child-parent links, MSF continuously monitors the load to/from parents
> and children.
>
> It then uses 6P to install/remove unicast cells whenever the current
> schedule appears to be under-/over- provisioned.
>
> ========
>
>
>
> Thank you,
>
> Simon
>
>
>
>
>
> On Sun, Nov 11, 2018 at 3:23 AM Pascal Thubert (pthubert) <
> pthubert@cisco.com> wrote:
>
> Dear WG :
>
>
>
> We are now starting the working group last call for the 6TiSCH
> Architecture based on
> https://www.ietf.org/id/draft-ietf-6tisch-architecture-17.txt. This
> document is the merge of the previous architecture and terminology
> documents.
>
>
>
> Authors of our WIP WG docs draft-ietf-6tisch-dtsecurity-zerotouch-join-03
> <https://datatracker.ietf.org/doc/draft-ietf-6tisch-dtsecurity-zerotouch-join/>,
> draft-ietf-6tisch-enrollment-enhanced-beacon-00
> <https://datatracker.ietf.org/doc/draft-ietf-6tisch-enrollment-enhanced-beacon/>,
> draft-ietf-6tisch-minimal-security-08
> <https://datatracker.ietf.org/doc/draft-ietf-6tisch-minimal-security/> and
> draft-ietf-6tisch-msf-01
> <https://datatracker.ietf.org/doc/draft-ietf-6tisch-msf/> are requested
> to pay particular attention on how their work is reflected in the
> Architecture, and are strongly encouraged to propose new text to improve
> the correctness of that representation.
>
>
>
> The architecture is a foundational product of the WG, providing the view
> on the whole stack that we designed, implemented and interop tested over
> the 5 years of activity of the group; it is in some form a testimony of the
> WG.
>
> With this in mind, please pay a very special attention when reviewing it.
>
>
>
> The WGLC ends on Friday November 30th, 2018.
>
>
>
> Many thanks in advance;
>
>
>
> The chairs.
>
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch
>
>