| Excerpts from transarc.system.ietf-822: 24-Sep-91 Re: Question on
| encapsulation Timo Lehtinen(_at_)sti(_dot_)fi (893)
|
| > | The algorithm I use is very simple -- I combine a variety of pieces of
| > | information (including parts of the current message, the local system
| > | name, the current date/time string, etc.) and feed the resulting very
| | long string into a digital signature algorithm.
| ....
| > | The resulting key is encoded into a printable form that's
| > | roughly 40 characters long.
|
| > No offense, but to me this sounds ridiculous. I really don't see
| > any reason to not use the boundary marking concept from RFC-934.
| > (I know RFC-XXXX hasn't had that for a long time).
|
| To recap, the reason not to use the RFC 934 concept was line folding of
| messages in transport. Such line folding (by existing mail-handling
| agents) could corrupt the RFC 934 method.
Well, I can only think of this problem with very heavily nested
bodyparts. Sounds like a moot point to me. Experience shows that
simplicity usually allways wins - even when there would be a
theoretical possibility of failure in the scheme.
Timo