RFC 8773: TLS 1.3 Extension for Certificate-Based Authentication with an External Pre-Shared Key
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9973.
Current version: RFC 9973 — TLS 1.3 Extension for Using Certificates with an External Pre-Shared Key
In plain English — editorial summary, not part of the RFC
This document specifies a TLS 1.3 extension that allows a server to authenticate with a combination of a certificate and an external pre-shared key (PSK).
Document record
- Document ID
- RFC8773
- Published
- March 2020
- Authors
- R. Housley
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 11
- Also known as
- —
- Obsoleted by:
- RFC 9973
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8778Use of the HSS/LMS Hash-Based Signature Algorithm with CBOR Object Signing and Encryption (COSE)Current
April 2020
- RFC 8782Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationObsoleted
May 2020
- RFC 8783Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel SpecificationCurrent
May 2020
- RFC 8784Mixing Preshared Keys in the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-quantum SecurityCurrent
June 2020
- RFC 8758Deprecating RC4 in Secure Shell (SSH)Current
April 2020
- RFC 8750Implicit Initialization Vector (IV) for Counter-Based Ciphers in Encapsulating Security Payload (ESP)Current
March 2020
- RFC 8747Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)Current
March 2020
- RFC 8744Issues and Requirements for Server Name Identification (SNI) Encryption in TLSCurrent
July 2020
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?