[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NULL

To: Rick Troth <troth@xxxxxxxxxxx>
Subject: Re: NULL
From: michael.derrico@xxxxxxxxxxxx (Michael D'Errico)
Date: Wed, 26 Oct 1994 13:37:22 -0700 (PDT)
Cc: ietf-822@xxxxxxxxxxxxxxxxxx
In-reply-to: <>

On Wed, 26 Oct 1994, Rick Troth wrote:

> > If [an MTA] claims support for RFC 1652 and changes bare CR's, bare 
> > LF's, or LFCR to CRLF, then it is broken. 
>  
> 	Taking Michael a little out of context:  I need to reply 
> with the subject line  "Lessons Learned"  regarding conversions. 

As long as this is done ABOVE the transport layer, and only to text parts
where this is not considered corruption, I would agree.  If the transport
layer does not "preserve all bits in each octet" then it is broken.  (Or
RFC 1652 is broken.)

Michael D'Errico
Software.com

References:
- Re: NULL
  - From: Rick Troth

Prev by Date: Re: About C-T-Es and transports (Re: NULL)
Next by Date: Re: unregistered subtypes in MIME
Previous by thread: Re: NULL
Next by thread: The dual meaning of c-t-e's
Index(es):
- Date
- Thread