I just caught up on the armor argument, and suggest that ASCII armor and
MIME are presentation issues, not message element issues.
Therefore, they should be in separate documents from the binary message
elements. A MIME conformant implementation will not necessarily
implement Armor, and vice versa.
To meet the requirements for IETF standard advancement, they will need
to demonstrate their interoperability separately, and thus must be
separate documents.
Note to the editor, could you please standardize on the term "element"
or "message element" instead of "packet". A packet has a well-known
networking definition.
WSimpson(_at_)UMich(_dot_)edu
Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32