Hi Ruediger, Thank you for your reply!
Regarding: >> 5) This document contains sourcecode: >> >> * Does the sourcecode validate? >> * Some sourcecode types (e.g., YANG) require certain references and/or text >> in the Security Considerations section. Is this information correct? >> * Is the sourcecode type indicated in the XML? (see information about >> sourcecode types). > > [Authors]: Yes, the data structures and source code have been validated and > tested. There are no known security considerations with regard to the code > snippets. The sourcecode type has been indicated in the text with the > following reference: [C-Prog] > ISO/IEC, "ISO/IEC 9899:1999 Programming languages - C", 1999. However, the > actual snippets simply use the <CODE BEGINS>...<CODE ENDS> identifiers > instead of <sourcecode type="c">...</sourcecode>, is this acceptable? > There's no standard YANG model which the authors are aware of (and none was > mentioned during review). While it is acceptable to leave the type attribute empty, it sounds like the type would be "c", which is on our list: https://www.rfc-editor.org/rpc/wiki/doku.php?id=sourcecode-types May we update the sourcecode elements to type="c"? Or are there certain figures that should be labeled type="c", and others that should be given a different type (if so, please indicate that)? Sincerely, Sarah Tarrant RFC Production Center > On Sep 22, 2025, at 9:22 AM, <[email protected]> > <[email protected]> wrote: > > Ruediger -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
