Hi Dale, It never occurred to me that "1# thing" meant "thing *( COMMA thing)" (I'm not an HTTP dev). To be honest I thought it was just an error that was never fixed as it never left draft state. I would have to imagine many others have misinterpreted the Diversion draft because of the use of "1#" (I believe this is what prompted this thread to begin with). When I saw rfc6044, I thought to myself "finally someone took the time to update the Diversion syntax to something that made sense." By the way thank you Marianne for doing that.
Now I see after reading the http rfc that the #rule is short hand for *rule followed by a ",". Having never remember seeing an instance of "1#" in any sip rfc's I would argue that it isn't the most intuitive convention for the reader. Now that I understand the #rule I don't care which convention is used, but one could argue there is a reason for sip extension rfc's to stay consistent with rfc3261. Thanks, Brandon On 04/05/2012 06:07 PM, Worley, Dale R (Dale) wrote: > There's a whole lot of confusion stemming from the fact that > people frequently *use* the "1#" repetition, but it is defined in > neither RFC 4234 nor RFC 5234. But it is (as far as I know) > always taken to mean "a comma-separated list of the specified > items". > > The latest reference I can find without actual work is in RFC 6455: > > Sec-WebSocket-Protocol-Client = 1#token > > And RFC 6455 normatively references RFC 5234. But it also > normatively references RFC 2616 for the definition of 1#, and > RFC 2616 has its own complete ABNF definition (which does define > '#'). > > In the context of SIP, 1#thing "should" mean: thing *( COMMA thing ) > > I suspect that the fact that in different contexts, the "comma" of a > comma-separated list differ is why there is no standard definition > of "#" in our ABNF. > > Perhaps there should be an id-nit requiring that RFC 5234 ABNF be > used? > > Ugh, > > Dale > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
