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
