This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27816 - IANA considerations review for definition of algorithms
Summary: IANA considerations review for definition of algorithms
Status: RESOLVED MOVED
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
: 29196 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-01-12 21:10 UTC by jimsch
Modified: 2016-05-24 00:29 UTC (History)
3 users (show)

See Also:


Attachments

Description jimsch 2015-01-12 21:10:20 UTC
Please consider this to be a possible IANA considerations review.  It is not completely clear that this is what I would say at the time the document shows up.  But it does indicate my current thinking and a discussion will likely help in forming final opinions.

This set of registrations is problematic due a change that has occurred since this path was initially embarked on.

The IESG made a request for algorithm analysis be added as part of the process of registering a new algorithm so that the designated experts would have a set of usable documents to determine what the security levels of algorithms are.  It was assumed that this was not necessary for the initial registrations as the working group had the chance to discuss this to death during the process.  This means that there is an additional requirement

  Algorithm Analysis Documents(s):
      References to publication(s) in well-known cryptographic
      conferences, by national standards bodies, or by other
      authoritative sources analyzing the cryptographic soundness of the
      algorithm to be registered.  The designated experts may require
      convincing evidence of the cryptographic soundness of a new
      algorithm to be provided with the registration request unless the
      algorithm is being registered as Deprecated or Prohibited.  Having
      gone through working group and IETF review, the initial
      registrations made by this document are exempt from the need to
      provide this information.

It is not clear to me that this is satisfiable for a number of algorithms that registration is being requested for in this case.  (It is also not clear that this field needs to be filled out unless it is requested by the DE so the fact that it is currently absent is not an apriori failure.)

It is very possible that after some discussions a resolution Won't fix is reasonable.
Comment 1 Ryan Sleevi 2015-11-14 21:52:00 UTC
*** Bug 29196 has been marked as a duplicate of this bug. ***
Comment 2 Mark Watson 2016-05-24 00:29:17 UTC
Moved to https://github.com/w3c/webcrypto/issues/79