Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement"

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 25 February 2011 22:01 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: keyassure@core3.amsl.com
Delivered-To: keyassure@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 114CD3A6A48 for <keyassure@core3.amsl.com>; Fri, 25 Feb 2011 14:01:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.473
X-Spam-Level:
X-Spam-Status: No, score=-101.473 tagged_above=-999 required=5 tests=[AWL=0.573, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 jZKSd+NpCRuU for <keyassure@core3.amsl.com>; Fri, 25 Feb 2011 14:01:46 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 4CA483A68BC for <keyassure@ietf.org>; Fri, 25 Feb 2011 14:01:46 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p1PM2c2c060661 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <keyassure@ietf.org>; Fri, 25 Feb 2011 15:02:39 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D6826FE.2080107@vpnc.org>
Date: Fri, 25 Feb 2011 14:02:38 -0800
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: keyassure@ietf.org
References: <9933A160-3DAF-42FA-B5FA-DDF185FA5C63@kumari.net>
In-Reply-To: <9933A160-3DAF-42FA-B5FA-DDF185FA5C63@kumari.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement"
X-BeenThere: keyassure@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Key Assurance With DNSSEC <keyassure.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyassure>
List-Post: <mailto:keyassure@ietf.org>
List-Help: <mailto:keyassure-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 22:01:47 -0000

On 2/25/11 1:31 PM, Warren Kumari wrote:
> Hi all,
>
> While we are all ruminating on the other issues, I figured we might as
> well try address this one:
>
> Need to specify which crypto algorithms and certificate types are
> mandatory to implement -- http://trac.tools.ietf.org/wg/dane/trac/ticket/21
>
> Description:
> Currently, the draft is silent on which crypto algorithms and
> certificate types must be implemented for interoperability. It should be
> specific before the document is finished.

Certificate type:

- Writing both type 1 and 2 must be supported by all DNS implementations

- Processing type 1 must be supported by all TLS clients.

- Processing type 2 should be supported by all TLS clients. The 
exceptions are TLS clients that do not use the PKIX certificate format 
for trust anchors.

Hash algorithm:

- All implementations must support SHA-256.

- All implementations should have the facility to later use other hash 
algorithms.