issues
search
tus
/
draft-digest-fields-problem-types
An Internet Draft defining Problem Types for Digest Fields
https://tus.github.io/draft-digest-fields-problem-types/draft-kleidl-digest-fields-problem-types.html
Other
1
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add @ioggstream as an author.
#21
ioggstream
closed
1 month ago
0
Problem type if the server does not want to compute digests
#20
Acconut
opened
1 month ago
0
Use `digest-` prefix for problem types
#19
Acconut
closed
1 month ago
0
Unsupported algorithm: one or all?
#18
Acconut
closed
3 weeks ago
2
Fix: #5. Mention intermediaries, fingerprinting in sec.
#17
ioggstream
closed
1 month ago
1
Use the `digest` prefix on all problem types
#16
ioggstream
closed
1 month ago
1
Editorial improvements on IANA considerations.
#15
ioggstream
closed
1 month ago
0
Add requests to examples
#14
Acconut
closed
1 month ago
0
Unsupported algos
#13
ioggstream
closed
1 month ago
1
Unsupported algorithm's feedback
#12
ioggstream
closed
1 month ago
2
Terminology from DIGEST.
#11
ioggstream
closed
4 months ago
0
Preliminary editorial
#10
ioggstream
closed
4 months ago
1
Inherit examples from Digest Fields
#9
ioggstream
opened
4 months ago
2
Add complete request-response examples
#8
ioggstream
closed
1 month ago
2
Relax recommendations on client behavior
#7
Acconut
closed
4 months ago
0
idea: maybe signatures would benefit from some problem types too?
#6
LPardue
opened
4 months ago
2
This may reveal information about intermediaries
#5
LPardue
closed
1 month ago
0
expected-digest seems prescient
#4
LPardue
closed
4 months ago
1
Don't mandate client behaviour
#3
LPardue
closed
4 months ago
0
Supported-algorthms duplicates want- response header?
#2
LPardue
closed
4 months ago
1
Clarify the problem statement and focus of the draft more
#1
LPardue
closed
4 months ago
1