RFC 5755 on An Internet Attribute Certificate Profile for Authorization

rfc-editor@rfc-editor.org Mon, 25 January 2010 18:20 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id F135228C132; Mon, 25 Jan 2010 10:20:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id Gtvj8-K5-Y6p; Mon, 25 Jan 2010 10:20:02 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 03EC228C11E; Mon, 25 Jan 2010 10:20:02 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 146A5E06C8; Mon, 25 Jan 2010 10:20:09 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5755 on An Internet Attribute Certificate Profile for Authorization
From: rfc-editor@rfc-editor.org
Message-Id: <20100125182009.146A5E06C8@rfc-editor.org>
Date: Mon, 25 Jan 2010 10:20:09 -0800
Cc: pkix@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2010 18:20:03 -0000

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

        RFC 5755

        Title:      An Internet Attribute Certificate Profile 
                    for Authorization 
        Author:     S. Farrell, R. Housley,
                    S. Turner
        Status:     Standards Track
        Date:       January 2010
        Mailbox:    stephen.farrell@cs.tcd.ie, 
        Pages:      50
        Characters: 101482
        Obsoletes:  RFC3281

        I-D Tag:    draft-ietf-pkix-3281update-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5755.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 obsoletes RFC 3281.  [STANDARDS TRACK]

This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC