idnits 2.17.1 draft-ietf-pkix-ac509prof-09.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3281 5 Title: An Internet Attribute Certificate Profile for 6 Authorization 7 Author(s): S. Farrell, R. Housley 8 Status: Standards Track 9 Date: April 2002 10 Mailbox: stephen.farrell@baltimore.ie, 11 rhousley@rsasecurity.com 12 Pages: 40 13 Characters: 90580 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-pkix-ac509prof-09.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3281.txt 20 This specification defines a profile for the use of X.509 Attribute 21 Certificates in Internet Protocols. Attribute certificates may be 22 used in a wide range of applications and environments covering a 23 broad spectrum of interoperability goals and a broader spectrum of 24 operational and assurance requirements. The goal of this document is 25 to establish a common baseline for generic applications requiring 26 broad interoperability as well as limited special purpose 27 requirements. The profile places emphasis on attribute certificate 28 support for Internet electronic mail, IPSec, and WWW security 29 applications. 31 This document is a product of the Public-Key Infrastructure (X.509) 32 Working Group of the IETF. 34 This is now a Proposed Standard Protocol. 36 This document specifies an Internet standards track protocol for 37 the Internet community, and requests discussion and suggestions 38 for improvements. Please refer to the current edition of the 39 "Internet Official Protocol Standards" (STD 1) for the 40 standardization state and status of this protocol. Distribution 41 of this memo is unlimited. 43 This announcement is sent to the IETF list and the RFC-DIST list. 44 Requests to be added to or deleted from the IETF distribution list 45 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 46 added to or deleted from the RFC-DIST distribution list should 47 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 49 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 50 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 51 help: ways_to_get_rfcs. For example: 53 To: rfc-info@RFC-EDITOR.ORG 54 Subject: getting rfcs 56 help: ways_to_get_rfcs 58 Requests for special distribution should be addressed to either the 59 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 60 specifically noted otherwise on the RFC itself, all RFCs are for 61 unlimited distribution.echo 62 Submissions for Requests for Comments should be sent to 63 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 64 Authors, for further information.