RE: Corrected Announcement: RFC 5280 on Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile

[Stefan Santesson <stefans@xxxxxxxxxxxxx>]

So finally, the successor of RFC 3280 has been published.

I want to extend a thank you to all participants in this work group that helped in the effort to get this standard published.
A special thanks to David Cooper who has done most of the tracking of issues and document changes throughout the editorial process.


Stefan Santesson
Senior Program Manager
Windows Security, Standards

> -----Original Message-----
> From: owner-ietf-pkix@xxxxxxxxxxxx [mailto:owner-ietf-
> pkix@xxxxxxxxxxxx] On Behalf Of rfc-editor@xxxxxxxxxxxxxx
> Sent: den 9 maj 2008 19:39
> To: ietf-announce@xxxxxxxx; rfc-dist@xxxxxxxxxxxxxx
> Cc: rfc-editor@xxxxxxxxxxxxxx; ietf-pkix@xxxxxxx
> Subject: Corrected Announcement: RFC 5280 on Internet X.509 Public Key
> Infrastructure Certificate and Certificate Revocation List (CRL)
> Profile
>
>
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 5280
>
>         Title:      Internet X.509 Public Key Infrastructure
>                     Certificate and Certificate Revocation List (CRL)
>                     Profile
>         Author:     D. Cooper, S. Santesson,
>                     S. Farrell, S. Boeyen,
>                     R. Housley, W. Polk
>         Status:     Standards Track
>         Date:       May 2008
>         Mailbox:    david.cooper@xxxxxxxx,
>                     stefans@xxxxxxxxxxxxx,
>                     stephen.farrell@xxxxxxxxx,
> sharon.boeyen@xxxxxxxxxxx,
>                     housley@xxxxxxxxxxxx, wpolk@xxxxxxxx
>         Pages:      151
>         Characters: 352580
>         Obsoletes:  RFC3280, RFC4325, RFC4630
>
>         I-D Tag:    draft-ietf-pkix-rfc3280bis-11.txt
>
>         URL:        http://www.rfc-editor.org/rfc/rfc5280.txt
>
> This memo profiles the X.509 v3 certificate and X.509 v2 certificate
> revocation list (CRL) for use in the Internet.  An overview of this
> approach and model is provided as an introduction.  The X.509 v3
> certificate format is described in detail, with additional information
> regarding the format and semantics of Internet name forms.  Standard
> certificate extensions are described and two Internet-specific
> extensions are defined.  A set of required certificate extensions is
> specified.  The X.509 v2 CRL format is described in detail along with
> standard and Internet-specific extensions.  An algorithm for X.509
> certification path validation is described.  An ASN.1 module and
> examples
> are provided in the appendices.  [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 list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution list
> should be sent to IETF-REQUEST@xxxxxxxxx  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST@xxxxxxxxxxxxxxx
>
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info@xxxxxxxxxxxxxx with the message body
>
> help: ways_to_get_rfcs. For example:
>
>         To: rfc-info@xxxxxxxxxxxxxx
>         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@xxxxxxxxxxxxxxx
> Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
> Submissions for Requests for Comments should be sent to
> RFC-EDITOR@xxxxxxxxxxxxxxx  Please consult RFC 2223, Instructions to
> RFC
> Authors, for further information.
>
>
> The RFC Editor Team
> USC/Information Sciences Institute
>
> ...
>