Skip to content

Issues: ietf-wg-scitt/draft-ietf-scitt-scrapi

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

25 Open 4 Closed
25 Open 4 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Do we really need 2.2.7 Request Nonce?
#47 opened Nov 5, 2024 by JAG-UK
Clarify scope of Resolve Issuer
#46 opened Nov 5, 2024 by JAG-UK
1
Minimally viable /.well-known/transparency-configuration CDDL for TS configruation?
#45 opened Nov 4, 2024 by aj-stein
3
Remove 'ResolveStatement' and associated IDs/references
#44 opened Nov 3, 2024 by JAG-UK
1
Problems with example register signed statement
#43 opened Nov 3, 2024 by JAG-UK
Clarify CLIENT AuthZ/AuthN early in doc
#42 opened Nov 3, 2024 by JAG-UK
Nothing to hold TS to account
#41 opened Nov 3, 2024 by JAG-UK
Keys in configuration example have no stated purpose
#40 opened Nov 3, 2024 by JAG-UK
1
Introduction and body are inconsistent about what is mandatory and what is optional
#39 opened Nov 3, 2024 by JAG-UK
Mixed JSON and CBOR is annoying for clients
#36 opened Oct 24, 2024 by JAG-UK
9
Capture a set of requirements that have must, should
#34 opened Aug 27, 2024 by SteveLasker
Add support for multiple notaries
#33 opened Aug 27, 2024 by SteveLasker
1
Replace all encoded protected headers with better examples
#32 opened Aug 20, 2024 by OR13
@henkbirkholz
2
Error code example MUST not be normative
#25 opened Aug 6, 2024 by SteveLasker
@aj-stein-nist
2
2.2.1 Issue Signed Statement.
#24 opened Jul 25, 2024 by roywill
@JAG-UK
2
2.1.2 Registration is Running
#23 opened Jul 25, 2024 by roywill
1
@JAG-UK
2
2.1.2.2 Registration is running.
#22 opened Jul 25, 2024 by roywill
@JAG-UK
2
2.1.2 Fresh receipts may be requested through the resource identified in the Location header.
#21 opened Jul 25, 2024 by roywill
@roywill
1
2.1.2 The identifier definitions are not clearly describing what it is meant to solve.
#20 opened Jul 25, 2024 by roywill
@roywill
1
2.1.1 & 2.1.2 Missing intent statements.
#18 opened Jul 15, 2024 by mkhraisha
@JAG-UK
1
2.2.4 Resolve Receipt encourages authentication
#14 opened Jun 23, 2024 by robinbryce
@JAG-UK
4
2.1.2.2 Status 202 requires the resolve receipts endpoint to do double duty
#13 opened Jun 23, 2024 by robinbryce
@JAG-UK
1
async registration policy checking apears disallowed by 2.1.2
#12 opened Jun 23, 2024 by robinbryce
@SteveLasker @JAG-UK
1
Workflow and details for signed-statement/issue
#10 opened May 23, 2024 by SteveLasker
@JAG-UK
1
API for Collections of Statements
#9 opened May 21, 2024 by SteveLasker
@JAG-UK
4
ProTip! Exclude everything labeled bug with -label:bug.