IETF Logo Mail Archive

Re: [Roll] Add ROVR in DAO?

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 23 August 2019 09:43 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 4D2B1120132 for <roll@ietfa.amsl.com>; Fri, 23 Aug 2019 02:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, URIBL_BLOCKED=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=QHrwrLgi; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=AhiFNYIU
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 jA4Xy5GDvt9A for <roll@ietfa.amsl.com>; Fri, 23 Aug 2019 02:43:28 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A335120115 for <roll@ietf.org>; Fri, 23 Aug 2019 02:43:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7244; q=dns/txt; s=iport; t=1566553407; x=1567763007; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=1AzAdrcBzjBy8i9y2XosBz86uBIevobtAAyPQ1S17EY=; b=QHrwrLgiYKQMXGDVcLZ7qK0ErDcUGzOzrDIzbXsz1tASlXPKZaC3ISBx omqYuIRrklyeTmLypqg/eAPoimrIQqxqz4NhIw1Z4V/SE4l6tdNtewCDj IcotIYFYi9QYZX3phgwvuAxetIEG+jX7VOSOEzu0+Z3uBrsaUnuwwyfCY w=;
IronPort-PHdr: 9a23:ZZp7shO2EtwydgspjUwl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu6w/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBjjMP73ZSEgAOxJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AJAABqtF9d/51dJa1kGgEBAQEBAgEBAQEHAgEBAQGBUwUBAQEBCwGBFS8kLANtViAECyqHZwOEUoYbglyQB4MCA4JaggGBLhSBEANUCQEBAQwBASUIAgEBhD8CgmUjNAkOAgoBAQQBAQMBBgRthS0MhUoBAQEBAxILEBMBATgPAgEIEQQBAS8yHQgBAQQTCBqDAYEdTQMdAQIMn3oCgTiIYYIlgnsBAQWFIRiCFgMGgTQBi24YgUA/gRFGgkw+gmEBAQIBgSYcHiuDEIImlCmXPAkCgh2GaocThl2CMocwjmqVSYxbg1gCBAIEBQIOAQEFgVA4gVhwFYMngkKDcoUUhT9yAYEoiyABAQ
X-IronPort-AV: E=Sophos;i="5.64,420,1559520000"; d="scan'208,217";a="619985629"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Aug 2019 09:43:26 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x7N9hQJw014037 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Fri, 23 Aug 2019 09:43:26 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 23 Aug 2019 04:43:26 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 23 Aug 2019 05:43:25 -0400
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 23 Aug 2019 04:43:25 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MhX+6A4sML62WT1E5YyFd4czbBEP7zPROW0P3s4TUT/VaE04HjgZ0Lf55uUpGxoeVX3hrI8Sd18KvnIWQ/N9M85DFOFYycZRZjkswq3lzLixu4RpKylNRtGGaubC2uE3oR9fvDnijzidXrD6iQYGdtawaNINto93tmp4YnbN+F9Rp6FddB0q/5IHnnoqlreNe6XG0S9YCTwsZY2F+Td7SRiPvXZD/Aju0wi4g94lBwoMXaQJwQZ68UppwOriD94oYR4YHh0lVtyHVvbAW4ERfhvgn5BxnkIfxFniPEwU4kWpBX1ut9VICbMc4QsOsLRb7sweI3yDSN6/uWpEnHQDLQ==
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=bjuKwJmmWKXqgbnJlpAt46jhEfHQbYEBsaD5DzXR6IM=; b=GLdFvUqa7+jt29OlabtNYbasGXKjEe0vLLdA9crHAF87HBW/tC+NvHxr04ldIXoeqrzI4SyZclvWj7bwGPGgfxzRaWdw5YRk6hOraVxCflINp/UPbmcA7py1+bsgbmXXugEx3xbQ+HBp7rVS3ul/HLB3rpuJlqchMp3oV3aC8BwwnfN+O68Kz0p/E+KmlWANLV7MSJhpHYuNROJa24qIEOTKVdU8U6stpiJ7/ZDgqX7BNsjfYfFIVGerOru1CXyA+3nHwDmqoNzYMU5CvwaKSU+L1IHyxnxMJQCxhycuwt+98VnCTxozud1ILfd3WVcSHl6i9GnzGdSBmEb3IZovaQ==
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=bjuKwJmmWKXqgbnJlpAt46jhEfHQbYEBsaD5DzXR6IM=; b=AhiFNYIUISIYpwwgFStL/yMMAn0sCJi3bwdX/IUjZKIlh1ygoiQ9/WVLBzsZGyXFowM7neBWmijhUcNkznY/cxvT8LifFQ0+XaaRmSXQ+YZ3+dQQbCz7MKf96aIHsK37fWVa7kv3ygzxmcS0rtyFY+6M9pT7CRGTqMz7tegFbgE=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3789.namprd11.prod.outlook.com (20.178.252.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2178.19; Fri, 23 Aug 2019 09:43:23 +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.2178.020; Fri, 23 Aug 2019 09:43:23 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: Add ROVR in DAO?
Thread-Index: AdVCahRZPRQ6beNIQb+VlVo9l/YWKAXLCFRQ
Date: Fri, 23 Aug 2019 09:43:16 +0000
Deferred-Delivery: Fri, 23 Aug 2019 09:42:19 +0000
Message-ID: <MN2PR11MB35653048AE54B21CCF055031D8A40@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <MN2PR11MB35652CCE7A961CD581EDE47DD8C60@MN2PR11MB3565.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB35652CCE7A961CD581EDE47DD8C60@MN2PR11MB3565.namprd11.prod.outlook.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: [2001:420:c0c0:1007::143]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e6aeec17-da7d-4b01-f9e2-08d727ae574f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3789;
x-ms-traffictypediagnostic: MN2PR11MB3789:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <MN2PR11MB37896F658609C27B6AD840D5D8A40@MN2PR11MB3789.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0138CD935C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(136003)(396003)(346002)(376002)(366004)(199004)(189003)(7736002)(606006)(66476007)(76116006)(53936002)(66946007)(66556008)(64756008)(66446008)(46003)(6246003)(33656002)(446003)(11346002)(229853002)(486006)(476003)(186003)(74316002)(86362001)(71200400001)(14444005)(71190400001)(256004)(6666004)(790700001)(6116002)(6916009)(2906002)(14454004)(8676002)(81156014)(81166006)(3480700005)(76176011)(7696005)(316002)(966005)(8936002)(478600001)(99286004)(53546011)(6506007)(102836004)(52536014)(5660300002)(25786009)(6306002)(9686003)(55016002)(6436002)(54896002)(236005); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3789; 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: QJx9mIz19zY2ZaU0mC50WxvdofH+poBSp1sz0rMcpFBShfDQcXenYM0EZbspjuIfOaxGeR6+lN88ii6E9a9BHHyzssOVaTqVlu9f0IZSNJYsYDtG4pryjZVe1v/U+ZVECqn8LuCgCt66fMB0cpZ4O/WYWQa4i+6NKIk8cCMizfMWaGonLsKAsR1WeUMueNFBUUGDAFFMklzyKX1wXB+AI8JOZZlur98mqW/9eOB2sHX5FptrfZj3XdgeHCrUDfp/tnIafw8jQB+QSRI+lJEXIAlFDK4FHFSIlXc+kxXMM8JuXFiQLhZoy2nsNuW2Kvu1tGbC06C+QgPHDIYmnr6BVYA3XNC2xF7VwDze7ovxS0GjySedRRH0nNWnZL7cXZHRxJQ8R9dHHpSzQc67FacQ2PHef7SPeqXDLSDq9R7g3Cs=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB35653048AE54B21CCF055031D8A40MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e6aeec17-da7d-4b01-f9e2-08d727ae574f
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Aug 2019 09:43:23.7307 (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: ic320HH1UWVGmrzHVJ1brTxrFrE1boAutOUYq7z8pm/VCBU8qQnEch0kphJ3zyknDnAacKTFuwQJC6JF9eWIYA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3789
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.16, xch-aln-006.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/tcZbWlUm4YqBF6Yf0gdsxunQ5tc>
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: Fri, 23 Aug 2019 09:43:30 -0000

Dear all

As noted below, and discussed at the WG meeting at IETF 105, it would be good to convey the ROVR field in the DAO, so if the Root and the 6LBR are different entities then the root can build a full EDAR as opposed to the dummy one.
It will also help make RPL more secure in the future. So I'm calling to confirm the discussion in Montreal and if there is no opposition I'll go ahead and propose a new option that can be placed with the DAO to transport a ROVR.
We'll also need something in the configuration option to trigger its use.

Comments and any hint on how to do that right are welcome.

All the best;

Pascal

From: Roll <roll-bounces@ietf.org> On Behalf Of Pascal Thubert (pthubert)
Sent: mercredi 24 juillet 2019 23:54
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: [Roll] Add ROVR in DAO?

Dear all

The only change I foresee in the unaware leaves draft is the addition of the RFC 8505 ROVR from the ND EARO into the DAO. After that I'd feel ready to call for WGLC.

The proposed change enables to build a full EDAR message at the root, and avoids the weird processing of the keep-alive EDAR (see https://tools.ietf.org/html/draft-ietf-roll-unaware-leaves-02#section-7.4)
If we do it now we can forget that weird format (all ones ROVR) and never code for it. This may also be useful when we work on securing the DAO using the AP ND proof of ownership all the way to the root..

Please let me know if there's disagreement to make that change

All the best

Pascal

v2.23.0 | Report a Bug | By Email