Archive

Re: [6lo] AP-ND 22

Abdussalam Baryun <abdussalambaryun@gmail.com> Mon, 27 April 2020 13:12 UTC

MIME-Version: 1.0
References: <MN2PR11MB3565BD638A8BCEE57216998BD8D00@MN2PR11MB3565.namprd11.prod.outlook.com> <CADnDZ8_0Bms-pGiGnAX6Cz496qhSOaCGNMggpg7fsQM5wn892w@mail.gmail.com> <20200427035234.GR27494@kduck.mit.edu> <CADnDZ89-sJ=rADyY-o8_fxbm-MB3cgmtC86GTXkmzLuf6ww66Q@mail.gmail.com> <MN2PR11MB3565871678BB9669515D194ED8AF0@MN2PR11MB3565.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB3565871678BB9669515D194ED8AF0@MN2PR11MB3565.namprd11.prod.outlook.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Mon, 27 Apr 2020 15:11:51 +0200
Message-ID: <CADnDZ8-Y=77G6xZNhYpBamrFVdeyX7s=_Soud1zCP2nxyOFVCw@mail.gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: Benjamin Kaduk <kaduk@mit.edu>, "6lo-chairs@ietf.org" <6lo-chairs@ietf.org>, "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, Mohit Sethi <mohit.m.sethi@ericsson.com>, Rene Struik <rstruik.ext@gmail.com>, "Shwetha Bhandari (shwethab)" <shwethab@cisco.com>, "6lo@ietf.org" <6lo@ietf.org>, Erik Kline <ek@loon.com>, Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary="00000000000008c36605a44576f4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/gH-tiVtEMLXxARNdr-htL7GHztk>
Subject: Re: [6lo] AP-ND 22
Precedence: list

Hello Pascal,

usually when I read RFCs I like to see the updates and to remind the
readers/users of standards relationships,
I would not like to always have to go to IANA registrations to see their
updates, I want to see IETF updates of their docs.


On Mon, Apr 27, 2020 at 2:32 PM Pascal Thubert (pthubert) <
pthubert@cisco.com> wrote:

> Hello Abdussalam:
>
>
>
> I added the suggested IANA
> https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-22#section-8.4 .
>
> I trust the IESG on the meaning of updating.
>

We all do trust them but just we may give reminders,

>
>
> Stay safe,
>

you too,

best regards

AB



>
>
> Pascal
>
>
>
> *From:* 6lo <6lo-bounces@ietf.org> *On Behalf Of *Abdussalam Baryun
> *Sent:* lundi 27 avril 2020 14:00
> *To:* Benjamin Kaduk <kaduk@mit.edu>
> *Cc:* 6lo-chairs@ietf.org; Pascal Thubert (pthubert) <pthubert=
> 40cisco.com@dmarc.ietf.org>gt;; Mohit Sethi <mohit.m.sethi@ericsson.com>om>;
> Rene Struik <rstruik.ext@gmail.com>om>; Shwetha Bhandari (shwethab) <
> shwethab@cisco.com>gt;; 6lo@ietf.org; Erik Kline <ek@loon.com>om>; Jim Schaad <
> ietf@augustcellars.com>
> *Subject:* Re: [6lo] AP-ND 22
>
>
>
>
>
>
>
> On Mon, Apr 27, 2020 at 5:52 AM Benjamin Kaduk <kaduk@mit.edu> wrote:
>
> On Sun, Apr 26, 2020 at 09:10:33AM +0200, Abdussalam Baryun wrote:
> >   The draft should indicated on top first page that it updates RFC6775,
> > 7400, and 8505, it only shows updating RFC8505.
>
> The 6775 case was discussed extensively during IESG Evaluation.
> Note that 8505 itself Updates 6775, and the changes in this document affect
> only what 8505 does (IIRC).  I'm not sure why you want this document to
> update 7400 -- it seems to just be allocating some bits from the "6LoWPAN
> capability Bits" registry established by 7400.
>
>
>
> IMO it updates section 3.4 in RFC7400, it is not only adding bits, it is
> adding the way of using 6CIO, we would not add bits only to add tasks in
> protocols,
>
>
>
> (Well, it would be if the
> IANA considerations were updated to state that, at least.)  Allocating bits
> from a registry is usually not seen to need an Updates relationship.
>
>
>
> yes IMO it should include also the IANA considerations
>
>
>
> best regards
>
>
>
> AB
>
>
>
>
> -Ben
>
>

[6lo] AP-ND 22 Pascal Thubert (pthubert)
Re: [6lo] AP-ND 22 Pascal Thubert (pthubert)
Re: [6lo] AP-ND 22 Michael Richardson
Re: [6lo] AP-ND 22 Abdussalam Baryun
Re: [6lo] AP-ND 22 Benjamin Kaduk
Re: [6lo] AP-ND 22 Pascal Thubert (pthubert)
Re: [6lo] AP-ND 22 Abdussalam Baryun
Re: [6lo] AP-ND 22 Pascal Thubert (pthubert)
Re: [6lo] AP-ND 22 Abdussalam Baryun
Re: [6lo] AP-ND 22 Abdussalam Baryun