> -----Original Message----- > From: Eric Burger [mailto:[EMAIL PROTECTED] > Sent: Friday, November 28, 2008 4:34 PM > > As far as handling one good and one bad Info Package: that is actually > a total non-issue (sorry Hadriel). The SIP stack understands the Info > Packages by virtue of indicating Recv-Info, there being an Info- > Package header, and the body being of the correct type. If there is a > single Info-Package that was not advertised in a Recv-Info, tough: the > whole SIP transaction fails (the INFO request). If all of the Info- > Packages are supported, but the contents of one of them is bad, tough: > the SIP transaction succeeded (200 OK). It is up to the application to > handle the particular bad package payload. That is 100% identical to > what the UAS does if it receives a single well-formed, but bad, INFO > request. Send the 200 OK and let the application sort out the body. > SIP has done its job - don't be a layer violator and conflate an > application error with a transport error!
I'm not, at least I don't think so. :) I said it adds protocol complexity to handle failure of processing of more than one info package body-part in a single INFO. Why? Because we would have to specify what order they get processed in, because that may affect what happens in the application layer. When it's just one package for an INFO, we don't have to say anything. But anyway that one piece was a minor point. :) -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
