| CARVIEW |
Select Language
HTTP/2 200
date: Wed, 08 Oct 2025 07:14:04 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=DB9URB3Vmj67kkdwPb7YCSGtEoXwrsDIeLo53nIAF98-1759907644-1.0.1.1-nKiLk8XTuBAT2RTLH0FQoa8PCxdhKlY1919rAOf5EsqyonD_EbpzaUf6bveut1GdBhpn6V7Pw75goEsMj3.UvPyfE5nQrhN.D4xwGGdu4Xk; path=/; expires=Wed, 08-Oct-25 07:44:04 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98b3d6d4997fc464-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8485 » RFC Editor
Search RFCs
RFC 8485
Vectors of Trust, October 2018
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- J. Richer, Ed.
L. Johansson - Stream:
- IETF
- Source:
- NON WORKING GROUP
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8485
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8485
Abstract
This document defines a mechanism for describing and signaling several aspects of a digital identity transaction and its participants. These aspects are used to determine the amount of trust to be placed in that transaction.
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