[standards-jig] UPDATED: Message Delivery Semantics (JEP-0079)

Casey Crabb crabbkw at nafai.dyndns.org
Tue Apr 22 00:11:11 UTC 2003

Another question:

What happens when an expire-on/expire-in has its action set to 'fail'
and the date/time to fail sometime in the distant future. The sender
may not be online at the time the error is generated. What semantic
rules apply? The JEP isn't clear about what happens and the examples
are mixed about what rules show up in the semantics tag of the message
of type error.

  <message to='foo at host.org/res' from='bar at example.com/ser' type='chat'>
    <semantics xmlns='http://jabber.org/protocol/msg-delivery'>
      <rule condition='expire-on' value='20040101' action='fail'/>

  January 2 of 2004 roles around and the message still hasn't been
delivered. bar at example.com/ser might or might not be online. What
packet should be send back as an error?

My thought is that the error sent back should not have a
http://jabber.org/protocol/msg-delivery namespaced element directly
under message at all. Example:

<message to='bar at example.com/ser' from='foo at host.org/res' type='error'>
  <error code='500' class='app'>Delivery failed
    <stanza-condition xmlns='http://jabber.org/protocol/msg-delivery/error>
      <delivery-failed xmlns:msg='http://jabber.org/protocol/msg-delivery'>
        <msg:rule condition='expire-on' value='20040101' action='fail'/>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20030421/cf054216/attachment.sig>

More information about the Standards mailing list