Hi Michael, Actually, there is no established practice for those.
If so, every extension (including modules with augment) would be tagged as updating their base RFC...while this is not the case. There are plenty examples out there. Cheers, Med > -----Message d'origine----- > De : Michael Richardson [mailto:[email protected]] > Envoyé : samedi 29 mai 2021 00:13 > À : BOUCADAIR Mohamed TGI/OLN <[email protected]> > Cc : Eliot Lear <[email protected]>; [email protected] > Objet : Re: [OPSAWG] please see draft-lear-opsawg-ol on licensing > > > <[email protected]> wrote: > > Agree it extends, but unless I'm mistaken we don’t have yet > those tags > > (draft-kuehlewind-update-tag). > > They are all variations of "Updates" > _________________________________________________________________________________________________________________________ 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
