I have posted about the issues around normative language in imagery over on
rfc-interest so that we can have a wider discussion there. I tried to sum
up this thread, hopefully i represented everyone's input in at least a
general way:
https://mailarchive.ietf.org/arch/msg/rfc-interest/QKmVJB0bzREMBq1A8w4kNf4Gvr8/

On Tue, May 13, 2025 at 1:46 PM Brian E Carpenter <
brian.e.carpen...@gmail.com> wrote:

> On 14-May-25 03:15, Michael Richardson wrote:
> >
> > Alexis Rossi <alexisrossir...@gmail.com> wrote:
> >      > NEW
> >      > "SVGs may be included in RFCs to help explain a concept more
> clearly, but
> >      > should not be the only representation of that concept. Normative
> >      > descriptions of concepts - which might include protocols,
> formats, or
> >      > system architectures - should be fully represented in the text of
> the RFC
> >      > whenever possible, and should not be contingent on comprehension
> of any
> >      > SVG."
> >
> > Suggestion:
> >
> > } "SVGs, like other diagrams, may be included in RFCs to help explain a
> concept more clearly, but
> >      > should not be the only representation of that concept. Normative
> >      > descriptions of concepts - which might include protocols,
> formats, or
> >      > system architectures - should be fully represented in the text of
> the RFC
> >      > whenever possible, and should not be contingent on comprehension
> of any
> > } diagram."
> >
> > That may go too far for this document, and might not clearly have IETF
> > Consensus (for IETF Stream documents!).  My reading of this thread is
> that
> > this statement was already true, just not well communicated.
>
> Unfortunately, RFC 2360/BCP 22 almost implies the opposite, since only
> packet diagrams are mentioned in its "Document Checklist". But the RSWG
> isn't paid to fix IETF process documents.
>
>     Brian
>
> >
> > --
> > Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
> >   -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*
> >
> >
> >
> >
>
> --
> rswg mailing list -- rswg@rfc-editor.org
> To unsubscribe send an email to rswg-le...@rfc-editor.org
>
-- 
rswg mailing list -- rswg@rfc-editor.org
To unsubscribe send an email to rswg-le...@rfc-editor.org

Reply via email to