Trust Anchor Publication Advice

Document Type Expired Internet-Draft (individual)
Authors Steven Bellovin  , Randy Bush  , Russ Housley  , Stephen Kent  , Sean Turner 
Last updated 2013-02-17 (latest revision 2012-08-16)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Many Internet protocols and services rely on credentials which use asymmetric keys. Many of these are hierarchic structures having certification authorities (CAs) that act as trust anchors (TAs). There is little general guidance on procedures for how these trust anchors can be distributed or otherwise published with prudence. To quote a well known security expert, "It's a matter of oral tradition in security circles." This document attempts to capture some of that lore.


Steven Bellovin (
Randy Bush (
Russ Housley (
Stephen Kent (
Sean Turner (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)