SHA3/SHAKE spec mirror sha1/2 domain changes?

[fliphil]

Hello,

I was wondering if at some point the SHA3/SHAKE specification will use a domain value for the messageLength (replacing inEmpty and inBit) and eliminating outBit? This would bring it inline with how the SHA1/2 spec is currently designed, and I like this approach.

Thanks!
Phil

[celic]

I also like the approach. The problem lies within the SHAKE MCTs. They are not well designed for a domain value at the moment. They require the domain to consist of a single minimum and maximum pair as the MCT algorithm has no concept of selecting a valid length from a varied domain.

I am also in favor of redesigning the SHAKE MCTs so that they can properly accept a domain. After that is completed, changing SHA3/SHAKE over to mirror SHA1/2 would be trivial.

[celic]

Stay tuned for SHA3 revision 2.0 which allows a registration similar to SHA2. Documentation in progress.

[celic]

Duplicate of #1003