Re: [6tisch] Handling Inconsistent Allocation in 6P
Qin Wang <qinwang6top@yahoo.com> Thu, 01 December 2016 20:55 UTC
Return-Path: <qinwang6top@yahoo.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 D90EF129B0F for <6tisch@ietfa.amsl.com>; Thu, 1 Dec 2016 12:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.596
X-Spam-Level:
X-Spam-Status: No, score=-5.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-2.896, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 KazlJ8zs26Ns for <6tisch@ietfa.amsl.com>; Thu, 1 Dec 2016 12:55:27 -0800 (PST)
Received: from nm25-vm1.bullet.mail.bf1.yahoo.com (nm25-vm1.bullet.mail.bf1.yahoo.com [98.139.212.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAF4D129CF5 for <6tisch@ietf.org>; Thu, 1 Dec 2016 12:46:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1480625171; bh=bkNVVJ54uRjqDo/ppovsE75AKwyqvjTZJADeqgdUPAI=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=h0+Nv3ZJowFBVvWUupAyZ8AHfi78gVPzbp7x0XI84037/kaO4PSOYzZ8CCzsUPaMFLIyb3aRDUXgbEkwMiJFssXDl3jatoXzddM2AyUnVhKKkMm4EeRPbImFTa+Qsj0nGzfk99bEHFxja7xbvHa5J1SVZ/6yKVa3qxLj6Y+XucivdcEo4gDWQHUYYRMHVX3t9EHwm/j4pz4k8SIFhW0fUNN3WSoY/lkjtpj6dgI84AISYCv6aA8rr3lLUQDEscZDeuNbEh/I5TwTZhNRYlXp4QyB5XUjwk+vn0oMPFr05f+I+QNXOU5GivptnKQcXYeLydAxU2prifoxSo2Z1QMsuA==
Received: from [66.196.81.172] by nm25.bullet.mail.bf1.yahoo.com with NNFMP; 01 Dec 2016 20:46:11 -0000
Received: from [98.139.215.248] by tm18.bullet.mail.bf1.yahoo.com with NNFMP; 01 Dec 2016 20:46:11 -0000
Received: from [127.0.0.1] by omp1061.mail.bf1.yahoo.com with NNFMP; 01 Dec 2016 20:46:11 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 873236.68166.bm@omp1061.mail.bf1.yahoo.com
X-YMail-OSG: H7ASjKsVM1lY7h8SjDUvMJNE8l9Z7OJ2htUuLV1JYjcXdPvooPfvXtGP0A75Acb F2enBgAqvaJXFUPVkx5gX8fYie1luTpst0BY84pGtA3171q7NIJyYmwJ4kBdLt5l7JVkbRUpzmNs djHoVM12t2PfIu3f1Jkr35XWEDOe6y59NGxEjh9Y6lrrBj1uJp.UQ7fqpMwGsWOjJW13s3Gh8ble lhYAq3L2wuzoU9PzJQ1gba11PH5lfU0z8akC1uh6p4eEqkqyIGOJ8zRPHmLMJuuzWqjJQxpPNt6r HzgYfgW.o2VBMwkfgU_KOKFExNEBuawIqbaqJYAJhpdPa3s09d9d0T2oIFGen7cAdF9I9cUEvfmo s0TUmZvvrkeUarNp_6lcBWuJxfydefojYT7jIR8PiupconSdES1iswHadQujGKSoeOtETNx_Pab7 6r6oa0DCg_pgbDRcARgqUmgkqAxKQMIHqWJMDAA9hSWmkyP_KCxs4DyzC.o8C52fYQ7bGgtu_H6s k2MIb2cZ9seeRNGCw8Iq2XjrN46nKS4EIeVQ-
Received: from jws400077.mail.bf2.yahoo.com by sendmailws105.mail.bf1.yahoo.com; Thu, 01 Dec 2016 20:46:11 +0000; 1480625171.465
Date: Thu, 01 Dec 2016 20:45:29 +0000
From: Qin Wang <qinwang6top@yahoo.com>
To: Yasuyuki Tanaka <yasuyuki9.tanaka@toshiba.co.jp>, "6tisch@ietf.org" <6tisch@ietf.org>
Message-ID: <1892811491.4637219.1480625129906@mail.yahoo.com>
In-Reply-To: <e6fd1612-6239-16d7-acad-6f6fdca05db9@toshiba.co.jp>
References: <1739694970.195512.1479755120596.JavaMail.root@vilafranca.uoc.es> <CAC9+vPiG9ZqziO8ktpuwJrc4YcRQ7Wj1e+ZciNHmZvUE9JafPw@mail.gmail.com> <CADJ9OA-BZrQHEX9yeSoj3_8p-NOoqq0g8o=6hZ_JS-53b+vNYQ@mail.gmail.com> <e431f7a2-48bb-0605-5a90-bdb0cc134322@toshiba.co.jp> <1833275349.763606.1479942137593@mail.yahoo.com> <b19ebf9e-f175-f871-3653-5c89f7201a6c@toshiba.co.jp> <417706060.2950304.1480455632701@mail.yahoo.com> <c1dcec38-7d34-a753-0e33-6a6e6b7582ff@toshiba.co.jp> <1761859297.3541335.1480523975213@mail.yahoo.com> <e6fd1612-6239-16d7-acad-6f6fdca05db9@toshiba.co.jp>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_4637218_85006544.1480625129903"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/Kk_YC8EN3XY90T1F3x43uwCiaV0>
Subject: Re: [6tisch] Handling Inconsistent Allocation in 6P
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Qin Wang <qinwang6top@yahoo.com>
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, 01 Dec 2016 20:55:34 -0000
Hi Yasuyuki, I think nodeA=>nodeB request process includes two parts, one is Tx from nodeA to nodeB, another part is for nodeB's MAC to process the Request message. As you mentioned, failure of the first part can be identified by mac-ack from nodeB, but not the second part. Right? ThanksQin On Wednesday, November 30, 2016 1:49 PM, Yasuyuki Tanaka <yasuyuki9.tanaka@toshiba.co.jp> wrote: Thanks, Qin. > (1) Timeout in nodeA can be triggered either by failure in > nodeA=>nodeB request process and by failure in nodeB=>nodeA response > process (i.e the process in above example). nodeA cannot tell exact > reason for a event of Timeout by itself. In another word, nodeA > cannot tell there is a inconsistency between its schedule and > nodeB's schedule just based on Timeout. Right? That is right; failure in the nodeA=>nodeB case is what I called "false positive." But, nodeA could lower the possibility of false positive by using MAC-layer ACK, implementation efforts. If nodeA doesn't receive a MAC-layer ACK to its request frame, nodeA can consider the transaction as having failed without inconsistency. > (2) sending CLEAR, or STATUS, or LIST usually happens after a > inconsistency is found, and the function of generation counter is > exactly to find out the inconsistency. Make sense? I'd say the generation counter is not the only way to detect inconsistency. STATUS/LIST could detect it as well, although STATUS/LIST always fails with RC_ERR_GEN in a case of inconsistency according to the latest draft. The generation counter can find inconsistency as you mentioned, but it has disadvantages: - It needs 6P to keep per-neighbor states (ignore SeqNum for now) even when there is no ongoing transaction. - It cannot detect inconsistency until a subsequent transaction; it may take a long time. The reactive approach using timeout doesn't have such disadvantages; furthermore, it's simpler than the the schedule generation management, in my opinion. I still cannot see why the generation management at 6P is really needed... Best, Yatch On 2016/11/30 17:39, Qin Wang wrote: > Hi Yasuyuki, > > (1) Timeout in nodeA can be triggered either by failure in nodeA=>nodeB request process and by failure in nodeB=>nodeA response process (i.e the process in above example). nodeA cannot tell exact reason for a event of Timeout by itself. In another word, nodeA cannot tell there is a inconsistency between its schedule and nodeB's schedule just based on Timeout. Right? > > (2) sending CLEAR, or STATUS, or LIST usually happens after a inconsistency is found, and the function of generation counter is exactly to find out the inconsistency. Make sense? > > Thanks > Qin _______________________________________________ 6tisch mailing list 6tisch@ietf.org https://www.ietf.org/mailman/listinfo/6tisch
- [6tisch] Handling Inconsistent Allocation in 6P Yasuyuki Tanaka
- Re: [6tisch] Handling Inconsistent Allocation in … Xavi Vilajosana Guillen
- Re: [6tisch] Handling Inconsistent Allocation in … Thomas Watteyne
- Re: [6tisch] Handling Inconsistent Allocation in … Yasuyuki Tanaka
- Re: [6tisch] Handling Inconsistent Allocation in … Qin Wang
- Re: [6tisch] Handling Inconsistent Allocation in … Yasuyuki Tanaka
- Re: [6tisch] Handling Inconsistent Allocation in … Qin Wang
- Re: [6tisch] Handling Inconsistent Allocation in … Yasuyuki Tanaka
- Re: [6tisch] Handling Inconsistent Allocation in … Qin Wang
- Re: [6tisch] Handling Inconsistent Allocation in … Yasuyuki Tanaka
- Re: [6tisch] Handling Inconsistent Allocation in … Qin Wang
- Re: [6tisch] Handling Inconsistent Allocation in … Yasuyuki Tanaka
- Re: [6tisch] Handling Inconsistent Allocation in … Xavi Vilajosana Guillen
- Re: [6tisch] Handling Inconsistent Allocation in … Yasuyuki Tanaka