Steve Gardell (sgardell@iperia.com)
Thu, 8 Nov 2001 16:42:41 -0500
> -----Original Message-----
> From: Shapira, Noam [mailto:Shapira_Noam@icomverse.com]
> Sent: Thursday, November 08, 2001 12:11 PM
> To: snap@lists.neystadt.org; vpim@lists.neystadt.org
> Cc: ietf-imapext@imc.org
> Subject: SNAP question
>
>
>
> Hi all,
>
> The SNAP next version is in it's final stages. As you can
> recall the SNAP
> draft defines the protocol between a messaging system (e.g.
> email server,
> voice mail) and a Notification Service. There are a few last
> open issues
> that I would be happy if I got some suggestions.
>
> In the last IETF (in London) I got some suggestions that it
> is important to
> mention the issue of configuring the SNAP in the messaging
> system - i.e. add
> the SNAP option for a user, configure the notification
> service he will use,
> what type of request will be sent for this user (new message,
> login, logout,
> etc.), the amount of retries and other options given in the SNAP.
>
> The big question is how should it be done?
>
> There are a few options like extensions of ACAP, LDAP, Sieve
> based protocol
> and others. Another option is that this is not an interesting
> questions and
> should be left open for different implementation.
>
This would tend to be my inclination based on the observation that
messaging system provisioning is currently outside the scope
of standard protocols. This feels like just another piece
of user provisioning to me in the same general vein as quotas,
etc. If it were to be standardized I would suggest following
the general lead of the SIP subscribe/notify proposals.
> Noam
>
This archive was generated by hypermail 2.0b3 on Thu Nov 08 2001 - 23:43:38 IST