X.509 Key and Signature Encoding for the KeyNote Trust Management System
RFC 5708
Revision differences
Document history
Date | By | Action |
---|---|---|
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This memo describes X.509 key identifiers and signature encoding for version 2 of the KeyNote trust-management … Received changes through RFC Editor sync (changed abstract to 'This memo describes X.509 key identifiers and signature encoding for version 2 of the KeyNote trust-management system (RFC 2704). X.509 certificates (RFC 5280) can be directly used in the Authorizer or Licensees field (or in both fields) in a KeyNote assertion, allowing for easy integration with protocols that already use X.509 certificates for authentication. In addition, the document defines additional signature types that use other hash functions (beyond the MD5 and SHA1 hash functions that are defined in RFC 2792). This document is not an Internet Standards Track specification; it is published for informational purposes.') |
2015-10-14
|
(System) | Notify list changed from angelos@cs.columbia.edu, rfc-editor@rfc-editor.org to rfc-editor@rfc-editor.org |
2010-01-25
|
Cindy Morgan | State Changes to RFC Published from RFC Ed Queue by Cindy Morgan |
2010-01-25
|
Cindy Morgan | [Note]: 'RFC 5708' added by Cindy Morgan |
2010-01-24
|
(System) | RFC published |