> -----Original Message----- > From: DRAGE, Keith (Keith) [mailto:[EMAIL PROTECTED] > Sent: Monday, December 08, 2008 6:25 PM > > > That's not always technically possible, AFAICT. If the body > > content is bad, there's no guarantee it even got to the app-layer. > > > > Now you are getting really confused on layers. These are the circumstances > where the correct error is 4xx - 6xx indicating that the SIP level was > unable to deliver to the application.
Ummm... no, that was the point *I* was making. :) Someone *else* in the email said: > > So I don't think we need we need a way of indicating in an INFO > > response problems with body content in the request. Let the > > application send an INFO request in the reverse direction. And I said that's not always possible - the app layer may have no idea about a malformed body content arriving. We need to allow 4xx-6xx to be body *content* formatting errors too. I.e., if you send me an INFO for a package "myXml" with body-part of C-T "application/xml" and that body-part's content is in fact just the string ":-P", I should be able to respond with a 4xx. The question is what the xx should be. -hadriel _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
