Hi all, 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?
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. See page 14 of RFC 3265: "If the NOTIFY request fails (as defined above) due to an error response, and the subscription was installed using a soft-state mechanism, the notifier MUST remove the corresponding subscription." Thoughts? Thanks, Rhys _______________________________________ Rhys Ulerich WebSphere IMS/SIP SOA Enablement Developer Email: [EMAIL PROTECTED] Office: 512-838-1428 IBM Software Group - Austin, TX _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
