-----BEGIN PGP SIGNED MESSAGE-----
Congratulations to Jon & Co. on the new draft. Much good bumf added.
Much as I hate to harp on the same example, I'm still dubious about
the example ASCII armoured message in 6.6; this time for two different
reasons.
First, isn't the count wrong? This time it's a new-style packet that
claims to be 42 bytes long (familiar number, there), but there is
only one byte of compression type followed by 40 bytes of data, so
it seems to me the count should be 41 (41 shall be the number of
the counting. 42 is straight out).
Second, unlike the example this one replaces, the compressed data
decompresses to straight text rather than to a valid literal packet.
Section 10.2 says decompressing a Compressed Data packet must yield a
valid OpenPGP Message, and this one doesn't. Am I misunderstanding the
spec here? It also differs from the original example in that it has an
explicit length rather than an old-style arbitrary length... is that the
difference, and, if so, should this different behaviour be documented?
Salvo Salasio <coderpunks(_at_)toad(_dot_)com>
Key ID = 0xFFFFFFFF
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQEPAwUBNT9YWcNH+A3/////AQEBEwfNE/VytU9M3kgLWukdbMWM7LvI1iyxnucU
/7ehZRwYv00bLqX7Zelp+k5vn5GEysSWBPycIetYugX0yLPod6cPSh2gXCj2jVSl
ESPEyfTC4rqlDJKUJg3UR6yVs+m4r+ugunPVNJpEodsj7l8NriCaxhpzuZdlXcFc
szDDWLwIQbfrCsGOhdW6zc8gHow0AtWtJlD3UCebUkl2rMR9XGA07t+NuavXn9ql
wMf5L3n5ZnyY2ut7PlYNJem10JUIfr/6+blOqpwZ3a5JjMYBPEtvi0M1sPAS2Ctr
u1Lxs0iLvMNOM2In5hzGEigGwZbWlrULZRPr+tk5AxaTHA==
=ZQda
-----END PGP SIGNATURE-----