IETF Logo Mail Archive

Re: [Roll] Eliding mechanism in 6550

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 01 October 2019 16:52 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 121C112022D for <roll@ietfa.amsl.com>; Tue, 1 Oct 2019 09:52:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=JNzZsd+v; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=BVhHtrW7
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 aDQAeyhU6BKW for <roll@ietfa.amsl.com>; Tue, 1 Oct 2019 09:52:23 -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 B77151200DB for <roll@ietf.org>; Tue, 1 Oct 2019 09:51:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2796; q=dns/txt; s=iport; t=1569948699; x=1571158299; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=lxnbWKZvZuohbcWVz3qKEWWlhFqNZOfGE4sPgTBGWEI=; b=JNzZsd+vdivQCIvYo73ZVpNIWy+1+6VoXIFbFoLw6Dh1V7Fpooeb5vkX vosNra5bLve/RudTUPEcTMBf0SPFjGaJM+IfAgICpj4uvJoEJnteDe1lW +v1SDD6vCd93AmFBi4aYJwrTJbg2dK59mBDnCeZjrcV0TbOqD4vTNAMn8 Q=;
IronPort-PHdr: 9a23:NihvExT8Ddepn385f9ge/gunC9psv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESXBNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOjQmHNlIWUV513q6KkNSXs35Yg6arw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AcAADUgpNd/4MNJK1mGgEBAQEBAgEBAQEMAgEBAQGBVQMBAQEBCwGBSlADbVYgBAsqCoQYg0cDil9Ngg+Xd4EugSQDVAkBAQEMAQEYCwoCAQGBTIJ0AheCGCM2Bw4CAwkBAQQBAQECAQUEbYUtDIVLAQEBAQIBAQEQEREMAQEsDAQHBAIBCBEEAQEBAgImAgICJQsVCAgCBBMIGoJ7BAKBagMODwECDKRtAoE4iGF1gTKCfQEBBYUEGIIXAwaBDCgBjA0YgUA/gVeCTD6CYQEBgUUegwsygiaMfoJpnUIKgiKVLJk5p0wCBAIEBQIOAQEFgVkELg2BS3AVO4JsUBAUgU8JGoNQhRSFP3SBKY8vAYEiAQE
X-IronPort-AV: E=Sophos;i="5.64,571,1559520000"; d="scan'208";a="342634660"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Oct 2019 16:51:38 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x91GpcFt031420 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Tue, 1 Oct 2019 16:51:38 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 1 Oct 2019 11:51:38 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 1 Oct 2019 11:51:36 -0500
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 1 Oct 2019 11:51:36 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Fy/iy9H4rTr+m4tYmsHPqhYFZqVYbBqcLHg5TP1kqskJhlAtrdPw/E2FDzVNsBkKUUVMldCKHSMJsOTugAa24cSDU9uvYvxoV2RbBsu8+koV9azAjHEGO2Kx88Ewpr9A1Nyklhbh68HtNgKKGZ4FTlVbkWRS2hNYde+5jNst03e+zdD3NW9QzfggYEUSMOplkIxlAr5g0uMAO2Q6FH8VXq9SkX5prXGo+LUjl9KVdS744A7FkdNYSP02lZ5V3mH8BeYClgLiD/jOiBi7M4/p7gpC2onHqOFrIJCC1fPu+GVnNRDMDByOMgwvYDew12UXCzMEjdNB2IaNU0aBDEfyUw==
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=lxnbWKZvZuohbcWVz3qKEWWlhFqNZOfGE4sPgTBGWEI=; b=eP1yF0u85W+wRan3nslaQAzyhaaqvEZRsfsPATT549+MTL4OOVCSIQWmqimBuMgEbiQ0GUf3rRiC+RX8AD8KlUEbQvEcTRmI/Az8JwFrru7pstKIIIiRy0uQjzTPdjMMxWoH/BZDiKTrUuJVXx64TYpDIFnOftUEcJs2fFXaX8kie/WnyMFGEkKOPn2iC5+SsLfC0R6VvT0njkGj5WVa0t8WaZT7SHKpZ6or+3gZ1HdBw4kgegrhol/410z3J9LwqzPipuAXQTgq+Mk0tYfQZ+9VS/e5oDwmtw+as1EKpWWh7Bdu5IlSixSZVufaxOzsJmjvjZ3mB2BIYo7p/WVkvQ==
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=lxnbWKZvZuohbcWVz3qKEWWlhFqNZOfGE4sPgTBGWEI=; b=BVhHtrW7Pujysm4xUPwgaFkIzF/uj/QfigjluJbXYeCBP9apl9k80SAGpqGkkIUGHFwZcPxcDOQLoYvh4FZ+UTZlFKENwf0X7WZLCueljCMvz+U3fbffjF4EOvZmVzTv1aL4HspYWFzCLrtMBG8hf4sBs7fljP8zpHP0lns6pk8=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3790.namprd11.prod.outlook.com (20.178.253.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.20; Tue, 1 Oct 2019 16:51:36 +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.2305.017; Tue, 1 Oct 2019 16:51:36 +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: AQHVdxWYTfJkX2vtREOJsDxTaX1EB6dDlT6AgAJTGzA=
Date: Tue, 01 Oct 2019 16:51:11 +0000
Deferred-Delivery: Tue, 1 Oct 2019 15:19:45 +0000
Message-ID: <MN2PR11MB35651A3D6FA6CC1B7CEDC41AD89D0@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <28599.1569796250@localhost> <5DBFE23C-9388-4FF3-949C-13846F68AF7C@cisco.com>
In-Reply-To: <5DBFE23C-9388-4FF3-949C-13846F68AF7C@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [128.107.241.185]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8ef907aa-8ab8-4c16-41c8-08d7468f9f2e
x-ms-traffictypediagnostic: MN2PR11MB3790:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR11MB37903C0A7D2D6F5CAEBFFC65D89D0@MN2PR11MB3790.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0177904E6B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(376002)(136003)(346002)(366004)(396003)(13464003)(189003)(199004)(33656002)(6666004)(53546011)(71190400001)(66574012)(6916009)(71200400001)(81166006)(8676002)(6116002)(476003)(6506007)(66066001)(7696005)(486006)(11346002)(6246003)(446003)(3846002)(25786009)(186003)(102836004)(26005)(76176011)(81156014)(74316002)(5660300002)(66556008)(66476007)(66946007)(64756008)(229853002)(66446008)(316002)(55016002)(99286004)(7736002)(6306002)(2906002)(8936002)(966005)(478600001)(14444005)(256004)(9686003)(305945005)(6436002)(86362001)(14454004)(52536014)(76116006); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3790; 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: 7zoVqtV9sZPKVNegy98i2nMcNO0KlQWWJtrzKnM9b8DX08ENOIyNS8m0KZEwP4Qd+YK48wRtEFPJRW+ocT23uQ/pItrOA5Nl4+LaA0A4ec7bSTgcGOMbgbBIsWxRdgbfUV5OKQkG7O8XcJC9ZSrARm4CM82/kRsGmVeRjQAAKl8SP3mMcrVqrTnxwO4DLNCshAbJeTFoLFrpsuZgGXZy2VyU9w2HCuCwypCcsZdi66TK+2Lcz+y6HZztioigyQinoH0Gna5cq+uMuCmhdx8+BAQfCPFNlEGYGygAS45uiPlHHDncYuAwqlqaoDCcqWSf4vgSd0RklRoJijetXjnYIscFGHY+Tsu/fJR2ZryyNAVu3CHoVI0Pk2VbRWlkp6IUQO51pUbHMhYn5FTEaEcK9DeGiXyxgavzK52FG3trMlP/Vw/E1GiXq72O85Pzx3kMvLa0j34kPFX4uT5O8SQe7w==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 8ef907aa-8ab8-4c16-41c8-08d7468f9f2e
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Oct 2019 16:51:35.9092 (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: sdK1Kp6B0VSl3b0VVIP+RjHWnijG5UM4sQJkcrRDd1hq0UO8w4u149c70JuU9yEHHdziudVPXGy8impkYRVjWg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3790
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/oCNeP2p9pnxhS6FzEkQxTY3YTAM>
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: Tue, 01 Oct 2019 16:52:26 -0000

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

v2.23.0 | Report a Bug | By Email