Re: [Roll] Add ROVR in DAO?

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 26 August 2019 09:25 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 ED232120121 for <roll@ietfa.amsl.com>; Mon, 26 Aug 2019 02:25:10 -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=UIrkWVyi; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=BzcBaGkF
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 wm2wf2_ViyW3 for <roll@ietfa.amsl.com>; Mon, 26 Aug 2019 02:25:09 -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 28A41120119 for <roll@ietf.org>; Mon, 26 Aug 2019 02:25:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1470; q=dns/txt; s=iport; t=1566811509; x=1568021109; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=7fbcyCd45m1mCj4fAjqty3JPq/VAeqj6CNli7f/i/vM=; b=UIrkWVyiI9R+wryc8tJnhSEkPFPedXwUlc2ndt5CqHK4SnKOnihKYxlU K0OVBnhUVwUsuUYXP1HBLQxLGMqpBcsT8F3jdHyTxr5iPLlxnzlgQgSQV 4gg87TctcP30ZldJP/YodQSqdAc1wb99NFM6KGP1x1NLz0O6NmTz7zwf+ U=;
IronPort-PHdr: 9a23:mfHYGxGeRxkCS/IGUUjRzJ1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4z1Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+eeb2bzEwEd5efFRk5Hq8d0NSHZW2ag==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CuAQAzpWNd/4oNJK1kHAEBAQQBAQcEAQGBVgQBAQsBgURQA4FDIAQLKodoA4ptTYIPl2iCUgNUCQEBAQwBAS0CAQGEPwKCZyM3Bg4CCgEBBAEBAQIBBgRthS0MhUoBAQEEEi4BATgLBAIBCBEEAQEBLjIdCAEBBBMIGoRrAx0BApwqAoE4iGGCJYJ7AQEFhH4YghYJgTQBi3EYgUA/gRFGUYF7PoQoHoM7giaMIIkQlj4JAoIelF6YT6YOAgQCBAUCDgEBBYFmIoFYcBWDJ4JCg3KKU3KBKY4GAQE
X-IronPort-AV: E=Sophos;i="5.64,431,1559520000"; d="scan'208";a="313770132"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Aug 2019 09:25:07 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x7Q9P7fx031374 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Mon, 26 Aug 2019 09:25:07 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 26 Aug 2019 04:25:07 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 26 Aug 2019 05:25:06 -0400
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 26 Aug 2019 05:25:06 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gnCITyaV+jewlkTFSHKvecCXIWaLou6WBTbLmtE5OYPJV0y35yjJV6i3yzQ3/5RUWL9qPxcXAooplZoUX7t2XohK+L2uZIK+4kwztgJnIzRAykd9RivpssZCnL9uof6m8G3XUfnNOtTpid3L2iwIiy66+RYYKgTzXDdCQLWvqfL0kI/ZnvOdpXVT5IlDkWDs8fzy6r/1/HtKxmFLQF3TDeaWnJE7t87n3NdRGQPlLxDNoVH3nuCLMGB2OedB1D2pcgJgT/QY28xhewDEKV3aEdpGxs0oPq8RFDo1x9fN0CdmYR13spOOedLSIa9+W0HXpFZSsa4ZbC9kCyNk6ym24Q==
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=szdWzT2VMVgP51KRiboeOctZaio2LscJmAGmFecFleQ=; b=HaozA543+3YIIc0HiqYXVymU6qQtjI1ielpUiGkgNgOOT8YPwoJrXegT0rAwjdU9If9byuG/cSjCjmZYeV4cqAdWL/6jfCGLAjfmmkTcqcdGPrEJLMXAevs5rTEsOWh8WHEYhFUQMTJJ62HsPc8zBakMm6jqXOyVQLVkMjZUZbh3tY2Bw/Mr4dSOAps4DgepOsQEGHzGW/yA7XIm0bpTQGaHNrivPtrNvH6W4ZiAuRVp6anjR9lB22Dda2KmMga2Zzj0PRK3FkAyQn+6seCl/AwQAIo1Yh4ENewKYrJ48OCDKG+qX3tdhNMwUCC5eh2yZIS9/gvWoJ96HWTOe2rkZw==
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=szdWzT2VMVgP51KRiboeOctZaio2LscJmAGmFecFleQ=; b=BzcBaGkFYfIaEC9fNEhDp/6be9MrtFp7gq21+P6v5ceZ8leFLu6rXrkDSi1Z2XqOEn+xnvTCqAfgKoqOyT8a1wK7a+uJVi8oI8PBcafdXK2BwoI83r7qpNA9PZsYr/j6AUuyPb+M7/JBlpM7IMoErPACpwPfUvthwwvyRc65Qxw=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3567.namprd11.prod.outlook.com (20.178.251.95) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2199.21; Mon, 26 Aug 2019 09:25:04 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::89cf:9d:8a75:266e]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::89cf:9d:8a75:266e%3]) with mapi id 15.20.2199.021; Mon, 26 Aug 2019 09:25:04 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] Add ROVR in DAO?
Thread-Index: AdVCahRZPRQ6beNIQb+VlVo9l/YWKAXLCFRQAB+Y+O4AddG70A==
Date: Mon, 26 Aug 2019 09:24:49 +0000
Deferred-Delivery: Mon, 26 Aug 2019 08:56:52 +0000
Message-ID: <MN2PR11MB356577CAA0C95F3293DBA373D8A10@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <MN2PR11MB35652CCE7A961CD581EDE47DD8C60@MN2PR11MB3565.namprd11.prod.outlook.com> <MN2PR11MB35653048AE54B21CCF055031D8A40@MN2PR11MB3565.namprd11.prod.outlook.com> <982B626E107E334DBE601D979F31785C5DFB6CBE@BLREML503-MBX.china.huawei.com> <24307.1566607218@localhost>
In-Reply-To: <24307.1566607218@localhost>
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: [2001:420:c0c0:1003::f7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fa3d9ced-8536-40f3-2a6c-08d72a074782
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600166)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR11MB3567;
x-ms-traffictypediagnostic: MN2PR11MB3567:
x-microsoft-antispam-prvs: <MN2PR11MB3567940721D492229489AC4DD8A10@MN2PR11MB3567.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01415BB535
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(396003)(39860400002)(376002)(366004)(199004)(189003)(13464003)(2906002)(478600001)(14454004)(11346002)(446003)(7736002)(86362001)(476003)(486006)(99286004)(76176011)(7696005)(74316002)(6116002)(33656002)(305945005)(186003)(46003)(102836004)(316002)(229853002)(6506007)(53546011)(6916009)(25786009)(71190400001)(71200400001)(256004)(66446008)(81156014)(66946007)(6246003)(76116006)(66556008)(66476007)(64756008)(81166006)(8676002)(55016002)(5660300002)(9686003)(53936002)(52536014)(6666004)(8936002)(6436002)(66574012); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3567; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: uJF1vvlrrApyHvM98kpekIU26AKwtThM/6/I5/UMCBPROicRzF2dR4NJo22H2weWvBl5APqzPM9wgClisSbdgM61n+OO77zFgs9ZhilC+QH3+dUBl0wz8rn3/j3bSTm+jiIw7ToKMXi0zlYv/VmJcm0XLn0SvzkMfNawLjzG55FqtxAu+hGkhdSZ0YG30HBnmGnV2XBUzEL2KC2LOaxXfKybu2TYx3GuHKgqCQE/WU+226W//GxwGZtqjhc9PsTrSSk6IJMqZ0UmiTQ4rrvZ0daVmLCiVUqw1LlWajv4r1WdGvhaTht+uAVASY1D0D55OLaWDdF5lzW+61CSdYRfaUO8iHVdGBGczuh0h7kLYiGTIEKldtbQz7ew208ai8ll0p4aHFuZxgN4I1ej587IH6Omg1wLGkIN8Kqoo6/EH0I=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: fa3d9ced-8536-40f3-2a6c-08d72a074782
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Aug 2019 09:25:04.7495 (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: 7GsCCuyH6c7Vcvy7FhppJnf0UZ70sWiZyII3DGirjJ4NCiNgqmfRfg4BlEETeo3Wv6oAhKUckx6GpUbKPVqX+g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3567
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.17, xch-aln-007.cisco.com
X-Outbound-Node: alln-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/JMTlTKj2FQVTJQTIJxELMYPEQQw>
Subject: Re: [Roll] Add ROVR in DAO?
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, 26 Aug 2019 09:25:11 -0000

> -----Original Message-----
> From: Roll <roll-bounces@ietf.org> On Behalf Of Michael Richardson
> Sent: samedi 24 août 2019 02:40
> To: Routing Over Low power and Lossy networks <roll@ietf.org>
> Subject: Re: [Roll] Add ROVR in DAO?
> 
> 
> Rahul Arvind Jadhav <rahul.jadhav@huawei.com> wrote:
>     > 1.       Remove the ROVR generation on the 6LBR on behalf of the 6LN.
>     > 2.       Use the ROVR from NS(EARO) directly in the DAO.
>     > 3.       This would eliminate Keep-Alive EDAR/EDAC during initial/first
> registration.
>     > 4.       This would eliminate the need for root node to set all ones in
>     > the ROVR field of keep-alive EDAR.
>     > This seems optimal.
> 
>     > But there is one downside if the DAO is used for such purpose; Adding a
>     > 64-bit ROVR field in DAO would mean that in storing MOP all the parents
>     > maintain the ROVR field in their routing table. This is an immense
>     > overhead, since it impacts the routing entry size even if the RPL
>     > network needs to support just a single RUL.
> 
> So, ideally, the RUL or 6LR would send some keepalives with the ROVR directly
> to the 6LBR even in storing mode.  Maybe not in DAOs.

Well, that's what we want to avoid, 2 keep alive messages all the way across the LLN when one could suffice.
In that case I'd rather live with a DAR with no ROVR the duplication of efforts.

All the best,

Pascal