Re: [Roll] Deprecating DCO status

Rahul Jadhav <rahul.ietf@gmail.com> Wed, 28 October 2020 15:45 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 E82B63A0062; Wed, 28 Oct 2020 08:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 tjWeXiE7NC8a; Wed, 28 Oct 2020 08:45:06 -0700 (PDT)
Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (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 0B8203A005F; Wed, 28 Oct 2020 08:45:06 -0700 (PDT)
Received: by mail-ej1-x62f.google.com with SMTP id gs25so7941983ejb.1; Wed, 28 Oct 2020 08:45:05 -0700 (PDT)
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 :cc:content-transfer-encoding; bh=MX+NJCKGXDM+gm9waZuv0IitfB2jcDLRCqgIgAyOz/o=; b=FIan4s9PHEYh0wDXb/s/b1hnwiYehjJEf19xGqf5oMzPhzmHEh/uYvP7NG+nw5Tn2f FMieJnoAa/231vy9WPMqF4DqFe+dhjMy1cypR6GY4CsAM3t6gTnJRoMXKE+yo+k/3Qjh oTFptW+mMRpoDqFVBb3JnM2XX+qx7qTm8z9kmOdZFRE8kDw9vJkvxDzf1RbvnER9aBKe +5iR+NDEn2k//omm76NUIjBoiWkRnZS/ZFZi0Ik51r6NrkezwL03xoWBlioO0lePvb1H QQwe5zYTthIjkK+QfvdtfldHzwkvZlIOuumIvsx/aIDOFsCRZERzcjoCMTKl6UR2b0lU 1dSg==
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:cc:content-transfer-encoding; bh=MX+NJCKGXDM+gm9waZuv0IitfB2jcDLRCqgIgAyOz/o=; b=o4X2bLV0Fc+H7YF7RSEi3TbfxHqtf3engd09vU21dXG+XeXyKUeyCVOhDb7kdGXUbq hjkF2SKpOorqbHkJnV2eQO/Ql+q9SHDBsqtPS77IK0YSy5E8qgmeTP2+AxZRsBIS8kTv FJWd8sJFP+qWFuGpK+pZzWdK/Rkaus9qXhkNgokVqZ7tFJgV4qDKbCyTMZ9YZl+sSshj XDbK0i7aB+nF1jIIG+qFQJDjEUv2fAvJ56DaL2kFbJUbkU9QBjr53mVkuPg5rXagYX60 w53tYRzsygEFguzYLnvryz1//nTthisGdP1bU6fAtpd3Mp7mTqaNzECoVBWTQ8kML3nH DMmg==
X-Gm-Message-State: AOAM532OR708CIGwyCoqdeYUnS6hrThRzzyhZ1XafboEnC2Vwmf5iO8W QEUXZxFUqxoB8RM6EkOwVM5Azj5gU5+4EoWIenI=
X-Google-Smtp-Source: ABdhPJxzXxen1gUpcY/MB9A/jVR3v7HteZRTKJKcRdR7qquZU29o/8hbKCT529lnUVbHs2aoCpww1+wHs4r9d6NJzO4=
X-Received: by 2002:a17:906:4a98:: with SMTP id x24mr7934056eju.319.1603899904482; Wed, 28 Oct 2020 08:45:04 -0700 (PDT)
MIME-Version: 1.0
References: <CY4PR11MB13521CF8420BF542D94557F4D8170@CY4PR11MB1352.namprd11.prod.outlook.com> <CAO0Djp3Fo7u-iFgNxYKA2264vNXOziP9-WkGxGvng28pbohpmA@mail.gmail.com> <CY4PR11MB135272610279D3EE5D5ED255D8170@CY4PR11MB1352.namprd11.prod.outlook.com> <CAMMESswcVq20TWe89rLzqWeFM4U_FJH9Z2WpWq_j2M-FWCZQ6g@mail.gmail.com>
In-Reply-To: <CAMMESswcVq20TWe89rLzqWeFM4U_FJH9Z2WpWq_j2M-FWCZQ6g@mail.gmail.com>
From: Rahul Jadhav <rahul.ietf@gmail.com>
Date: Wed, 28 Oct 2020 21:14:53 +0530
Message-ID: <CAO0Djp30p9_5Y90-czgjhsA5k=YmxO3bfyJSEF_MEAD3kzrMaQ@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, Pascal Thubert <pascal.thubert@gmail.com>
Cc: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "roll-chairs@ietf.org" <roll-chairs@ietf.org>, Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/mbz0ICZ7ilQ24IXqkKRyRYiFzVE>
Subject: Re: [Roll] Deprecating DCO status
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, 28 Oct 2020 15:45:08 -0000

Thanks, Pascal, Alvaro for the edits.

@Pascal Thubert, Regarding "('E' flag set and 'A' flag not set)", this
may confuse the reader and also may not be relevant for this spec
since it is ok for an implementer to simply use 0/1 as a Status value
without the understanding of E/A flags in unaware-leaves. Can we skip
that part since anyways we are referencing unaware-leaves?

@Alvaro Retana, I will not submit unless explicitly told to do.

Thanks,
Rahul

On Wed, 28 Oct 2020 at 20:47, Alvaro Retana <aretana.ietf@gmail.com> wrote:
>
>
> Hi!
>
> The last part (“This specification adds…”) is not correct, as unaware-leaves is the one defining the value.  Maybe “This specification uses…” would be more appropriate.
>
>
> Rahul:  Please don’t submit anything yet.  Because IANA already created the registry (from the efficient-npdao draft), I want to check with them what is the right thing to do: if we just delete the registry, or if we need to leave it and deprecate it somehow.
>
> Thanks!
>
> Alvaro.
>
> On October 28, 2020 at 11:06:39 AM, Pascal Thubert (pthubert) (pthubert@cisco.com) wrote:
>
> Hello Rahul
>
> I believe that you need to indicate that the status is a RPL Status and refer to section 6.5.1. of RPL " Format of the DAO-ACK Base Object". I'm sure Alvaro will propose an improvement but my knee jerk:
>
> Before:
>
> Status: Indicates the completion status. Section 12.5 of [I-D.ietf-roll-unaware-leaves] defines the status values. A value of 0 is defined as unqualified acceptance. A value of 1 is defined as "No routing-entry for the indicated Target found".
>
> After:
>
> Status: RPL Status indicating the completion. The RPL Status is defined in section 6.5.1. of [RFC 6550] and updated in
> section 6.3 of [I-D.ietf-roll-unaware-leaves]. This specification adds the RPL rejection value ('E' flag set and 'A' flag not set) of 1, defined as "No routing-entry for the indicated Target found".
>
> Works?
>
> Take care;
>
> Pascal
>
>
> > -----Original Message-----
> > From: Rahul Jadhav <rahul.ietf@gmail.com>
> > Sent: mercredi 28 octobre 2020 13:43
> > To: Pascal Thubert (pthubert) <pthubert@cisco.com>
> > Cc: Alvaro Retana <aretana.ietf@gmail.com>om>; roll-chairs@ietf.org; Routing
> > Over Low power and Lossy networks <roll@ietf.org>
> > Subject: Re: Deprecating DCO status
> >
> > Hi Pascal, Alvaro,
> >
> > I am mostly clear on the changes required. Please find attached an HTML-diff
> > for the suggested changes.
> > The only concern for me was if we remove the registry where would the Status
> > 1 indicating "No routing-entry for the indicated Target found".
> > But I see that unaware-leaves has made an update to its IANA section to
> > include this status. So it works.
> > Thus, I am referencing unaware-leaves for Status values.
> >
> > Regards,
> > Rahul
> >
> > On Wed, 28 Oct 2020 at 14:44, Pascal Thubert (pthubert)
> > <pthubert@cisco.com> wrote:
> > >
> > > Hello Rahul:
> > >
> > >
> > >
> > > Attracting your attention on the particular point below in Alvaro’s AD review
> > of unaware leaves:
> > >
> > >
> > >
> > > > > So we should update the NPDAO draft and remove that entry shouldn't
> > we?
> > >
> > > > > Note that NPDAO is already in missref because of this draft
> > >
> > > > > https://www.rfc-editor.org/cluster_info.php?cid=C310
> > >
> > > >
> > >
> > > > Yes.
> > >
> > > >
> > >
> > > > Also, the specification of the DAO-ACK needs to be changed to at
> > > > least make it
> > >
> > > > clear that the "DCO-ACK Status" field refers to the "RPL Status".
> > >
> > > >
> > >
> > > > About deprecating the registry... We should ask IANA what to do:
> > > > they already
> > >
> > > > created the registry, but the efficient-npdao hasn't been published
> > > > as an
> > >
> > > > RFC. I don't know if we just delete §6.2 or if we have to formally
> > > > deprecate the
> > >
> > > > registry (possible in this document).
> > >
> > > >
> > >
> > > > Please ack to this to make sure we're in sync before asking IANA.
> > >
> > >
> > >
> > > The change Alvaro and I want to make in the efficient npdao draft is
> > > that the DCO status is now of the same type as the RPL status in DAO
> > > ACK, and should be specified as such in
> > > https://tools.ietf.org/html/draft-ietf-roll-efficient-npdao-18#section
> > > -4.3.4
> > >
> > > Which means that we do not need the registry that we ask for in
> > > https://tools.ietf.org/html/draft-ietf-roll-efficient-npdao-18#page-17
> > >
> > >
> > >
> > > Do you agree?
> > >
> > >
> > >
> > > Keep safe!
> > >
> > >
> > >
> > > Pascal
> > >
> > >