Re: [Roll] Eliding mechanism in 6550

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 07 October 2019 10:17 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 2E5BC120804 for <roll@ietfa.amsl.com>; Mon, 7 Oct 2019 03:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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=Ke8M+ggN; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=DPOZRBpx
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 oGQxIGRVt5gC for <roll@ietfa.amsl.com>; Mon, 7 Oct 2019 03:17:17 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F293120077 for <roll@ietf.org>; Mon, 7 Oct 2019 03:17:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10535; q=dns/txt; s=iport; t=1570443437; x=1571653037; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=2aF90ZrFsZ0+sVcBdQsM2nTiIWk8s0gTIToG6+aiq8g=; b=Ke8M+ggNq83LFigBHBI7ins2qW6c4FswvsTrlZOcjHbu6km7Td14Lr3O AW6x6y6Zjy7MwhkSbUDiAKg3u6iOsP9Hpe+5MrWqmykcOneMBvBGZYaQc zFEhRleGvyg5hVspiYX/uNsl2ZlMja0aHx/y5u/RYDWmMTaIfGZ+bepSv M=;
IronPort-PHdr: =?us-ascii?q?9a23=3Ac4656xdx07NrbZL4lscWRieYlGMj4e+mNxMJ6p?= =?us-ascii?q?chl7NFe7ii+JKnJkHE+PFxlwGQD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFn?= =?us-ascii?q?pnwd4TgxRmBceEDUPhK/u/dzA6Ac5PTkNN9HCgOk8TE8H7NBXf?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DhAACwD5td/5tdJa1mGwEBAQEDAQE?= =?us-ascii?q?BDAMBAQGBVgMBAQELAYEbAS5QA21WIAQLKgqEGYNHA4pJTYIPkxuEYYJSA1Q?= =?us-ascii?q?JAQEBDAEBGAEKCgIBAYFMgnQCF4JCIzcGDgIDCQEBBAEBAQIBBQRthS0MhUs?= =?us-ascii?q?BAQEDAQEBEBEdAQElBwwEBwQCAQgRBAEBASoCAgIlCx0IAgQTIoJ7BAEBgR1?= =?us-ascii?q?NAw4PAQIBC6FCAoE4iGF1gTKCfQEBBYJJgkAYghcDBoE0AYwNGIFAP4ERJx+?= =?us-ascii?q?CTD6CYQEBgUUkJYJgMoImjQOCaoU1mB4KgiKVGBuZP6deAgQCBAUCDgEBBYF?= =?us-ascii?q?oIw2BS3AVOyoBgkFQEBSBTwkag1CFFIU/dIEpjyABgSIBAQ?=
X-IronPort-AV: E=Sophos;i="5.67,267,1566864000"; d="scan'208,217";a="339337862"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Oct 2019 10:17:16 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x97AHGGm025332 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Mon, 7 Oct 2019 10:17:16 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 7 Oct 2019 05:17:15 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 7 Oct 2019 05:17:15 -0500
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 7 Oct 2019 05:17:15 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iwhJB2tIRsDORdUfaUWwDTzEcH/RnZoLERNamsgTf3qCCBWLvzKZsQC0Kx6aMjAQ/0gqbv3TcN6AbF/lt1KNO8eo54ymnXXCZymWjKqIQJnMmXjgBCA0y3SQTgAOR8dYLHeV3JZDVpYe90t6nOZSYibL+ry/8AjD96SK3cFDT5Q7Honasax6wfXyLWE6imSk2LtQooOwtFgTWArOOrSXcq1ctVU3Lr60Y/EIWASJL3iV7RDsoee2kBh+Pt6iY9DwP0oRCjouoVyrJoUGGSVRuW03EM5R7JasJ2+mQesAVRS1ISf0kFvpzYNNzKDMYsJ0qtXQ0oS6drhoPruE0WQHbw==
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=2aF90ZrFsZ0+sVcBdQsM2nTiIWk8s0gTIToG6+aiq8g=; b=C7UXJajhzb/gpoCmml1bjFefnNFtsV5ZW24S4rUN2JsuvkopsopSLUIRiqXlaAT0otDVz3ZUAx/cWVKDpbCoyWlNPnL8un6rhfGu3Jcyr3Nw2msnvmUePw4bKIrVC0lPpPi6UiGtO6R4xMreV9I+ewXoizl/oRkTXgufYteOXTca/0RxOs6Dkz86HB8H6LvjGToDMwgiwqq4uZ3hFWPu7UNeOxpC2WopX/564RlahxwJnvwrftlbd3Bo5EDsg+L1QunfAUm9E2CcRHks2mdDGLs+YTgZVaNHTwdaDJHlVzndCsf2f6EGxjPbsorgupTmLRr4dQBApmAvZwgBPM67CA==
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=2aF90ZrFsZ0+sVcBdQsM2nTiIWk8s0gTIToG6+aiq8g=; b=DPOZRBpxqlP1cRPz+bQ8t/XWpZPBnMilOwZS+GIaSOQK1gZNzVNVDuhLupGb24N4jpHNTBbMEGXw5OHcJ5hUHLb4RAxb9Dh/xOF7KZf1WCkaZyb7B8fmffV9JcJp27xteGFnNCQj9cuH1Yq03mOipN0NsKaJcbc4wNjE4B6fx9k=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3776.namprd11.prod.outlook.com (20.178.251.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2327.24; Mon, 7 Oct 2019 10:17:14 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::652e:fba0:4959:7ce8]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::652e:fba0:4959:7ce8%7]) with mapi id 15.20.2327.023; Mon, 7 Oct 2019 10:17:14 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] Eliding mechanism in 6550
Thread-Index: AQHVdxWYTfJkX2vtREOJsDxTaX1EB6dDlT6AgAJTGzCACNfNAIAAQnSA
Date: Mon, 7 Oct 2019 10:17:14 +0000
Message-ID: <11B729F6-924B-447D-A263-D7EB385FA323@cisco.com>
References: <BM1PR01MB2612F28DFB810043C7316EB5A99B0@BM1PR01MB2612.INDPRD01.PROD.OUTLOOK.COM>
In-Reply-To: <BM1PR01MB2612F28DFB810043C7316EB5A99B0@BM1PR01MB2612.INDPRD01.PROD.OUTLOOK.COM>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [91.69.164.91]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d857dc5d-8501-4795-4973-08d74b0f8657
x-ms-traffictypediagnostic: MN2PR11MB3776:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR11MB37766A53A68DA9C22A9F6898D89B0@MN2PR11MB3776.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01834E39B7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(136003)(396003)(39860400002)(376002)(366004)(189003)(199004)(13464003)(476003)(7736002)(99286004)(6486002)(2616005)(76176011)(25786009)(486006)(33656002)(478600001)(2906002)(11346002)(66574012)(6246003)(446003)(5660300002)(71200400001)(45080400002)(71190400001)(36756003)(66066001)(316002)(14454004)(102836004)(6512007)(229853002)(8676002)(6436002)(81166006)(81156014)(236005)(3846002)(53546011)(6116002)(186003)(54896002)(6306002)(6916009)(966005)(86362001)(26005)(8936002)(256004)(6506007)(14444005)(66556008)(64756008)(66446008)(66476007)(66946007)(76116006)(91956017)(606006)(244885003); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3776; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +porm7c8qL0sYZg7rRbNWW4GYr7TqttEaQYvYo95MGQXMl1egz7svbs6i78lD/5a1l220uzIZU9VNOm34Dw79qtNHfJd4HoyeWhTLbwXzXZgJ9gYwsA05xsJ6GnRv/digvJkdatxCBjq01IZ4BFiDmDZEM9sXSV9RytGEyY7gCaSEevfRvgEZUsyXuwDzIUAaqSlByiwu/dSpDsqG3GHjPCOaNmFZOlY8sXPPqntiBxlhkfSTt/031LdYnwuTKtvGXSGTBN5egiTulnAYgkFGhCXz9383BfP7ACyqEZNwxp+YNiSRsDcYJg0QLzxdXseJ1vI0DskYozk2ht/xPiQO9GGVH9sXHwJ9a5X5T1myeK6FyMjwj1WQeZLklvfm08slDa7IcEc96d7ECbWRzbeMmvQj6EICBqPjG3lZHV5oU93FyS46xp8lCAUPY7ZjVS/3Xs6ubaBICXrBKVuRUwPog==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_11B729F6924B447DA263D7EB385FA323ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d857dc5d-8501-4795-4973-08d74b0f8657
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Oct 2019 10:17:14.4855 (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: wxoSgQNuLoPJ7n6pBAwugxWgep3MOFhrBPS/gBbNISW4Pv1nxGj5zWuwTlK4ogyMMOR20WzohLcdqk0J38rjeQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3776
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.30, xch-rcd-020.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/gVpov-URapKdAmHLvjqvabbH1lE>
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, 07 Oct 2019 10:17:20 -0000

Yes it could certainly. We might also consider SCHC as an alternative to GHC for extremely constrained networks...


Regards,

Pascal

Le 7 oct. 2019 à 08:19, Rahul Jadhav <nyrahul@outlook.com> a écrit :


Maybe DODAGID is not a good example but how about other static information such as Prefix Information Option carried in DIO. Can it be a candidate for eliding?
________________________________
From: Roll <roll-bounces@ietf.org> on behalf of Pascal Thubert (pthubert) <pthubert@cisco.com>
Sent: Tuesday, October 1, 2019 4:51 PM
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] Eliding mechanism in 6550

Typo by autocorrection: Before my phone knew better I meant  DIO... So:
I would not compress the identification of the message otherwise a DIO for another DODAG may be confused.
The DODAGID indicates which DODAG this DIO is about, it should not be elided...

Pascal

-----Original Message-----
From: Roll <roll-bounces@ietf.org> On Behalf Of Pascal Thubert (pthubert)
Sent: dimanche 29 septembre 2019 20:47
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] Eliding mechanism in 6550

I would not compress the identification of the message otherwise a FIO for another DODAG me be confused ...


Regards,

Pascal

> Le 30 sept. 2019 à 00:31, Michael Richardson <mcr+ietf@sandelman.ca> a écrit :
>
> 
> Rahul Jadhav <nyrahul@outlook.com> wrote:
>> During the interim Pascal/Michael suggested the use of counter to
>> track the freshness of the Config Option. This could further extend
>> to track MOPex and CAP options freshness.
>
>> The suggestion was to use the reserved bits in the base DIO message for such a counter.
>
> Yup.
>
>> 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?
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
>
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll
_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll
_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll