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.

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

Reference security.txt as RFC9116 #522

Closed
tschmidtb51 opened this issue Apr 28, 2022 · 2 comments · Fixed by #543
Closed

Reference security.txt as RFC9116 #522

tschmidtb51 opened this issue Apr 28, 2022 · 2 comments · Fixed by #543
Assignees
Labels
CSDPR02_feedback Feedback on CSD02/CSDPR02 editor-revision already worked on in the editor revision non_material Similar to editorial this status is specific to public review editions

Comments

@tschmidtb51
Copy link
Contributor

Situation

It looks like the security.txt got a RFC number assigned. If that is stable, we should refer to that as well.

Proposal

Add a reference to RFC9116.

@tschmidtb51 tschmidtb51 added non_material Similar to editorial this status is specific to public review editions CSDPR02_feedback Feedback on CSD02/CSDPR02 labels Apr 28, 2022
@tschmidtb51
Copy link
Contributor Author

@sthagen Could you please double check on the RFC status?

@sthagen
Copy link
Contributor

sthagen commented Apr 29, 2022

Published: https://www.rfc-editor.org/rfc/rfc9116 I think about two days ago (depending on the timezone one is living in): https://datatracker.ietf.org/doc/rfc9116/

tschmidtb51 added a commit to tschmidtb51/csaf that referenced this issue May 13, 2022
- resolves oasis-tcs#522
- add RFC 9116 in informative references
tschmidtb51 added a commit to tschmidtb51/csaf that referenced this issue May 13, 2022
- resolves oasis-tcs#522
- adopt reference and process status
@tschmidtb51 tschmidtb51 added the editor-revision already worked on in the editor revision label May 13, 2022
This was referenced May 13, 2022
tschmidtb51 added a commit to tschmidtb51/csaf that referenced this issue May 18, 2022
- addresses parts of oasis-tcs#522
- rephrase informative comment about RFC 9116 and status of registration
@tschmidtb51 tschmidtb51 mentioned this issue May 18, 2022
tschmidtb51 added a commit to tschmidtb51/csaf that referenced this issue May 18, 2022
- addresses parts of oasis-tcs#522
- rephrase informative comment about RFC 9116 and status of registration (as discussed during the TC meeting)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CSDPR02_feedback Feedback on CSD02/CSDPR02 editor-revision already worked on in the editor revision non_material Similar to editorial this status is specific to public review editions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants