40 likes | 158 Views
This document outlines the latest changes to the IMDN (Instant Message Disposition Notification) specifications as discussed in IETF67. Key updates include the consolidation of terminology for enhanced readability, the introduction of a "Processing" state, and the renaming of headers to IMDN-Record-Route and IMDN-Route. A RelaxNG schema has been created to address IMDN routing in MSRP. Additionally, we explore whether to explicitly forbid certain headers in MSRP and consider the definition of an "In-Progress" state, incorporating percentage transferred details.
E N D
IMDN Hisham Khartabil Eric Burger SIMPLE WG IETF67
Changes since -00 • Consolidated terminology and restructured to make it more readable • Introduced “Processing” IMDN • Renamed Really-From and Really-To headers to IMDN-Record-Route and IMDN-Route • Created a RelaxNG schema
Issue 1: IMDN routing in MSRP • IMDN-Record-Route and IMDN-Route header are useful for URI-List servers for page-mode IMs • Do not make much sense for MSRP • Should we explicitly forbid them from an MSRP SEND, say they are useless, or don’t say anything?
Issue 2: “In-Progress” state • “Processing” Notification has “processed” and “stored” as states. • OMA would like “in-progress” state with other information like %age transferred. • Should we add? If so, what indications are needed?