Well, anybody can post whatever as an I-D. Probably it is fine to just
ignore this entirely for now. Of if you plan to continue to discuss
this, make sure the author of the I-D is getting involved instead us
speculating about things.

/js

On Wed, Feb 22, 2023 at 12:21:02PM +0000, tom petch wrote:
> From: Jürgen Schönwälder <[email protected]>
> Sent: 22 February 2023 10:34
> 
> Perhaps some bits of history. Back in the SMIv2 world, with a growing
> number of MIB modules, we found it helpful to have a template for
> security considerations. The OPS AD and the SEC AD back then settled
> on an online template for MIB modules (which was occasionally revised
> and updated). This approach was later carried over to YANG and our
> YANG guidelines (RFC 8407, BCB 216) refer to the template using the
> following URL:
> 
> https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines
> 
> What might be happening right now (and here I a speculating) is that
> the IETF considers to retire trac and this may have triggered to copy
> text into an I-D. The reason back in a day to use an online place was
> to be able to make changes easily. Looking back, changes do happen but
> not very frequently, so perhaps even having the template published as
> a small RFC may be workable. (Except that you never know what really
> happens if you want to just make a small change to an RFC.)
> 
> <tp>
> 
> Thanks for that.  The processes with SMI I remember well but had not thought 
> of the retirement of trac.  Any such action would need an update to RFC8407 
> IMHO which the I-D I cited quite ignores.
> 
> Tom Petch
> 
> /js
> 
> On Wed, Feb 22, 2023 at 10:17:01AM +0000, tom petch wrote:
> > From: Kent Watsen <[email protected]>
> > Sent: 21 February 2023 03:34
> >
> > True, that claim seems overstated and one would think that such should be 
> > in NETMOD.
> >
> > Searching OPSAWG, I don't see it.  Can you provide a link?
> >
> > <tp>
> > Do you mean for the I-D?  It is
> >   draft-moriarty-yangsecuritytext-01
> > with no indication that it is intended to touch the sides on any IETF WG.
> >
> > Tom Petch
> >
> > > On Feb 20, 2023, at 12:27 PM, tom petch <[email protected]> wrote:
> > >
> > > I see an I-D has appeared recently with the title
> > >      Security Considerations Template for YANG Module Documents
> > >
> > > It says
> > > " The text has been developed and
> > >   refined over many years on an Operations Area working group mailing
> > >  list"
> > >
> > > Tom Petch
> > > _______________________________________________
> > > netconf mailing list
> > > [email protected]
> > > https://www.ietf.org/mailman/listinfo/netconf
> >
> >
> > _______________________________________________
> > netmod mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/netmod
> 
> --
> Jürgen Schönwälder              Constructor University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>

-- 
Jürgen Schönwälder              Constructor University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to