>
>> It's basically a minimal encoding to deal only
>> with the flaws found in actual NNTP implementations (such as not coping
>> with nuls and unmatched CR or LF characters) and dot-stuffing, and is
>> pretty close to not compressing.
Which do you think makes more sense for encapsulating John's CDAT data,
something that looks more like BDAT (length indicator), or something
that looks more like yEnc ("quoted unprintable")?
Definitely something like CDAT. Although the choice between a CDAT command
and session-level compression isn't clear to me.
Ned
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp