Darian Anthony Patrick <[EMAIL PROTECTED]> writes:

> Chris Dolan wrote:
>>> Yes. RFC 1924 specifies a way to convert an IPv6 address to ASCII, by
>>> treating it as 128 bit integer, writing the number in base 85, then
>>> expressing
>>> each base 85 digit as an ASCII character
>>>
>>> btoa and PDFs break up a stream of bytes into ASCII by treating it as 32
>>> bit
>>> integers (4 bytes become 5 ASCII characters), and (in the case of PDFs)
>>> then
>>> representing last odd 1 to 3 bytes as 2 to 4 ASCII characters. They also
>>> use
>>> a different subset of printable ASCII from RFC 1924

You may note that RFC 1924 was issued on April 1 1996, so any
reference to it should be done with tongue firmly in cheek.

Highlights:

7. Implementation Issues

   Many current processors do not find 128 bit integer arithmetic, as
   required for this technique, a trivial operation.  This is not
   considered a serious drawback in the representation, but a flaw of
   the processor designs.

   It may be expected that future processors will address this defect,
   quite possibly before any significant IPv6 deployment has been
   accomplished.

8. Security Considerations

   By encoding addresses in this form, it is less likely that a casual
   observer will be able to immediately detect the binary form of the
   address, and thus will find it harder to make immediate use of the
   address.  As IPv6 addresses are not intended to be learned by
   humans, one reason for which being that they are expected to alter
   in comparatively short timespan, by human perception, the somewhat
   challenging nature of the addresses is seen as a feature.

   Further, the appearance of the address, as if it may be random
   gibberish in a compressed file, makes it much harder to detect by a
   packet sniffer programmed to look for bypassing addresses.

The second paragraph of (7) seems particularly prescient, given that
this RFC was written 12 years ago.  :-)

----Scott.

Reply via email to