Hi Carsten, That's more a profiling thing than updating the base spec.
Let's consider an example that you are very familiar with: RFC7252. The core WG published RFC8768 which says "New CoAP proxies MUST implement this option and have it enabled by default" without marking this as updating 7252. What I'm really concerned about is consistent use of the "update" header. Cheers, Med > -----Message d'origine----- > De : Carsten Bormann [mailto:[email protected]] > Envoyé : vendredi 4 juin 2021 08:53 > À : BOUCADAIR Mohamed INNOV/NET <[email protected]> > Cc : Michael Richardson <[email protected]>; [email protected] > Objet : Re: [OPSAWG] please see draft-lear-opsawg-ol on licensing > > On 2021-05-31, at 10:10, [email protected] wrote: > > > > 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. > > This is not a syntactical issue (augment and all that), but a > semantic one: > RFC 8520 is updated with a "SHOULD use this". That is the RFC 8520 > update, not the new module. > > Grüße, Carsten _________________________________________________________________________________________________________________________ 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
