Im fine with leaving it in since it is the most commonly used format. As
you say, it isnt mandatory anyway.
On Tue, Mar 17, 2015 at 11:35 AM Derek Atkins <warlord(_at_)mit(_dot_)edu>
wrote:
Wyllys Ingersoll <wyllys(_at_)gmail(_dot_)com> writes:
Agree. Perhaps there could multiple optional-to-implement formats -
ASCII
Armor, JSON, pure base64, XML (*ugh*), etc - each specified separately.
4880 section 6 has a very detailed description of the ASCII format -
should
that be pulled out into a separate document and just referenced in the
core
spec?
It could, but that actually *adds* complexity instead of reducing it.
IMHO it's much nicer, from an implementation point of view, to have
everything in one document instead of having to go off and reference a
dozen or more documents.
If you don't want to implement section 6 in your implementation then
just skip section 6.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord(_at_)MIT(_dot_)EDU PGP key available
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp