RFC 5937 on Using Trust Anchor Constraints during Certification Path Processing

rfc-editor@rfc-editor.org Thu, 19 August 2010 23:21 UTC

Return-Path: <wwwrun@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 758573A6A2D for <ietf-announce@core3.amsl.com>; Thu, 19 Aug 2010 16:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.356
X-Spam-Level:
X-Spam-Status: No, score=-102.356 tagged_above=-999 required=5 tests=[AWL=0.244, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 3o1T5BH2GElt for <ietf-announce@core3.amsl.com>; Thu, 19 Aug 2010 16:21:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id B6D243A67EF for <ietf-announce@ietf.org>; Thu, 19 Aug 2010 16:21:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D8FBCE06D9; Thu, 19 Aug 2010 16:21:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5937 on Using Trust Anchor Constraints during Certification Path Processing
From: rfc-editor@rfc-editor.org
Message-Id: <20100819232153.D8FBCE06D9@rfc-editor.org>
Date: Thu, 19 Aug 2010 16:21:53 -0700 (PDT)
Cc: 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: Thu, 19 Aug 2010 23:21:19 -0000

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

        
        RFC 5937

        Title:      Using Trust Anchor Constraints during 
                    Certification Path Processing 
        Author:     S. Ashmore, C. Wallace
        Status:     Informational
        Stream:     IETF
        Date:       August 2010
        Mailbox:    srashmo@radium.ncsc.mil, 
                    cwallace@cygnacom.com
        Pages:      8
        Characters: 16900
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-wallace-using-ta-constraints-02.txt

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

This document describes how to use information associated with a
trust anchor public key when validating certification paths.  This
information can be used to constrain the usage of a trust anchor.
Typically, constraints are used to limit the certificate policies and
names that can appear in certification paths validated using a trust
anchor.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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
Association Management Solutions, LLC