> From: Vivek Talwar [[email protected]] > > So SIP message can have multiple priv-values in privacy header but the > combination of "none" with any other priv-value is invalid. So "none" > and "id" is not valid. Although , if present "none" should take > preference over "id"
If the Privacy header is invalid per RFC 3323, if the element were to "guess" how to interpret the Privacy header, there is a high probability that it would fail to provide the privacy functions desired by the user. So the element should reject the request. Looking at RFC 3323 section 5, it appears that the preferred error response for problems with Privacy is 500: If the 'critical' privacy level is present in the Privacy header of a request, then if the privacy service is incapable of performing all of the levels of privacy specified in the Privacy header then it MUST fail the request with a 500 (Server Error) response code. The reason phrase of the status line of the response SHOULD contain appropriate text indicating that there has been a privacy failure as well as an enumeration of the priv-value(s) which were not supported by the privacy service (the reason phrase SHOULD also respect any Accept- Language header in the request if possible). Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
