Skip to content

Issues: mirjak/draft-kuehlewind-updates-tag

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

13 Open 0 Closed
13 Open 0 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Can Proposed Standard update Standard documents?
#21 opened Jul 8, 2024 by mirjak
1
Give more guidance on describing what has changed
#20 opened Jul 8, 2024 by mirjak
How many tags to use?
#16 opened Jul 30, 2021 by mirjak
3
Do we need "see also"?
#15 opened Jul 30, 2021 by mirjak
3
Limit to IETF stream for now?
#14 opened Jul 30, 2021 by mirjak
2
Run this as an experiment or propose as BCP?
#13 opened Jul 30, 2021 by mirjak
4
draft-roach-bis-documents
#12 opened Jul 20, 2021 by larseggert
1
probably need to update RFC 7991
#10 opened Feb 28, 2020 by mirjak
Give examples for amends/extents
#9 opened Dec 2, 2019 by mirjak
Who makes finally judgement of when to apply amends/extends?
#7 opened Aug 22, 2019 by mirjak
How does this apply to different streams?
#6 opened Aug 22, 2019 by mirjak
Given an example on how these tags would apply to informational or process RFCs
#5 opened Aug 22, 2019 by mirjak
Should this document update RFC7322 or do we rather bis the style guide?
#4 opened Aug 22, 2019 by mirjak
ProTip! Type g i on any issue or pull request to go back to the issue listing page.