RFC 5081: Using OpenPGP Keys for Transport Layer Security (TLS) Authentication
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6091.
Current version: RFC 6091 — Using OpenPGP Keys for Transport Layer Security (TLS) Authentication
In plain English — editorial summary, not part of the RFC
This memo proposes extensions to the Transport Layer Security (TLS) protocol to support the OpenPGP key format. The extensions discussed here include a certificate type negotiation mechanism, and the required modifications to the TLS Handshake Protocol. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5081
- Published
- November 2007
- Authors
- N. Mavrogiannopoulos
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 8
- Also known as
- —
- Obsoleted by:
- RFC 6091
Topics
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 3373Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point AdjacenciesObsoleted
September 2002
- RFC 2759Microsoft PPP CHAP Extensions, Version 2Current
January 2000
- RFC 2433Microsoft PPP CHAP ExtensionsCurrent
October 1998
- RFC 5080Common Remote Authentication Dial In User Service (RADIUS) Implementation Issues and Suggested FixesCurrent
December 2007
- RFC 5083Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content TypeCurrent
November 2007
- RFC 5084Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax (CMS)Current
November 2007
- RFC 5090RADIUS Extension for Digest AuthenticationCurrent
February 2008
- RFC 5070The Incident Object Description Exchange FormatObsoleted
December 2007
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?