Re: [Roll] Adopting turnon 8138

Abdussalam Baryun <abdussalambaryun@gmail.com> Mon, 11 November 2019 06:55 UTC

Return-Path: <abdussalambaryun@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 1D4BA12022E for <roll@ietfa.amsl.com>; Sun, 10 Nov 2019 22:55:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, 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 KxsyZ39k1nJW for <roll@ietfa.amsl.com>; Sun, 10 Nov 2019 22:55:09 -0800 (PST)
Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230]) (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 908D812024E for <roll@ietf.org>; Sun, 10 Nov 2019 22:55:09 -0800 (PST)
Received: by mail-oi1-x230.google.com with SMTP id e9so10585640oif.8 for <roll@ietf.org>; Sun, 10 Nov 2019 22:55:09 -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=4PCfeSDdY0DGpnbyWjtYmAFRFaeXPSmpKEELsV+LThI=; b=MtS0KHYKTqsBh1QWmcbjMh7T38QoBkF+TRL2OHNbBbRW8OZE4bYO3GB61d9S46gEZX j1ThqOJPeyri4FjicwbyaJX/0JKEs34AlT42lirUPOY5tz/CsZD8AoLzE6ZByznOds3a nj53pmb87QqWOrESVCk4arBPwkfibRpYyi7LT7+4VNoLD6pEFA11PtgCt1OfrxiOkKxb WUmJ9hSm8n2EmyrIVcn0KOwRxmLxl+0sNNs/NBonkuZa0O1jcCFCimBSBr7c8IHf6MG3 KGJDShU60N/2529+1lwhFh+rkfEDUiYB3Wkhhn7w1DQpNkjSFgRDY63KGfe/1KbakgK/ egfg==
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=4PCfeSDdY0DGpnbyWjtYmAFRFaeXPSmpKEELsV+LThI=; b=OHiTHJxzxw8jVmx5r7B8pdu5cTpezIZEgB95V3MQ7687Tevli5EWw41O9vTjRzDldx T82aspzC9vmZLoaKCRze+v7WgzagiwR+79amzH/XhwXKyheBZWv7Eea5mnTdnBOV7P0v b5SlR4VBYuR8oHJcCgN1k8tAV9cvvILOvBwEfjyKwy7f1lP0PReXHwMgIURKgvG5ys+2 pwvZKbDMCEigvKH7nppxMuMa/KiHOgWpjDgoTfbrd8bS027TfezJEu6+6mRO/qD9/xZT NFMg4v1tyZmIEuRP3rQUyJXaBaujtfl/JPf7sAielJg2aFY5qXVKR2DS7wFxDoORyWJ8 caGw==
X-Gm-Message-State: APjAAAW8jIHtcID+7fOnp1nBydgTowHfJ1nNpgP/9OQrDxwh+agc87mn sEWCM+BisNilL0FhiQ1B1oUcQUnm00UcM9xyR4Ftmg==
X-Google-Smtp-Source: APXvYqyA6SW7zGjIqLxLiwIGyRR28GqPAzF2+S6KtQ0SYpOBBMknHHSuqkXj/u7oYwsVqXgFqG1EzZHEaBlaib/7uZw=
X-Received: by 2002:aca:a8d4:: with SMTP id r203mr5280441oie.12.1573455308748; Sun, 10 Nov 2019 22:55:08 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB3565D8323B4C7860396B2F8DD8610@MN2PR11MB3565.namprd11.prod.outlook.com> <CADnDZ8-p+HiLw9eoq8zKnRh9PqiT4HGYXdg_Cqid=eGQmd=V5g@mail.gmail.com> <CAP+sJUebKNAAEixtJQ-BFTDt3Aq9X2=MvgYJw_NrCrbtd1P3=g@mail.gmail.com> <76EB15DE-5CCD-4088-AE87-FF68436BC267@cisco.com>
In-Reply-To: <76EB15DE-5CCD-4088-AE87-FF68436BC267@cisco.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Mon, 11 Nov 2019 08:54:48 +0200
Message-ID: <CADnDZ885qdYWVfSbykavK5ziXLWCKCDo0yQsyj=3SfhgDnGbbw@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bf7d5005970c9c77"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/h1yKvjoCmFyzj-Qo87FsLwgX4xo>
Subject: Re: [Roll] Adopting turnon 8138
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, 11 Nov 2019 06:55:12 -0000

On Tue, Nov 5, 2019 at 9:31 AM Pascal Thubert (pthubert) <pthubert@cisco.com>
wrote:

> DODAG configuration as it’s name indicates is configuration. The goal is
> to tell dynamically how the protocol is operated as opposed to configuring
> all nodes separately.
>

The draft is not about configuring the DAG, it is for compression, why your
proposal mixes them?

>
> RPL operates in control plane and data plane. It does proactive route
> setup and reactive invalidation. These are all trade offs that are chosen
> to optimize energy and bandwidth efficiency vs. some theoretical perfection.
>

yes, so we need to give RPL more options and alternatives and not use its
few reserved,

>
> The current proposal does not generate any additional transmission.
>

how can we be sure of this if we do not separate functions specially while
RPL is in both data and control planes.

Defining a new protocol to set one bit might appear more perfect but would
> require bandwidth and code footprint that we do not have.
>

I agree but this draft proposed is already a new protocol defined as
standard and updating standards. Updates for protocols can make things very
more complicated.

>
> You are very free to propose an alternate solution with enough details so
> we can understand it, even push a draft, and then the WG will make the best
> of all it sees.
>

We are now trying to understand your proposal and your request to adopt and
to find good solutions, why we are asking for another draft or solutions?

AB



>
> Pascal
>
> ---------- Forwarded message ---------
>
> From: Abdussalam Baryun <abdussalambaryun@gmail.com>
> Date: Fri, Nov 1, 2019 at 11:55 AM
> Subject: Re: [Roll] Adopting turnon 8138
> To: Routing Over Low power and Lossy networks <roll@ietf.org>
>
>
> I don't think it is the right approach, why using the DODAG configuration
> for compression? this compression turn on/off is not for the DODAG
> construction but for packets. I think we should separate configurations of
> the RPL routing standards and of the packet compression standards. We may
> add another configuration option per DODAG or another way.
>
> What do you think?
>
> AB
>
> On Tue, Oct 29, 2019 at 4:34 PM Pascal Thubert (pthubert) <
> pthubert@cisco.com> wrote:
>
>> Dear all
>>
>> *   https://tools.ietf.org/html/draft-thubert-roll-turnon-rfc8138-03
>> <https://tools.ietf.org/html/draft-thubert-roll-turnon-rfc8138-03> is a
>> simple draft that completes RFC 8138 with bits in the config option to
>> enable turning it on in an brown field. There’s no black magic and it would
>> be good to progress it in the background rather than forget it.. Could we
>> consider adoption?   All the best   Pascal *
>>
>>
>>
>>
>> * _______________________________________________ Roll mailing list
>> Roll@ietf.org <Roll@ietf.org> https://www.ietf.org/mailman/listinfo/roll
>> <https://www.ietf.org/mailman/listinfo/roll> *
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>