RFC 3281 on An Internet Attribute Certificate

RFC Editor <rfc-ed@isi.edu> Sat, 11 May 2002 00:34 UTC

Message-Id: <200205110009.g4B09nm12156@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3281 on An Internet Attribute Certificate
Cc: rfc-editor@rfc-editor.org, ietf-pkix@imc.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 10 May 2002 17:09:49 -0700
From: RFC Editor <rfc-ed@isi.edu>
Sender: owner-ietf-pkix@mail.imc.org
Precedence: bulk

A new Request for Comments is now available in online RFC libraries.


        RFC 3281

        Title:	    An Internet Attribute Certificate Profile for
                    Authorization 
        Author(s):  S. Farrell, R. Housley
        Status:	    Standards Track
	Date:       April 2002
        Mailbox:    stephen.farrell@baltimore.ie,
                    rhousley@rsasecurity.com 
        Pages:      40
        Characters: 90580
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-pkix-ac509prof-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3281.txt


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 is a product of the Public-Key Infrastructure (X.509)
Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3281.txt"><ftp://ftp.isi.edu/in-notes/rfc3281.txt>

RFC 3281 on An Internet Attribute Certificate RFC Editor