[Roll] Review of draft-ietf-roll-enrollment-priority-05

"Huimin She (hushe)" <hushe@cisco.com> Thu, 19 August 2021 09:48 UTC

Return-Path: <hushe@cisco.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 F18563A0958; Thu, 19 Aug 2021 02:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.588
X-Spam-Level:
X-Spam-Status: No, score=-9.588 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_NONE=0.001, T_MIME_MALF=0.01, URIBL_BLOCKED=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=iqsKILwo; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=OVPAr9n5
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 r2FrqzxE1hYZ; Thu, 19 Aug 2021 02:48:45 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 997133A095D; Thu, 19 Aug 2021 02:47:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=69413; q=dns/txt; s=iport; t=1629366469; x=1630576069; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ZCU5f9lNHlRKQ3ZtA3xJAPkE/frbsANHIYYsINpwsvU=; b=iqsKILwopkunu7NS55ncnz8wUlTA3OiZw5dAq/uliEj1pJEKeGuKT8f2 igof5nI/zZsK9zl5ACzYdGtkL5R1fsfLJGtd1pn6+oySyI4AjdX+4wtha 4XbNbwBQwlZ/NkoAYMeho7vB5yV7CK/0X/jwjSnhFwXdbHU0pg9uNaQHP Q=;
X-IPAS-Result: =?us-ascii?q?A0B/AwDJJx5hl4MNJK1aHgEBCxIMQIJ8MCMGKH5aNzGID?= =?us-ascii?q?wOFOYhqA49zikqBQoERA1QLAQEBDQEBQQQBAYRjAoIuAiU4EwECBAEBAQEDA?= =?us-ascii?q?gMBAQEBBQEBBQEBAQIBBgQUAQEBAQEBAQGBCIVoAQyGQgEBAQECARIIASUBA?= =?us-ascii?q?TcBBAcEAgEZAwEBARYLAQ0yHQgCBA4FCBMHgkoEAQGBflcDDiEBnQ8BgToCi?= =?us-ascii?q?h94gTOBAYIHAQEGBASFLgMVgjQJgTqCfoJyU0iCbIN8JxyBSUSBFUNUgQ2FP?= =?us-ascii?q?A0EGAUbBRkYB4MOgi6EEBEBWgY+HA4NIhQUBQ4LOx4dLRoGAwEaEAwUCgIfC?= =?us-ascii?q?g+ROQSMG59fCoRanT0SpnWFPZBXoBcEBAuEdAIEAgQFAg4BAQaBdyIPHoEuc?= =?us-ascii?q?BWDJFAZD44gGYENAQIFCAeCNYpecwIBNQIGCwEBAwmJI14BAQ?=
IronPort-PHdr: A9a23:sCV5QRPOKXa8HrQvalsl6ncfWUAX0o4cdiYU54YpzbVUfffr85fjO RnZ4vNgxB/MUJ7A4v1Jw+zRr+j7WGMG7JrA1RJKcJFFWxIfz8lDmQsmDZ2EBFH1avnwYH9yE MFLTlQw+Xa9PABcE9r/YFuHpHq04HYSFxzzOBAzKP7yH9vZjt+80Ka5/JiACzg=
IronPort-HdrOrdr: A9a23:qZGNzqu0/G/tH4dl3aqZWO6X7skC1IMji2hC6mlwRA09TyXGra GTdaUguyMc1gx/ZJh5o6H+BEGBKUmskqKdkrNhQ4tKPTOW+VdASbsD0WKM+UyaJ8STzJ856U 4kSdkDNDSSNyk7sS+Z2njDLz9I+rDum8rE6Za8vhVQpENRGtxdBmxCe2Cm+zhNNXF77O0CZe OhD6R81l6dUEVSSv7+KmgOXuDFqdGOvonhewQ6Cxku7xTLpS+06ZbheiLonSs2Yndq+/MP4G LFmwv26uGIqPeg0CLR0GfV8tB/hMbh8N1eH8aB4/JlaAkEyzzYIbiJaYfy+wzdk9vfrmrCV+ O8+ivICv4Dr085uFvF+ScFlTOQiwrGoEWSuGNwyUGT0fARAghKUfaoQeliA0fkA41KhqAg7E sD5RPri7NHSRzHhyjz/N7OSlVjkVe1u2MrlaoJg2VYSpZ2Us4dkWUzxjIfLH47JlOx1GnnKp gYMOjMoPJNNV+KZXHQuWdihNSqQ3QoBx+DBkwPoNac3TRalG1wixJw/r1Rol4QsJYmD5VU7e XNNapl0LlIU88NdKp4QOMMW9G+BGDBSQ/FdGiSPVPkHqcaPG+lke+63JwloOWxPJAYxpo7n5 rMFFteqG4pYkrrTdaD2ZVamyq9CFlVnQ6dg/22wqIJ9IEUaICbRBFreWpe5fdI+c9vcPEzc8 zDTK5rPw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.84,334,1620691200"; d="scan'208,217";a="766514194"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Aug 2021 09:47:46 +0000
Received: from mail.cisco.com (xbe-aln-003.cisco.com [173.36.7.18]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 17J9ljBg030907 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Thu, 19 Aug 2021 09:47:46 GMT
Received: from xfe-rcd-002.cisco.com (173.37.227.250) by xbe-aln-003.cisco.com (173.36.7.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Thu, 19 Aug 2021 04:47:45 -0500
Received: from xfe-rcd-002.cisco.com (173.37.227.250) by xfe-rcd-002.cisco.com (173.37.227.250) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Thu, 19 Aug 2021 04:47:45 -0500
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (72.163.14.9) by xfe-rcd-002.cisco.com (173.37.227.250) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15 via Frontend Transport; Thu, 19 Aug 2021 04:47:45 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=i8Eb4eXiVhEpq5+9twUCa5Q0XdBEl82Hw3zjMrcPLuO1RnwT1IemgZng69yHcxawLnjPTjailPevOc9K3B9JLxi1Z7olzb34fNF6Db1q2Bx6eGwCiuMlz5CkR/V/zS6OP86hxiNLFtOHNFpHqdfI8rJTioi/TW+h2+dyOCJhl//TsCcGKXHOKEkxEU/Z/rX30rD6gZwRcZ/YYHb5j8K8PalIY0af77yj9Oz/x7sI9LmCXezGeWn7iGGeZIBWA10xaWR/j17xOmrjvWV8K2ihN9UTtJBq/tya+DX66Gf0UmZ1E8jlCH6mqP2M4Cj75IbBXso+SPfv6HcSDdxTlatM9w==
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=b6+ORGwqzFZcnJP19Ljbja0K6ZmASTbSSsMeXuzmL4Y=; b=cxVFeiSjL5iEpu3Ui4qXO4gn6wuaTkC5TCFkcB01l/hghJJBzDnQGXplBg7kh/5E/25dhoG/aef4kixwVYq2eOG5367GVpRKcS1UDflxkgWsyjcM5f9zRQQIA29KkyMbPKmC6EWXG0amt+iULylARcpWxY2Jtd/RD7UWA0Rratg0QJy9/MBGR+K92Tku/d1YN1yc7Lylr4YmhdFZ8CgrO+2HbqPA2y0s8KDzInuTCKH09CyPHd/xTLfanCOQuBfW4i0Xj8/wZDsm3O0D9O7Z4KS8iimqbtLtTJTsEkFhUagB1NnoptZPBRy9MprgDpHlBCVLc9PVDHKyUh0IqTv5eg==
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=b6+ORGwqzFZcnJP19Ljbja0K6ZmASTbSSsMeXuzmL4Y=; b=OVPAr9n5OdNHY1NBkBAoeT3FAibQJyIIYrD7MI1c2Mc6p4nvUNAQPrQx9DqKpEGnjuj2clSE+qjSUzDGGCUp+N8SUOqZaWHRBUA9ppGw0/1btuy6QLcTVqXbpdhSQV90B+yh9mN/6h4uhA/SBa8fHDJtm0fGT2KFh+aUepaDJME=
Received: from DM6PR11MB3803.namprd11.prod.outlook.com (2603:10b6:5:141::30) by DM6PR11MB4363.namprd11.prod.outlook.com (2603:10b6:5:14f::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.19; Thu, 19 Aug 2021 09:47:43 +0000
Received: from DM6PR11MB3803.namprd11.prod.outlook.com ([fe80::68d9:b44b:b6c1:21af]) by DM6PR11MB3803.namprd11.prod.outlook.com ([fe80::68d9:b44b:b6c1:21af%6]) with mapi id 15.20.4415.024; Thu, 19 Aug 2021 09:47:43 +0000
From: "Huimin She (hushe)" <hushe@cisco.com>
To: "roll@ietf.org" <roll@ietf.org>
CC: "roll-chairs@ietf.org" <roll-chairs@ietf.org>
Thread-Topic: [Roll] Review of draft-ietf-roll-enrollment-priority-05
Thread-Index: AQHXlN9BE7+Pe0GmLEC3OwAqijuyxg==
Date: Thu, 19 Aug 2021 09:47:43 +0000
Message-ID: <DM6PR11MB3803DC294871CE93A6FCA8F6A3C09@DM6PR11MB3803.namprd11.prod.outlook.com>
References: <mailman.6244.1628761663.6855.roll@ietf.org>
In-Reply-To: <mailman.6244.1628761663.6855.roll@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=cisco.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e37d7720-2b74-42f7-4252-08d962f66472
x-ms-traffictypediagnostic: DM6PR11MB4363:
x-microsoft-antispam-prvs: <DM6PR11MB43634C7C8209C1D4C59EF44FA3C09@DM6PR11MB4363.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +btgtkanUuHkqOO0huRz0wqSvGVM+PZOe64iTPb3tsOqymOgsoNtK8d+EsY7SRF6c0FDO3htMuvS1CbfnMBtf49TdjN3LdjS9gjykdMHeay/ynr2awXZNiY2JdTw34mnSQnv8uxhQ/44QCdlE2GdvIr9ADV8lusizT1oUzsV9Ib/ynLLSrxy3BsZZsqpXp3WiWp4hE5Fy5+9TonFX51fYimF3W1dBdA+LBcqHdFXoESDedwKAuk91zB96WQNPnMmaGfz2ejL9D33WTtllDq4xv/jXgr5/VDy7SnkeTEFTGqLFCFMrF4doCH3IFPYgUpjgM8CNTF7dRUldND5XNLVE5HdUL6byHMQZiEuzyDAOWvve0teDXPhDvH/oK3oRvGa5wb/ZJIdSPeeffs+0HPZHIpzZV8RIi1mPzOKOImu5Z97pAbD/uKM4J6xSnWGHwKpmEfr/iJgRD3ncBwboa8eoG38RcPY1TJ3iZf8InaX8ibM7V+qIOJcuYX0Hxv+UZtm79E/Ahi8klV8vr/N/s7YEeRRlekGu0QvklC7Y5uSqWTi+kodT7x7s2R3sX3b20SxjyLLfa177rUsfYMJqbpZARWczcUosAtwr/XcqEovkXVbLd0Ev+9jIagweCyv5Dpl0M8kGETq/TXhOSKzy1RFsyrrW/bn2rzXTG7WlT9aRIBHSzUHcmbA5d/XEVVFLEtolVGDuyAAMOtTOELEsSoEjA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR11MB3803.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(136003)(396003)(376002)(346002)(366004)(39860400002)(76116006)(450100002)(38100700002)(52536014)(45080400002)(91956017)(55016002)(71200400001)(7696005)(478600001)(53546011)(8676002)(66556008)(66946007)(66476007)(66446008)(64756008)(30864003)(6506007)(9686003)(5660300002)(86362001)(316002)(33656002)(186003)(83380400001)(122000001)(4326008)(6916009)(8936002)(2906002)(38070700005); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?Windows-1252?Q?2SNsj+gxceEM/dvEirvTwGCawVtwjV+ygZDQ4LlVa46f28y14sfJ+cHh?= =?Windows-1252?Q?tRhW10j2YU/RJW0RqtSC2i1xf93JoPQ9YDLCG7GSjfRwajnYxiTF/+vd?= =?Windows-1252?Q?Gg0l5VRvdbv25RL8dc/W0PjaYD5nVp5qG5cvnrtlXD7UhWvUwfK3GZe1?= =?Windows-1252?Q?umBH9k/xG+Vb4Q3sDD8/W57ecapngZ+YSYmhp30aFoKHnhwXCc4f4PFZ?= =?Windows-1252?Q?wdq75+PJ6CGVceqTLfq+rDngTDe8UgMSmJoe+y1C2YID6R4LwaeE4zlt?= =?Windows-1252?Q?VcHbTHd/koo9qJkFpeDRrtBmj1bxTv80mL0VvZLgyOS3DsCNmqUhV6BL?= =?Windows-1252?Q?Ar8f5k5Sxdg9/2C0Cz9QzSseD85AytS2MyjizgaXehT7T+VFX/is1Uw5?= =?Windows-1252?Q?NdA+osfobL4Z1z1vl/NrNU6LmH1ODk6OFij487Tp/vF/L6GrJGdJRQKQ?= =?Windows-1252?Q?+vu7ZVWX7zIjGCf26tUZZRYMRHp7IOCrJcMsfFerZaByG74gse88cEnb?= =?Windows-1252?Q?ukkDhpE6NWRN3PRozwojWoXuDGYE5MHDgN6FkAg1+5ehBaSgmFliX5Tw?= =?Windows-1252?Q?vNasTNURSS9zxuklFcdSdt8Uub0T9bq/UjZYCZLbCxGRTiB/HeTmaUm8?= =?Windows-1252?Q?iZRifb087WrSRaM0uSe3RNqUSj1JXO4vU5aHgWU4HYj9O2qWK75hx+ng?= =?Windows-1252?Q?J68KBmE2EL33b5QVtL6aMbqeSkC+H2OaT28gRfp11Db5nLzoaLzAu2E4?= =?Windows-1252?Q?JkfP4SS2X44ktFFysr63IHK/GH8aWObczkZO2pdpQ5N+xSquzXwB1AR9?= =?Windows-1252?Q?iahF9UXxaa/OxSJLv7VQLgQA+aVdeZwdAfOo+t8Mfs3X5HCmRLIrFdWh?= =?Windows-1252?Q?mq2H/CeyuOOaWlV8vQVEv0dxeG9qF2w1oD2Yw0wU+1xW1euYyBALaLHO?= =?Windows-1252?Q?KlgEc2H0nDQzGeIl5xnPgU/NwVfEvyRSwyYGK+D+HwlQfg9KjcV5uFWO?= =?Windows-1252?Q?AT5RN2QK/ckyCHUzC08ePLPugKur2lCgy3AWhUJdmGlnAfEG2aeY6vep?= =?Windows-1252?Q?dw37PWq5fhLpjKMruDCZCCeNWqJtIZKvwP9LDgVTfq5aE7z4CIPbB6J0?= =?Windows-1252?Q?Y0doTcUmD1L9Gu+J85mdYOCT5r3qTnO6nago0FFitcTy3ZHmZClSEwTL?= =?Windows-1252?Q?Bm1BkS+HNxR4rWSdpj3F9Rtjn/1P1eWBlM8MPQZi0V8euV+Q2TsRhAPE?= =?Windows-1252?Q?dL+V3ecucl70GJ6kD3lnAXN8ORssVP+zPkLi+urenBJeniiJbeAa8nxe?= =?Windows-1252?Q?ZvEQkt13Xc+MJMWP9Mg6FabRlZB7ahdARiKLyIkoTBsItCXXFAt3QJFi?= =?Windows-1252?Q?/LNZQ6hkrS8GcwZqxIdqZ9bW71XJV40ROm96YDCwSTnwExzoegg7dn3M?= =?Windows-1252?Q?grhLGvWJoc8/vpKuf4Q8Vj6MExyW87zPA3DBvKW6ozGSCgxd2zTfYp6D?= =?Windows-1252?Q?+1F5Vimor/4O2gXBUeYVKyPp6XX9ig=3D=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR11MB3803DC294871CE93A6FCA8F6A3C09DM6PR11MB3803namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB3803.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e37d7720-2b74-42f7-4252-08d962f66472
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Aug 2021 09:47:43.4663 (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: KtQYyiphL/mLZPALgbuSX6jAl6aDYVJcy9+tTIaMLIBGdsp1FwkUTFqeS1I5PaKP
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB4363
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.18, xbe-aln-003.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/bRH2klKapG5d7xzjR4rj13zL_Q4>
Subject: [Roll] Review of draft-ietf-roll-enrollment-priority-05
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: Thu, 19 Aug 2021 09:48:52 -0000

Hi,

Thanks to Konrad for very comprehensive comments.

I am in favor of the “IDEA 1 (GLOBAL)”. There are two reasons:

  1.  The min enrollment priority provides a criterion for selecting the join proxy not the parent. So it is mainly meaningful for the DODAG root. I do not see a use case of local/flexible enrollment priority.


  1.  As you already discussed on it, if the min enrollment priority is local/Flexible, how should a child react when receiving different values from different children.

Best regards,
Huimin

----------------------------------------------------------------------

Message: 1
Date: Wed, 11 Aug 2021 23:24:36 +0200
From: Konrad Iwanicki <iwanicki@mimuw.edu.pl>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Cc: roll-chairs <roll-chairs@ietf.org>
Subject: [Roll] Review of draft-ietf-roll-enrollment-priority-05
Message-ID: <9b7eabc7-e521-bf82-4087-c65e08fc9fc0@mimuw.edu.pl>
Content-Type: text/plain; charset=utf-8; format=flowed

Dear Rahul, Pascal, Michael, and all,

As promised, I am sending my remarks about the enrollment priority
draft, version 05, so as to point out the issues I have with the draft,
thereby providing some starting point for discussion at the August
interim. Sorry for the text being rather lengthy, but I wanted to
highlight all major issues that came to my mind. I am not providing any
editorial changes, because those below are more important at this point.


PROTOCOL OPERATION WRT. FIELD MIN PRIORITY

Based on your comments on my previous review, I gather that there are
two different ideas on how the protocol should work, clarifying which
was also the reason for the questions I put in my previous review (of
the draft version 04).

Unless noted otherwise, the text below refers only to the management of
field min priority. In other words, let us completely ignore field
DODAG_Size for a while. We will return to it later.


IDEA 1 (GLOBAL)

The first idea on how the min priority field should be managed is
supported by Pascal, and I will refer to it as GLOBAL. Essentially, it
works as follows:

1. The min priority values are generated solely by the DODAG root node;
other nodes are not allowed to change these values.

2. A node extracts the value from a received option, stores it locally,
and uses it as a base when computing the proxy priority for EBs, which
may also account for the node's local constraints (e.g., load); however,
per 1., only the originally received (and stored) value of min priority
is used in the options in DIOs sent by the node.

3. An option received from ANY node can be used as the source of the min
priority value but the receiving node has to be able to judge whether
the received value is fresher than the one it already stores locally.

4. To this end, a lollipop sequence counter that I proposed, let's call
it OSN, can be used. I suggested adding it to the option, but others
suggested using some existing counters. This is immaterial for
now---more on that later; instead, let us just assume that we have OSN
mapped to some counter.

5. In any case, the root node bumps its OSN when it produces a new value
of min priority. (This condition can also be relaxed but I'd rather not
make this text longer. We can discuss this during the interim.)

6. Whenever a node receives an option with a value of OSN that is
greater than its own local value of OSN, it adopts the received value of
OSN and the received value of min priority as its local ones. Those
values will then be sent in the options in DIOs transmitted by the node.

This is a really simple and robust solution. Its main advantage is that
there are normally many paths that allow a node to learn the value of
min priority, which alleviates the problem of nodes that do not support
the option or nodes that experience (temporal) down times, overload, and
the like. The problem of the different paths being asynchronous, and
hence offering different propagation times for the values of min
priority, is in turn solved by OSN: the counter unambiguously
discriminates between fresher and older values. The effect is that as
long as each node has at least one neighbor (not necessarily a parent)
that supports the option, the min priory values will be eventually
consistent globally.

In contrast, the main drawback of this solution is that the value of min
priority is global. In particular, it does not take into account any
heterogeneity in the load, available resources, etc. in different
regions of the DODAG.


IDEA 2 (FLEXIBLE)

Michael and Rahul thus advocate an alternative idea, let's call it
FLEXIBLE. In this approach, it is possible to adjust the value of min
priority per node by incrementing the base value the node has originally
received. Although the new version (05) of the draft does not describe
this in sufficient detail, from Michael's comments I gather that the
envisioned solution is something as follows:

1. The root sets a value of min priority in the option in its DIOs.

2. A non-root node obtains the value of its min priority only from an
option received from its preferred parent and stores this value locally.
It can then only increase the local value, for instance, accounting for
its local constraints, before putting it into EBs and the options
transmitted in its own DIOs to its children. In other words, the value
of min priority can only grow at each hop, reflecting the local
constraints of the nodes on the path upward to the root.

3. Since for each node, there is only one source of min priority values
(its preferred parent), there are no conflicts. Consequently, in theory,
we could omit OSN, as is the case in the current version of the draft.
(This approach is wrong, as we will see shortly.)

4. To be compatible with the DIO processing rules in RFC 6550, a node
receiving an option with min priority from any neighbor performs the
processing according to the following rule (currently missing in the
draft): "When processing the option, a node ignores the value of min
priority in the option if the option does not come from the node's
preferred parent." (This rule is again wrong, as we will see shortly.)

5. If the node's preferred parent does not support the option, the node
assumes a default value (0x40) for its local min priority. This value,
potentially increased to account for the node's local constraints, is
put in the options in the DIOs transmitted by the node to its children.

The main advantage of this approach is that the min priority value can
be adjusted in a DODAG subtree. The approach thus offers much more
flexibility in configuring the values: an entire subtree that is
overloaded or experiences other problems can adopt a higher min priority
values so as to deflect enrollment traffic to other parts of the DODAG.
A disadvantage is in turn that the approach precisely defines the path
along which a node has to learn its value.


PROBLEMS WITH IDEA 2 (AND A POSSIBLE SOLUTION)

However, because of the existence of just a single path for propagating
min priority value to each node, FLEXIBLE, as presented hitherto, is wrong.

To explain, an important use-case, mentioned also in the present version
of that draft, is disabling enrollment in an entire DODAG. This is done
by the DODAG root setting its min priority value to 0x7f. Now suppose
the DODAG root has done this and that there exists a node, let's call it
X, in the DODAG that does not support the option. The children of node X
would thus adopt values 0x40+delta (depending on their local
constraints) as their min priority values. Since 0x40+delta need not be
equal to 0x7f, an entire subtree of node X need not disable enrollment,
which is invalid.

In general, in FLEXIBLE, nodes that do not support the option are a
major problem, as their ancestors disregard any decisions of upstream
nodes, including the root. The problem can be solved as follows.

- We use multiple paths for propagating min priority information but one
of them is preferred by each node (the one through the node's preferred
parent).

- To ensure consistency, we do employ the aforementioned OSN. Again, for
simplicity let's assume that it is incremented whenever the DODAG root
produces a new value of min priority but, like in GLOBAL, this condition
can be relaxed.

- There is no default value (0x40) a node ever adopts for its min
priority. (Apart perhaps from the value accompanying the initial OSN value.)

- Each node locally stores:
   * the last value of OSN
   * the accompanying value of min priority
   * a bit, let's call it PB, indicating whether the above values come
from the node's preferred parent (1) or not (0)

- In contrast, to the present version of the draft, we maintain the
following invariant:
     "For a given OSN value, the value of min priority at any node is
greater than or equal to the value of min priority at the root node."
   This is to ensure that no node, including the children of a node that
does not support the option, is able to override the root's setting of
min priority down for a given value of OSN. In particular, the invariant
ensures that if the root disables enrollment globally, then so will all
nodes (under the same assumptions on connectivity as in GLOBAL).

Given these points, the specific rules for processing the option are as
follows:

1. If a node receives an option with a greater value of OSN than its
local one, then eventually it adopts the received values of OSN and min
priority as local ones, and sets PB appropriately (i.e., to 1 if the
option is received from its preferred parent or 0 otherwise). It does
not have to do this immediately. In particular, it may wait for a while
to receive the option with the greater OSN from its preferred parent.
Nevertheless, eventually it MUST adopt the greater OSN (and an
accompanying min priority).

2. If a node receives an option with the same value of OSN as its local
one then:
   a. if the option is received from its preferred parent, then it
adopts the value of min priority from the option and sets PB to 1.
   b. otherwise,
     i. if its local PB is 1, then it ignores the received option;
     ii. if its local PB is 0, then it sets its local min priority to
the minimum of its local min priority and the value of min priority from
the option

3. If a node receives an option with a smaller value of OSN than its
local one, then it ignores the received option.

4. If a node changes its preferred parent, then it sets its PB to 0.

5. If a node sends the option in its own DIO, then it puts in the option
its local value of min priority or a greater value (e.g., taking into
account the node's local constraints). It can never sent the option with
a lower value of min priority than its local one.

This should do what I would expect from FLEXIBLE. However, I wrote this
up in a haste, so it would be great if somebody verified the above
algorithm.

As a side note, the algorithm suggests that FLEXIBLE is indeed a bit
more involved than GLOBAL, so a decision should be made, which of them
to put in the draft.


FURTHER ISSUES UNCOVERED IN THE DRAFT OR TO BE DISCUSSED AT THE INTERIM

Irrespective of the decision whether to settle down on GLOBAL or
FLEXIBLE, I believe that the following issues also have to be covered in
the draft (and discussed during the interim).

1. Should DODAG_Size be part of the option?

I mentioned this in my previous review and there has been some
discussion already. I would just like to add one observation to that
discussion: whereas min priority can follow either GLOBAL or FLEXIBLE, I
believe there is an agreement that DODAG_Size should follow GLOBAL when
it comes to propagating its value in the network. This information may
influence our decision on which of the approaches to adopt for min
priority and whether to put DODAG_Size in the option at all or move it
to another one.

2. Which counter to use as OSN?

I proposed a dedicated counter, which I believe is a clean solution.
However, there are other possibilities. I also believe that we agreed
that DTSN from DIO base is not the best choice. In my view, nor is
DODAGVersion but we can discuss this.

3. How do changes to min priority (and OSN) affect DIO Trickle timers?

This is currently not covered in the draft. However, I would imagine
that some decisions regarding min priority should be propagated fast in
a DODAG, and hence require Trickle timer resets. In particular, I would
expect that disabling enrollment globally should be disseminated as soon
as possible. Therefore, if I were to suggest anything, I would say that
a change by a node of min priority to the maximal value (0x7f) from a
lower one MUST entail a Trickle timer reset. In turn, a change from the
maximal value to a smaller one MAY/SHOULD entail a Trickle timer reset.
Other changes are, at least in my view, not that important, but this can
and should be discussed.

4. How does a (temporal) lack of a preferred parent affect the proxy
priority of the node in EBs (and in general, the node's behavior)?

This is also ignored in the draft but it may happen that a node does not
have any preferred parent for a while. In this case, it is unable to
handle any enrollments. What should it do? I would expect that it would
advertise the maximal proxy priority in EBs. However, should it also
modify its local min priority? I would probably be against.

Plus there are smaller issues I mentioned earlier, and I probably forgot
something. In any case, sorry again for such long a text but I hope it
may help during the interim.

Best,
--
- Konrad Iwanicki.



------------------------------

Message: 2
Date: Thu, 12 Aug 2021 09:47:16 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Cc: roll-chairs <roll-chairs@ietf.org>
Subject: Re: [Roll] Review of draft-ietf-roll-enrollment-priority-05
Message-ID:
        <CO1PR11MB488177A3BBB15404F812521FD8F99@CO1PR11MB4881.namprd11.prod.outlook.com>

Content-Type: text/plain; charset="iso-8859-1"

Hello Konrad,

This is great explanations of both options and how they could be made to work.

 What we need to add is, what do we want them for, which use case are we serving?

GLOBAL serves the need for a node to compare the load of the current DODAG with that of other DODAGs it could jump to. The use case is balancing DODAGs.

FLEXIBLE gives an indication of load of a preferred path. What would be the use of that?

- in storing mode it could indicate the capability of creating DAO state. But you'll find looking at it that you'd need a lot more than good or bad. If a node moves to another parent and has 100 children it needs to know that the new parent and its path up to the root have 100 rooms left. OK, it would split the DAOs between 2 parents, but if the bottleneck is up there where the paths from the parents cross, it fails. Bottom line, hard problem that we avoided so far.

- in any mode, it could indicate the throughput load. But then:
  * usually (P2MP or MP2P with homogeneous radios) that overload affects primarily the root's radio space, so there is no benefit in increasing the minimum, the root's one is the worst already.
  * there's the need to normalize the increment, IOW to explain by what the min value should be increased by the 6LRs and when so the result down there is comparable between preferred parent chains. Like the Rank computation which imposes a single OF, you need to impose a single operation throughout. From there, all the problems of updating OFs, using multiple OFs, etc...
  * the real need would be to rebalance the tree, but rebalancing a tree in a distributed protocol is another hard problem, subject to loops

So what is FLEXIBLE for? Convince me we need it and I'll support doing both.

On the side, I completely agree with you sequence counter in any case. The counter should follow section 7 of RFC 6550, including freshness assertion, etc... in which case there's little additional to describe.

Keep safe,

Pascal



> -----Original Message-----
> From: Roll <roll-bounces@ietf.org> On Behalf Of Konrad Iwanicki
> Sent: mercredi 11 ao?t 2021 23:25
> To: Routing Over Low power and Lossy networks <roll@ietf.org>
> Cc: roll-chairs <roll-chairs@ietf.org>
> Subject: [Roll] Review of draft-ietf-roll-enrollment-priority-05
>
> Dear Rahul, Pascal, Michael, and all,
>
> As promised, I am sending my remarks about the enrollment priority draft,
> version 05, so as to point out the issues I have with the draft, thereby
> providing some starting point for discussion at the August interim. Sorry
> for the text being rather lengthy, but I wanted to highlight all major
> issues that came to my mind. I am not providing any editorial changes,
> because those below are more important at this point.
>
>
> PROTOCOL OPERATION WRT. FIELD MIN PRIORITY
>
> Based on your comments on my previous review, I gather that there are two
> different ideas on how the protocol should work, clarifying which was also
> the reason for the questions I put in my previous review (of the draft
> version 04).
>
> Unless noted otherwise, the text below refers only to the management of
> field min priority. In other words, let us completely ignore field
> DODAG_Size for a while. We will return to it later.
>
>
> IDEA 1 (GLOBAL)
>
> The first idea on how the min priority field should be managed is
> supported by Pascal, and I will refer to it as GLOBAL. Essentially, it
> works as follows:
>
> 1. The min priority values are generated solely by the DODAG root node;
> other nodes are not allowed to change these values.
>
> 2. A node extracts the value from a received option, stores it locally,
> and uses it as a base when computing the proxy priority for EBs, which may
> also account for the node's local constraints (e.g., load); however, per
> 1., only the originally received (and stored) value of min priority is
> used in the options in DIOs sent by the node.
>
> 3. An option received from ANY node can be used as the source of the min
> priority value but the receiving node has to be able to judge whether the
> received value is fresher than the one it already stores locally.
>
> 4. To this end, a lollipop sequence counter that I proposed, let's call it
> OSN, can be used. I suggested adding it to the option, but others
> suggested using some existing counters. This is immaterial for now---more
> on that later; instead, let us just assume that we have OSN mapped to some
> counter.
>
> 5. In any case, the root node bumps its OSN when it produces a new value
> of min priority. (This condition can also be relaxed but I'd rather not
> make this text longer. We can discuss this during the interim.)
>
> 6. Whenever a node receives an option with a value of OSN that is greater
> than its own local value of OSN, it adopts the received value of OSN and
> the received value of min priority as its local ones. Those values will
> then be sent in the options in DIOs transmitted by the node.
>
> This is a really simple and robust solution. Its main advantage is that
> there are normally many paths that allow a node to learn the value of min
> priority, which alleviates the problem of nodes that do not support the
> option or nodes that experience (temporal) down times, overload, and the
> like. The problem of the different paths being asynchronous, and hence
> offering different propagation times for the values of min priority, is in
> turn solved by OSN: the counter unambiguously discriminates between
> fresher and older values. The effect is that as long as each node has at
> least one neighbor (not necessarily a parent) that supports the option,
> the min priory values will be eventually consistent globally.
>
> In contrast, the main drawback of this solution is that the value of min
> priority is global. In particular, it does not take into account any
> heterogeneity in the load, available resources, etc. in different regions
> of the DODAG.
>
>
> IDEA 2 (FLEXIBLE)
>
> Michael and Rahul thus advocate an alternative idea, let's call it
> FLEXIBLE. In this approach, it is possible to adjust the value of min
> priority per node by incrementing the base value the node has originally
> received. Although the new version (05) of the draft does not describe
> this in sufficient detail, from Michael's comments I gather that the
> envisioned solution is something as follows:
>
> 1. The root sets a value of min priority in the option in its DIOs.
>
> 2. A non-root node obtains the value of its min priority only from an
> option received from its preferred parent and stores this value locally.
> It can then only increase the local value, for instance, accounting for
> its local constraints, before putting it into EBs and the options
> transmitted in its own DIOs to its children. In other words, the value of
> min priority can only grow at each hop, reflecting the local constraints
> of the nodes on the path upward to the root.
>
> 3. Since for each node, there is only one source of min priority values
> (its preferred parent), there are no conflicts. Consequently, in theory,
> we could omit OSN, as is the case in the current version of the draft.
> (This approach is wrong, as we will see shortly.)
>
> 4. To be compatible with the DIO processing rules in RFC 6550, a node
> receiving an option with min priority from any neighbor performs the
> processing according to the following rule (currently missing in the
> draft): "When processing the option, a node ignores the value of min
> priority in the option if the option does not come from the node's
> preferred parent." (This rule is again wrong, as we will see shortly.)
>
> 5. If the node's preferred parent does not support the option, the node
> assumes a default value (0x40) for its local min priority. This value,
> potentially increased to account for the node's local constraints, is put
> in the options in the DIOs transmitted by the node to its children.
>
> The main advantage of this approach is that the min priority value can be
> adjusted in a DODAG subtree. The approach thus offers much more
> flexibility in configuring the values: an entire subtree that is
> overloaded or experiences other problems can adopt a higher min priority
> values so as to deflect enrollment traffic to other parts of the DODAG.
> A disadvantage is in turn that the approach precisely defines the path
> along which a node has to learn its value.
>
>
> PROBLEMS WITH IDEA 2 (AND A POSSIBLE SOLUTION)
>
> However, because of the existence of just a single path for propagating
> min priority value to each node, FLEXIBLE, as presented hitherto, is
> wrong.
>
> To explain, an important use-case, mentioned also in the present version
> of that draft, is disabling enrollment in an entire DODAG. This is done by
> the DODAG root setting its min priority value to 0x7f. Now suppose the
> DODAG root has done this and that there exists a node, let's call it X, in
> the DODAG that does not support the option. The children of node X would
> thus adopt values 0x40+delta (depending on their local
> constraints) as their min priority values. Since 0x40+delta need not be
> equal to 0x7f, an entire subtree of node X need not disable enrollment,
> which is invalid.
>
> In general, in FLEXIBLE, nodes that do not support the option are a major
> problem, as their ancestors disregard any decisions of upstream nodes,
> including the root. The problem can be solved as follows.
>
> - We use multiple paths for propagating min priority information but one
> of them is preferred by each node (the one through the node's preferred
> parent).
>
> - To ensure consistency, we do employ the aforementioned OSN. Again, for
> simplicity let's assume that it is incremented whenever the DODAG root
> produces a new value of min priority but, like in GLOBAL, this condition
> can be relaxed.
>
> - There is no default value (0x40) a node ever adopts for its min
> priority. (Apart perhaps from the value accompanying the initial OSN
> value.)
>
> - Each node locally stores:
>    * the last value of OSN
>    * the accompanying value of min priority
>    * a bit, let's call it PB, indicating whether the above values come
> from the node's preferred parent (1) or not (0)
>
> - In contrast, to the present version of the draft, we maintain the
> following invariant:
>      "For a given OSN value, the value of min priority at any node is
> greater than or equal to the value of min priority at the root node."
>    This is to ensure that no node, including the children of a node that
> does not support the option, is able to override the root's setting of min
> priority down for a given value of OSN. In particular, the invariant
> ensures that if the root disables enrollment globally, then so will all
> nodes (under the same assumptions on connectivity as in GLOBAL).
>
> Given these points, the specific rules for processing the option are as
> follows:
>
> 1. If a node receives an option with a greater value of OSN than its local
> one, then eventually it adopts the received values of OSN and min priority
> as local ones, and sets PB appropriately (i.e., to 1 if the option is
> received from its preferred parent or 0 otherwise). It does not have to do
> this immediately. In particular, it may wait for a while to receive the
> option with the greater OSN from its preferred parent.
> Nevertheless, eventually it MUST adopt the greater OSN (and an
> accompanying min priority).
>
> 2. If a node receives an option with the same value of OSN as its local
> one then:
>    a. if the option is received from its preferred parent, then it adopts
> the value of min priority from the option and sets PB to 1.
>    b. otherwise,
>      i. if its local PB is 1, then it ignores the received option;
>      ii. if its local PB is 0, then it sets its local min priority to the
> minimum of its local min priority and the value of min priority from the
> option
>
> 3. If a node receives an option with a smaller value of OSN than its local
> one, then it ignores the received option.
>
> 4. If a node changes its preferred parent, then it sets its PB to 0.
>
> 5. If a node sends the option in its own DIO, then it puts in the option
> its local value of min priority or a greater value (e.g., taking into
> account the node's local constraints). It can never sent the option with a
> lower value of min priority than its local one.
>
> This should do what I would expect from FLEXIBLE. However, I wrote this up
> in a haste, so it would be great if somebody verified the above algorithm.
>
> As a side note, the algorithm suggests that FLEXIBLE is indeed a bit more
> involved than GLOBAL, so a decision should be made, which of them to put
> in the draft.
>
>
> FURTHER ISSUES UNCOVERED IN THE DRAFT OR TO BE DISCUSSED AT THE INTERIM
>
> Irrespective of the decision whether to settle down on GLOBAL or FLEXIBLE,
> I believe that the following issues also have to be covered in the draft
> (and discussed during the interim).
>
> 1. Should DODAG_Size be part of the option?
>
> I mentioned this in my previous review and there has been some discussion
> already. I would just like to add one observation to that
> discussion: whereas min priority can follow either GLOBAL or FLEXIBLE, I
> believe there is an agreement that DODAG_Size should follow GLOBAL when it
> comes to propagating its value in the network. This information may
> influence our decision on which of the approaches to adopt for min
> priority and whether to put DODAG_Size in the option at all or move it to
> another one.
>
> 2. Which counter to use as OSN?
>
> I proposed a dedicated counter, which I believe is a clean solution.
> However, there are other possibilities. I also believe that we agreed that
> DTSN from DIO base is not the best choice. In my view, nor is DODAGVersion
> but we can discuss this.
>
> 3. How do changes to min priority (and OSN) affect DIO Trickle timers?
>
> This is currently not covered in the draft. However, I would imagine that
> some decisions regarding min priority should be propagated fast in a
> DODAG, and hence require Trickle timer resets. In particular, I would
> expect that disabling enrollment globally should be disseminated as soon
> as possible. Therefore, if I were to suggest anything, I would say that a
> change by a node of min priority to the maximal value (0x7f) from a lower
> one MUST entail a Trickle timer reset. In turn, a change from the maximal
> value to a smaller one MAY/SHOULD entail a Trickle timer reset.
> Other changes are, at least in my view, not that important, but this can
> and should be discussed.
>
> 4. How does a (temporal) lack of a preferred parent affect the proxy
> priority of the node in EBs (and in general, the node's behavior)?
>
> This is also ignored in the draft but it may happen that a node does not
> have any preferred parent for a while. In this case, it is unable to
> handle any enrollments. What should it do? I would expect that it would
> advertise the maximal proxy priority in EBs. However, should it also
> modify its local min priority? I would probably be against.
>
> Plus there are smaller issues I mentioned earlier, and I probably forgot
> something. In any case, sorry again for such long a text but I hope it may
> help during the interim.
>
> Best,
> --
> - Konrad Iwanicki.
>