In response to comments on and off list, I have revved the draft to
produce a -02

* Have fixed the omission of the scheme and algorithm in
/.well-known/di/sha-256
* Have changed the colon separating the algorithm and the digest to a
semi-colon on advice that some parsers will choke otherwise
* Have taken out the SHA-128 scheme and instead put in support for
truncation on an arbitrary 32 bit boundary. [This needs a security
consideration of course]

I guess I should have added the acknowledgements section as well.


Stephen and I have had discussions off list. If all goes well this
should be the last version of this draft before we get to a merge. The
outcome that seems to be most likely to suit people's needs would be
to have two drafts. The first would just have the core syntax and
security considerations for using digest identifiers. The second would
have all the interesting stuff link locators and encryption and stuff.
Content-type would likely be in the second.

I am going off to write some code.

-- 
Website: http://hallambaker.com/
_______________________________________________
websec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/websec

Reply via email to