[rfc-i] Next steps for draft-kuehlewind-update-tag

Michael Richardson mcr+ietf at sandelman.ca
Sat Aug 14 08:45:20 PDT 2021


Robert Sparks <rjsparks at nostrum.com> wrote:
    > improvement in clarity can be achieved with prose. For the first
    > experiment, add a "Updates Consideration" near the beginning to any
    > document that might have used the new tags whether it uses the Updates
    > tag or not. Have the IESG ensure there is IETF consensus on what the
    > prose in that section says. If it turns out that the text to put there

I can live with this as a compromise.

I am happy with Extends, Amends and See Also.
If additional terms are needed, then great.
If these don't serve well, then we'll fix them.

--
Michael Richardson <mcr+IETF at sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide




-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20210814/f75f103f/attachment.asc>


More information about the rfc-interest mailing list