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

Error code example MUST not be normative #25

Open
SteveLasker opened this issue Aug 6, 2024 · 3 comments
Open

Error code example MUST not be normative #25

SteveLasker opened this issue Aug 6, 2024 · 3 comments
Assignees
@aj-stein-nist
Labels
pending-close

Comments

@SteveLasker
Copy link
Collaborator 

          I like the guidance we are giving in this area, but we use an example to define the specific error to return.  

As an example, submitting a Signed Statement with an unsupported signature algorithm **would** return a 400 Bad Request status code and the following body:

Must it be 400 or is that a suggestion?

Originally posted by @roywill in #2 (comment)
@SteveLasker SteveLasker mentioned this issue Aug 6, 2024
Closed
@aj-stein-nist
Copy link
Contributor

I can pick this one up per discussion in an editors' meeting.

@SteveLasker
Copy link
Collaborator Author

ping @aj-stein-nist for some 👀

aj-stein added a commit to aj-stein/draft-ietf-scitt-scrapi that referenced this issue Nov 2, 2024
@aj-stein
Use normative language for error code per ietf-wg-scitt#25
e7747a4
SteveLasker added a commit that referenced this issue Dec 3, 2024
@aj-stein @SteveLasker
Use normative language for error code per #25 (#37)
e7751b5 
* Use normative language for error code per #25
* Update draft-ietf-scitt-scrapi.md
---------

Co-authored-by: Steve Lasker <[email protected]>
@SteveLasker
Copy link
Collaborator Author

@roywill, @aj-stein can you see if #51 addresses this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aj-stein-nist aj-stein-nist

Labels
pending-close
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SteveLasker @aj-stein-nist