-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9/23/13 9:16 AM, Alexey Melnikov wrote: > On 23/09/2013 15:45, Peter Saint-Andre wrote: >> 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, > Hi Peter, >> 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? > Yes, but there are some inconsistencies in whether they are allowed > at the end of the value.
FWS at the end doesn't sound like a great idea. > Many header fields include "[CWFS]" (folding whitespace with > optional comments) instead of "[FWS]". For simplicity of parsing I > would avoid using these, unless needed. But if you choose to use > [CFWS], that would still be fine. Personally I see no need to allow comments. Keep it simple. So I suggest: Jabber-ID = "Jabber-ID:" [SP] [FWS] pathxmpp CRLF I even wonder about the FWS... 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/ iQIcBAEBAgAGBQJSQGNGAAoJEOoGpJErxa2pTbQP/iaZR1xnV0BhOunDXh/57A0a 9opEqsfPVT2KwJC9VCEmsLmzfmcgxkjZAdxci16RnZvrYyVD49pXvtdpQKaZktub FxZ88VnVjkki5bkQjV6WAVZCs3HofMe5kniXzcl3bxABJL69pQtJIFexmHK9eU/S 3AUfNM63sAKtu6ye7ppTP8HOIFvGwnSuUtToDDnhrtQqG8tHuQxn1hsJs61sCmVR P5fuAVW5LDlSt/W2B8RjCR3zaoPq3YObi3vPtMzUhX8k78Wz1Vd0RM/HoIL41s7e svwfaYIpRW5A41owAEI6w3i7R7UFmIRtSOOP7DrjmMGVRErCD05tQ64EstxISpl+ MlHzIXdioQU5Ods3EQXCeARZWgUcrYQO6p5UejGabCUPviCK3QJVKZcQXrAAh6yO /ste0eQCVf38OrdS313eXmIOMkH5AzdkDdvroGqmaxT3iZ8uIjZ0fS1uO2WP0tje rtajna2l3uVvHUNtFG7i7MO0R1bTNcjmGhsgtB8L2YKGV79BGeJYKIKUoXoxg35c yM9shRD4I3bu+3z9gVReuziulgiHgyX37WNUnL1g8u86gzoEORwhn3ot6cJ/0JpU s/hbOXPEpv79TiYePFDoSqzre5q5uLUaLFbW5m9+pa6tfuhiYz/XTIs4BDDgPH38 QPyVgHtfGPoHvkj7XMI+ =+nR3 -----END PGP SIGNATURE-----
