Hi Iñaki, > > Even if you get a good conclusion for this question, the problem would > be: will your xcap server, your SIP presence server and all your SIP > clients sharing the same account interpret such empty <conditions> > element in the same way? If not, you have a problem (as all the > SIMPLE/XCAP implementors) because client-1 couuld render a contact as > blocked while client-2 (same AoR) could render the same contact as > allowed. >
Well, of course I can't do that, but as a client generating this payload, I can prevent if from happening by inserting a 'foo' condition on a different namespace as <conditions> element child. This way the server and clients would evaluate it to false because they don't 'understand' it. Thanks for the input! -- /Saúl http://saghul.net | http://sipdoc.net _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
