fix: state the nesting depth requirement at a single strength#80
Open
liady wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Fixes #68.
The nesting depth requirement appeared at two strength levels: Organizing Catalogs said clients SHOULD impose a maximum depth, while Security Considerations said they MUST. ADR 0001 records the decision as SHOULD/RECOMMENDED, "to allow flexibility for edge cases while establishing a clear norm".
This softens the Security Considerations sentence to SHOULD so both spec sections match the recorded decision. If the group later decides DoS protection warrants a hard MUST here, that should go through an ADR 0001 update and change both sections together.