IETF Logo Mail Archive

Re: [Roll] MOPex CAPs splitup

Rahul Jadhav <rahul.ietf@gmail.com> Thu, 21 November 2019 02:24 UTC

Return-Path: <rahul.ietf@gmail.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 8D7FF12090C for <roll@ietfa.amsl.com>; Wed, 20 Nov 2019 18:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level:
X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Pz2RGisNXwk1 for <roll@ietfa.amsl.com>; Wed, 20 Nov 2019 18:24:19 -0800 (PST)
Received: from mail-vk1-xa32.google.com (mail-vk1-xa32.google.com [IPv6:2607:f8b0:4864:20::a32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16102120950 for <roll@ietf.org>; Wed, 20 Nov 2019 18:24:19 -0800 (PST)
Received: by mail-vk1-xa32.google.com with SMTP id l5so360737vkb.4 for <roll@ietf.org>; Wed, 20 Nov 2019 18:24:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=8OVDJ+ABUpjV9omA+qRTE4T28MJZBBkEj7K3vZukM7k=; b=FoXFWiRyErCzaIRd9W7Fls/mo4vOPpzOmxttLNZku1vErSBkjOcCgi8pEVAMmEevjc afJ0oPAWIVk3XJDCN6Kqm1alpazsyBui2WZillrwFr6ruHLSxQI31DGMsQeZ8Jl9n7Tw DohTUGg/itNn14FTmiLx3/ngctm6r+PIibTXKBwFUt/W268ZhZR4EuCAFXxIN3Uy4ZpC ZllaqBmLEUsp1rmDgoGMyEgTNacBqF8ZEiNIRHqrfaoBoJTWnM+nnzs21pWzij2GUeHz S5J5ixW1mNRAIFCjB0Pxpfbn20AGJ2C6lPAqgopeXyP3s7kAD1g+0z5+qAJNQ6++NFao il9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=8OVDJ+ABUpjV9omA+qRTE4T28MJZBBkEj7K3vZukM7k=; b=WpCgkon7TUMmQCTn/QFyDGk/HfcUXrSmlC4xV5zwov99iCPd+AUstmGNqBJieDlEuE GZWV2x3JmSP/EkhOMauHwB8LfhCk9jiMEQDnX7NUC+C92U04LuzeU6+6stu55Pye4X1c Pha62XTMurE5PppWhwc8rHqZGo8b9SU7FHRhjnCxzLK37Q0wchYMQt6YsG8EnTMdKDmz 5SQc0jBWS+OQC86mF9OuhllE32rvYbovTMIckCGYv9RFLiu9GPoEyau2rqILLz6abHaS uA1OZpXMQLfrbyLKg1PeckID4yfQOF2UYMnoEycE2j5+QZ+At3S4sZeoaFM9BBi6AkLK Rcpw==
X-Gm-Message-State: APjAAAUOKTh6kVJG5J6ImgU8Kv0qC1Le/mRMmcYYoZwjmYdlccCkuGTz qyA+SxXJqGCD9cq/eFa3Vs9zF6qcfWFA87Gibe36ebLTxm0=
X-Google-Smtp-Source: APXvYqyy8EaFuca1XwQpzAsfulEP6L2VM6CJEOs1UuXfhQLvef69onOrCyqtOwqt6nb3prFdIrOE0g6XnkLBF0roAjc=
X-Received: by 2002:a1f:2b0f:: with SMTP id r15mr3893172vkr.91.1574303057972; Wed, 20 Nov 2019 18:24:17 -0800 (PST)
MIME-Version: 1.0
References: <CAO0Djp20PRZnzTO4pU0KPmiCPcdEiitJYLdoLWOmOkgj6-vzmA@mail.gmail.com> <CAPT0++2LCS-_qLu7J23R7-08G27OazkcKjE99urnaBnU2z7GXQ@mail.gmail.com>
In-Reply-To: <CAPT0++2LCS-_qLu7J23R7-08G27OazkcKjE99urnaBnU2z7GXQ@mail.gmail.com>
From: Rahul Jadhav <rahul.ietf@gmail.com>
Date: Thu, 21 Nov 2019 10:24:06 +0800
Message-ID: <CAO0Djp0Z6pgAyNaZwbShwpqHfT5ayAERr8XGY+oTFOCrH5cPoQ@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008a11a20597d1fe7f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/GkkBZIvfeNeyp7LwTiAn9V3h_WM>
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:24:21 -0000

> 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.

v2.23.0 | Report a Bug | By Email