Rohan Mahy (rohan@cisco.com)
Fri, 23 Mar 2001 18:59:28 -0800
Hi,
Glenn asked me to send an update on the SIP message waiting draft to the
list. The current version of the draft is
http://search.ietf.org/internet-drafts/draft-mahy-sip-message-waiting-01.txt
> The SIP WG is in the process of rechartering, and splitting into two
> WGs. Subscribe/Notify is a proposed charter item in the SIP WG, and
> message waiting is a proposed charter item in the proposed SIPPING WG.
>
> draft-roach-sip-subcribe-notify-04.txt -> draft-ietf-sip-...-00
> draft-mahy-sip-message-waiting-01.txt -> -02 or
> draft-ietf-sipping-...-00
>
> Message waiting -01 greatly simplifies and shortens the -00 version.
>
> 1) The generic behavior of SUBSCRIBE/NOTIFY is now greatly clarified
> in [SUB/NTFY] and made consistent with PINT and SIP for presence.
> This message waiting draft is now consistent with [SUB/NTFY].
>
> 2) The XML format has been removed due to lack of immediate
> interest. At a future date, similar functionality may be added as
> another event package with an appropriate MIME type.
>
> 3) An IANA Considerations section was added to register the new
> "application/simple-message-summary" MIME type and the "simple-
> message-summary" SIP event package.
>
> 4) The "flag-list" was removed due to lack of interest and to
> encourage simplicity.
>
> 5) Due to synchronization issues, and the recommendation of the VPIM
> Working Group, support for message count "deltas" was removed.
>
> 6) The Messages-Waiting line in the body is now mandatory.
>
> 7) This version of the draft clarifies the role of caller
> preferences as optional but encouraged.
>
> 8) A set of SMTP-like headers from the triggering messages may now
> optionally follow the message summaries, provided that the resulting
> NOTIFY on UDP fits in a single datagram.
>
> 9) The draft now references draft-ietf-vpim-hint-02.txt for message
content
This archive was generated by hypermail 2.0b3 on Sat Mar 24 2001 - 06:02:16 IDT