RFC 5755: An Internet Attribute Certificate Profile for Authorization
In plain English — editorial summary, not part of the RFC
This specification defines a profile for the use of X.509 Attribute Certificates in Internet Protocols. Attribute certificates may be used in a wide range of applications and environments covering a broad spectrum of interoperability goals and a broader spectrum of operational and assurance requirements. The goal of this document is to establish a common baseline for generic applications requiring broad interoperability as well as limited special purpose requirements. The profile places emphasis on attribute certificate support for Internet electronic mail, IPsec, and WWW security applications. This document obsoletes RFC 3281. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5755
- Published
- January 2010
- Authors
- S. Farrell; R. Housley; S. Turner
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 50
- Also known as
- —
- Obsoletes:
- RFC 3281
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 2401Security Architecture for the Internet ProtocolObsoleted
November 1998
- RFC 5703Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and EnclosureCurrent
October 2009
- RFC 5863DomainKeys Identified Mail (DKIM) Development, Deployment, and OperationsCurrent
May 2010
- RFC 5322Internet Message FormatUpdated
October 2008
- RFC 5660IPsec Channels: Connection LatchingCurrent
October 2009
- RFC 5879Heuristics for Detecting ESP-NULL PacketsCurrent
May 2010
- RFC 5996Internet Key Exchange Protocol Version 2 (IKEv2)Obsoleted
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?