1 / 5

IMDN

IMDN. draft-ietf-simple-imdn-00 Hisham Khartabil Eric Burger IETF 66. Changes (1). Draft combines 2 individual submission IMDN now stands for Instant Message Disposition Notification

gavin
Download Presentation

IMDN

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IMDN draft-ietf-simple-imdn-00 Hisham Khartabil Eric Burger IETF 66

  2. Changes (1) • Draft combines 2 individual submission • IMDN now stands for Instant Message Disposition Notification • Endpoints MAY send positive delivery notifications and SHOULD send negative delivery notifications if requested to • Status changed from sip style to strings (“success instead of “200”)

  3. Changes (2) • Added Really-From and Really-To headers • Really-From indicates previous hop (intermediary) in order to send the IMDN • Really-From headers converted to Really-To headers in IMDNs • Aggregation text was added • Message-ID not mandated but needed if sender keeps state (sent items box)

  4. Open Issue 1 • Do we want to allow the sender to invoke the "required" mechanism to tell the recipient to please just reject the message if it does not support IMDN? • I vote NO • Rejecting the IM based on this will reveal such private information about the recipient to the sender.

  5. Open Issue 2 • “An intermediary that forwards an IM may change the recipient address in the CPIM To header field when forwarding (for example, a URI-List server change the recipient address from its own to the address of the final recipient of that message). In this case, the intermediary MUST add a CPIM Original-To header to the CPIM message.” • Is this a problem for end-to-end encryption? If so, how to go through GWs?

More Related