issues
search
nuts-foundation
/
nuts-specification
Contains the source of the Nuts specification RFCs.
https://nuts-foundation.gitbook.io
2
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
RFC004 clarify lc + lc drops
#226
pascaldekloe
closed
1 year ago
0
RFC011: refer to Nuts v1 JSON-LD context
#225
woutslakhorst
closed
1 year ago
0
RFC011: add cryptographic hash to JSON-LD context URL to avoid tampering
#224
reinkrul
opened
1 year ago
3
Using the network to distribute JSON-LD contexts and rule sets
#223
reinkrul
opened
1 year ago
2
RFC011: Describe how changes relate to versions
#222
reinkrul
opened
1 year ago
0
Add validation requirements for a VC to RFC011
#221
woutslakhorst
closed
1 year ago
2
Sync wcs JOSE with new wc from W3C
#220
pascaldekloe
closed
1 year ago
3
repudiation bit clarify in RFC002
#219
pascaldekloe
closed
1 year ago
1
Login Contract Registration
#218
pascaldekloe
opened
1 year ago
0
Proposal: yank v1 and fix some stuff
#217
stevenvegt
closed
1 year ago
1
V1 RFCs are no longer a draft
#216
gerardsn
closed
1 year ago
0
Update welcome page with more context
#215
stevenvegt
closed
1 year ago
0
added some info on JSON-LD Nuts context to RFC011
#214
woutslakhorst
closed
2 years ago
0
remove json-ld context limitation
#213
woutslakhorst
closed
2 years ago
0
RFC011: Remove requirement on Nuts context for VCs
#212
woutslakhorst
closed
2 years ago
0
RFC014: Add json-ld context information
#211
stevenvegt
closed
1 year ago
2
Remove algorithmic steps from RFC011
#209
stevenvegt
closed
2 years ago
0
moved NutsAuthorizationCredential specific validations to RFC014
#208
woutslakhorst
closed
2 years ago
0
add clock skew for access token request
#207
woutslakhorst
closed
2 years ago
0
update RFC006: conflict detection for create transactions
#206
woutslakhorst
closed
2 years ago
0
RFC004: Fix JWS example
#205
woutslakhorst
closed
2 years ago
0
RFC013: renamed IRMA proof
#204
woutslakhorst
closed
2 years ago
0
RFC004: add SHOULD requirement to prevs field
#203
woutslakhorst
closed
2 years ago
0
updated graph
#202
woutslakhorst
closed
2 years ago
0
RFC004: limit number of prevs
#201
woutslakhorst
closed
2 years ago
0
RFC008: Use of PKIOverheid Private certificates hampers use of public (HTTP) endpoints
#200
reinkrul
closed
2 years ago
1
small changes to a conversation and range query
#199
woutslakhorst
closed
2 years ago
0
changed requirement of TX to point to all prevs
#198
woutslakhorst
closed
2 years ago
2
RFC017: Specify gRPC status code when authentication fails
#197
reinkrul
closed
2 years ago
1
Diagram out of date
#196
stevenvegt
closed
2 years ago
0
extended privacy considerations
#195
woutslakhorst
closed
2 years ago
0
RFC006: Elaborate on privacy concerns
#194
woutslakhorst
closed
2 years ago
1
Obsolete rfc005
#193
woutslakhorst
closed
2 years ago
0
Deprecate RFC005
#192
stevenvegt
closed
2 years ago
0
RFC015: Refer to RFC6125 for validating node identity v.s. certificates
#191
reinkrul
closed
2 years ago
0
RFC017/RFC005/RFC008: Require at least TLS v1.2 for connections
#190
reinkrul
closed
2 years ago
0
RFC017: Extend TransactionList message and update flow
#189
gerardsn
closed
2 years ago
0
RFC017: update IBLT description
#188
gerardsn
closed
2 years ago
1
changes to rfc017 musts to shoulds
#187
woutslakhorst
closed
2 years ago
0
RFC017: change message answers to SHOULD
#186
woutslakhorst
closed
2 years ago
0
RFC017: extend TransactionList message with MessageNumber and TotalMessages
#185
gerardsn
closed
2 years ago
0
RFC017: Specify peer diagnostics (as in protocol v1)
#184
reinkrul
closed
2 years ago
0
Introduce 'message not supported' error in v2
#183
reinkrul
closed
2 years ago
0
Specify what errors may be returned in protocol v2
#182
reinkrul
closed
2 years ago
0
various RFC017 fixes
#181
woutslakhorst
closed
2 years ago
1
clarify which transaction should be in a gossip msg
#180
woutslakhorst
closed
2 years ago
0
added reference to RFC017 for §10 private TX of RFC014
#179
woutslakhorst
closed
2 years ago
0
RFC017: specify mandatory payload body for public TXs
#178
woutslakhorst
closed
2 years ago
0
tie up loose ends for V2 protocol
#177
woutslakhorst
closed
2 years ago
0
RFC017 change requirements on XOR
#176
gerardsn
closed
2 years ago
0
Previous
Next