[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 #26 from Harry Halpin <hhalpin@w3.org> ---
Just to be clear, "extension point" means that other specifications *which
normatively reference the base specification* and *which are not explicitly
referenced in the base specification itself* can use the operations of the base
specifications with new algorithms that are not listed in the base
specification. We have, for example, the Editor's Draft of Curve 25519 from
Trevor Perrin. 

I do not see any clear arguments against this and it's a pretty reasonable
request give the state of crypto right now. 

I don't see any normative or informative references to "as yet to written
specifications" (caveat being that we already have an extension spec for Curve
25519), rather than just making sure that the spec as written does not hardcode
anything that makes it impossible or difficult to extend. 

If folks don't want to implement Cuve25519 or other algorithms, they can just
not implement them (including anything outside the base specification) and this
will be recorded in the test suite for the base specification or any other
future specification like the Curve25519 spec. 

I do not see how Mark's edits cause more work for implementers and, given they
provide at least a first try at the needed extensibility points, I do not see
why they should be removed. "Not liking something" is not a sufficient reason I
think.

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

Received on Wednesday, 8 October 2014 15:18:49 UTC