[Simple] Re: IM delivery reports for conferencing

On Mar 15, 2006, at 7:30 PM, Sean Olson wrote:

>
> Looking at:
> http://tools.ietf.org/wg/simple/draft-khartabil-simple-im-receipts 
> -00.tx
> t
> And: http://tools.ietf.org/wg/simple/draft-burger-simple-imdn-03.txt
>
> Neither seems to address the use case of an "exploder" or IM
> conferencing where a single IM may have multiple recipients. My
> suggestion is that the schema you choose for the notification allow
> multiple delivery notifications to be batched together with each entry
> distringuished by the recipient URI.

It does address it to an extent. That's what the "uri" attribute is  
there for. If we want to allow aggregation of receipts before sending  
the receipt to the IM sender, then we also need to start thinking about  
what the sender wants and how to indicate it in the IM itself.

Hisham

>
> For example:
>
> For Draft-khartabil-simple-im-receipts-00
>
>          <status-receipt>
>             <message-id>34jk324j</message-id>
>             <recipient uri="bob@example.com">
>                  <type>read</type>
>                  <status>200</status>
>                  <note lang="en">The message has been read</note>
>             </recipient>
>             <recipient uri="alice@example.com">
>                  <type>error</type>
>                  <status>415</status>
>                  <note lang="en">The message could not be
> delivered</note>
>             </recipient>
>          </status-receipt>
>
> Or, for Draft-burger-simple-imdn-03
>
>         <imdn>
>             <original-message-id>
>                1542af3e8b@eburger@example.com
>             </original-message-id>
>             <reporting-uas uri="im:hisham.khartabil@example.net">
>                <original-recipient-uri>
>                   im:hisham.khartabil@example.net
>                </original-recipient-uri>
>                <disposition>read</disposition>
>             </reporting-uas>
>             <reporting-uas uri="im:eric.burger@example.net">
>                <original-recipient-uri>
>                   im:eric.burger@example.net
>                </original-recipient-uri>
>                <disposition>read</disposition>
>             </reporting-uas>
>         </imdn>
>
> Sorry if this has been discussed before. Was there a reason this was
> omitted previously?
>
> Thanks,
> Sean
>

_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple