Re: [Roll] capability handling

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 11 May 2020 14:39 UTC

Return-Path: <pthubert@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 8E4EE3A0BA4 for <roll@ietfa.amsl.com>; Mon, 11 May 2020 07:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 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_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=HOPpJi03; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=byZU0dVg
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 omhAuIzdw-7K for <roll@ietfa.amsl.com>; Mon, 11 May 2020 07:39:13 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B75AD3A0B97 for <roll@ietf.org>; Mon, 11 May 2020 07:38:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14474; q=dns/txt; s=iport; t=1589207925; x=1590417525; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=U1TandEun5F1aJdLRfQGdY/snrONhnfV4MjEwUspQOY=; b=HOPpJi03uYhI+gD5sLlJ1hnavlAWyjoP0U7wcr3tMKgBGyQPrq+VrC3k S/3K5O6e98QUoYPESSzvc+WqRcih58gpevGZDxhXFkreZqXnQWTCleXT8 u5/kaKWb8KfFizpY9keTgw+i6n0sfKkxMjYJSbt6x+16jdRxmUE5qyedJ w=;
IronPort-PHdr: =?us-ascii?q?9a23=3AiuFTYBKRY/aoBJf5C9mcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeGvK8/jVLVU8Pc8f0Xw+bVsqW1X2sG7N7BtX0Za5VDWl?= =?us-ascii?q?cDjtlehA0vBsOJSCiZZP7nZiA3BoJOAVli+XzoMEVJFoD5fVKB6nG35CQZTx?= =?us-ascii?q?P4Mwc9L+/pG4nU2sKw0e36+5DabwhSwjSnZrYnJxStpgKXvc4T0oY=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DZDwAbYrle/4YNJK1mHgEBCxIMQIJ?= =?us-ascii?q?sAS5RBW9YLyyHagOLMYIRk1SEY4JSA1QLAQEBDAEBLQIEAQGERAKCDiQ4EwI?= =?us-ascii?q?DAQELAQEFAQEBAgEFBG2FVgyFcQEBAQEDEhsTAQE4DwIBCBEEAQEoBzIUCQg?= =?us-ascii?q?CBBMIGoMFgX5NAy4Bo1oCgTmIYXSBNIMBAQEFhSMYgg4JgTiCY4JJhxgagUE?= =?us-ascii?q?/gVSCTT6ELAEBAiA0gxGCLY5GiSqafwqCSphFnTqOUZ52AgQCBAUCDgEBBYF?= =?us-ascii?q?pIoFWcBWDJFAYDZBAg3KKVnQ3AgYIAQEDCXyOBwEB?=
X-IronPort-AV: E=Sophos;i="5.73,380,1583193600"; d="scan'208,217";a="476775181"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 May 2020 14:38:44 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id 04BEciJE026569 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Mon, 11 May 2020 14:38:44 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 11 May 2020 09:38:44 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 11 May 2020 10:38:43 -0400
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 11 May 2020 09:38:43 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=BXxhKhdmw62ioX/EK26LAsHLjzTm1qTrFfnTkHnNIb53evJ/JqBZFCc2RgQYMDtyhj+A8wTyMd5NItr84pUT6MM/5ebUil5MiFJgwheneCj17uQY4Z2zSsHvpmW0kPSP2HkUpXTdQnue7fKQMp03K6vo54waoZkQ/eHcNNRu0EFqRYhYyjGIZn6G6xku4jmkpal3ZgnJ+JrT1qeHyyK2j5S3wQrH884xPKipVp0iS0i8+pKYiQVhFacCviefmFzlSf7SK+dpDOHGIuBh5X6b1P4Ya+qHFM8QIk4lqS6Fk9JVXwakHKVu8VSxRSD28r/jenml1JIokF+TpE5zffcr9g==
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=Yks6zWrQhfy7Mp0cdZOFVCILQ0X/u4A/j3W8ALuj6lY=; b=Zc+VcUqABTBEv98YZc3lV0Faz2ZgLqwftxVvu31AodbGVn54CrZyEyYTmOBverZDqhSuFKX5gaBDCRY5mcJVIyDS/8rKukNl9LUfGwJGGo7EP3wOutZ22t0hLw8w2QZl2cpXXsyyfJ08MriC7JchLbjIOmVn8OpT0QR2nkkfb4ET6YZIU50bjTwctyBO+O3L7GPWIoesTghl5WVT7w81/IQOKS2kMN1jXGQTTsRdODdIUH2CVLjjD88AcLQ5m5NVu0Wc5CygXnSBioy5z4Nb0UWX04MZCu/oNy6e4PQOe3PpZbAGW/7yfYpzWO7wPtuZ/LQXtKKx9mC9wuo6TgdZ8Q==
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=Yks6zWrQhfy7Mp0cdZOFVCILQ0X/u4A/j3W8ALuj6lY=; b=byZU0dVgjJWgUZcCKur1d+ABM8gJi6ZFt5jSbcCV19VaAehto9ihyJWBKt9rS9xup83p+j7yKwTd4BmzJ3DVLD+Ri4P8kY20P5Eg+xIFydtxzABvIV61Cz97Jgew1CRNOJ0HM7H6UEXchvLBFU0w/3qAKiM5fvqd+dV7FEf5G6A=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (2603:10b6:208:ea::31) by MN2PR11MB4254.namprd11.prod.outlook.com (2603:10b6:208:18f::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2979.34; Mon, 11 May 2020 14:38:41 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::113b:3127:ef12:ea7]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::113b:3127:ef12:ea7%7]) with mapi id 15.20.2979.033; Mon, 11 May 2020 14:38:41 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: capability handling
Thread-Index: AQHWJFAsZwgiM3y4ZEmUmGVmctTxoKicWyMegAacV3A=
Date: Mon, 11 May 2020 14:38:14 +0000
Deferred-Delivery: Mon, 11 May 2020 14:37:55 +0000
Message-ID: <MN2PR11MB3565DEA642FD973CD5A52E4ED8A10@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <BM1PR01MB402011EE18D8BE1C70A15AE4A9A50@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM> <BM1PR01MB4020A5A77C7B4C9C16AA0598A9A50@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM>
In-Reply-To: <BM1PR01MB4020A5A77C7B4C9C16AA0598A9A50@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM>
Accept-Language: fr-FR, 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-originating-ip: [2a01:cb1d:4ec:2200:41a1:12a8:8f5a:bbb0]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c64baa0e-e034-4bd8-1fd3-08d7f5b90007
x-ms-traffictypediagnostic: MN2PR11MB4254:
x-microsoft-antispam-prvs: <MN2PR11MB4254C93201FC0F85E03D5D1FD8A10@MN2PR11MB4254.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 04004D94E2
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 5MwVLH9MGSYGTd3ZWwpbGGbMd3/3YtGhFJnRD/i0J/qF2wo54Scw76EwkoazhgdLJn7EcqCIoFVGSj/b+jn+LmhGNmg/AzOBNfMbmkgmL1UGIkQj4YL1aMHWYlSN3R2WmyLbncPAKjV+xXWbM7OjofrNW3uCd+QPupXqQWw/zQmWIQhgkK3Q60AYid+TmlXPgkvKoEjrZLZlNBM7gQ4W45iupWCxVpEKo81MED2JhmshRRJSFEgdr6dLybCY0/jCtIg4ddX4aCVbAKXHssDd1uoJh7TDTi4ENpvcFeo+noR4z6RYP5LL+zcsa70VUeaa4jc/eVHiDiNFQaaaBls2PUZXTgnu5ua/OalXxF7KkZXWbxJCidvIUP08DRrbsqfJPtvN56RK3ceuMnf5JsI3KBh6pPdrhxNtuPc1kedLcZTnyr3hqhBkYPLivjmgIWosh8vMm4yQ2IgprT/O/L33ApSbXXpuvKjhH6auJMNFdTXmOXPwRHf/TIsnoIjqW9ScDxHU2p1f55RzWAv9qgpe4w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR11MB3565.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(136003)(396003)(39860400002)(366004)(346002)(376002)(33430700001)(53546011)(6506007)(66556008)(64756008)(316002)(7116003)(478600001)(5660300002)(52536014)(8936002)(55016002)(9686003)(2906002)(66946007)(66476007)(86362001)(7696005)(33656002)(33440700001)(66446008)(76116006)(3480700007)(8676002)(6916009)(6666004)(71200400001)(66574014)(186003); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: Mcc0t4KFeJGhhOCrtzCpci6ZNJYa0xaoWb+KdoavBQZTzbPIYw9MTHEn/k8kBNGooSYC0uHjsJr4lFpBIrocYDx9k96kvYSrF1gqGZiFi4RONug0e+ooZbWjRrLB2nKlEe1jWDdxp3+rfi8fCt3ODdosRpxaZjzgYSuJJ3CMfO+0ZYhQtUws4pxVZYHbQs+TtVn68qCzFrg8SB2cYcCE6vlzfmR8E7krDWSDnGZyqQqIAurqpQ714+7bIpER+GlF0yfIx2MxCSleU57RrX2HCJCBCz9utbXV1OqxW2mScfTcF/vn0ecj/VKRiS1+4B0a4hoqTqUXW3UX7LISXyQy6zksqtoKaSMqtDh+KtKj3N5SSKf7qxC0TC3fa0r3C4ZazexULu2J3OW8GTaaY5zlf5xsdGy3qd/22cqN2VjB+aN3hbS5rnpZZ5J26Car4LRRTztIM2Qwa6huuzzdF+lyeevUVq+uZyaOubi2MFtnF+EnjNse4h8VL7+cK8AEQeTCEnMOmC6SoguEJHJEMN/velx4FHMpqCFHVE1fl4mFbN5iuEJyR3jMRfabLWonZR2y
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB3565DEA642FD973CD5A52E4ED8A10MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c64baa0e-e034-4bd8-1fd3-08d7f5b90007
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 May 2020 14:38:41.2627 (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: W6h1tVXaWDaQo/xuYMVTLZZ6LrHh8Mv9BH0UZzKWhqY+R+D5yvPl+DEzMoKYmbw2JH755lDlQh4yw0Pb+OckBw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4254
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/1sQwLx9FadU2OyUk2mQkufmGGTA>
Subject: Re: [Roll] capability handling
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: Mon, 11 May 2020 14:39:29 -0000

Hello Rahul

Sorry for being late on this:

There are different things we may want to convey:
- local/global: indicates whether to forward the bit. Local is a parent property, Global is a DODAG property. It boils down to your "copy" action so to your point we do not need both the G and the copy bits. Note that RPL also uses the term "propagate", and I tend to prefer using it again here rather than copy.

Then there's the things we define for the configuration which may also apply to capabilities:
- critical/elective: indicates what to do when the capability is not known; Ignore this capability vs. drop the message
- router/leaf: I'm wondering if we have a case where the node should become a leaf if there's a capability it does not understand. That would be another bit.

Does that help?

Pascal


From: Roll <roll-bounces@ietf.org> On Behalf Of Rahul Jadhav
Sent: jeudi 7 mai 2020 11:37
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] capability handling

