Opened 7 years ago

Closed 7 years ago

#28 closed defect (fixed)

Algorithm agility

Reported by: kent@… Owned by: draft-ietf-trans-rfc6962-bis@…
Priority: major Milestone:
Component: rfc6962-bis Version:
Severity: - Keywords:
Cc:

Description

6962-bis does not address algorithm agility. Revise the document to acknowledge the need for algorithm agility and identify the mechanisms that support agility wherever algorithms are used through the design. For example, log operators must advertise the algorithms they use to sign log entries and SCTs and STHs as part of log metadata, they must advertise the algorithms they accept for certs that are submitted, etc.

Change History (1)

comment:1 Changed 7 years ago by benl@…

  • Resolution set to fixed
  • Status changed from new to closed

I believe that cert algorithms are already specified by reference to the relevant RFCs, and whatever agility mechanisms those have.

For the log algorithms, fixed in https://github.com/google/certificate-transparency-rfcs/commit/0c5b808345812946d8d36c692f0607b5262ca9a3.

Note: See TracTickets for help on using tickets.