Hi all, RFC 3261 sec 19.1.1 says that any SIP URI parameters that are not recognized should be silently ignored.
However, in the case that an invalid (not allowed by ABNF in sec 25) character is encountered (such as a white space or a ^) in a SIP URI on in the Request URI, what should and UAS do? Ex: "INVITE sip:b...@1.2.3.4:5066;parameterName=valueOne valueTwo SIP/2.0\r\n" or "INVITE sip:b...@1.2.3.4:5066;parameterName=valueOne^ SIP/2.0\r\n" I see three possible behaviors that I listed in order of perceived correctness. 1) Answer with a 400 Bad Request - Malformed SIP URI Parameter. 2) Ignore the SIP URI parameter and proceed with the processing of the request. 3) Ignore the request. (Answer nothing) Thank you, Sorin _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
