Document Action: 'Trust Anchor Management Requirements' to Informational RFC

The IESG <> Mon, 30 August 2010 17:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C07613A6849; Mon, 30 Aug 2010 10:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.441
X-Spam-Status: No, score=-102.441 tagged_above=-999 required=5 tests=[AWL=0.158, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 50O0uxs5zvlw; Mon, 30 Aug 2010 10:20:23 -0700 (PDT)
Received: from [] (localhost []) by (Postfix) with ESMTP id DCCC63A6855; Mon, 30 Aug 2010 10:20:19 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Document Action: 'Trust Anchor Management Requirements' to Informational RFC
X-Test-IDTracker: no
Message-ID: <20100830172019.25339.88834.idtracker@localhost>
Date: Mon, 30 Aug 2010 10:20:19 -0700
Cc: pkix mailing list <>, pkix chair <>, Internet Architecture Board <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 30 Aug 2010 17:20:24 -0000

The IESG has approved the following document:
- 'Trust Anchor Management Requirements'
  <draft-ietf-pkix-ta-mgmt-reqs-06.txt> as an Informational RFC

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

The IESG contact persons are Tim Polk and Sean Turner.

A URL of this Internet Draft is:

Technical Summary

A trust anchor represents an authoritative entity via a public key and
associated data.  The public key is used to verify digital signatures and
the associated data is used to constrain the types of information for
which the trust anchor is authoritative.  A relying party uses trust
anchors to determine if a digitally signed object is valid by verifying a
digital signature using the trust anchor's public key, and by enforcing
the constraints expressed in the associated data for the trust anchor. 
This document describes some of the problems associated with the lack of a
standard trust anchor management mechanism and defines requirements for
data formats and push-based protocols designed to address these problems.

Working Group Summary

This document entered the working group following the Trust Anchor
Management BOF and was a successor to the problem statement developed for
that BOF.  The working group discussed the requirements at length and set
the draft aside following working group last call pending completion of
work on technical specifications that fulfill the requirements in this
draft.  Now that work on the specifications is nearing conclusion, this
draft is being progressed as informational to capture the discussion that
preceded and accompanied the development of the technical specifications.

Document Quality

The document is reasonably well-written.


   Steve Kent is the Document Shepherd; Tim Polk is the 
   Responsible Area Director.