Re: [Roll] capability handling

Rahul Jadhav <nyrahul@outlook.com> Sat, 09 May 2020 12:46 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 80F2B3A0A4E for <roll@ietfa.amsl.com>; Sat, 9 May 2020 05:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 3FphCZ0lUzsv for <roll@ietfa.amsl.com>; Sat, 9 May 2020 05:46:22 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-oln040092253068.outbound.protection.outlook.com [40.92.253.68]) (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 D9E1C3A0A3C for <roll@ietf.org>; Sat, 9 May 2020 05:46:21 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ffny90wSfpmJcTsuG28uam0QawVVQDOcC9eIEIsSL84ug331Tve8JKrY8dCBhbcIgpvbsCLu0tGl7UlIUdj/HGnvWP0P+tIQp/RsKpzF5EeSVG/GyCd6mEJkPngx9UmdUuuhSHhwSVJpWim8KnPuinFEbNySTYQc93QxDcfGinwYNhTzq1y1bmtjcwaHbETMedvugcwz8iNs/03CkCk6Rdky2dTCdSOd7Iyh9lA1w4+MUx6CFPSIahOm8eB48t70g9V5Atz/XY0w5ajCCHlNsEzDVxcYftP4inPjWrPaw628iO5ermMt4rV9R6QScyuDlWlyX84/TdIOCR7kxsXWnQ==
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=7mL82512o7AligCvyZkF0HrbpkJhNdjWz8M5hTjLMuE=; b=h0sOjLMBOlzWY/z8FP/TOPra+3gLk+/LjFE5BvLp+Blxb6N3+G0Ayrk9uX3Zutpce6mAaA7TdZ8JBj9C2/SDkZrfCYYFdXKGf8xSvBpaEvoNHEFA6bIE8+1rShr4p2grSMPTuanM4aNBbUhrMyZNc4vcpK/wbY1fCckbNe7CaXMYESyxkwdTnn4CuH1w4Sc1RPyXGLj/tkgwvXVBWpNib/kQvEw3FDT7XFqgPp6vvZQe+i3gO9RQVwqwyeVQln+kxdtsn1sfSu0ZlC8TnLsRYsDxKbg/1n4xnRT5BM6qnBVfWp1JCvTbxVZEeoG5chAfuDXy1zXlGcqJWkzlNjkLeg==
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=7mL82512o7AligCvyZkF0HrbpkJhNdjWz8M5hTjLMuE=; b=YlvTLd81f2FfGtbmiJl6OsZ0qhgXvWpuBxIzfWUJU8ZHW+xdwgiXLSn3oB39VMyh9W0bxA1qIZCHxktQbW+sKB4yhm9oW3+y1ERgUTywaVZisvUXkzindj2xUqQOi+XTk/Xbiry+geeo/CETuKbWAFYMh2p5Quf8uqBpfvJfagNo3BNgYNb58uX9HFt/iGpyebD9YmmKmDCfnHFoY6eb/g+DJFOkeJlTshImiemhCiPqui/1wXCOt8yLyUo98TnnBDA/0YRmpJe+jueXOK80P4dxYcLkdCZTa+Cs1DRboBECpfbsicLNWP9iP8XRVbBbYWjx+OckozwgpJaRRRnC4A==
Received: from HK2APC01FT037.eop-APC01.prod.protection.outlook.com (2a01:111:e400:7ebc::45) by HK2APC01HT183.eop-APC01.prod.protection.outlook.com (2a01:111:e400:7ebc::237) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2979.27; Sat, 9 May 2020 12:46:18 +0000
Received: from BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM (10.152.248.59) by HK2APC01FT037.mail.protection.outlook.com (10.152.248.223) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2979.27 via Frontend Transport; Sat, 9 May 2020 12:46:18 +0000
Received: from BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM ([fe80::6174:ad1b:55:41be]) by BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM ([fe80::6174:ad1b:55:41be%7]) with mapi id 15.20.2979.033; Sat, 9 May 2020 12:46:18 +0000
From: Rahul Jadhav <nyrahul@outlook.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] capability handling
Thread-Index: AQHWJFAsZwgiM3y4ZEmUmGVmctTxoKic6mMAgAE5Y8+AAFodgIABOC3n
Date: Sat, 9 May 2020 12:46:18 +0000
Message-ID: <BM1PR01MB402013BCAA111B49554F286DA9A30@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM>
References: <BM1PR01MB402011EE18D8BE1C70A15AE4A9A50@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM>, <31727.1588874478@localhost> <BM1PR01MB40200BA596F107A09BD89DC6A9A20@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM>, <25184.1588961129@localhost>
In-Reply-To: <25184.1588961129@localhost>
Accept-Language: en-IN, en-US
Content-Language: en-IN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:08DDC697E4F700879533B2858B0F5DCA6EFDD172A9E2EF57A4C7660B4A4CEA63; UpperCasedChecksum:DC9220DAE7CE6E6FD22C0308F2378923D48B74299CB8384180D58D0B78BB980D; SizeAsReceived:6955; Count:44
x-tmn: [P7J7VNbxmCdFeeiTTZh/wBup30/O5iDd]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 30f96988-1523-4bc8-e5bd-08d7f416f841
x-ms-traffictypediagnostic: HK2APC01HT183:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +P4JtN/kPWTFxGRp0hJeq5IE0zB81ySCnDtXweQK1Q+FkN6DGm06A+MWFaL2FnjQu6nlu1BPB4mlQFcR076C+c6wjk9vh2k1pTD5pUdJVglTkoaJIInSl5pI/6hUAVB3TFMkh7t0V/5t5hKDOXL3Qd/NmWCk4RhXaOvdB//gKjuyIukbbp36+YGxWIG3nEGw/RMLVMgDhGwDgE+ovf0sTw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:0; SRV:; IPV:NLI; SFV:NSPM; H:BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFTY:; SFS:; DIR:OUT; SFP:1901;
x-ms-exchange-antispam-messagedata: J0+U77EejR77c+ktJiZG5Dch1WuuJTvE/be67GDZGrRD+XD8SB1e6DEOKpwZnrff5P77l37T50ITVk75Gkzf+bzwBx26c4RBDnPQZrRhKCIiO+vQErmsVO4jSA3hvtdXWGDEsR2R/xD3AEZaKqaC4Q==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BM1PR01MB402013BCAA111B49554F286DA9A30BM1PR01MB4020INDP_"
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: 30f96988-1523-4bc8-e5bd-08d7f416f841
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 May 2020 12:46:18.6711 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT183
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/8hXgKtBeCJ95UwW3PkdXAagzIyk>
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: Sat, 09 May 2020 12:46:25 -0000

