ioggstream/draft-polli-resource-digests-http

Issues

• Define a different encoding for id-sha-*

  #33 opened 6 years ago by ioggstream
  1

• Use http-core or 723x?

  #18 opened 6 years ago by ioggstream
  2

• Investigate the usage of PATCH

  #4 opened 6 years ago by ioggstream
  2

• Using Digest in signatures

  #20 opened 6 years ago by ioggstream
  4

• Create a threat model

  #29 opened 6 years ago by ioggstream
  2

• Clarify digest-algorithm syntax

  #34 opened 6 years ago by ioggstream
  4

• Digest of "empty" representation

  #35 opened 6 years ago by ioggstream
  3

• Use ABNF for digest-header

  #41 opened 6 years ago by ioggstream
  0

• Managing multiple digest values

  #36 opened 6 years ago by ioggstream
  3

• Elaborate on the use cases for a Digest

  #15 opened 6 years ago by jyasskin
  8

• Define an encoding for binary payload data examples

  #22 opened 6 years ago by ioggstream
  1

• Remove non-cryptographic algorithms

  #16 opened 6 years ago by ioggstream
  8

• Consider using multiformats (multihash) for future proofing

  #39 opened 6 years ago by dlongley
  6

• Introduction refers to TCP instead of TLS

  #14 opened 6 years ago by jyasskin
  7

• "resource" wg doesn't exist

  #13 opened 6 years ago by jyasskin
  0

• Example for content-encoding importance

  #9 opened 6 years ago by ioggstream
  1

• GitHub pages is a little messed up

  #3 opened 6 years ago by LPardue
  4

• "identity" is not a content coding

  #5 opened 6 years ago by ioggstream
  1

• DISCOURAGES is not an RFC2119 keyword

  #8 opened 6 years ago by LPardue
  2