[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] INFO Framework - one pakage per INFO
On Dec 9, 2008, at 5:56 PM, Paul Kyzivat wrote:
This seems to make it *incorrect* to return any error response in
the case where the content of the body is incorrect. (For instance
if the syntax of the body part is inconsistent with the Content-Type
declared for that part.
If the syntax is correct enough for the MIME layer t decode the
object, SIP is happy.
For example, let;s say it is an image/jpeg of your girlfriend. If the
SIP Stack can unpack the image/jpeg from the MIME, SIP is happy. If it
turns out to be a bad picture of your girlfriend and makes her look
like the clown from "It", that's not SIP's problem. If it's actually
an image/gif with an erroneous image/jpeg tag on it, that's also not
SIP's problem.
While I am ok with *allowing* the UAS to return a 200 in this case,
I think we go too far to say they UAS MUST NOT return an error for
this situation.
I'm thinking this should be normative, actually. If it's an error that
SIP can't detect, reporting it as a SIP error seems bogus. If we have
to have application-driven errors, we probably need a new response code.
--
Dean
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip