Closed guusdk closed 1 day ago
Council said the MUST is better changed to a SHOULD so it is backward compatible with implementations that don’t include it.
Further discussion in the Council MUC suggest that most (if not all) Council members also agree to retaining the MUST when a note is added to comment on compatibility with earlier versions of the specification. I've pushed such a note moments ago.
Even if no reason or alternate venue is provided, a
<destroy/>
element is needed to distinguish between other presence unavailable.