[rfc8659] CAA RR Change references to RFC 6844 to 8659. #1798
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
djc
approved these changes
Oct 13, 2022
djc
reviewed
Oct 14, 2022
darnuria
force-pushed
the
rfc/rfc8659
branch
2 times, most recently
from
9c02787
to
431995c
Compare
|
whops fill fix the links to point to https://tools.ietf.org/ and not datatracker. |
RFC 8659 published in december 2019 fixed errata in 6844.
The Incident Object Description Exchange Format [RFC7970](https://www.rfc-editor.org/rfc/rfc7970)
|
@djc did an auto-review and found some incorrect link, also found that also The Incident Object Description Exchange Format were updated. |
djc
approved these changes
Oct 16, 2022
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
code was written here circa 2017, in 2019 rfc8659 was issued.