IETF Logo Mail Archive

Re: [Roll] Eliding mechanism in 6550

Rahul Jadhav <nyrahul@outlook.com> Mon, 30 September 2019 02:19 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 5AB921200F9 for <roll@ietfa.amsl.com>; Sun, 29 Sep 2019 19:19:06 -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 PIb9m4kSQz2m for <roll@ietfa.amsl.com>; Sun, 29 Sep 2019 19:19:04 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255050.outbound.protection.outlook.com [40.92.255.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E5061200C7 for <roll@ietf.org>; Sun, 29 Sep 2019 19:19:03 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Z4aWv7iVBr5GsgUsGsYYD7S2kOQ2F/eOBKj1hOkBlNUgg8vei/C5QSCoSfp0gufudSlTDXny5QEJehSNDvMEPTM5zSfaAAG31Hw9dra46fsi+uPp3zwLM9t/y4jteCmt3kutlshQwHKDNCvT9WZWpjJxHteUIUqICLyb4YQc4ox0DqPFUy/LkIANTmRHkIj4VckLHf1/XyfRtr7XFBVOBKmpMDj9tkzlvEM0F5uPGdcoDC/Q0eryVppXK/cMsISsyWIlCs2TaaXFC1wdOo/EsfiL+0gnJnhr17QXhOLNQfP5RAc5PrOUQnQb6Aw25QmKWLaAebN9FVVwS+a2WO6PBw==
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=Igck5/GBr7/oUNSPzfZ1bMxjC9TcoG3Os1LDNDAA3so=; b=oMoaYl5vq7zkblmSl49Wxw97vrJQGM5oKnHZ4W4iMr2vi0snnUr1alA/GdLn+gh28LsYmxw1uD2ueZMdwEZ2Lm39b3UWC929wBHpOrma9mW83Xo5E8yxgtYxLwVYl58E6jO+I03qqc3s+M2MPxF1HmwWWXj4YDU5yvcEk7Cynvq9LHhNiTKQycjh1v9CsITTGrKaBj8lQKbyU4/N3f5ubxJjuGHdRtpD7bBN1Nbeu+U9Fu9LeZ5jIow1hVm/3sp017ggBbLCOjT3SjqR2AcKrzWp9T1Ku8AfOUiEANKy8OIkJt/qYu1agNuNOFeOQRo7shXcvVelyCKmsX6wN3XkLg==
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=Igck5/GBr7/oUNSPzfZ1bMxjC9TcoG3Os1LDNDAA3so=; b=mB44bqRR4uMtEWKKfkM+kXOXnXLkjI1XHWPcVhYR8zvy22A61GQS3ViWdarl0TLARazvly/3gLFYNOT0/cI6f4XBOrnprPFi1Z6aw2fWcNmI8tO1wZBE3XN2Bm32jleabwRDdFTp17qaIwjdDwlysT4rkV27P37gjh8xn7aa4DaaxGymsGo9RtcnALRrOSrmQGS4+sXBwQFAopkGRCm5HCsrhWDLRCSyTYsVAUoYMj3xQU3ufXZigFyJvCJFMP4Iy0UIvoCNAyIH2UrZL63GVovNg4gZ9KRXgn0VDH2qgeACeAqlUVynD4FcAW12547pXEH71RxaV4SmaAz8cbZRiA==
Received: from HK2APC01FT040.eop-APC01.prod.protection.outlook.com (10.152.248.56) by HK2APC01HT215.eop-APC01.prod.protection.outlook.com (10.152.249.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2305.15; Mon, 30 Sep 2019 02:19:01 +0000
Received: from BM1PR01MB2612.INDPRD01.PROD.OUTLOOK.COM (10.152.248.57) by HK2APC01FT040.mail.protection.outlook.com (10.152.249.42) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2305.15 via Frontend Transport; Mon, 30 Sep 2019 02:19:00 +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.2305.017; Mon, 30 Sep 2019 02:19:00 +0000
From: Rahul Jadhav <nyrahul@outlook.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] Eliding mechanism in 6550
Thread-Index: AQHVdUhliZ040nQflUyScFbwadE6vadDQIYAgAA8/gE=
Date: Mon, 30 Sep 2019 02:19:00 +0000
Message-ID: <BM1PR01MB2612D8305DF9900C7D3255C2A9820@BM1PR01MB2612.INDPRD01.PROD.OUTLOOK.COM>
References: <BM1PR01MB2612A9D3C37CD5D009626CCFA9810@BM1PR01MB2612.INDPRD01.PROD.OUTLOOK.COM>, <28599.1569796250@localhost>
In-Reply-To: <28599.1569796250@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:2E491D34F388DEB5FDCE34F711EAD804AAD9AA0A10156E9C07EB9811F649B70C; UpperCasedChecksum:FAB7C0F10A26F56D5EC758B5C97B0A8DD9720557BFB1BA738855D709ACE90FFA; SizeAsReceived:6815; Count:43
x-tmn: [Vf5ZvQQKCL/M31qrpa7r+sN17JnlcPkYKDtVuOYvrdw=]
x-ms-publictraffictype: Email
x-incomingheadercount: 43
x-eopattributedmessage: 0
x-ms-traffictypediagnostic: HK2APC01HT215:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Bk0g/CLB9tF7FLmeqcSmTFawHDK6yMtxx3BnFDak9GldoabrVTl3wr3fOCkEQLTE9HbD0U6El0xq6Rtg+E0fSeFshAH8Xdod08hwVhdtA5/bv3W1YkLBZwdDuBFfD76T6VNhZAOrKbJ9GB6nbk2Sq9bKFl2RiM2tqFK7NToVjpav9uU0SWGilmr1RBJCDNMJ
x-ms-exchange-transport-forked: True
Content-Type: multipart/mixed; boundary="_004_BM1PR01MB2612D8305DF9900C7D3255C2A9820BM1PR01MB2612INDP_"
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: a42efcbe-fdf6-4856-e8e1-08d7454c8e9d
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Sep 2019 02:19:00.7569 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT215
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/MAiD0BKIn2kZd64LPz1Gm3IM7Ww>
Subject: Re: [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: Mon, 30 Sep 2019 02:19:06 -0000


    > 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?

My question is what are the sizes of the DIOs, and how close are we to
fragmentation already?

[RJ] The typical size of DIO is 93 bytes in my simulation framework.
ICMPv6 Hdr: 4B
DIO Base object: 8B
DODAGID: 16B
Config Option: 16B
Prefix Info: 32B
Remaining bytes are IPv6 and lower layer headers.
Attached is the pcap.

v2.23.0 | Report a Bug | By Email