Jim,
From: James M Galvin <galvin(_at_)tis(_dot_)com>
Subject: summary of technical issues
Date: Wed, 21 Dec 1994 12:09:00 -0500
If I've overlooked a technical issue please send me a note I'll take
care of it right away.
[deleted]
2. Suggestion to canonicalize text line breaks prior to encryption
Currently the specification requires the line break canonicalization
for the digital signature service but not for the encryption service.
It was pointed out that MIME should handle the necessary
canonicalization for encryption.
I've not received a separate note for (2) yet but I go to my third
comment for PEM/MIME. (I have two more things to say.)
If line break canolicalization is adopted for encryption, following
comment is also applied to the encryption service.
draft-ietf-pem-sigenc-02.txt allows CTE: 7bit, 8bit and binary for CT:
multipart/{signed, encrypted}. But draft-ietf-pem-mime-07.txt
denies the use of 8bit and binary. I think this is not good idea.
My suggestion is that CTE: 8bit should be allowed for its body part,
at least for CT: text/plain. 7bit domain charset like US-ASCII and ISO
2022 does not get trouble with the 7bit domain limitaion. For 8bit
domain charset like ISO 8859 x, however, this limitaion is very much
inconvenient. As you explained the intention of MIC-CLEAR before,
pepole want to sign up an *original* (non-encoded) text.
I've not found the strong reason to deny CTE: 8bit. Since it's line
based, the line break cononicalization is easy to apply for CTE: 8bit.
On the day of 8BITMIME, limiting to 7bit is not good idea.
--Kazu