[Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec

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

--- Comment #41 from Brian LaMacchia <bal@microsoft.com> ---
(In reply to Boris Zbarsky from comment #39)
> > "I want to ship S1 and have the flexibility to add a new hash
> > algorithm/elliptic curve/KDF/padding mode/whatever in some scenario quickly
> > without needing to reopen S1"
> 
> As an implementation matter, you can just add it, right?  If you really need
> to do it quickly, you can't wait for the likely-long process of S2 going to
> REC.

But I need a way to do it without violating S1, which I don't have today. 
Using my previous example, without extensibility points like Mark was adding I
can't add support for "SHA-3" to the RSA-PSS list without violating the
S1-specified behavior.  The base spec needs to have cryptographic agility built
in or I have to break the behavior contract to extend it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 9 October 2014 16:22:37 UTC