RFC 5816: ESSCertIDv2 Update for RFC 3161

In plain English — editorial summary, not part of the RFC

This document updates RFC 3161. It allows the use of ESSCertIDv2, as defined in RFC 5035, to specify the hash of a signer certificate when the hash is calculated with a function other than the Secure Hash Algorithm (SHA-1). [STANDARDS-TRACK]

Document record

Document ID

RFC5816

Published

April 2010

Authors

S. Santesson; N. Pope

Status

PROPOSED STANDARD

Stream

IETF

Area

sec

Pages

5

Also known as

—

Updates:

RFC 3161

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC5816

Topics

• signer certificate
• secure hash algorithm
• sha-1

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 5754Using SHA2 Algorithms with Cryptographic Message SyntaxCurrent

  January 2010

• RFC 9142Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)Current

  January 2022

• RFC 4194The S Hexdump FormatCurrent

  October 2005

• RFC 5802Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API MechanismsUpdated

  July 2010

• RFC 5801Using Generic Security Service Application Program Interface (GSS-API) Mechanisms in Simple Authentication and Security Layer (SASL): The GS2 Mechanism FamilyUpdated

  July 2010

• RFC 5836Extensible Authentication Protocol (EAP) Early Authentication Problem StatementCurrent

  April 2010

• RFC 5793PB-TNC: A Posture Broker (PB) Protocol Compatible with Trusted Network Connect (TNC)Current

  March 2010

• RFC 5792PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC)Current

  March 2010

Also filed under

• PROPOSED STANDARD
• 2010
• IETF stream
• sec area