On Mon, 2006-05-15 at 14:28 -0500, Rhys D Ulerich wrote: > On receipt of a valid NOTIFY within an existing dialog and with the > correct Content-Type, what should the subscriber's behavior be if the > NOTIFY message content is invalid or malformed? E.g. for the RFC > 3856-defined presence event package, what should a subscriber do if the > incoming PIDF document is malformed?
It seems to me that there should be a defined 4xx code for "body is invalid for its declared content-type". > After a scan through RFCs 3265 and 3856 I'm not seeing anything that > directly addresses this point. I'm hesitant to just kick back a 4xx > response because that may cause the subscription to be torn down > prematurely, and the bad XML may be a one-time thing. On the other hand, if the software is well-written, the bodies should *never* be invalidly formatted. So I would argue that implementations should turn such "soft" errors into gross and obvious failures, so implementors correct their code. Dale --- interop.pingtel.com -- the public SIP phone interoperability test server _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
