RFC 7070: An Architecture for Reputation Reporting
In plain English — editorial summary, not part of the RFC
This document describes a general architecture for a reputation-based service, allowing one to request reputation-related data over the Internet, where "reputation" refers to predictions or expectations about an entity or an identifier such as a domain name. The document roughly follows the recommendations of RFC 4101 for describing a protocol model.
Document record
- Document ID
- RFC7070
- Published
- November 2013
- Authors
- N. Borenstein; M. Kucherawy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7071A Media Type for Reputation InterchangeCurrent
November 2013
- RFC 7072A Reputation Query ProtocolCurrent
November 2013
- RFC 7073A Reputation Response Set for Email IdentifiersCurrent
November 2013
- RFC 7489Domain-based Message Authentication, Reporting, and Conformance (DMARC)Obsoleted
March 2015
- RFC 9057Email Author Header FieldCurrent
June 2021
- 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
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?