RFC 5698: Data Structure for the Security Suitability of Cryptographic Algorithms (DSSC)
In plain English — editorial summary, not part of the RFC
Since cryptographic algorithms can become weak over the years, it is necessary to evaluate their security suitability. When signing or verifying data, or when encrypting or decrypting data, these evaluations must be considered. This document specifies a data structure that enables an automated analysis of the security suitability of a given cryptographic algorithm at a given point of time, which may be in the past, the present, or the future. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5698
- Published
- November 2009
- Authors
- T. Kunz; S. Okunick; U. Pordesch
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 40
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6454The Web Origin ConceptCurrent
December 2011
- RFC 2754RPS IANA IssuesObsoleted
January 2000
- RFC 9305Locator/ID Separation Protocol (LISP) Generic Protocol ExtensionCurrent
October 2022
- RFC 6065Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group MappingsCurrent
December 2010
- RFC 4998Evidence Record Syntax (ERS)Current
August 2007
- RFC 7070An Architecture for Reputation ReportingCurrent
November 2013
- RFC 7071A Media Type for Reputation InterchangeCurrent
November 2013
- RFC 7072A Reputation Query ProtocolCurrent
November 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?