IETF Logo Mail Archive

[Roll] Eliding mechanism in 6550

Rahul Jadhav <nyrahul@outlook.com> Fri, 27 September 2019 15:59 UTC

Return-Path: <nyrahul@outlook.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57E58120956 for <roll@ietfa.amsl.com>; Fri, 27 Sep 2019 08:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.025
X-Spam-Level:
X-Spam-Status: No, score=-2.025 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.026, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.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 Yhm-j9N8XiqZ for <roll@ietfa.amsl.com>; Fri, 27 Sep 2019 08:59:23 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-oln040092254065.outbound.protection.outlook.com [40.92.254.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3970B120939 for <roll@ietf.org>; Fri, 27 Sep 2019 08:59:23 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=W9xBFkQvOj3qtAf03gmCNBTLNs2YlxWpFj9ZPQWCku9htBDm8YwSRczHB63JTZrX//QxXarUsKrppt4kaPgNx1fveDQn1dl5qmvuQ9ZsRLrkBDUN7XzxTIKbjj4CzpgJ1bV6GhUo6g30vJzxLTKCfWtnEmT0sEoPNfWSg8IHxnMR1uYfLPI+/LrVbeaJV4zLxm5gxaU7v909hSJHN+oyazRylHiQdVpZKaQ4PH4vRB1WYoxUtZ/PewloxELohnNc8vk50Rs5JTR81B2pPO9WkyVYjqbzwAPTrJKpvEGt1o/es0LMW1zWCGsAuCFyuWOFgYquCjR+4p6Up3QI2bsKbQ==
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=KTQ2shLfXnwAsCI3DsEub6XDLlk6DKf+kOxdH1HhrII=; b=mtxWDPtZ2uYeE1T15XAIpeMbtSw46bd/HIRS1nz2ME7i3xdiGqu7NO4tcuTqnJKunDpzgI0fMxpI4o2JNQsx0e2Nzf4rFUQ7f4tGoh1vDAl59iKlgZyiRNmyiAu9MrdNC2EOcN4EPkBgP6fY8CXfw6EPdyDsql+hnjdOvi9XTOYPyAxKgwUhuIOO1I0Ck0VorppzxrTe91cYwIVNR+h8+kY1u2WhXf2AUGl/EH0qWB4K6JFczo9/Q/bGOhnHZ3iBgKlGXI0ZGkcYt/SexVz3TUxPP8iSUWQAtyj8CnHdv15AnzXUqqvEmv061LRowa3pJFy4U2rG5NM68bSPRJpKcQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KTQ2shLfXnwAsCI3DsEub6XDLlk6DKf+kOxdH1HhrII=; b=ZTvBSmHEuSL1Ryvqu4fyPKot2ehWPnovvVSkQ+xCukrz3rvr6Xcrx+kuHftUMKtlCGT9r0NAgcl9eY++asbjnZYXtAIzq+Wp2xL5PNQ4H/wFf1WO6JmdFtQP2OmoooJRE8NpHjWoLR2BXxhhFXnxIcCJudZLxrNuGFkg3zxQdnGkns/B9SSa5AIa75HORzrCnrswFoMhsEvbSSJ5gcKi1MgbNW0hbSkEk0irw8mLtKHa8x91hpAT/LOpjrcVBN2H7XQ+RPOWMmq90yykly5vZzsTO8vU9691gzP+C2FsUCOEt1SltDM/myljntBxBtMx8Me1F80SeZy2kC61B3JnQw==
Received: from PU1APC01FT023.eop-APC01.prod.protection.outlook.com (10.152.252.53) by PU1APC01HT146.eop-APC01.prod.protection.outlook.com (10.152.253.169) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2305.15; Fri, 27 Sep 2019 15:59:20 +0000
Received: from BMXPR01MB2613.INDPRD01.PROD.OUTLOOK.COM (10.152.252.52) by PU1APC01FT023.mail.protection.outlook.com (10.152.253.4) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2305.15 via Frontend Transport; Fri, 27 Sep 2019 15:59:20 +0000
Received: from BMXPR01MB2613.INDPRD01.PROD.OUTLOOK.COM ([fe80::5d02:1b65:98bc:e61b]) by BMXPR01MB2613.INDPRD01.PROD.OUTLOOK.COM ([fe80::5d02:1b65:98bc:e61b%5]) with mapi id 15.20.2305.017; Fri, 27 Sep 2019 15:59:20 +0000
From: Rahul Jadhav <nyrahul@outlook.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: Eliding mechanism in 6550
Thread-Index: AQHVdUhliZ040nQflUyScFbwadE6vQ==
Date: Fri, 27 Sep 2019 15:59:20 +0000
Message-ID: <BM1PR01MB2612A9D3C37CD5D009626CCFA9810@BM1PR01MB2612.INDPRD01.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:2E761426F1390E1B9526A270AD0F9F5B10625297A139A4254B0D4DB3D37EB3FD; UpperCasedChecksum:987E19E7079D8A466BFC04F009EE26603DB445A786406D5FDCC43B4EBC671CAD; SizeAsReceived:6578; Count:41
x-tmn: [jPBjvYWejOcOS9oMIhQZTfqpcFYUonrM]
x-ms-publictraffictype: Email
x-incomingheadercount: 41
x-eopattributedmessage: 0
x-ms-traffictypediagnostic: PU1APC01HT146:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: LFFQCgMH8w5+BLinjYR2Hgm0zyKNUzCdm/bl7XSsl2swZtuMu0+5nVB40nrP0iTZbqMZsKwhYa9YpmqxJM5Og4JAdBrOXbThxCBjL56AWtLmy8dWzwEWr9UGfE3ck5KzQdpNTP/1MCw5zEwO3fhr073VjaA0/qnCC1KRRnXaDjCZKJB20q+UVXWPyWXz0fsr
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BM1PR01MB2612A9D3C37CD5D009626CCFA9810BM1PR01MB2612INDP_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 854e89d6-7fb3-4e4b-1122-08d74363a8b2
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Sep 2019 15:59:20.6410 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT146
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/QPCmwYJCrfiJNzua2sDYI4JlkO0>
Subject: [Roll] Eliding mechanism in 6550
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2019 15:59:25 -0000

Hello all,

During the interim, we discussed about the eliding mechanism in 6550.
Basically, 6550, allows DIO Configuration Option to be elided for multicast DIO. However, 6550 does not provide any guidelines on how to do it.  We found that under transient network conditions, it was possible that a node may continue to use the stale configuration option without realizing that an updated option is in circulation.
During the interim Pascal/Michael suggested the use of counter to track the freshness of the Config Option. This could further extend to track MOPex and CAP options freshness.

The suggestion was to use the reserved bits in the base DIO message for such a counter.

I was wondering if the DODAGID in the DIO could also be elided under the same guise? Basically the point is to elide all the "static" information which rarely changes.
Clearly this has issues in multi-DODAG networks but it is possible to handle such issues. Considering that this directly results in 16 bytes savings per DIO multicast message, do you think it is worth the effort or if there are other issues?

Regards,
Rahul

v2.23.0 | Report a Bug | By Email