Traceable Anonymous Certificate
RFC 5636, “Traceable Anonymous Certificate”, is an Experimental document published in August 2009 by S. Park, H. Park, Y. Won, J. Lee, S. Kent. The canonical text is published by the RFC Editor.
Abstract
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.
What “Experimental” means
Describes a specification that is part of a research or development effort, published so the community can gain experience with it.
The canonical text of RFC 5636 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5635 Remote Triggered Black Hole Filtering with Unicast Reverse Path Forwarding
- RFC 5637 Authentication, Authorization, and Accounting Goals for Mobile IPv6
- RFC 5634 Quick-Start for the Datagram Congestion Control Protocol
- RFC 5638 Simple SIP Usage Scenario for Applications in the Endpoints
- RFC 5633 Nominating Committee Process: Earlier Announcement of Open Positions and Solicitation of Volunteers
- RFC 5632 Comcast's ISP Experiences in a Proactive Network Provider Participation for P2P Technical Trial
- RFC 5640 Load-Balancing for Mesh Softwires
- RFC 5641 Layer 2 Tunneling Protocol Version 3 Extended Circuit Status Values