RFC 3739 on Internet X.509 Public Key Infrastructure: Qualified Certificates Profile
rfc-editor@rfc-editor.org Fri, 19 March 2004 23:07 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29522 for <ietf-announce-archive@odin.ietf.org>; Fri, 19 Mar 2004 18:07:17 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1B4SxH-0001Ed-Px for ietf-announce-list@asgard.ietf.org; Fri, 19 Mar 2004 17:59:07 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1B4Svh-00014U-3A for all-ietf@asgard.ietf.org; Fri, 19 Mar 2004 17:57:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28854 for <all-ietf@ietf.org>; Fri, 19 Mar 2004 17:57:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B4Svf-0005UK-00 for all-ietf@ietf.org; Fri, 19 Mar 2004 17:57:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B4Suf-0005Op-00 for all-ietf@ietf.org; Fri, 19 Mar 2004 17:56:26 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1B4Stn-0005JV-00 for all-ietf@ietf.org; Fri, 19 Mar 2004 17:55:31 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i2JMtVk20400; Fri, 19 Mar 2004 14:55:31 -0800 (PST)
Message-Id: <200403192255.i2JMtVk20400@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3739 on Internet X.509 Public Key Infrastructure: Qualified Certificates Profile
Cc: rfc-editor@rfc-editor.org, ietf-pkix@imc.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 19 Mar 2004 14:55:31 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.1 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3739 Title: Internet X.509 Public Key Infrastructure: Qualified Certificates Profile Author(s): S. Santesson, M. Nystrom, T. Polk Status: Standards Track Date: March 2004 Mailbox: stefans@microsoft.com, magnus@rsasecurity.com, wpolk@nist.gov Pages: 34 Characters: 67436 Obsoletes: 3039 I-D Tag: draft-ietf-pkix-sonof3039-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3739.txt This document forms a certificate profile, based on RFC 3280, for identity certificates issued to natural persons. The profile defines specific conventions for certificates that are qualified within a defined legal framework, named Qualified Certificates. However, the profile does not define any legal requirements for such Qualified Certificates. The goal of this document is to define a certificate profile that supports the issuance of Qualified Certificates independent of local legal requirements. The profile is however not limited to Qualified Certificates and further profiling may facilitate specific local needs. 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.