On 21/09/2013 03:34, Peter Saint-Andre wrote:
To my chagrin, I just realized that this header field is in fact registered:
http://www.iana.org/assignments/message-headers/message-headers.xhtml#prov-headers
It's been so long since I looked into this issue that I must have forgotten.
However, I do plan to get an RFC published so that there is stable
documentation for the Jabber-ID header field.
Hi Peter,
Some comments on -10:
Your ABNF in Section 2:
Jabber-ID = SP *WSP pathxmpp *WSP CRLF
And your example in at the end of 3.2 is:
Following the rules in [RFC5122] and the Jabber-ID header field
syntax, the resulting header field might be as shown below (note that
this representation includes folding white space, which is allowed in
accordance with the ABNF):
Jabber-ID:
ji%C5%99i@%C4%8Dechy.example
I think this doesn't match your ABNF I think the ABNF should be:
Jabber-ID = SP [FWS] pathxmpp [FWS] CRLF
For your convenience, the definition of FWS is quoted below:
FWS = ([*WSP CRLF] 1*WSP) / obs-FWS
; Folding white space
I would also make the leading SP optional. While Netnews spec decide to make
this explicit, software should cope with the lack of it. (But I don't feel
strongly about the leading SP, most software always insert it anyway.)
Best Regards,
Alexey
