> I don't see anything in the material you quote > that says whether or not the quoted diversion > and the unquoted diversion mean the same thing. > They are both reasons, but are they the same reason? > In this context it seems probable that they > ought to mean the same thing, but its not entirely clear. > > I *presume* the point here is to allow values > with the form of tokens to be supplied without > quotes, but also to allow values that require > quotes to be entered with quotes. But it would > have been better if the text was clearer about this.
I agree. I just wasn't sure if there was some default behavior defined somewhere causing quote removal when the contents is being used. Consider the display-name of the From which allows tokens and quoted-string. Since nothing (that I'm aware of) overrides the default behavior, the quotes of a quoted string are actually part of the name to be displayed. Thus it is currently impossible for a user desiring comma within display name to be communicated without is also causing the quotes to be rendered (unless receiver assumes quotes extraneous). Thanks, Brett _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
