[ltans] I-D Action:draft-ietf-ltans-dssc-12.txt

Internet-Drafts@ietf.org Wed, 30 September 2009 08:00 UTC

Return-Path: <root@core3.amsl.com>
X-Original-To: ltans@ietf.org
Delivered-To: ltans@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id BFBB73A6A1C; Wed, 30 Sep 2009 01:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090930080001.BFBB73A6A1C@core3.amsl.com>
Date: Wed, 30 Sep 2009 01:00:01 -0700 (PDT)
X-Mailman-Approved-At: Wed, 30 Sep 2009 03:36:44 -0700
Cc: ltans@ietf.org
Subject: [ltans] I-D Action:draft-ietf-ltans-dssc-12.txt
X-BeenThere: ltans@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LTANS Working Group <ltans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltans>, <mailto:ltans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ltans>
List-Post: <mailto:ltans@ietf.org>
List-Help: <mailto:ltans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltans>, <mailto:ltans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2009 08:00:01 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Long-Term Archive and Notary Services Working Group of the IETF.

	Title           : Data Structure for the Security Suitability of Cryptographic Algorithms (DSSC)
	Author(s)       : T. Kunz, et al.
	Filename        : draft-ietf-ltans-dssc-12.txt
	Pages           : 48
	Date            : 2009-09-30

Since cryptographic algorithms can become weak over the years, it is
necessary to evaluate their security suitability.  When signing or
verifying data, or when encrypting or decrypting data, these
evaluations must be considered.  This document specifies a data
structure that enables an automated analysis of the security
suitability of a given cryptographic algorithm at a given point of
time which may be in the past, at the present time or in the
future.Conventions used in this document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
document are to be interpreted as described in [RFC2119].

A URL for this Internet-Draft is:

Internet-Drafts are also available by anonymous FTP at:

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the