[Notifications] Re: I-D ACTION:draft-ietf-sieve-notify-02.txt

Alexandros Vellis <avel@noc.uoa.gr> Tue, 07 February 2006 13:11 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6SdK-00056b-EB; Tue, 07 Feb 2006 08:11:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6SdB-00054I-EH for notifications@megatron.ietf.org; Tue, 07 Feb 2006 08:11:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23996 for <notifications@ietf.org>; Tue, 7 Feb 2006 08:09:50 -0500 (EST)
Received: from msa.uoa.gr ([195.134.100.72]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6SpO-0007jX-Ur for notifications@ietf.org; Tue, 07 Feb 2006 08:24:20 -0500
Received: by MSA with id 9644AC95A9E61D4102AD9E9BEE1C59A2E65DD1C1
Received: from null.noc.uoa.gr (null.noc.uoa.gr [195.134.100.40]) (authenticated bits=0) by msa.uoa.gr (8.12.11/8.12.11) with ESMTP id k17DBBmS002855 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 7 Feb 2006 15:11:12 +0200 (EET)
From: Alexandros Vellis <avel@noc.uoa.gr>
To: ietf-mta-filters@imc.org
In-Reply-To: <20060207110513.GA10924@nostromo.freenet-ag.de>
References: <E1F6DJB-0001Ck-JY@newodin.ietf.org> <20060207110513.GA10924@nostromo.freenet-ag.de>
Content-Type: text/plain
Organization: National & Kapodistrian University of Athens
Date: Tue, 07 Feb 2006 15:11:44 +0200
Message-Id: <1139317905.5030.19.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.1
Content-Transfer-Encoding: 7bit
X-UoAMSAId: 9644AC95A9E61D4102AD9E9BEE1C59A2E65DD1C1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
Cc: notifications@ietf.org
Subject: [Notifications] Re: I-D ACTION:draft-ietf-sieve-notify-02.txt
X-BeenThere: notifications@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Message Notifications interest group discussion list <notifications.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/notifications>
List-Post: <mailto:notifications@ietf.org>
List-Help: <mailto:notifications-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=subscribe>
Sender: notifications-bounces@ietf.org
Errors-To: notifications-bounces@ietf.org

[Cc: ing notifications list]

On Tue, 2006-02-07 at 12:05 +0100, Michael Haardt wrote:

> I suggest that allowed modifications MUST or at least SHOULD be
> documented.
> 
>    Usage:  valid_notif_method <notification-uris: string-list>
> 
> Of course that is real easy to implement, but it is also real ugly.
> There is nothing I know of else in Sieve that checks certain options
> of actions for validity.  I still suggest a generic extension for
> exception handling.

I don't know about generic exception handling, but wouldn't it make more
sense, in this particular case, that the available notifications are
present in the capabilities of the Sieve server?

So, just as IMAP4 Capability responds with a set such as AUTH=DIGEST-MD5
AUTH=ANONYMOUS or THREAD=ORDEREDSUBJECT THREAD=REFERENCES, a Sieve
server could respond with "notify notifymethod=mailto
notifymethod=xmpp", or something similar.

For a client implementation that has no idea what is suppored on the
server, this would be ideal. It will also save my client implementation
from an extra configuration option. :)

> Since we broke compatibility with the original draft, I repeat my
> point of view to remove ":method" and change its argument to an
> argument of "notify", as in:
> 
>   notify "mailto:0123456789@sms.example.net";

Good idea. I think that the current plan is a bit awkward. The Cyrus
implementation uses the :options field to define the email address:

 notify :method "mailto" :options "foo@example.org"

draft-ietf-sieve-notify-xmpp on the other hand uses the :method for the
entire destination:

 notify :method "xmpp:romeo@example.com"

How about a 'target' option, or as you suggest, no option at all, and a
general plan to use existing URLs defined in other documents.

For instance:

* mailto URI: 
:target "mailto:foo@example.org?subject=Mail%20Notification"

*XMPP URI according to draft-saintandre-xmpp-iri
:target "xmpp:romeo@example.com"

* SMS URI according to
http://www.ietf.org/internet-drafts/draft-wilde-sms-uri-10.txt :
:target "sms:+41796431851;pid=smtp:erik.wilde@dret.net"

* tel: URI according to RFC3966. Could probably leave a preconfigured,
implementation-specific voice mail message:
:target "tel:+306999999999"

And so on.

-- 
Alexandros Vellis
avel@noc.uoa.gr


_______________________________________________
Notifications mailing list
Notifications@ietf.org
https://www1.ietf.org/mailman/listinfo/notifications