RE: BCP97bis

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Murray,

 

Good idea. You may echo this text from Section 3.9 of RFC8407: 

 

   For every import or include statement that appears in a module
   contained in the specification that identifies a module in a separate
   document, a corresponding normative reference to that document MUST
   appear in the Normative References section.

 

Cheers,

Med

 

De : ietf <ietf-bounces@xxxxxxxx> De la part de Murray S. Kucherawy
Envoyé : lundi 18 octobre 2021 06:56
À : ietf <ietf@xxxxxxxx>
Objet : Re: BCP97bis

 

On Sun, Oct 17, 2021 at 9:52 PM Murray S. Kucherawy <superuser@xxxxxxxxx> wrote:

On Fri, Oct 15, 2021 at 10:12 AM Murray S. Kucherawy <superuser@xxxxxxxxx> wrote:

I've got a draft that seeks to update BCP 97, which is the guidance around how we handle normative downward references.  It's currently made up of three separate RFCs and an erratum, so this will consolidate those into a single document.  The main mission here, though, is to update the guidance around normative references to external documents, especially those behind paywalls.

 

The draft is being sponsored by Erik Kline and can be found in the datatracker here:

[...]

 

I've captured the feedback from several of you so far into -01 of this document, which is now posted.  Please let me know if I messed anything up.

 

It occurs to me that the MIB reference is correct but rather stale by now.  Can anyone dream up a replacement comment about something modern like, say, YANG?

 

-MSK

_________________________________________________________________________________________________________________________

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.

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux