Re: [netmod] tree diagram guidelines

Hi All,

I think having the tree-related guidelines in the tree draft and finalizing 6087bis as planned is useful.
That said a NETMOD wiki explaining the available guidelines with pointers can be used as a starting point and would be additionally helpful.

Mehmet

> -----Original Message-----
> From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of Robert
> Wilton
> Sent: Wednesday, November 15, 2017 6:53 PM
> To: Martin Bjorklund <mbj@tail-f.com>; netmod@ietf.org
> Subject: Re: [netmod] tree diagram guidelines
> 
> I liked the suggestion from Chris Hopps:
> 
> I think that it was along the lines of ...
> 
> The RFC contains a reference at the top that states that updates to the
> guidelines is available on a wiki at ....
> 
> Every few years the guidelines on the wiki can be folded into a latest version
> of the guidelines draft.
> 
> 6087bis looks to be 3.5 years old.  Should folks, e.g. at BBF,, IEEE, or MEF be
> using the latest draft guidelines, or should then use the published RFC until
> 6087bis is actually republshed?
> 
> Thanks,
> Rob
> 
> 
> On 15/11/2017 10:14, Martin Bjorklund wrote:
> > Hi,
> >
> > There was a proposal in the meeting today to have the guidelines for
> > tree diagrams in a wiki, instead of having them in 6087bis or in the
> > tree diagram document.
> >
> > Was the proposal really to have a wiki for just the tree guidelines,
> > or was the proposal to withdraw 6087bis from the process and instead
> > publish all guidelines as a wiki?
> >
> > If it is the former, is it really worth it?
> >
> > Advantages with a wiki:
> >
> >    +  It can be updated more easily
> >
> > Some drawbacks:
> >
> >    -  It can be updated more easily
> >       (meaning they are less stable)
> >
> >    -  Wikis tend to not be alive after some time, and are not that
> >       easy to find.  Just try to find the various YANG-related wikis
> >       we've tried to maintain over the years.
> >
> >    -  Links in RFCs also have problems.  Sites are re-orginized etc.
> >       As an example, the link to the security guidelines template in
> >       RFC 6087 doesn't work anymore.
> >
> >    -  People that are looking for a stable reference will have problems
> >       (I think Rob mentioned that IEEE still refer to RFC 6087 (which
> >       is understandable; that's the published version).
> >
> >    -  Who maintains the Wiki, and what are the rules for updating it?
> >
> >
> > I suggest we have the tree-related guidelines (actually just a few
> > sentences) in the tree draft, and since 6087bis already refers to this
> > document it is not a big problem that guidelines are spread out over
> > several documents that are difficult to find.
> >
> >
> >
> > /martin
> >
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> > .
> >
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod