Re: [6tisch] downstream traffic adaptation

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 07 October 2019 13:03 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 F19B9120020; Mon, 7 Oct 2019 06:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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 header.b=lriQegjE; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ii//HRL2
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 NqKSqDo5uNzQ; Mon, 7 Oct 2019 06:03:21 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3B9912007C; Mon, 7 Oct 2019 06:03:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29960; q=dns/txt; s=iport; t=1570453401; x=1571663001; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=gkxsRTHoSChBatErSLyA/1/0juKfOk8cZtWzvDGQO0s=; b=lriQegjEfKUTsasP0c1wSaDFN374vto+4LbOt2o1ZH7pcizeZ6SYkYZW QjyrwpjOMHIPkSzZ6dqhEBKe24r4BCdRvS5RPshkygoIl4ODqES/O6YEK 5sq/zmbR0Yz0gUkzAcCzNWOTkAjS2VI55/6jyVowlCno3AgdpLXDhVjYU c=;
IronPort-PHdr: =?us-ascii?q?9a23=3AEHEP6BL6IT2lBEMagdmcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeBvKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXFXnLOPgYjYmNM9DT1RiuXq8NBsdFQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AmAAC2Nptd/40NJK1mGwEBAQEDAQE?= =?us-ascii?q?BDAMBAQGBVAUBAQELAYEbL1ADbVYgBAsqhCODRwOKSYJcl3yBLhSBEANUCQE?= =?us-ascii?q?BAQwBARsSAgEBhEACF4JEIzUIDgIDCQEBBAEBAQIBBQRthS0MhUsBAQEEEhE?= =?us-ascii?q?KEwEBNwEPAgEGAhEEAQEhBwMCAgIwFAkIAgQBDQUIGoMBgR1NAx0BApIWkGE?= =?us-ascii?q?CgTiIYXWBMoJ9AQEFhQoYghcJgTQBhRWGeBiBQD+BEUaCTD6EEQESAQcaNAi?= =?us-ascii?q?CTzKCJo9thTWYHgqCIpUzgjqHToQsiwuOLJkyAgQCBAUCDgEBBYFTATdncXA?= =?us-ascii?q?VgycJRxAUgU8MF4NQhRSFP3SBKY1xDRcHgicBAQ?=
X-IronPort-AV: E=Sophos;i="5.67,268,1566864000"; d="scan'208,217";a="641088982"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Oct 2019 13:03:20 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x97D3KMY026124 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 7 Oct 2019 13:03:20 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 7 Oct 2019 08:03:20 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 7 Oct 2019 08:03:19 -0500
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 7 Oct 2019 08:03:19 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YPAhDcoNOgbkhtWw+FQ7Ch/5F31W2l5RdLb/Iy1Xj4evwiuN+AQcq8xr1BujM6CKrC8OO8OvfVbhDTZExJju5jC98CdHMysyZIkMPWZW1lK0281MinO86Vz3xy5Tq42wvHJQLVQd6qT4Pb9N28RyfwSmkbOiqySbPR3+FMSyCVbXazMH5w46cPXdbxfQEJGd6IYZP3rEtNzBqfJfT+9YenkraaVvQDC+Mjw9AzKm4kRYuOX+VCzdzQx9xHcnT7BvjuulI9gEjgD07Wpx6aJp0iLDWnLFz8Spd+KbcFMOlPFkY/R75TrHz7V/zjCzUdhC60YrE2ROLRa1D2Hn+GH1mA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=gkxsRTHoSChBatErSLyA/1/0juKfOk8cZtWzvDGQO0s=; b=WsBuxtXh5SDzmTBvDt+PfUtOD0hu0Ab0Z1ULpIjyAIpbK5ZiE+cVHLaVzbI+hTncve/Zh+8Nrg0OnOtXO8s1kA0HAl/Bve1fH3rQR5NpdFSpxHpzR7L7r2b7zWucdNtRLWCB7lVY/x3+Cy85OLDgvmR05aBbP5ZK2YgENMFBe/wbzB4eWRw9qRhfrVGQvu7QA2EFANuSafeJSPmC7eGWOK73+LkrgEuT0SmYMByEzAEXEqfXPoKaJSRTUtYjPCpJofVYqJ+K6o0vIKV3rm4WZhGyLf4KOUPupreICKM2kaJIjfK71hl090of9E6hik8uvcDWfdG6SoapB8S4yxxhXg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=gkxsRTHoSChBatErSLyA/1/0juKfOk8cZtWzvDGQO0s=; b=ii//HRL20ZNdG2dL2hDKDRnjCvHwfr+zY/YJ13SwNUTYF8leFv9XcrQe7aMZQ64K0act1RNMJJ7AHXFIVWEjRCCi+KiOs9HNVUA5N9eQPNfhxVWNOsAsaXkdrx1yu4hoxS0wtzMZzbQipP1+zhMBcevgBvg4HIQw/nCfo1GFy/Q=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3888.namprd11.prod.outlook.com (10.255.181.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.15; Mon, 7 Oct 2019 13:03:18 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::652e:fba0:4959:7ce8]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::652e:fba0:4959:7ce8%7]) with mapi id 15.20.2327.023; Mon, 7 Oct 2019 13:03:18 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Tengfei Chang <tengfei.chang@gmail.com>, "draft-ietf-6tisch-msf@ietf.org" <draft-ietf-6tisch-msf@ietf.org>
CC: 6tisch <6tisch@ietf.org>
Thread-Topic: [6tisch] downstream traffic adaptation
Thread-Index: AQHVWa4+wcUOpreJQEuRUNjjka4TOacIruvAgEIc0YCABJygMA==
Date: Mon, 7 Oct 2019 13:03:02 +0000
Deferred-Delivery: Mon, 7 Oct 2019 12:53:54 +0000
Message-ID: <MN2PR11MB35651B251F960AC970015C99D89B0@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <CAAdgstTrkiBHykPqVv6EnGAxKyVHzc4EHFSH4Z0xGF2nOqvJHg@mail.gmail.com> <MN2PR11MB35652FA7DEE598BDA8579AFFD8A40@MN2PR11MB3565.namprd11.prod.outlook.com> <CAAdgstT-Oq-_aYq+Nq+yeyZOkbGuDDkVbFOnFbG_PBiSuKOuqw@mail.gmail.com>
In-Reply-To: <CAAdgstT-Oq-_aYq+Nq+yeyZOkbGuDDkVbFOnFbG_PBiSuKOuqw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [2001:420:c0c8:1008::17]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 28e4c336-52af-46b4-bddb-08d74b26b937
x-ms-traffictypediagnostic: MN2PR11MB3888:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR11MB3888DF3EB3AC52BDA7C895B0D89B0@MN2PR11MB3888.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01834E39B7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(136003)(366004)(39860400002)(376002)(346002)(189003)(199004)(53754006)(229853002)(4326008)(6246003)(476003)(5024004)(11346002)(81166006)(46003)(81156014)(256004)(66946007)(446003)(66476007)(186003)(8936002)(6506007)(790700001)(66556008)(55016002)(236005)(9686003)(54896002)(6436002)(102836004)(66446008)(64756008)(8676002)(478600001)(14454004)(6306002)(71190400001)(6116002)(606006)(99286004)(2906002)(110136005)(25786009)(33656002)(7696005)(7736002)(486006)(52536014)(76176011)(76116006)(6666004)(5660300002)(2501003)(53546011)(316002)(74316002)(71200400001)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3888; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Is09kEOeXK1w2qI4x0av5r8tjKVsD/GqvA/C/fZDYNytXRNhRxkAL1jsWswybd6KSmJCkDQsqSxjJtWg14m1qGE1vpW57tdncc8sFFuhbMgMD9Phemzezhi8ElZ+p0hqOpR2490IxmIPki7VorknSme0+lkQtuZJc3GTk4F5gnKQP9bxcF5RmcJI4g310FdOBAA0McrGaltxHzoful1eQd+/x8ZMRItSMztLxYuxvn9x7ajuj7fypVtk28W3JI7HdaIE/8iCylP2ZAZkOboIB/oOheN+jL+Er81IgDU3E9PbBcMDJRQCKAlDLTeNGn/Xm9HuDT4as9TiyQnARxPSnwZQHJpcXJY68Rp8DFvQO+emW/pRjyr8hHBA6yYiE6x4w2WLvFpbUT/idNYNO4Z9aEkNpMkVw0loAXeOYee3kOJmcKLzSIxA8SePIemhQY7KwZSfCVyP24Bn8fnB9xMx9g==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB35651B251F960AC970015C99D89B0MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 28e4c336-52af-46b4-bddb-08d74b26b937
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Oct 2019 13:03:18.2504 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vi4d1JgOggspSiN3v80hzQaRGbM89Ivq7dYAIMB3Hv7HjwpwBLBYxAEnZ1aPQ3ntqRLMy+4gw/Tevjo11WV0Nw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3888
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.24, xch-rcd-014.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/Fk7KNNfaYLJzkc89a9fN0eLYvYc>
Subject: Re: [6tisch] downstream traffic adaptation
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 07 Oct 2019 13:03:24 -0000

