Re: [v6ops] draft-linkova-v6ops-nd-cache-init to working group draft

On Tue, Jul 23, 2019 at 9:39 PM Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> 3) I'm not convinced it needs to update 4861. If what it does is explain the conditions in which an RFC2119 "SHOULD" should be ignored, that is *not* an update to the standard. To me it sounds exactly like a Best Current Practice.

That's was my impression  as well, glad to see I'm not alone ;)

"SHOULD NOT This phrase, or the phrase "NOT RECOMMENDED" mean that
   there may exist valid reasons in particular circumstances when the
   particular behavior is acceptable or even useful, but the full
   implications should be understood and the case carefully weighed
   before implementing any behavior described with this label."

So I guess as long as we document the case and implications,
recommending routers to have a configuration knob to ignore "SHOULD"
is not violating RFC4861.
Probably getting the document reviewed by 6man WG would make sense as
well to ensure that implications are understood.

> On 23-Jul-19 20:29, Fred Baker wrote:
> > In yesterday's meeting, the sense of the room and a discussion of charters at the mike suggested that draft-linkova-v6ops-nd-cache-init should become a working group draft. Doing so will require 6man to agree to let v6ops suggest specific changes to RFC 4861 under the rubric of "operational solutions", as discussed in the draft and https://datatracker.ietf.org/meeting/105/materials/slides-105-v6ops-neighbor-cache-entries-on-first-hop-routers-operational-considerations-00; the argument for not kicking those out to 6man is that the authors of RFC 4861 are no longer in a position to approve errata to it, which would be the other obvious approach (I'm not sure that's true of Erik Nordmark, but whatever). It would also need to be considered to update RFC 4861.
> >
> > Do we agree to take draft-linkova-v6ops-nd-cache-init as a working group draft?
> >
> > Ron and I look through this thread next week and take the necessary action, whatever the outcome might be.
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> > .
> >
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

-- 
SY, Jen Linkova aka Furry