* Ben Escoto wrote:
From section 3.1.1 of the draft:
:RfC 2015 ... contains all information necessary to strip or apply this layer.
:It may make use of the Ascii Armor layer, but the octect stream may also
:encoded directly using MIME itself.
The above seems to permit PGP output not being ascii-encoded
but rather base-64 encoded. Is my interpretation correct?
Yes.
The section implies that nothing from rfc2015 has changed, but section 2
of that document says "The ASCII armor output is the REQUIRED method
for data transfer."
True. So our RfC will update RfC 2015.
So, can the octet-stream portion of PGP/MIME messages be a
base64 encoding of 8-bit PGP output? Thanks.
Yes, that's the solution to choose in future (IMHO). There is no need for a
special session layer in the session layer. Of course, it's not backward
compatible to software do not understand MIME, but this does not harm.