Hello Tengfei and all

I see that the 2 issues of IETF 105

  *   Rules for CellList
  *   Downward traffic adaptation
Were discussed and there was no objection. Do you fell ready for WGLC now?

All the best

Pascal

From: 6tisch <6tisch-bounces@ietf.org> On Behalf Of Tengfei Chang
Sent: vendredi 4 octobre 2019 07:25
To: Pascal Thubert (pthubert) <pthubert@cisco.com>
Cc: 6tisch <6tisch@ietf.org>
Subject: Re: [6tisch] downstream traffic adaptation

Hi Pascal,

Yes, it is implemented and tested, the result is shown in the (long) email "[6tisch] validating the downstream traffic adaptation in draft-ietf-6tisch-msf-06".
I attached the figure here as well.

Though that email is long, all the information is the explaination of the result figure, trying to make it clear.
You can check the figure directly, I think is understandable for people following the msf well.

Tengfei

On Fri, Aug 23, 2019 at 4:23 PM Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Looks good Tengfei. Did you already implement and test?

Pascal

From: 6tisch <6tisch-bounces@ietf.org<mailto:6tisch-bounces@ietf.org>> On Behalf Of Tengfei Chang
Sent: vendredi 23 août 2019 14:28
To: 6tisch <6tisch@ietf.org<mailto:6tisch@ietf.org>>
Subject: [6tisch] downstream traffic adaptation

Hi All,

As discussed in IETF 105, we are going to support adapting downstream traffic.
And now this feature is added in draft-ietf-6tisch-msf-06 published one weeks ago.

Some main changes related to this feature are:

  1.  After joined the network and got Rank, the node will only add one Tx Cell to its parent (NOT add Rx Cell)
  2.  When adapting downstream traffic, the mote will check the cell usage on the Rx Cells.
  3.  At each Rx cell to parent, the NUMCELLELAPSE increments
  4.  If there is any frames received on the Rx cell, the NUMCELLUSED increments
  5.  If NUMCELLELAPSE reaches MAX_NUMCELLS, check the percentage of cell usage, if higher than the high threshold, add one Rx cell to parent, if lower than the low threshold, remove one Rx cell to parent.
  6.  The AutoRx cell is used for downstream as well and will never be removed.
Those changes are integrated into version 06 content.. You can read it to check exactly how we did the changes.
Please let me know if you have comments on them.. Thanks!

Tengfei

--
Chang Tengfei,
Postdoctoral Research Engineer, Inria


--
——————————————————————————————————————

Dr. Tengfei, Chang
Postdoctoral Research Engineer, Inria

www.tcahng.org<http://www.tcahng.org>
——————————————————————————————————————