GPGSplit output

[Matthias Frank]

> You'll need to reed the rfc (at http://ietf.org/rfc/rfc2440.txt --
> hand-crafted link, but I believe it's very close). I believe the
document
> is quite clearly written; you might need to have a look at the newest
draft of
> rfc2440bis (use google - version 7 or 8 is the newest, not sure) as
some of
> the features gpg uses are not documented in the current standard yet.

Hi Adrian,

thx for your reply. I've read the 2440. 

Here an example what i mean, first a gpgsplitted example 
public key:

98 8B 04 3E F9 DC 5A 01 04 00 9E FE 46 92 CB 26 70 04 23 B3 
1E 34 71 1A 93 84 BF B9 BD 5C 7B 0F 7B 49 6A 9C C0 0C A6 91 
92 23 F4 84 38 AF 8D B6 F6 B2 64 EE 3A C1 3E 92 F6 68 88 EA 
D6 7F DE C1 A9 1E 05 56 51 50 C3 AE 9D 5E AC F3 50 A5 97 E4 
2E 07 5C 4A 96 B6 10 56 88 07 18 EA 23 44 1E D9 65 2D A8 6E 
FA C5 12 71 6C B5 55 F8 A9 9E C6 AA A0 9B 74 9D 91 4D DF 5C 
56 12 0D B2 3E DE 6E DE F3 F0 DE 44 0A 41 27 1A 23 41 00 06 
29

According to the RFC, the third byte (04) stands for the version,
the following four bytes (3E F9 DC 5A) are the timestamp, the
following (01) is for the used algorithm and the next two
(04 00 hex = 1024 dec.) is for the length of the public key.
What for are the first 2 bytes (98 8B)? Even if I "kill" these
mentioned bytes (should be 10) there are still 131, where 128
should be.

Greetz,
Matthias