On Thursday 11 December 2003 19:04, David Shaw wrote:
I disagree we need to change anything here. There is already only one
separator permitted. Using your example:
Version: 1.0.0 non-commercial, upgrade to Version: 2.0.0-commercial
The second instance of colon-space is NOT a separator. It's just part
of the value.
As long as the line is not split, you are correct.
This isn't very complicated. I'd be quite surprised to hear of any
parser that didn't do:
a) Find the leftmost colon-space.
b) The string to the left is the key.
c) The string to the right is the value.
That's how email works (note the subject line of this message has two
colons!), how news works, and how OpenPGP works.
With one notable difference: in the case any MTA splits headerlines, it will
add space(s) in front of the next line, which is defined to continue the line
in RFC822. When a MUA or MTA splits body lines it will not add anything
(maybe except for some ">" characters). So the receiving system will not be
able to tell the difference between a new header line an a continuation.
I'm a newbie to implementing OpenPGP - so please forgive me, if my question is
stupid: why consider the additional headers at all? They seem to me to only
have any value to human readers and none at all to OpenPGP itself, since all
important information is already encoded into the binary message blocks (once
you got them out of their armor). Is there any technical reason for the RFC
not saying "Implementations shall ignore header lines."?
Konrad
pgp80TNPbWpxg.pgp
Description: signature