Thanks Med, That answers me and I will work something into the shepherd write-up.
A -----Original Message----- From: [email protected] <[email protected]> Sent: 18 July 2022 10:28 To: [email protected]; [email protected] Cc: [email protected] Subject: RE: Informative/Normative references in draft-ietf-opsawg-sap Hi Adrian, We are actually following this part from RFC8407: o References -- verify that the references are properly divided between normative and informative references, that RFCs 2119 and 8174 are included as normative references if the terminology defined therein is used in the document, that all references required by the boilerplate are present, that all YANG modules containing imported items are cited as normative references, and that all citations point to the most current RFCs, unless there is a valid reason to do otherwise (for example, it is okay to include an informative reference to a previous version of a specification to help explain a feature included for backward compatibility). Be sure citations for all imported modules are present somewhere in the document text (outside the YANG module). If a YANG module ^^^^^^^^^^^^^^^^ contains reference or "description" statements that refer to an ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I-D, then the I-D is included as an informative reference. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ For the specific example you cited, the initial intent was to provide an informative reference. Cheers, Med > -----Message d'origine----- > De : Adrian Farrel <[email protected]> > Envoyé : dimanche 17 juillet 2022 02:22 > À : [email protected] > Cc : [email protected] > Objet : Informative/Normative references in draft-ietf-opsawg-sap > > Hi there, > > Another question as I work through the shepherd write-up. > > There are some I-Ds that appear as references in the module (i.e., > in Reference clauses). This implies that to understand the object > concerned you _might_ need to read the reference. For example, > > identity sdwan { > base vpn-common:service-type; > description > "PE-based Software-Defined Wide Area Network (SDWAN)."; > reference > "draft-ietf-bess-bgp-sdwan-usage: BGP Usage for SDWAN > Overlay Network"; > } > > But the referenced documents in these cases show up as Informative > References. > > What do we feel about this? > - Are the references just supplying background information or are > they "must read"? > - If we make them Normative References, are we prepared to let the > document wait in the RFC Editor Queue until all of the references > pop out? > > Thanks, > Adrian ____________________________________________________________________________ _____________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
