| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 01 Aug 2025 02:27:05 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=eaYZotLJuhltm2.v1t72KHBTDXYiHT78c6nI4v7LkUc-1754015225-1.0.1.1-zGbR5gxFJ3mwtpZjLL5xuEcerHHk_VVHAuMqHpZkao_H3I8_9RH63E45gadAza1E5d88yW0SkRCt5MTvVKJYnto5hvQGFET9HojUR7H8.h8; path=/; expires=Fri, 01-Aug-25 02:57:05 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 9681e4f06909a403-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 7071 » RFC Editor
Search RFCs
RFC 7071
A Media Type for Reputation Interchange, November 2013
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- N. Borenstein
M. Kucherawy - Stream:
- IETF
- Source:
- repute (app)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7071
Discuss this RFC: Send questions or comments to the mailing list domainrep@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7071
Abstract
This document defines the format of reputation response data ("reputons"), the media type for packaging it, and definition of a registry for the names of reputation applications and response sets.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us