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

"dane issue tracker" <trac+dane@trac.tools.ietf.org> Fri, 11 March 2011 18:51 UTC

Return-Path: <trac+dane@trac.tools.ietf.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 2C6D53A6C6F for <keyassure@core3.amsl.com>; Fri, 11 Mar 2011 10:51:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[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 0DYkMGU0qx5e for <keyassure@core3.amsl.com>; Fri, 11 Mar 2011 10:51:31 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 182DA3A6B49 for <keyassure@ietf.org>; Fri, 11 Mar 2011 10:51:31 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.74) (envelope-from <trac+dane@trac.tools.ietf.org>) id 1Py7SE-0007Id-C9; Fri, 11 Mar 2011 10:52:50 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "dane issue tracker" <trac+dane@trac.tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: warren@kumari.net
X-Trac-Project: dane
Date: Fri, 11 Mar 2011 18:52:50 -0000
X-URL: http://tools.ietf.org/dane/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/dane/trac/ticket/21#comment:1
Message-ID: <069.9ae8482dba590afd3b16d4ebca74bf9d@trac.tools.ietf.org>
References: <060.7d08a09e8dc701e85028c142516ecaa0@trac.tools.ietf.org>
X-Trac-Ticket-ID: 21
In-Reply-To: <060.7d08a09e8dc701e85028c142516ecaa0@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: warren@kumari.net, keyassure@ietf.org
X-SA-Exim-Mail-From: trac+dane@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: keyassure@ietf.org
Subject: Re: [keyassure] [dane] #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
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, 11 Mar 2011 18:51:32 -0000

#21: Need to specify which crypto algorithms and certificate types are mandatory
to implement

Changes (by warren@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 We are calling (rough) consensus as:

 SHA-256 MUST be implemented.
 SHA-512 SHOULD be implemented.

 We fully expect to support SHA-3 once it is finalized, but we are not
 currently reserving code-points for it.
 We can re-visit code-points for SHA-3 as we know more about it, how many
 code-points it should have, etc.

-- 
-----------------------------------+----------------------------------------
 Reporter:  paul.hoffman@…         |        Owner:        
     Type:  defect                 |       Status:  closed
 Priority:  major                  |    Milestone:        
Component:  protocol               |      Version:        
 Severity:  -                      |   Resolution:  fixed 
 Keywords:                         |  
-----------------------------------+----------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/dane/trac/ticket/21#comment:1>
dane <http://tools.ietf.org/dane/>