IETF Logo Mail Archive

Re: [6tisch] 6tisch-pre-reqs-00 <- can it be implemented??

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 09 August 2017 09:59 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 8321B1320CF for <6tisch@ietfa.amsl.com>; Wed, 9 Aug 2017 02:59:10 -0700 (PDT)
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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LGq5fpM5rUT2 for <6tisch@ietfa.amsl.com>; Wed, 9 Aug 2017 02:59:07 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 459D8131CD7 for <6tisch@ietf.org>; Wed, 9 Aug 2017 02:59:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1876; q=dns/txt; s=iport; t=1502272747; x=1503482347; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=o04IVlvmt810GhdVfUchWaDZQwVjXDjQLTGZUhGgafk=; b=M++YN+jdxox9RUEyf5K+VpBK4hbfGtQexhL8/7vngucPQXe2/xlk0cr5 fsg8rHHbYh/Kd4dqDXZLJaUwDOofwmOaPq1S+EsQEeC7qaoaqDoOqdars 3piOcyDpup9zQwJWbHjxKSu0VNtm3CijNDtr7CgFNQey5LIDqVEl+lrH4 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DGAAAx3IpZ/4oNJK1cGQEBAQEBAQEBAQEBBwEBAQEBg1pkgRQHjgiQBYFulhWCEiELgWCCJkZPAoR6PxgBAgEBAQEBAQFrKIUYAQEBAQMBAWwXBAIBCBEEAQEoBycLFAkIAgQBEgiKJxCwT4tSAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWDKIICgUyFCopnBZFDjlQClCuSWpYKAR84gQp3FUmHGnaIeIEPAQEB
X-IronPort-AV: E=Sophos;i="5.41,346,1498521600"; d="scan'208";a="270055278"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 09 Aug 2017 09:59:06 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v799x6U6008799 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 9 Aug 2017 09:59:06 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 9 Aug 2017 04:59:05 -0500
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.1210.000; Wed, 9 Aug 2017 04:59:05 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "6tisch@ietf.org" <6tisch@ietf.org>
Thread-Topic: [6tisch] 6tisch-pre-reqs-00 <- can it be implemented??
Thread-Index: AQHTEG2OHnGvfbDJJU+dbix4T24EG6J7yTWg
Date: Wed, 09 Aug 2017 09:59:04 +0000
Deferred-Delivery: Wed, 9 Aug 2017 09:59:00 +0000
Message-ID: <c81398a91eef44ecbbe8763a4a105978@XCH-RCD-001.cisco.com>
References: <32294.1502214069@obiwan.sandelman.ca>
In-Reply-To: <32294.1502214069@obiwan.sandelman.ca>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.76.86]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/La8GFM2MInqGFSH8waKaJaW2Qp4>
Subject: Re: [6tisch] 6tisch-pre-reqs-00 <- can it be implemented??
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.22
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 Aug 2017 09:59:10 -0000

Unsure what your question is, Michael.

The node that is scheduled to overhear can see the cell as shared, to it will not ack.
There is the problem of the dMAC. In 6TiSCH tracks we set it to broadcast. But this is not really a broadcast since only the intended nodes are scheduled to wake up and listen to that cell. So the GMPLS properties of the cell turn it in a multicast group, the mcast group of nodes selected by routing as being progress towards the destination from the point of view of the sender.

Note that ISA100.11a has a concept of Duocast, whereby the MAC layer of the sender expects 2 acks and is happy if one comes. The first ack is aligned to the end of the frame whereas the second if aligned to the end of the time slot.

There is no 'hardware' per se, since unless I miss something, all this is upper MAC, classically software. So anyone shuld be able to try it on its preferred gear. We used OpenMotes.

Take care,

Pascal

-----Original Message-----
From: 6tisch [mailto:6tisch-bounces@ietf.org] On Behalf Of Michael Richardson
Sent: mardi 8 août 2017 19:41
To: 6tisch@ietf.org
Subject: [6tisch] 6tisch-pre-reqs-00 <- can it be implemented??

<#part sign=pgpmime>

I was reading draft-papadopoulos-6tisch-pre-reqs-00, and I came across:

   Considering that each frame may be transmitted
   twice in unicast to each parent, then depending the transmission,
   either DP will acknowledge the frame or AP will.

I think the possibilities of this are amazing, but I wonder if this will realistically work with many pieces of hardware.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -= IPv6 IoT consulting =-



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

v2.23.0 | Report a Bug | By Email