Re: Cohen's paper on byte order

From: Douglas A. Gwyn (DAGwyn_at_null.net)
Date: 04/29/03 

Date: Tue, 29 Apr 2003 21:33:04 GMT

Brian Gladman wrote:
> In general I would see this as an implementation responsibility but since
> the byte array interface is very widely used and is even present in the
> FIPS, there is a solid case for including it in the FIPS.

Thank you. Since there is unlikely to *be* any other
operative standard to guide AES implementors than the
FIPS, interoperability requires that the FIPS address it.
Perhaps FIPS-197-1 is in order; there are a few other
technical details that could be cleaned up as well.

Relevant Pages

  • Re: Cohens paper on byte order
    ... > organized as multibit numerical values onto AES ... Brian Gladman and you have both ... In my view the pseudo code in the FIPS implicitly establishes this external ... byte array interface and this mapping. ...
    (sci.crypt)
  • Re: Cohens paper on byte order
    ... >> In my view the pseudo code in the FIPS implicitly establishes this ... >> byte array interface and this mapping. ... > interested in the AES interoperability issue). ... the byte array interface is very widely used and is even present in the ...
    (sci.crypt)
  • Re: Cohens paper on byte order
    ... >> organized as multibit numerical values onto AES ... Brian Gladman and you have both ... > In my view the pseudo code in the FIPS implicitly establishes this external ... With this convention, hardware with big-endian byte ...
    (sci.crypt)
  • Re: Cohens paper on byte order
    ... Brian Gladman wrote: ... > but had the FIPS been perfect there would have been two versions of AES. ... Which is a strange notion of "perfection". ...
    (sci.crypt)
Quantcast