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

Warren Kumari <warren@kumari.net> Fri, 25 February 2011 21:30 UTC

Return-Path: <warren@kumari.net>
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 2A8803A6A60 for <keyassure@core3.amsl.com>; Fri, 25 Feb 2011 13:30:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.474
X-Spam-Level:
X-Spam-Status: No, score=-102.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, 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 I3a2ZdjTNA1p for <keyassure@core3.amsl.com>; Fri, 25 Feb 2011 13:30:50 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by core3.amsl.com (Postfix) with ESMTP id D980A3A6A6E for <keyassure@ietf.org>; Fri, 25 Feb 2011 13:30:49 -0800 (PST)
Received: from [172.19.118.186] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id E273B1B41296 for <keyassure@ietf.org>; Fri, 25 Feb 2011 16:31:42 -0500 (EST)
Message-Id: <9933A160-3DAF-42FA-B5FA-DDF185FA5C63@kumari.net>
From: Warren Kumari <warren@kumari.net>
To: keyassure@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 25 Feb 2011 16:31:40 -0500
X-Mailer: Apple Mail (2.936)
Subject: [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 21:30:53 -0000

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.


W