home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.mail.mime
- Path: sparky!uunet!pipex!pavo.csi.cam.ac.uk!ag129
- From: ag129@cus.cam.ac.uk (Alasdair Grant)
- Subject: Re: X.400 and multimedia mail
- Message-ID: <1992Dec11.201947.17868@infodev.cam.ac.uk>
- Sender: news@infodev.cam.ac.uk (USENET news)
- Nntp-Posting-Host: bootes.cus.cam.ac.uk
- Organization: U of Cambridge, England
- References: <davecb.724004446@yorku.ca> <1992Dec11.153138.2198@ericsson.se> <1galsqINNr88@gap.caltech.edu>
- Date: Fri, 11 Dec 1992 20:19:47 GMT
- Lines: 19
-
- In article <1galsqINNr88@gap.caltech.edu> jack@ccsf.caltech.edu (Jack Stewart) writes:
- >As I understand, the main reason for MIME to use base64 encoding (as
- >opposed to uuencode, 8bit transparent, XDR, or BER ) was that they
- >needed an encoded scheme that would remain uncorrupted accross all
- >platforms and architectures and existing mailers. Apparently this is
- >a real problem with IBM VM/CMS machines. base64 encoding was the only
- >thing that would survive these machines. Hopefully these machines
- >will go away some day and then we can use a more reasonable encoding
- >mechanism.
-
- Yes, but this is a minor problem compared to the presence of machines
- which use the 7-bit American ASCII code, where the top bit is a parity
- bit. EBCDIC, as used by VM/CMS (and MVS and DOS), is an 8-bit code.
- Neither uuencode nor base64 are 'reasonable', since they both 'waste'
- bandwidth, but the reason they exist is fundamentally because ASCII
- is a 7-bit code.
-
- By the way, there are lots of other machines which have even _fewer_
- printable characters than VM/CMS.
-