Re: [6tisch] 6P and Sf0 issue: Token to identify transactions in 6P

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 09 March 2016 07:13 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 A4B0212DF0B for <6tisch@ietfa.amsl.com>; Tue, 8 Mar 2016 23:13:06 -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 lszp_HRmwZDl for <6tisch@ietfa.amsl.com>; Tue, 8 Mar 2016 23:13:04 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E70412DF04 for <6tisch@ietf.org>; Tue, 8 Mar 2016 23:13:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13492; q=dns/txt; s=iport; t=1457507584; x=1458717184; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=b/POUyQZ/zg2Mf0s3gZatcB9rjWiVqHY0yAGM3IFqMo=; b=V/dQojGVC9SB+pmQUIf/eZiK7pbmDcwrRjM8ByzGSPWr63IAat1Udqzz BhmEGOqPm3wHe8vhZvoyp1rAQh5C5txb8QBt/+QC3kBvSwD7hyaQwzoSP bXmnfiGNWBmqZcIxOxlXiYdgMDEoXZfZO9bqWLi8I3IMCLeTdedwmXurN 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D+AQCHzN9W/5ldJa1SCoJuTFJtqjKQN?= =?us-ascii?q?QENgWkXAQmFJEoCgUI4FAEBAQEBAQFkJ4RBAQEBBAEBAWsLDAQCAQgRBAEBKAc?= =?us-ascii?q?hBgsTAQkIAgQOBYgPAxIOukwNhEkBAQEBAQEBAQEBAQEBAQEBAQEBAQERBIYXg?= =?us-ascii?q?XMIgkeCPYFTCwEBg0iBDwWGHQyFDot4AYt7BoFvjnuHD4dKAR4BAUKDZGqIIYE?= =?us-ascii?q?yAQEB?=
X-IronPort-AV: E=Sophos;i="5.24,310,1454976000"; d="scan'208,217";a="247238452"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Mar 2016 07:13:02 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u297D2XT007939 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 9 Mar 2016 07:13:02 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 9 Mar 2016 01:13:02 -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 01:13:02 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Qin Wang <qinwang6top@yahoo.com>
Thread-Topic: [6tisch] 6P and Sf0 issue: Token to identify transactions in 6P
Thread-Index: AQHReX63XjQKnV8qLUijcPjy30pd9p9Qsz7R
Date: Wed, 9 Mar 2016 07:13:02 +0000
Message-ID: <83F03D1D-FC7D-4502-80D5-9793DDE02DDF@cisco.com>
References: <e5d44e727c8746fab93d6b8b5b3b9401@XCH-RCD-001.cisco.com>, <847953799.6165746.1457471332301.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <847953799.6165746.1457471332301.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_83F03D1DFC7D450280D59793DDE02DDFciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/A2ga9oyCvrLJtr97ZXQEkLMw_ww>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, "Prof. Diego Dujovne" <diego.dujovne@mail.udp.cl>, Tengfei Chang <tengfei.chang@gmail.com>, Tero Kivinen <kivinen@iki.fi>
Subject: Re: [6tisch] 6P and Sf0 issue: Token to identify transactions in 6P
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 07:13:06 -0000

Hello Qin:

Token 1 needs to be the same as token 2 when it is a retry. That's the whole point.

In your second case, say this is a child asking for a cell:

- If this is a time out because the response from the parent was lost, the parent should respond with the same cell as in the lost message.

- But if the child got the response and still needs more bandwidth, then the parent needs to allocate a second cell.

How does the parent know?

The main point of the sequence number is to be able to correlate the retry.

As it goes, it also enables to avoid the serialization of requests but I agree that is a non goal today.

Regards,

Pascal

Le 8 mars 2016 ? 22:10, Qin Wang <qinwang6top@yahoo.com<mailto:qinwang6top@yahoo.com>> a ?crit :

Hi all,

I'm not convinced that token is necessary yet. From the discussion in the last WG meeting, we have agreed that the Token is used in the 6P message exchange between neighbors. Based on the agreement, let's consider the two following scenarios.

(1) nodeA send ADD_Request(token=1) to nodeB, and not receive Response from nodeB before Timeout. Then, nodeA send ADD_Request(token=2) to nodeB, and receive Response(token=2) from nodeB.

(2) nodeA send ADD_Request to nodeB, and not receive Response from nodeB before Timeout. Then nodeA send ADD_Request to nodeB again, and receive Response from nodeB.

The question is if it is possible for nodeA to receive Response(token=1) from nodeB later in (1). Since nodeA will send the second ADD_Request after Timeout, I don't think it could happen. If I'm correct, I think the two sequences function similarly. Thus, I wonder if it is necessary to have the Token

What do you think?

Thanks
Qin



On Tuesday, March 8, 2016 10:10 AM, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:


Oh yes, Tero,

we agree on the bottom line and on your points.

Cheers,

Pascal

> -----Original Message-----
> From: Tero Kivinen [mailto:kivinen@iki.fi<mailto:kivinen@iki.fi>]
> Sent: mardi 8 mars 2016 15:50
> To: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>
> Cc: Tengfei Chang <tengfei.chang@gmail.com<mailto:tengfei.chang@gmail.com>>; 6tisch@ietf.org<mailto:6tisch@ietf.org>; Prof. Diego
> Dujovne <diego.dujovne@mail.udp.cl<mailto:diego.dujovne@mail.udp.cl>>
> Subject: RE: [6tisch] 6P and Sf0 issue: Token to identify transactions in 6P
>
> Pascal Thubert (pthubert) writes:
> > But this is another discussion entirely. It is about the transaction
> > that associates new timeslots to a bundle and why we need a
> > correlator, or transaction ID. I was explaining that if the parent
> > wait for the ack to allocate a slot that was negotiated, and there is
> > no flow after that, then if the ack is lost the child thinks the slot
> > is allocated and the parent does not. The child may start using it
> > wrongly.
>
> Which is why you should not use ACK for anything like that, but instead use
> application level messages for that kind of things.
>
> > The point behind this is that if the transaction does not complete, it
> > must be retried from scratch with the same sequence, or it must time
> > out and roll back.
>
> Receiving or not receiving ACK should not cause transaction to complete or
> not to complete, there must be some kind of application level message to
> indicate that it was successful if that information is needed in the peers.
> --
> kivinen@iki.fi<mailto:kivinen@iki.fi>

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