Re: [netmod] Long trees RE: Next steps for draft-ietf-netmod-rfc8407bis

2024-03-05 Thread Xufeng Liu
Hi Med and all, Sorry that I would not agree with the proposed text, especially the following: "If the complete tree diagram is too long (more than 5 pages, typically) even with groupings unexpanded (Section 2.2 of [RFC8340]), the authors SHOULD NOT include it in the document. A s

Re: [netmod] Long trees RE: Next steps for draft-ietf-netmod-rfc8407bis

2024-03-05 Thread Andy Bierman
On Tue, Mar 5, 2024 at 1:47 PM Kent Watsen wrote: > In addition to improving IETF-published artifacts, it would be nice if > there were a module-browser that acted a little bit like an IDE, jumping to > where in other modules imported bits are defined. Perhaps in > NetconfCentral or YANG Catalog

Re: [netmod] Long trees RE: Next steps for draft-ietf-netmod-rfc8407bis

2024-03-05 Thread Kent Watsen
In addition to improving IETF-published artifacts, it would be nice if there were a module-browser that acted a little bit like an IDE, jumping to where in other modules imported bits are defined. Perhaps in NetconfCentral or YANG Catalog. This jumping behavior could exist in both the text and

Re: [netmod] On prefixes RE: Next steps for draft-ietf-netmod-rfc8407bis

2024-03-05 Thread Andy Bierman
On Tue, Mar 5, 2024 at 1:39 AM Jürgen Schönwälder wrote: > Hi Med, > > I believe it is a misconception that text not written in capital letters > is not normative. I also believe we need _guidelines_ on the choice of > identifiers like prefixes and not hard rules. > > Prefixes do not have to be u

Re: [netmod] Long trees RE: Next steps for draft-ietf-netmod-rfc8407bis

2024-03-05 Thread Italo Busi
I like the idea of relying on tooling with hyperlinks For txt and pdf, I agree that a link is the best option since these formats are not optimized for including YANG trees Italo From: Kent Watsen Sent: martedì 5 marzo 2024 16:02 To: mohamed.boucad...@orange.com Cc: Italo Busi ; Qin Wu ; Mahes

Re: [netmod] Long trees RE: Next steps for draft-ietf-netmod-rfc8407bis

2024-03-05 Thread Kent Watsen
It seems that there are two camps: 1) those that want the tree-diagrams to be as DRY as possible 2) those that want the tree-diagrams to be as WET as possible DRY = Don't Repeat Yourself WET = Write Every Time Tooling can help both cases. For (1)

Re: [netmod] On prefixes RE: Next steps for draft-ietf-netmod-rfc8407bis

2024-03-05 Thread Per Andersson (perander)
Hi! Jürgen Schönwälder on Tuesday, March 5, 2024 10:38: > I believe it is a misconception that text not written in capital letters > is not normative. Indeed. RFC 8174 Section 2. Clarifying Capitalization of Key Words states: In many IETF documents, several words, when they are in all capi

Re: [netmod] On prefixes RE: Next steps for draft-ietf-netmod-rfc8407bis

2024-03-05 Thread Jürgen Schönwälder
Hi Med, I believe it is a misconception that text not written in capital letters is not normative. I also believe we need _guidelines_ on the choice of identifiers like prefixes and not hard rules. Prefixes do not have to be unique. It is nice if they are for widely used modules, but we are on a

Re: [netmod] On prefixes RE: Next steps for draft-ietf-netmod-rfc8407bis

2024-03-05 Thread mohamed . boucadair
Hi Jürgen, Please see inline. Cheers, Med > -Message d'origine- > De : netmod De la part de Jürgen Schönwälder > Envoyé : lundi 4 mars 2024 20:44 > À : netmod@ietf.org > Objet : Re: [netmod] On prefixes RE: Next steps for draft-ietf-netmod- > rfc8407bis > > Hi, > > the statement "sh

Re: [netmod] Long trees RE: Next steps for draft-ietf-netmod-rfc8407bis

2024-03-05 Thread mohamed . boucadair
Hi Italo, Thanks for sharing your thoughts. Please see inline. Cheers, Med De : Italo Busi Envoyé : lundi 4 mars 2024 19:38 À : Qin Wu ; Mahesh Jethanandani ; BOUCADAIR Mohamed INNOV/NET Cc : netmod@ietf.org Objet : RE: [netmod] Long trees RE: Next steps for draft-ietf-netmod-rfc8407bis Hi