Re: transformative content-transfer-encoding in core profiles

> everyone--
> 
> What should a BEEP peer do when it receives an initial greeting message 
> in a transformative content transfer encoding?
> 
> For example:
> 
> 	RPY 0 0 . 0 nnn
> 	Content-Type: application/beep+xml; charset="iso-8859-1"
> 	Content-Transfer-Encoding: quoted-printable
> 
> 	<greeting/>
> 	END
> 
> RFC 3080 seems to be silent on the subject.
> 
> If the IETF ever revises the BEEP core specification, is it possible we 
> might see an outright ban on the use of the Content-Transfer-Encoding 
> entity header in all of the core profiles?  At least a strong 
> recommendation against?

hmmm... i don't think that seeing a CTE on channel zero is any different than seeing a CTE on any other channel. it's just wrong. each channel is supposed to be 8-bit clean. can anyone come up with a reason as to why a CTE is needed?

if not, then i think this falls under the category of "being liberal in what you accept"...if an implementation treated it as a fatal error, i wouldn't complain about that...

/mtr