RFC 5636 on Traceable Anonymous Certificate

rfc-editor@rfc-editor.org Mon, 24 August 2009 23:47 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F218628C3BF for <ietf-announce@core3.amsl.com>; Mon, 24 Aug 2009 16:47:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.895
X-Spam-Level:
X-Spam-Status: No, score=-16.895 tagged_above=-999 required=5 tests=[AWL=0.704, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gLKWMFOaFe-E for <ietf-announce@core3.amsl.com>; Mon, 24 Aug 2009 16:47:01 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id EB3FF28C3BD for <ietf-announce@ietf.org>; Mon, 24 Aug 2009 16:47:00 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 4EB7930F52E; Mon, 24 Aug 2009 16:46:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5636 on Traceable Anonymous Certificate
From: rfc-editor@rfc-editor.org
Message-Id: <20090824234652.4EB7930F52E@bosco.isi.edu>
Date: Mon, 24 Aug 2009 16:46:52 -0700
Cc: ietf-pkix@imc.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, 24 Aug 2009 23:47:02 -0000

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

        
        RFC 5636

        Title:      Traceable Anonymous Certificate 
        Author:     S. Park, H. Park,
                    Y. Won, J. Lee,
                    S. Kent
        Status:     Experimental
        Date:       August 2009
        Mailbox:    shpark@kisa.or.kr, 
                    hrpark@kisa.or.kr, 
                    yjwon@kisa.or.kr,
                    jilee@kisa.or.kr, 
                    kent@bbn.com
        Pages:      31
        Characters: 70316
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pkix-tac-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5636.txt

This document defines a practical architecture and protocols for
offering privacy for a user who requests and uses an X.509 certificate
containing a pseudonym, while still retaining the ability to map such
a certificate to the real user who requested it.  The architecture is
compatible with IETF certificate request formats such as PKCS10 (RFC
2986) and CMC (RFC 5272).  The architecture separates the authorities
involved in issuing a certificate: one for verifying ownership of a
private key (Blind Issuer) and the other for validating the contents
of a certificate (Anonymity Issuer).  The end entity (EE) certificates
issued under this model are called Traceable Anonymous Certificates
(TACs).  This memo defines an Experimental Protocol for the 
Internet community.

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


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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
USC/Information Sciences Institute