Re: [Roll] MOPex CAPs splitup

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 21 November 2019 02:56 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 C56CB1207FF for <roll@ietfa.amsl.com>; Wed, 20 Nov 2019 18:56:41 -0800 (PST)
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=MjKlIyFH; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=J2Wo56dt
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 XngvafisWH9t for <roll@ietfa.amsl.com>; Wed, 20 Nov 2019 18:56:40 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB16B1200E5 for <roll@ietf.org>; Wed, 20 Nov 2019 18:56:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7602; q=dns/txt; s=iport; t=1574304999; x=1575514599; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=BI0gS0VmholFm9vws3idiNaSMTbsz13aQRkVB0VoNz8=; b=MjKlIyFHdkxMUSC6ONxipkU3YcbHIsVZTXFQ7gBv29wCSDZXc7L8EBbE 69o20mm8u8Kyd7eJZllF9arRw+ggMio+hkIdzo4gZd01kbss4qF5hWCb4 JURRZbrLhtYyqGIdTGKGyxZ90Y9TS2yRORfhhRcZibQUC4CX2LOcRdoB2 Q=;
IronPort-PHdr: 9a23:4yU+cB9/Rm4vTf9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+8ZR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVdaZCVDxIeT2Ryc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ALEQBe/NVd/4kNJK1bChwBAQEBAQcBAREBBAQBAYF+gRwvUAVsWCAECyoKhCCDRgOKbE6CEJMehGKCUgNUCQEBAQwBASMKAgEBhEACF4IQJDgTAgMNAQEEAQEBAgEFBG2FNwyFUQEBAQECARIRChMBATgECwIBCBEEAQErAgICMB0IAgQTCBqDAYF5TQMOHwEBAgyjRAKBOIhgdYEygn4BAQWFCBiCFwMGgTaMFhiBQD+BV4JMPoJiAoE2Dx4rgmMygiyQFYVImFUKgiuHGo5QmhSXAJFUAgQCBAUCDgEBBYFpIoFYcBWDJ1ARFIZGg3OKU3SBKI5/AYEOAQE
X-IronPort-AV: E=Sophos;i="5.69,224,1571702400"; d="scan'208,217";a="580599708"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 Nov 2019 02:56:38 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id xAL2ucqF030738 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Thu, 21 Nov 2019 02:56:38 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 20 Nov 2019 20:56:38 -0600
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 20 Nov 2019 20:56:37 -0600
Received: from NAM01-SN1-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; Wed, 20 Nov 2019 21:56:37 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=m83qTOiNQcA80BgcpwnAdnGNG9Z+zrjjHYqXISHu2xciZL66wgNHtldbUAKsO8WFymNlrr3CERM9/OqMQLJkEIr+E9DRfSqMTf1ZHaVbOqqlTcKUUL7G96i2/bpZV/5+KudWvYqtRsIWUqUDpuezmp7MPE2DYoYGfIbtst5GNw+aJbXHwPSz4z2HYNfxT03F2vTpmqPj3elamATlNzYNj3CZQAgUkqB4UaX+PUIaG7Q759d/kJ7Gw/OlRSIm//9Wa+k6f9BVpOvqETIXH6wj54ZDjdvzkkAxevBH1kVgEbr3FfHqTavZ7XDD3yOMOTIbx4YDnfeO66LmDpYgSy3zfg==
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=BI0gS0VmholFm9vws3idiNaSMTbsz13aQRkVB0VoNz8=; b=fw711bNzS5VcFxk3JTFlmt/mm/snvZXHUwpXuQ4Ia/pZ3Dxgj3yfKP78aXhxBbetiZoT3hsf4hktsBrzzVemimxwEfDSvUTbtSkaO0U/mR8ogZPsU0gzUe2wlZRsZrRQMF/fLB5yqxcWw4GJKP6UawUgjgx52ZP45PPq5MmoBbfg/lT9zm1UYO3TSmKvV1AYcbGIIguzxdMx2ldU2l9XM5jMy6d1AatsZzVRgJfPUQt+1uf34zXcNCkIzx+RN+eDEcuTEcmn6bepg3xIzunbP9W2/eb0UE9P/WUrkp30gdVEib/rmnjvTRqNG4jsHWGajSopF3qi3JzrtjgIDvd9/Q==
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=BI0gS0VmholFm9vws3idiNaSMTbsz13aQRkVB0VoNz8=; b=J2Wo56dtmQkB8TaQJ0KAOZaXV99DkzhhRDJlILqysgI8jYyYjEUAMYAdVwXsnUG19wRy18PWria6zPw63ehNmkciGfmzZYmQGL7N8A766SDIQvxv95vV/S9nhfijXRCKad5U2XMBFSMhF8zMTClXCz2rqi+ehlLS4LA+L4JDwBs=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3646.namprd11.prod.outlook.com (20.178.253.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2451.28; Thu, 21 Nov 2019 02:56:35 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::3037:66f1:dc79:b564]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::3037:66f1:dc79:b564%7]) with mapi id 15.20.2451.031; Thu, 21 Nov 2019 02:56:35 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] MOPex CAPs splitup
Thread-Index: AQHVn05D0V9PcGqXBUez+F8bVM/zJaeU5uIAgAAIAiA=
Date: Thu, 21 Nov 2019 02:56:22 +0000
Deferred-Delivery: Thu, 21 Nov 2019 02:55:45 +0000
Message-ID: <MN2PR11MB35654BEA3757C3F383C11A1AD84E0@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <CAO0Djp20PRZnzTO4pU0KPmiCPcdEiitJYLdoLWOmOkgj6-vzmA@mail.gmail.com> <CAPT0++2LCS-_qLu7J23R7-08G27OazkcKjE99urnaBnU2z7GXQ@mail.gmail.com> <CAO0Djp0Z6pgAyNaZwbShwpqHfT5ayAERr8XGY+oTFOCrH5cPoQ@mail.gmail.com>
In-Reply-To: <CAO0Djp0Z6pgAyNaZwbShwpqHfT5ayAERr8XGY+oTFOCrH5cPoQ@mail.gmail.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: [101.100.166.67]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 45aa2ac4-9e39-489d-4742-08d76e2e6c26
x-ms-traffictypediagnostic: MN2PR11MB3646:
x-microsoft-antispam-prvs: <MN2PR11MB3646E5EEA4AA8056B509C665D84E0@MN2PR11MB3646.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0228DDDDD7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(346002)(396003)(376002)(39860400002)(199004)(189003)(81156014)(64756008)(81166006)(8936002)(52536014)(7736002)(2906002)(186003)(53546011)(6506007)(316002)(6116002)(66066001)(476003)(71200400001)(76176011)(6666004)(7696005)(71190400001)(229853002)(9686003)(6436002)(606006)(6306002)(54896002)(256004)(55016002)(236005)(11346002)(446003)(486006)(74316002)(33656002)(66556008)(6916009)(26005)(66476007)(790700001)(14454004)(86362001)(66946007)(102836004)(3846002)(25786009)(5660300002)(6246003)(76116006)(99286004)(478600001)(66446008)(8676002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3646; 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: BCL:0;
x-microsoft-antispam-message-info: Cvv/C8+MODjfDyEG9Cc52ha1MRCRqd8gnXZooM6TXw57+mUZtElNQrj4u3eiFDXKAofiLgXmiq8c1ZETnlG816wcp748ajOw5ZVM3lyeck+siKmnjTF+3r7gAvCmsEm8CntSQMk2crTtDm6cyJEdymleU6XnSWxp3fpxs+NZLW3rqFkMsXfmV2llSk1FvdZNudU4HIGrdk4l2tu1KS6ZWt3zGVB+ihdDj1vTDCZCij5tsDpZ1b9o4PL0L7B7SlsMDYE7FNJY2Io/YBQrxScehDtHXqZv6Mgi//0vmFMeIxj1OTTDdkA6evifdwreKNYuLz68gjebNNGASaxq8LsgUjMiFusqVsIQpYojcm9MN0FL7HDJQ6V98+5DcT/gKMtcCou7Y/umo6FNIe0qj0Z6DbkRIVDq7AaoY794iYtSsk28s79NeamLnbYQgpVlWAY+
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB35654BEA3757C3F383C11A1AD84E0MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 45aa2ac4-9e39-489d-4742-08d76e2e6c26
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Nov 2019 02:56:35.6514 (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: zj8+BtBnvekBnaeDLsZhTpe1mtPdetwihGnnXt0jLuSUn9SAen3+38ykO4ywD5VLw/eUdeiUnYcZRkBchDo3TQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3646
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/huSgsDyDFwMF8cgvv6fByxXhwu8>
Subject: Re: [Roll] MOPex CAPs splitup
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: Thu, 21 Nov 2019 02:56:42 -0000

Agreed as well. Basically there will be a parent local pull and a global pull. The multicast address of all children of  apparent might be useful there.

From: Roll <roll-bounces@ietf.org> On Behalf Of Rahul Jadhav
Sent: jeudi 21 novembre 2019 10:24
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] MOPex CAPs splitup




> For capabilities i have a suggestion. We can split the capabilities into two different categories.
> 1-- Network Capabilities (Global) . Capabilities, those all nodes in the network need to support to act as an LR. Ex support of SRH Compression
> 2-- Node Specific capabilities (Local). Ex. NBR Cache size, route table size, DAO Projection, etc
>
> This will help us to identify which capabilities should be disseminated throughout the network and which shouldn't..
>

Thanks, Rabi for the suggestion. And yes you are right, Global vs local differentiation needs to be done and the eliding-dio-information draft already has differentiated handling for global cap option. The same needs to be clarified in the cap-draft.
Would it be possible for you to propose the text for the cap-draft as you see fit as a PR on GitHub repo?
I have added an issue<https://github.com/roll-wg/Capabilities/issues/5> in GitHub repo for this.