Opened 5 years ago

Closed 5 years ago

#171 closed defect (wontfix)

Simplify Log IDs

Reported by: rlb@… Owned by: draft-ietf-trans-rfc6962-bis@…
Priority: major Milestone: review
Component: to-be-decided Version:
Severity: - Keywords:


It's unclear to me why the log IDs are OIDs, as opposed to say a uint32 from a
first-come-first-served registry. That would save both bytes and encode/decode
logic. The only drawback would be that logs would have to email IANA, but they
would have to have do that anyway to get an OID arc. If there's concern about
private/vendor identifiers, such space can be allocated in the registry.

Change History (4)

comment:1 Changed 5 years ago by rob.stradling@…

  • Component changed from client-behavior to to-be-decided

comment:2 Changed 5 years ago by eranm@…

The original discussion is in

comment:3 Changed 5 years ago by eranm@…

  • Milestone set to review

From a discussion with the other -bis authors, we've concluded the following:

  • OIDs can already be 4 bytes long, so switching to INT32 does not save any space.
  • Using INT32 requires asking an ID allocation from IANA for every log, even testing logs, since even test logs should have unique identities.
  • "Private" IDs are dangerous: them being used publicly would lead to similar issues presented by private MIME types.
  • Clients don't need to parse LogID OIDs, they can treat them as opaque blobs.

comment:4 Changed 5 years ago by melinda.shore@…

  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.