Re: [6tisch] 6P and Sf0 issue: Piggybacking data packet with IE confirmation

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 09 March 2016 08:05 UTC

Return-Path: <pthubert@cisco.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 B144A12DBDF for <6tisch@ietfa.amsl.com>; Wed, 9 Mar 2016 00:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([127.0.0.1]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2K5IXXgk3e6m for <6tisch@ietfa.amsl.com>; Wed, 9 Mar 2016 00:05:09 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EA6312D50F for <6tisch@ietf.org>; Wed, 9 Mar 2016 00:05:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18987; q=dns/txt; s=iport; t=1457510709; x=1458720309; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Ks9PHiPuDltJRZAFoycs4a4FFtbr44NK9qUaV7RqoZ0=; b=cTAVOZsXXAs2sDEFH8ZwjPC5Rr17ihaYtzYYt5n3njt2tKX9t6t5FnB1 xvKaIgpTD8NnKENq8TCxV4BDqE27C3NXmLGpwLsxN+oqkMlaMblvN8QTV 6EqZ/px1vebzO2sCmvrSftVEHfYnDRJ5IGN251Z1htQl1useggUWFZUJt 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D9AQBO2N9W/5FdJa1cgm5MUm2qMpA1AQ2BaRcBCYUkSgKBRDgUAQEBAQEBAWQnhEEBAQEEAQEBRiULEAIBCBEEAQEoBycLEwEJCAIEDgWIDwMSDr8nAQEBAQEBAQEBAQEBAQEBAQEBAQEBFYYXgXMIgkeCPYFNEQEpIgEICIJtgQ8Fhh0MgTODW4IyiUYBhHyBVYUwgW+BZIREiFOBMoVdh0oBHgEBQoNkaogYBwIXBIEXAQEB
X-IronPort-AV: E=Sophos;i="5.24,310,1454976000"; d="scan'208,217";a="246566869"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Mar 2016 08:05:08 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u29858LK003811 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 9 Mar 2016 08:05:08 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 9 Mar 2016 02:05:07 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1104.009; Wed, 9 Mar 2016 02:05:07 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Qin Wang <qinwang6top@yahoo.com>
Thread-Topic: [6tisch] 6P and Sf0 issue: Piggybacking data packet with IE confirmation
Thread-Index: AQHReYI8CyTsZHHXvUqmCkkME34sSp9QwcWM
Date: Wed, 09 Mar 2016 08:05:07 +0000
Message-ID: <9162F00F-D55B-4915-852F-ECC378AECBDB@cisco.com>
References: <008701d17614$9f0a4950$dd1edbf0$@cdac.in>, <1841052088.6188684.1457472774706.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <1841052088.6188684.1457472774706.JavaMail.yahoo@mail.yahoo.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_9162F00FD55B4915852FECC378AECBDBciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/ISrW3KoVRr80IQgF4e_4ZXxc98Q>
Cc: Lijo Thomas <lijo@cdac.in>, "6tisch@ietf.org" <6tisch@ietf.org>, "Prof. Diego Dujovne" <diego.dujovne@mail.udp.cl>
Subject: Re: [6tisch] 6P and Sf0 issue: Piggybacking data packet with IE confirmation
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: Wed, 09 Mar 2016 08:05:11 -0000

Hello Qin:

Please consider the message by Tero.

The ack is Mac-layer before upper layer processing and does not guarantee success in the stack.

What we'd really want is suppress the MAC layer ack but not the 6P response.

Another angle (for the sake of making sure we left no stone unturned).

If we think transactionality is too difficult to achieve and that parent/child may lose sync: it is possible to avoid the issues with transactionality by using a bitmap to represent cells like LoRa does with frequencies.

Step 1 the parent provides a list of cells (say 16) that it may allocate to that child in the future. The list may differ per child and may overlap with other children to enable to parent to temporarily give a cell to one child or another.

Step 2 (runtime) the parent sends the bitmap of the cells, bit set if the cell is use child to parent. If this is sent regularly like a frame relay full status, things will eventually sync.

What do you think?

Pascal

Le 8 mars 2016 à 22:34, Qin Wang <qinwang6top@yahoo.com<mailto:qinwang6top@yahoo.com>> a écrit :

Hi Diego,

I also have question regarding to the third message, i.e. Child acknowledge.

In this case, the Child must accept the selected cells in the Parent's message if it received the message. Right? In another word, if the Parent knows the Child has received the message correctly, the Parent can be sure that the selected cells will be added/deleted into/from the Child's schedule. Since the MAC layer ACK can tell Parent the Child has received its message correctly, I think there is no need for the Child to send back the 6P layer Acknowledgement.

Do I miss something?

Thanks
Qin


On Friday, March 4, 2016 7:51 AM, Lijo Thomas <lijo@cdac.in<mailto:lijo@cdac.in>> wrote:


Hi Diego,


Do we really require 3 transactions for 6P operations as mentioned.

The second transaction from the parent contains all the required information  for the task.

In case the 2nd packet is lost, the parent will schedule a RX link which will be unutilized for the time being and can be reallocated depending on the scheduling function.

But if the 3rd transaction is lost, the client will allocate the TX link  and will start transmitting packets.

So can we avoid the ACK packet(3rd transaction) from the client, or is there any added benefit.


Thanks & Regards,
Lijo Thomas





From: 6tisch [mailto:6tisch-bounces@ietf.org] On Behalf Of Prof. Diego Dujovne
Sent: 03 March 2016 21:11
To: 6tisch@ietf.org<mailto:6tisch@ietf.org>
Subject: [6tisch] 6P and Sf0 issue: Piggybacking data packet with IE confirmation

Dear all,
            Given that there is parent preference in cell
selection, a child-initiated transaction triggers a three-step
exchange:
1- Child sends request to Parent with whitelist/blacklist of slotoffsets
2- Parent selects cells
3- Child acknowledges and finishes the transaction
The main idea is to enable an optional Piggybacking of the IE on a
data packet to reduce the number of transmitted packets, but there
are latency concerns when the (data) traffic is low.
Is it worth to enable this option given the added complexity?
Regards,
                                Diego Dujovne

--
DIEGO DUJOVNE
Académico Escuela de Ingeniería en Informática y Telecomunicaciones
Facultad de Ingeniería UDP
www.ingenieria.udp.cl<http://www.ingenieria.udp.cl/>
(56 2) 676 8125

-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------

_______________________________________________
6tisch mailing list
6tisch@ietf.org<mailto:6tisch@ietf.org>
https://www.ietf.org/mailman/listinfo/6tisch


_______________________________________________
6tisch mailing list
6tisch@ietf.org<mailto:6tisch@ietf.org>
https://www.ietf.org/mailman/listinfo/6tisch