[Bug 20861] Should <keygen> be conforming-but-obsolete

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20861

Michael[tm] Smith <mike@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P3
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX
           Severity|normal                      |editorial

--- Comment #6 from Michael[tm] Smith <mike@w3.org> ---
(In reply to Henri Sivonen from comment #5)
> I came here to make the comments Julian already made.
> 
> (In reply to comment #4)
> > Eventually, the Web Cryptography API
> > https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html though
> > at this point we need to get implemented in more UAs
> 
> That doc says key provisioning is out of scope. <keygen> is used for CA
> enrollment processes.
> 
> I think we should not obsolete it without a replacement.

Agreed, so moving this to resolved=wontfix.

There's been no new information on this in 2+ years and it does not seem
important enough to merit being kept open for another N years with nothing
happening. I can of course be re-opened if anything has changed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 17 June 2015 03:12:50 UTC