RFC 5913: Clearance Attribute and Authority Clearance Constraints Certificate Extension
In plain English — editorial summary, not part of the RFC
This document defines the syntax and semantics for the Clearance attribute and the Authority Clearance Constraints extension in X.509 certificates. The Clearance attribute is used to indicate the clearance held by the subject. The Clearance attribute may appear in the subject directory attributes extension of a public key certificate or in the attributes field of an attribute certificate. The Authority Clearance Constraints certificate extension values in a Trust Anchor (TA), in Certification Authority (CA) public key certificates, and in an Attribute Authority (AA) public key certificate in a certification path for a given subject constrain the effective Clearance of the subject. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5913
- Published
- June 2010
- Authors
- S. Turner; S. Chokhani
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5636Traceable Anonymous CertificateCurrent
August 2009
- RFC 5924Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 CertificatesCurrent
June 2010
- RFC 5912New ASN.1 Modules for the Public Key Infrastructure Using X.509 (PKIX)Updated
June 2010
- RFC 5914Trust Anchor FormatCurrent
June 2010
- RFC 5911New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIMEUpdated
June 2010
- RFC 5930Using Advanced Encryption Standard Counter Mode (AES-CTR) with the Internet Key Exchange version 02 (IKEv2) ProtocolCurrent
July 2010
- RFC 5934Trust Anchor Management Protocol (TAMP)Current
August 2010
- RFC 5879Heuristics for Detecting ESP-NULL PacketsCurrent
May 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?