Re: Cohen's paper on byte order

From: Douglas A. Gwyn (DAGwyn@null.net)
Date: 04/06/03 

Date: Sat, 05 Apr 2003 18:25:26 -0500
From: "Douglas A. Gwyn" <DAGwyn@null.net>

Mok-Kong Shen wrote:
> Couldn't one say the same for the quicksort algorithm,
> for example??

No. That is a bad analogy.

> ... When these processed bits are to be
> transmitted to the outside world, say over a serial
> channel, well, there is a normal convention that he
> has somehow to observe in transmitting 'any' chunks
> of bits of his hardware (in any applications, not
> only encryption, e.g. 32 bits representing an integer)
> out, isn't it? (What has that particularly to do with
> AES??)

AES is intended to be used to standardize an aspect of
information interchange, a.k.a. *communication*. That
means that leaving critical decisions to "somehow" is
inappropriate.

The practical issue can be seen when somebody implements
AES and finds that he is unable to communicate with
somebody else who has his own implementation of AES.
If you think that doesn't matter then further discussion
is futile.

Relevant Pages

  • Re: Cohens paper on byte order
    ... > for correct communication of the formatted data. ... Indeed AES is just a solid block to create ... AES is defined on a sequences of 128 bits only as data and a sequence ... and consistent - exectly what I need from a standard. ...
    (sci.crypt)
  • Re: Cohens paper on byte order
    ... > AES is intended to be used to standardize an aspect of ... > inappropriate. ... different technologies and their corresponding standards. ... AES does only a very tiny job in communication, ...
    (sci.crypt)
Quantcast