-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
this is talking about parallizing processing of an individual message.
the application for this is packet processing in a protocol stack,
or "lower", packet processing in hardware below+/inside the protocol
stack.
you can't parallelize IPsec, for example, as you can't process the HMAC
at the end until you've encrypted the body.
P.s, when he spoke at Stanford I asked about patents and he said
it was patented, and he said NIST is trying to get them to put it
in the public domain.
At 10:32 AM 12/8/00 -0800, Bram Cohen wrote:
>No word, of course, on how the thing actually works, or whether they
>intend to patent it.
>
>A note to the clueful about it being 'parellelizable' - almost all crypto
>stuff can be parallelized by putting different tasks on different
>processors, since the vast majority of crypto applications have multiple
>tasks on a server going on at once.
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0
iQA/AwUBOjOuJz/0TyQ4fTjtEQKVZgCg714v3imy9hER3PPwGsIj4UBPaFMAoO35
ieU2BbfR4ozm/8qUbWkl5YRi
=8tTs
-----END PGP SIGNATURE-----