Please find comments inline.

________________________________
From: Roll <roll-bounces@ietf.org> on behalf of Michael Richardson <mcr+ietf@sandelman.ca>
Sent: 09 May 2020 02:05 AM
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] capability handling


Rahul Jadhav <nyrahul@outlook.com> wrote:
    > There was ‚Äčanother point we discussed during the interim in context to
    > Capability Indicators: How to arrange the Indicator bits?  a. Using
    > left to right b. Or using right to left (currently in the draft [1])

    > If we use right to left then we can give every bit a number, for e.g.,
    > currently the 'T' bit is 0x1. The length can be set accordingly i.e. if
    > the indicators are less than 8 bits then the length will be one.  This
    > is simpler to handle in implementation as well. Thoughts?

(1) If we number from right to left, can we expand the field to be as many octets
    are we like?  So len=3 is just an example?  Don't transmit zero bytes.

[RJ] Yeah len=3 is just an example.

(2) If we number from left to right, then we could number them "bit 0" through
    "bit 7" of byte 0 through 255.

The IANA considerations for this might be a bit weird either way.
I guess there is a maximum number of octets that we can get into the field
anyway, so we declare it to be a field with that many bits and ask IANA to
allocate contiguously.

The effect is the same: we don't transmit bytes which are zeros, it's just
whether we consider those zeros on the left or right.

I think that (2) might easier to code because the offset of each flag will
not move as the structure gets longer, and it doesn't confuse people into
thinking they need 64-bit ints, which then fail on capability #65. (actually #64)

[RJ] This point makes sense. If the indicators go more than (or eq to) 64 then the operations are not so straightforward to handle. With left to right, the complexity is constant regardless of the number of bits.