RFC 3281: An Internet Attribute Certificate Profile for Authorization
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5755.
Current version: 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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3281
- Published
- May 2002
- Authors
- S. Farrell; R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 40
- Also known as
- —
- Obsoleted by:
- RFC 5755
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3602The AES-CBC Cipher Algorithm and Its Use with IPsecCurrent
September 2003
- RFC 2409The Internet Key Exchange (IKE)Obsoleted
November 1998
- RFC 2407The Internet IP Security Domain of Interpretation for ISAKMPObsoleted
November 1998
- RFC 2406IP Encapsulating Security Payload (ESP)Obsoleted
November 1998
- RFC 2404The Use of HMAC-SHA-1-96 within ESP and AHCurrent
November 1998
- RFC 2402IP Authentication HeaderObsoleted
November 1998
- RFC 2401Security Architecture for the Internet ProtocolObsoleted
November 1998
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
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?