issues
search
ietf-wg-scitt
/
draft-ietf-scitt-scrapi
Transparency Service REST API
https://datatracker.ietf.org/doc/draft-ietf-scitt-scrapi/
Other
2
stars
6
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
change roles
#48
OR13
closed
6 days ago
0
Do we really need 2.2.7 Request Nonce?
#47
JAG-UK
opened
1 week ago
0
Clarify scope of Resolve Issuer
#46
JAG-UK
opened
1 week ago
1
Minimally viable `/.well-known/transparency-configuration` CDDL for TS configruation?
#45
aj-stein
opened
2 weeks ago
3
Remove 'ResolveStatement' and associated IDs/references
#44
JAG-UK
opened
2 weeks ago
1
Problems with example register signed statement
#43
JAG-UK
opened
2 weeks ago
0
Clarify CLIENT AuthZ/AuthN early in doc
#42
JAG-UK
opened
2 weeks ago
0
Nothing to hold TS to account
#41
JAG-UK
opened
2 weeks ago
0
Keys in configuration example have no stated purpose
#40
JAG-UK
opened
2 weeks ago
1
Introduction and body are inconsistent about what is mandatory and what is optional
#39
JAG-UK
opened
2 weeks ago
0
First tranche of CBOR All The Things
#38
JAG-UK
opened
2 weeks ago
0
Use normative language for error code per #25
#37
aj-stein
opened
2 weeks ago
1
Mixed JSON and CBOR is annoying for clients
#36
JAG-UK
opened
3 weeks ago
9
Add 'chck operation' endpoint
#35
JAG-UK
closed
2 weeks ago
6
Capture a set of requirements that have must, should
#34
SteveLasker
opened
2 months ago
0
Add support for multiple notaries
#33
SteveLasker
opened
2 months ago
1
Replace all encoded protected headers with better examples
#32
OR13
opened
3 months ago
2
Add exchange receipt
#31
OR13
closed
2 months ago
0
Change signed statement example
#30
OR13
closed
2 months ago
0
Remove DID Resolution Resource
#29
OR13
closed
2 months ago
0
Clarify intent statements for mandatory endpoints
#28
JAG-UK
closed
3 months ago
0
Extra detail on polling for in-progress receipts
#27
JAG-UK
closed
3 months ago
0
Clarify need (or not) for authentication on Regsiter Signed Statement
#26
JAG-UK
closed
3 months ago
0
Error code example MUST not be normative
#25
SteveLasker
opened
3 months ago
2
2.2.1 Issue Signed Statement.
#24
roywill
opened
3 months ago
2
2.1.2 Registration is Running
#23
roywill
opened
3 months ago
2
2.1.2.2 Registration is running.
#22
roywill
opened
3 months ago
2
2.1.2 Fresh receipts may be requested through the resource identified in the Location header.
#21
roywill
opened
3 months ago
1
2.1.2 The identifier definitions are not clearly describing what it is meant to solve.
#20
roywill
opened
3 months ago
1
2.1.2 Signed Statement Registration MUST implement authentication.
#19
roywill
closed
3 months ago
2
2.1.1 & 2.1.2 Missing intent statements.
#18
mkhraisha
opened
4 months ago
1
Fixes for idnits
#17
SteveLasker
closed
4 months ago
0
Shorten text for IETF tools/formatting
#16
SteveLasker
closed
4 months ago
0
reference and markdown fixes
#15
SteveLasker
closed
4 months ago
0
2.2.4 Resolve Receipt encourages authentication
#14
robinbryce
opened
4 months ago
4
2.1.2.2 Status 202 requires the resolve receipts endpoint to do double duty
#13
robinbryce
opened
4 months ago
1
async registration policy checking apears disallowed by 2.1.2
#12
robinbryce
opened
4 months ago
1
Update API Heading to Sign-Statement
#11
SteveLasker
closed
5 months ago
0
Workflow and details for signed-statement/issue
#10
SteveLasker
opened
5 months ago
1
API for Collections of Statements
#9
SteveLasker
opened
6 months ago
4
Spelling errors and markdown nits
#8
SteveLasker
closed
6 months ago
0
Remove deprecated reference to Decentralized Identifiers
#7
SteveLasker
closed
5 months ago
3
Spelling and Markdown Nits
#6
SteveLasker
closed
8 months ago
0
Add Security Considerations consistent with RFC 3552
#5
JAG-UK
closed
8 months ago
1
Test suite
#4
aj-stein-nist
closed
4 months ago
2
Add GS1 examples
#3
OR13
closed
4 months ago
1
using media types for errors
#2
johnandersen777
closed
3 months ago
9
Pre IETF 119 Update
#1
OR13
closed
8 months ago
2