RFC 5518: Vouch By Reference
In plain English — editorial summary, not part of the RFC
This document describes the Vouch By Reference (VBR) protocol. VBR is a protocol for adding third-party certification to email. It permits independent third parties to certify the owner of a domain name that is associated with received mail. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5518
- Published
- April 2009
- Authors
- P. Hoffman; J. Levine; A. Hathcock
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 8553
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 7001Message Header Field for Indicating Message Authentication StatusObsoleted
September 2013
- RFC 7601Message Header Field for Indicating Message Authentication StatusObsoleted
August 2015
- RFC 6008Authentication-Results Registration for Differentiating among Cryptographic ResultsCurrent
September 2010
- RFC 6212Authentication-Results Registration for Vouch by Reference ResultsCurrent
April 2011
- RFC 8601Message Header Field for Indicating Message Authentication StatusCurrent
May 2019
- 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?