Thanks for the responses. Replies inline. > So by this it means that "deflection" and deflection > (without quotes) mean the same.
It depends upon what two things you are considering. The shown deflection within the ABNF does not indicate the use of quotes; thus the quotes are not shown within the example. Because quoted-string is allowed per the ABNF, it means that someone can define a reason value actually having the quotes. However within a SIP message, a non quoted deflection does not match a quoted deflection. They do not match because the default behavior is that they do not match and nothing has overridden the default behavior. For clarity, the non quoted deflection has been defined and has meaning; the quoted deflection has not been defined and no meaning can be automatically assumed. > > diversion-reason = "reason" "=" > > ( ... | "deflection" | ... | token | quoted-string ) > > > > Notice that unquoted deflection is a reason value > > and that quoted-string is also possible. > > If a device uselessly or erroneously > > sends reason="deflection" instead > > of reason=deflection does > > "deflection" have the same meaning as deflection? > > More specifically if a device sends reason="deflection", > > are the quotes considered an error or useless based upon > > the rfc4485, rfc3261, and ABNF? > > In the above, "deflection" in the *rule* means that > the rule will match a sequence of characters that match > the string "deflection" (without the quotes) is a case > insensitive way. The quoted-string part of the rule will > match "deflection" *with* the quotes. > > So the rule will match a message containing deflection > with or without quotes. I don't have the draft in front > of me, so I don't know if there is a semantic difference > between the two. Nothing has assigned a meaning to the quoted deflection. Thus as you mentioned, quoted and non quoted deflection match different parts of the rule; and subsequently nothing has been defined to cause them to be equal. Here is latest version that I found on the web: http://www.softarmor.com/wgdb/docs/draft-levy-sip-diversion-08.txt _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
