Skip to content
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

Jump to bottom

Update: if approved does not appear in history tab of the RFC to be updated. #7364

Open
1 task done
paulwouters opened this issue Apr 25, 2024 · 2 comments
Open
1 task done

Update: if approved does not appear in history tab of the RFC to be updated. #7364

paulwouters opened this issue Apr 25, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@paulwouters
Copy link

Describe the issue

Looking at https://datatracker.ietf.org/doc/rfc4880/history/ I don't see in the "RFC part listing" that there is a bis draft being worked on despite draft-ietf-openpgp-cryptorefresh having marked this RFC as "Update if approved"

Code of Conduct
@paulwouters paulwouters added the bug Something isn't working label Apr 25, 2024
@rjsparks
Copy link
Member

And you shouldn't.

The bis may never be approved.

The history of the RFC should NOT show things that might affect the RFC in the future.

If you want the datatracker to make it easy to see that proposed work is underway, we can discuss that. But note that anyone can mark a draft as "Updates if approved", and if you want to pursue this, I encourage restricting any such lists to drafts that are in a stream.

@cabo
Copy link
Collaborator

cabo commented Apr 26, 2024

The bis may never be approved.

Right. To do this properly, the document should be

  • a WG document
  • specifically designated by the WG as a document that should come up for information with the document currently in force.

(This is a bit like the "replaces" relationship, except that it is just a prediction and does not change any status.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests

3 participants
@cabo @rjsparks @paulwouters