[6tisch] [6P+SF0] CALL FOR CONSENSUS: sending a CLEAR request to old parents
Thomas Watteyne <thomas.watteyne@inria.fr> Tue, 22 November 2016 07:16 UTC
Return-Path: <thomas.watteyne@inria.fr>
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 4DD7D12963F for <6tisch@ietfa.amsl.com>; Mon, 21 Nov 2016 23:16:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level:
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-1.497] 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 KtHXn6nlELED for <6tisch@ietfa.amsl.com>; Mon, 21 Nov 2016 23:16:56 -0800 (PST)
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) (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 5497B12946D for <6tisch@ietf.org>; Mon, 21 Nov 2016 23:16:56 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.31,531,1473112800"; d="scan'208,217";a="246040859"
Received: from mail-wj0-f180.google.com ([209.85.210.180]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 22 Nov 2016 08:16:54 +0100
Received: by mail-wj0-f180.google.com with SMTP id mp19so37949957wjc.1 for <6tisch@ietf.org>; Mon, 21 Nov 2016 23:16:54 -0800 (PST)
X-Gm-Message-State: AKaTC03qPfu/Rw2Donw4xwcelUIfoY+rkqFl8DFyp+cv3F7J9iqcNCYeak6OwUSVGCQX9rTmXGnB/x92w7D2Jw==
X-Received: by 10.195.18.71 with SMTP id gk7mr14806770wjd.175.1479799014715; Mon, 21 Nov 2016 23:16:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.142.23 with HTTP; Mon, 21 Nov 2016 23:16:34 -0800 (PST)
From: Thomas Watteyne <thomas.watteyne@inria.fr>
Date: Tue, 22 Nov 2016 08:16:34 +0100
X-Gmail-Original-Message-ID: <CADJ9OA9ueXO4ySVJA3CEyR9tEEUy4Ji9+asEuFdTWjsHwbVAjg@mail.gmail.com>
Message-ID: <CADJ9OA9ueXO4ySVJA3CEyR9tEEUy4Ji9+asEuFdTWjsHwbVAjg@mail.gmail.com>
To: "6tisch@ietf.org" <6tisch@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c2822a9c7bd20541de8eda"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/evkKvtDREcZ65z69HElHdK5ZcpI>
Subject: [6tisch] [6P+SF0] CALL FOR CONSENSUS: sending a CLEAR request to old parents
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 22 Nov 2016 07:16:58 -0000
In thread "Node Behavior at Boot in SF0" ( https://www.ietf.org/mail-archive/web/6tisch/current/msg04883.html) we ended up discussing the following paragraph https://tools.ietf.org/html/draft-ietf-6tisch-6top-sf0-02#section-10: In order to define a known state after the node is restarted, a CLEAR command is issued to each of the neighbor nodes to enable a new allocation process. The 6P Initial Timeout Value provided by SF0 should allow for the maximum number of TSCH link-layer retries, as defined by Section 4.3.4 of [I-D.ietf-6tisch-6top-protocol]. TODO/ REMARK: The initial timeout is currently under discussion. The suggestion on the table is to: step 1. Change https://tools.ietf.org/html/draft-ietf-6tisch-6top-sf0-02#section-10 to: The 6P Initial Timeout Value provided by SF0 should allow for the maximum number of TSCH link-layer retries, as defined by Section 4.3.4 of [I-D.ietf-6tisch-6top-protocol]. TODO/ REMARK: The initial timeout is currently under discussion. step 2. Add the following text to draft-ietf-6tisch-6top-protocol, by possibly adding a 4.3.X section: 4.3.X. Disconnecting from a neighbor If the SF realizes connection to a particular neighbor is no longer needed (for example a change in parent by the routing protocol), the SF MAY send a CLEAR request to that neighbor to speed up the cleanup process of the cells allocated with that neighbor. I'm hereby opening a call for WG consensus. Please +1 or comment/suggest. The chairs will summarize on Fridat 25 Nov. Thomas -- _______________________________________ Thomas Watteyne, PhD Research Scientist & Innovator, Inria Sr Networking Design Eng, Linear Tech Founder & co-lead, UC Berkeley OpenWSN Co-chair, IETF 6TiSCH www.thomaswatteyne.com _______________________________________
- [6tisch] [6P+SF0] CALL FOR CONSENSUS: sending a C… Thomas Watteyne
- Re: [6tisch] [6P+SF0] CALL FOR CONSENSUS: sending… Lijo Thomas
- Re: [6tisch] [6P+SF0] CALL FOR CONSENSUS: sending… Tengfei Chang
- Re: [6tisch] [6P+SF0] CALL FOR CONSENSUS: sending… Yasuyuki Tanaka
- Re: [6tisch] [6P+SF0] CALL FOR CONSENSUS: sending… Prof. Diego Dujovne
- Re: [6tisch] [6P+SF0] CALL FOR CONSENSUS: sending… Qin Wang
- Re: [6tisch] [6P+SF0] CALL FOR CONSENSUS: sending… Pascal Thubert (pthubert)
- Re: [6tisch] [6P+SF0] CALL FOR CONSENSUS: sending… S.V.R.Anand