-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/23/13 7:21 AM, Alexey Melnikov wrote:
> 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:

Hi Alexey,

Thanks for the feedback. When I submitted this I-D to the ISE, I said
that you'd be a potential reviewer. It seems I was right. :-)

> 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

Thanks for the correction. Do most of the header field definitions
allow folding white space? I was trying to make it consistent with
general practices, but I admit that I last looked at this almost 6
years ago. I'll check some of the header fields that are registered
with IANA.

> 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.)

I agree that applying Postel's law here would be appropriate.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSQFPyAAoJEOoGpJErxa2pjMIP/08rovIor+/qvsxM+1O7Z8IP
tvGhvH6eIaLHmpVJ7fNyjc778BGP67dXcEKNsA5wh2HoLX5+kXwModTnp7BrhD3f
S41UGYdmf6wAbsw7GUUvHrCSKEDPxRDKREfCIyI3AidElR4CqJbZz+sF1iPznlkB
l+Ao+F/V/H0PChxhmD7WsRRn1c+EArnNfL5MNTh65wN3n1qrpV/QxBk2LZd6z7Ql
QLlSm0LVy12nYSqmB+3ba4RGA6zMk27WrghqWlfhu49BvGroLG4gA+kEBfUKve+v
j6dy1QatiiLI+CfM3Y0/UoyjPJvKUIvvayxobGGEZ+9ZKE6wlkMNuu3YIFrx/ukI
SfEWvkCSxB+upo8TuX5XdtySrVvGYZd7N/pYXdHYYssERpEKuMZF3EcQF5I63Irx
E0rO5rExPlhDAmaUkwV6g3weddJH3+W4OI4Que74F/5gAhWRe1g1tZ/8Sfq+3ax4
/C4N2YOMyRE7DyqvD30EU7S38/YaJBLTmCt5QNaSEx95dXQ47IXwPlN41cCHuVK5
UgsbMZgKo2gtzG94YXSP+xepYV9SAYX1Mp4T7B0p5zuwq1KzX5inUxsBFqzTrSv6
XJa0M3t6LZD2Qb0Ze2wvqlR5PVnyBUVbTKgckLXYm2zNjjSr3Zv1wpD9VpxYn3oF
BG/+xbWWyD0Tr3GxGFBq
=4Ar2
-----END PGP SIGNATURE-----

Reply via email to