MISP/misp-rfc

Issues

• JSON Schema vs RFC

  #48 opened 2 years ago by 0xThiebaut
  1

• Are Objects' and Object References' `uuid` field mandatory?

  #42 opened 2 years ago by 0xThiebaut
  0

• Sightings uses `uint` to reference `string` identifiers

  #45 opened 3 years ago by 0xThiebaut
  0

• Several of the attribute attributes refer to their context as "event", maybe C&P error?

  #24 opened 6 years ago by acruise
  3

• Add a description in the core format about hashes.csv for the manifest part

  #38 opened 4 years ago by adulau
  0

• update misp-core-format info and raw.md.txt to available draft 08

  #33 opened 5 years ago by bernhardreiter
  0

• Add a section about current implementation (following BP from RFC 7942)

  #26 opened 5 years ago by adulau
  0

• `type` codes appear to be duplicated for Attribute and ShadowAttribute; should probably refer to a single appendix table

  #25 opened 6 years ago by acruise
  1

• Missing misp-objects in JSON-Schema

  #14 opened 6 years ago by nbareil
  0

• Fields containing only numbers should be JSON integers

  #3 opened 8 years ago by rhaist
  2

• Clarify meaning of ID "human-readable identifier"

  #9 opened 7 years ago by rooterkyberian
  2

• Sample UUID and example orgs should be added

  #5 opened 8 years ago by adulau
  1

• Timestamps should all be in the same format

  #4 opened 8 years ago by rhaist
  2

• warning-list format Internet-Draft

  #7 opened 7 years ago by adulau
  0

• incorrect information on sharing_group_id

  #2 opened 8 years ago by iglocska
  0