[auth] swap CIMD SSRF wording for IETF draft reference#1840
Merged
Conversation
pcarleton
changed the title
localden
approved these changes
Nov 20, 2025
localden
added
the
rc-high-priority
pcarleton
deleted the
pcarleton/cimd-reference-draft-security-considerations
branch
github-project-automation
bot
moved this from In review
to Done
in 2025-11-25 Implementation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation and Context
In #1296 it came up that the wording around SSRF was a bit ambiguous. Since there is also a section in the IETF draft that covers that, it seems better to reference those and not re-state it in the spec. If we want additional concerns to be flagged, it seems better to include those in the IETF draft.
How Has This Been Tested?
n/a
Breaking Changes
no
Types of changes
Checklist
Additional context