Avasarala Ranjit-A20990 wrote:
>
> Hi Paul
>
> Below is the semantics for the diversion header from the draft
>
> The syntax of the Diversion header is:
>
> Diversion = "Diversion" ":" 1# (name-addr *( ";" diversion_params ))
> diversion-params = diversion-reason | diversion-counter |
> diversion-limit | diversion-privacy |
> diversion-screen | diversion-extension
> diversion-reason = "reason" "="
> ( "unknown" | "user-busy" | "no-answer" |
> "unavailable" | "unconditional" |
> "time-of-day" | "do-not-disturb" |
> "deflection" | "follow-me" |
> "out-of-service" | "away" |
> token | quoted-string )
> diversion-counter = "counter" "=" 1*2DIGIT
> diversion-limit = "limit" "=" 1*2DIGIT
> diversion-privacy = "privacy" "=" ( "full" | "name" |
> "uri" | "off" | token | quoted-string )
> diversion-screen = "screen" "=" ( "yes" | "no" | token |
> quoted-string )
> diversion-extension = token ["=" (token | quoted-string)]
>
> And an example shows as
>
> | INVITE [EMAIL PROTECTED]>|
> | | | Diversion: [EMAIL PROTECTED] |
> | | | ;reason=unconditional --> no quotes
> here
>
> So by this it means that "deflection" and deflection (without quotes)
> mean the same.
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.
Note that based on token matching, reason=foo should be the same as
reason=Foo. But without some text about it, reason="foo" ought to be
different than reason="Foo". So are reason=Foo and reason="Foo" the
same? Reason=foo and reason="Foo"?
Paul
> Regards
> Ranjit
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Paul Kyzivat
> Sent: Thursday, April 03, 2008 4:05 AM
> To: Brett Tate
> Cc: [email protected]
> Subject: Re: [Sip-implementors] rfc3261 and rfc4485: gen-value
> andquoted-string
>
> I agree with Robert.
>
> The following is a more direct answer to your specific question.
>
> Brett Tate wrote:
>> Greetings,
>>
>> Concerning rfc3261 and rfc4485 usage of gen-value and quoted-string,
>> are the quotes considered part of the value during use?
>>
>> Since I didn't notice a good example within rfc3261, I'll ask more
>> specifically concerning the forbidden draft-levy-sip-diversion. :)
>>
>> 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.
>
> It is really in the realm of the draft that includes the BNF to say what
> these mean.
>
> Paul
>
>> If the answer mentioned within an rfc (excluding strict upon send and
>> lenient upon receive paradigm), please also provide indicate the
>> reference.
>>
>> Concerning rfc3261's display-name, some vendors render the quotes to
>> user and others don't. I didn't notice rfc3261 indicating to de-quote
>
>> the display-name.
>>
>> Concerning auth stuff like realm, the rfc explicitly indicates when
>> de-quote is needed.
>>
>> Thanks,
>> Brett
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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