<< sorry my last mail was sent incomplete>>

Hello All,

We would like to solicit some feedback about two points in context to capabilities:

1. Capability Instances: Currently the document instantiates two capabilities viz,
        a) Capability Indicators (which can be used to carry flags such as support of 6LoRH)
        b) Routing Resource capability which indicates total RIB capacity the node has. This should be useful for DAO Projection.
        Do you think we should add Neighbor Cache capacity indication as well and what would be the use-case?

2. Regarding the use of 'G' (global) flag on per capability basis:
       Do we need an explicit 'G' flag? We already have a flag (C-copy) which indicates that nodes have to copy the cap if they don't understand the cap. A global capability from the root can be advertised with this bit set. Nodes understanding this cap will anyways know how to handle and nodes not understanding it will copy it based on the 'C' flag. Thus not requiring another 'G' flag.

Best,
Rahul
________________________________
From: Rahul Jadhav
Sent: 07 May 2020 05:28 PM
To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
Subject: capability handling

Hello All,

We would like to solicit some feedback about two points in context to capabilities:

1. Capability Instances: Currently the document instantiates two capabilities viz,
        a) Capability Indicators (which can be used to carry flags such as support of 6LoRH)
        b) Routing Resource capability which indicates total RIB capacity the node has. This should be useful for DAO Projection.
        Do you think we should add Neighbor Cache capacity indication as well and what would be the use-case?

2. Regarding the use of 'G' (global) flag on per capability basis: