IETF Logo Mail Archive

Re: [Roll] MOPex CAPs splitup

rabi narayan sahoo <rabinarayans0828@gmail.com> Wed, 20 November 2019 02:57 UTC

Return-Path: <rabinarayans0828@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 763791201E0 for <roll@ietfa.amsl.com>; Tue, 19 Nov 2019 18:57:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 6fHI7_U27I2A for <roll@ietfa.amsl.com>; Tue, 19 Nov 2019 18:57:49 -0800 (PST)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 139BA1200B8 for <roll@ietf.org>; Tue, 19 Nov 2019 18:57:49 -0800 (PST)
Received: by mail-io1-xd2d.google.com with SMTP id s3so25933752ioe.3 for <roll@ietf.org>; Tue, 19 Nov 2019 18:57:49 -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=mSQHV0afwe+ULIarCh6GpYsgyxTtki7tuXlLGJa/GI0=; b=S7tP4RDbG0gpuYa0hRho8O3qjwrBZJeyI2z3kc5EPwMgi46jssE7WrE6YY62iW1+iB 9Q0MRxonywaczqv7F6ho69jw3e45mcuibWEb5mPXhcm4YIjDjAbdC78hD1gLGadPQhmZ Klh6rznJ5d4ycRRsSXG0eOVGizxNY9TFvnRj3jSolSM/w81gyeH9Uagz4dzMOWwDwi/t ETOZpAx1Kb2YH8tQpYAzsV5aEyCbIZOmqXqM4T0jGA/obDAYpJbmgPwAY/iJhh3RvX8O 8zIugtmIh6i0rmaGegXcA4W2M31lkTI3LqBQV3NQfH4zl4iYofC5IdvHdZJbbIeep/IB 7ypw==
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=mSQHV0afwe+ULIarCh6GpYsgyxTtki7tuXlLGJa/GI0=; b=HXq82M+SouqNtZyacjxqqwIESfzAyQFAvL09IJhrHSBZKyVtBUIogtbpE2EmtgVtaT SnQjsMupptU6bJhrXUQm5sPqJFgg/CM6GxFTqBusfaY/ba7cE+RFxJvjYIaJVDNxhJ8U xKOpQmvNyKV/1/yfZg2RxEoTEg5ghWsFCJjcMrLc/6tmeJbRyWh3Qqf+2KOEiaAZhCqk wpAgUNeWsVGLRDnf5YXF5JwBiecEN56KnTvvg9fcTGnTFeJ570OLQmKGeKJM3qj4b/UL hNYQ8IdNcBgp1XMVlr+5aUbSI+DWJbTY5zhc9oPKtPijK0EqHOrh88GECusahguho69A R1xA==
X-Gm-Message-State: APjAAAW/aWvRXYT4Bxgn/UiDQL1GoooftK0abSPZ+cnIwVZ/xUTJIRFl BO71p3vbMwhujWs5ljCiYkVPmk4Bq6ESMBpvlKv171GB
X-Google-Smtp-Source: APXvYqymXZfTE80aNST03DqhU+IL8gl28NF9jawmlG4dtZMbX2iOIJZGS+iicm77zqs55lmlTmXcYX6MTDfHFriYapM=
X-Received: by 2002:a6b:f60f:: with SMTP id n15mr199835ioh.263.1574218668152; Tue, 19 Nov 2019 18:57:48 -0800 (PST)
MIME-Version: 1.0
References: <CAO0Djp20PRZnzTO4pU0KPmiCPcdEiitJYLdoLWOmOkgj6-vzmA@mail.gmail.com>
In-Reply-To: <CAO0Djp20PRZnzTO4pU0KPmiCPcdEiitJYLdoLWOmOkgj6-vzmA@mail.gmail.com>
From: rabi narayan sahoo <rabinarayans0828@gmail.com>
Date: Wed, 20 Nov 2019 08:27:36 +0530
Message-ID: <CAPT0++2LCS-_qLu7J23R7-08G27OazkcKjE99urnaBnU2z7GXQ@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000839aac0597be5869"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/zkbpdPqOxZ-7kC6UkS4dWiOWCPE>
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: Wed, 20 Nov 2019 02:57:50 -0000

I am Sorry  i was unable to attend the sessions remotely.
I do agree with the split. MOPEx and Capabilities should be two separate
draft.
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 a 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
through out the network and which shouldn't.

Thanks
Rabi

On Tue, Nov 19, 2019 at 4:16 PM Rahul Jadhav <rahul.ietf@gmail.com> wrote:

> Hello All,
>
> During IETF106 we discussed splitting up MOPex and capabilities,
> reasons have been:
> 1. MOPex and capabilities are not dependent on each other
> 2. Capabilities draft may take a while for WGLC, while MOPex can be
> shipped sooner.
>
> Please let us know of your opinions.
>
> The following is the link for the separated draft.
> https://datatracker.ietf.org/doc/draft-jadhav-roll-mopex/
>
> Reviews are highly appreciated.
>
> Thanks,
> Rahul
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>

v2.23.0 | Report a Bug | By Email