IETF Logo Mail Archive

Re: [Roll] Following up on seq Counter to protect the config option and others

Rahul Jadhav <nyrahul@outlook.com> Tue, 15 October 2019 03:47 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 C633112006D for <roll@ietfa.amsl.com>; Mon, 14 Oct 2019 20:47:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 27KHfaemeN-N for <roll@ietfa.amsl.com>; Mon, 14 Oct 2019 20:47:21 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255018.outbound.protection.outlook.com [40.92.255.18]) (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 79F26120013 for <roll@ietf.org>; Mon, 14 Oct 2019 20:47:21 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DUrkZxKOUadLdhigAl4VufoHU7zrL6bTZ58r/uKMGvME9KdNxMF82aXMxG6EBMWy30CUS9i+9anH6QpE/QHjDeJ0D0KWnYyPXpkXAN85oOwXHjkLUjijqIlzh4HqlSFZQKAZZBrl7lEVAcxiwRuxfhCIFSt2ECIYGoJ/HxS9vxnOL0BeqyrAj8epLpv6KFQC8eX10IiWz7yrVledNzGI0eu1pWLI6+yTTRpSeFkmMG70OFFy5StJ2apVRq3HKuB9nzWeVx1qTz7wlxAw4RmwqfOOtNQ90e+ZUAOKuFtaZkIKkyacjbaLX/5SaxC/YMKdfQS3gLFYCC7e6akowB7tgQ==
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=eO1+qKsreXf70jCq4iU1mwSAXA5HIr29ncIgLVLSxPU=; b=SAwfI2sSOBpV24u2pXuBInCsEK8EiUjbKmtNrueU8FjhoAPw8aa3hHeFnptHTJclPIWqrWg/vRRpmC3FUFIcC0oDiidA4J+MveZxQy7Ur+c8bHJ4fAPAUHeIrUxKovV0DNDbDxP9yDizF5+hbOBM5qG1gF+GvZ4GyFWmnmfsHQZddahCSTqscRJfntmKAZayKol5FsE4UGGhrtjcGcKGxtR4hso/BahrT26JRTSE7GbPhjmJk702k0TyMp8iHu4c1pa5p9sdjv0oAHVyj/2Rc0OiIVmMLC+RmsYDN47uRe4zsSpKSjdClCxwzlDD4CyAMVUwI58+eiWs4OOCrdRl5Q==
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=eO1+qKsreXf70jCq4iU1mwSAXA5HIr29ncIgLVLSxPU=; b=Qzadro5/vxnBaCr6t9FQmnlsuIIfvmNTWuQbgZ6yw+sw9j07HKzFBASOSz/CsW5qOcUCMzjKxMBvThaVV9EoG8Q2TDXLI9yyaqbCRP0CnfbJitlVP8N8/jbsVe1avU2QCE6fQHjv42gRpwykzdyyawKdtu/3BpRlOQ3DzXQrvn4XBfv0FNtYaG/7z4VH+3/1F+4VfE7G5xvUCg/c5D7MIxhzlCeD8/Xf4P6BkK0jmApiebAn97M5t08G8iMP3mHRfyBcQjaqxsKGO56wY9o7pZq8owkSAZnkiC4CBbxO1ZrRUHcnKenwdPDMsQvhqW0vWxz3HJUXzilsauXD6uhJeA==
Received: from SG2APC01FT009.eop-APC01.prod.protection.outlook.com (10.152.250.60) by SG2APC01HT120.eop-APC01.prod.protection.outlook.com (10.152.251.109) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.16; Tue, 15 Oct 2019 03:47:19 +0000
Received: from BM1PR01MB2612.INDPRD01.PROD.OUTLOOK.COM (10.152.250.54) by SG2APC01FT009.mail.protection.outlook.com (10.152.250.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.16 via Frontend Transport; Tue, 15 Oct 2019 03:47:19 +0000
Received: from BM1PR01MB2612.INDPRD01.PROD.OUTLOOK.COM ([fe80::8a1:677d:4fb6:b932]) by BM1PR01MB2612.INDPRD01.PROD.OUTLOOK.COM ([fe80::8a1:677d:4fb6:b932%6]) with mapi id 15.20.2347.021; Tue, 15 Oct 2019 03:47:19 +0000
From: Rahul Jadhav <nyrahul@outlook.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: Following up on seq Counter to protect the config option and others
Thread-Index: AdWCrxPZcTH2VHjHRxWHUI79NH4rSgAWqh1a
Date: Tue, 15 Oct 2019 03:47:18 +0000
Message-ID: <BM1PR01MB261263B41F4E94D9329CB698A9930@BM1PR01MB2612.INDPRD01.PROD.OUTLOOK.COM>
References: <MN2PR11MB3565FFC5F9C48EC4E7CAD65DD8900@MN2PR11MB3565.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB3565FFC5F9C48EC4E7CAD65DD8900@MN2PR11MB3565.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:A3170B05009E5528A8B98D64B07BF5592B165E5564267B39A57C67C731250D8B; UpperCasedChecksum:87BC305332A1505574B82AB3C7D58C218E89314B8F7DBEF4C468D89C0E7BC42D; SizeAsReceived:6882; Count:43
x-tmn: [s6DFIuhDBbSkQg9uhRI54B2Eftv/3qLG]
x-ms-publictraffictype: Email
x-incomingheadercount: 43
x-eopattributedmessage: 0
x-ms-traffictypediagnostic: SG2APC01HT120:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: fB8NJFX58SJac5mvsk4UfpswphJKfj3Vei6LHuI8ttBUh8pblOYhVHQQc3v0xUCpwdzdwlr5jmxmcj/Eh7fi/fJKcnidQJhgHKD1AtUTILQXLj95KLbQ0uJBinydgWAHeQx72DPLmuKJszG8stnrr1cVdjpJyH4ZC4EOu3adUV23bu33adMtgGI7zK65psJD
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BM1PR01MB261263B41F4E94D9329CB698A9930BM1PR01MB2612INDP_"
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: 59296030-a6c6-4550-5906-08d7512260dd
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Oct 2019 03:47:18.8673 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT120
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/5Xr2T5YzY-d-mqnsdzw8TFNrST0>
Subject: Re: [Roll] Following up on seq Counter to protect the config option and others
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: Tue, 15 Oct 2019 03:47:24 -0000

Note that this also means that the capabilities have to be split between the parent capabilities (not protected) and the network-wide that are (item 5 above).

The alternate is that the RCSS covers everything a parent advertises in which case it is not set by the root but by individual parents.


[RJ] I think RCSS can be handled by individual parents (similar to DTSN in storing MOP). The only problem would be that additional memory i.e., one byte per parent would be required in this case. May not be a big problem since the parent set is limited in size.



Or do we need 2 counters?


[RJ] IMO, This won't be a good option, memory-wise or handling-wise.

v2.23.0 | Report a Bug | By Email