Subject: Proposed agenda for the Sieve WG meeting in Vancouver

From: Alexey Melnikov <[email-masked]>
Date: Thu, 22 Nov 2007 18:23:21 +0000

Hi folks,
Chairs didn't do their job and forgot to post agenda for Vancouver in time.

Below is my proposed agenda for the Vancouver meeting:

========================================
SIEVE IETF 70, Vancouver, December 2007

Agenda

Document status review                                              ( 5 mins)
Notify (draft-ietf-sieve-notify-10.txt) IETF LC Comments            ( 7 mins)
Notify XMPP (draft-ietf-sieve-notify-xmpp-06.txt) IETF LC Comments  ( 8 mins)
Notify Mailto (draft-ietf-sieve-notify-mailto-05.txt) Status        (20 mins)
IMAP Sieve (draft-ietf-lemonade-imap-sieve-04.txt)                  (20 mins)
Reject/Refuse (draft-ietf-sieve-refuse-reject-05.txt) *             (20 mins)
Mime Loops (draft-ietf-sieve-mime-loop-03.txt) *                    (20 mins)

Non WG documents:
XML representation for Sieve (draft-freed-sieve-in-xml-00.txt) *    (10 mins)
Notify SIP (draft-melnikov-sieve-notify-sip-message-00.txt)         (10 mins)

Total:                  120 mins
=================================

Items marked with * depend on presence of editors for corresponding documents.

Comments?

Regards,
Alexey

Date: Thu, 22 Nov 2007 18:23:21 +0000
From: Alexey Melnikov <[email-masked]>
To: MTA filtering mailing list <[email-masked]>
Subject: Proposed agenda for the Sieve WG meeting in Vancouver
Sender: [email-masked]

Hi folks,
Chairs didn't do their job and forgot to post agenda for Vancouver in time.

Below is my proposed agenda for the Vancouver meeting:

========================================
SIEVE IETF 70, Vancouver, December 2007

Agenda

Document status review                                              ( 5 mins)
Notify (draft-ietf-sieve-notify-10.txt) IETF LC Comments            ( 7 mins)
Notify XMPP (draft-ietf-sieve-notify-xmpp-06.txt) IETF LC Comments  ( 8 mins)
Notify Mailto (draft-ietf-sieve-notify-mailto-05.txt) Status        (20 mins)
IMAP Sieve (draft-ietf-lemonade-imap-sieve-04.txt)                  (20 mins)
Reject/Refuse (draft-ietf-sieve-refuse-reject-05.txt) *             (20 mins)
Mime Loops (draft-ietf-sieve-mime-loop-03.txt) *                    (20 mins)

Non WG documents:
XML representation for Sieve (draft-freed-sieve-in-xml-00.txt) *    (10 mins)
Notify SIP (draft-melnikov-sieve-notify-sip-message-00.txt)         (10 mins)

Total:                  120 mins
=================================

Items marked with * depend on presence of editors for corresponding documents.

Comments?

Regards,
Alexey

From: The IESG <[email-masked]>
To: [email-masked], [email-masked]
Reply-To: [email-masked]
Date: Fri, 09 Nov 2007 12:39:37 -0500
Subject: ID Tracker State Update Notice: draft-ietf-sieve-notify
Sender: [email-masked]

'State Changes to In Last Call from Last Call Requested by Amy Vezza'
ID Tracker URL: https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13695&rfc_flag=0

To: IETF-Announce <[email-masked]>
From: The IESG <[email-masked]>
Subject: Last Call: draft-ietf-sieve-notify (SIEVE Email Filtering:  Notifications) to Proposed Standard 
Reply-To: [email-masked]
Cc: <[email-masked]>
Date: Fri, 09 Nov 2007 12:39:37 -0500
Sender: [email-masked]

The IESG has received a request from the Sieve Mail Filtering Language 
WG (sieve) to consider the following document:

- 'SIEVE Email Filtering: Notifications '
   <draft-ietf-sieve-notify-10.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
[email-masked] mailing lists by 2007-11-23. Exceptionally, 
comments may be sent to [email-masked] instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-10.txt

IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13695&rfc_flag=0

From: The IESG <[email-masked]>
To: [email-masked], [email-masked]
Reply-To: [email-masked]
Date: Fri, 09 Nov 2007 12:28:30 -0500
Subject: ID Tracker State Update Notice: draft-ietf-sieve-notify
Sender: [email-masked]

'State Changes to Last Call Requested from AD Evaluation::AD Followup by Lisa Dusseault'
ID Tracker URL: https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13695&rfc_flag=0

To: [email-masked]
Cc: [email-masked]
From: [email-masked]
Subject: I-D Action:draft-ietf-sieve-notify-10.txt 
Date: Fri, 09 Nov 2007 11:30:01 -0500
Sender: [email-masked]

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title           : SIEVE Email Filtering: Notifications
	Author(s)       : A. Melnikov, et al.
	Filename        : draft-ietf-sieve-notify-10.txt
	Pages           : 21
	Date            : 2007-11-09

Users go to great lengths to be notified as quickly as possible that
they have received new mail.  Most of these methods involve polling
to check for new messages periodically.  A push method handled by the
final delivery agent gives users quicker notifications and saves
server resources.  This document does not specify the notification
method but it is expected that using existing instant messaging
infrastructure such as XMPP, or SMS messages will be popular.  This
draft describes an extension to the Sieve mail filtering language
that allows users to give specific rules for how and when
notifications should be sent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-10.txt

To remove yourself from the I-D Announcement list, send a message to
[email-masked] with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-sieve-notify-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-notify-10.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email-masked]"

Content-Type: text/plain
Content-ID:     <[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-notify-10.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-notify-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2007-11-09112535.I-D\@ietf.org>

--OtherAccess--

--NextPart--

To: [email-masked]
Cc: [email-masked], [email-masked], [email-masked], [email-masked], [email-masked]
From: IETF I-D Submission Tool <[email-masked]>
Subject: New Version Notification for draft-ietf-sieve-notify-10 
Date: Fri, 09 Nov 2007 11:25:38 -0500
Sender: [email-masked]

A new version of I-D, draft-ietf-sieve-notify-10.txt has been successfuly submitted by Alexey Melnikov and posted to the IETF repository.

Filename:	 draft-ietf-sieve-notify
Revision:	 10
Title:		 SIEVE Email Filtering: Notifications
Creation_date:	 2007-11-07
WG ID:		 sieve
Number_of_pages: 21

Abstract:
Users go to great lengths to be notified as quickly as possible that
they have received new mail.  Most of these methods involve polling
to check for new messages periodically.  A push method handled by the
final delivery agent gives users quicker notifications and saves
server resources.  This document does not specify the notification
method but it is expected that using existing instant messaging
infrastructure such as XMPP, or SMS messages will be popular.  This
draft describes an extension to the Sieve mail filtering language
that allows users to give specific rules for how and when
notifications should be sent.

The IETF Secretariat.

To: IETF-Announce <[email-masked]>
From: The IESG <[email-masked]>
Subject: Last Call: draft-ietf-sieve-notify-xmpp (Sieve Notification  Mechanism: xmpp) to Proposed Standard 
Reply-To: [email-masked]
Cc: <[email-masked]>
Date: Fri, 09 Nov 2007 10:30:08 -0500
Sender: [email-masked]

The IESG has received a request from the Sieve Mail Filtering Language 
WG (sieve) to consider the following document:

- 'Sieve Notification Mechanism: xmpp '
   <draft-ietf-sieve-notify-xmpp-06.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
[email-masked] mailing lists by 2007-11-23. Exceptionally, 
comments may be sent to [email-masked] instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-xmpp-06.txt

IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14161&rfc_flag=0

From: The IESG <[email-masked]>
To: [email-masked], [email-masked]
Reply-To: [email-masked]
Date: Thu, 08 Nov 2007 11:03:39 -0500
Subject: ID Tracker State Update Notice: draft-ietf-sieve-notify
Sender: [email-masked]

'State Changes to AD Evaluation::Revised ID Needed from Publication Requested by Lisa Dusseault'
ID Tracker URL: https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13695&rfc_flag=0

To: [email-masked]
Cc: [email-masked]
From: [email-masked]
Subject: I-D Action:draft-ietf-sieve-notify-xmpp-06.txt 
Date: Wed, 07 Nov 2007 11:40:02 -0500
Sender: [email-masked]

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title           : Sieve Notification Mechanism: xmpp
	Author(s)       : P. Saint-Andre, A. Melnikov
	Filename        : draft-ietf-sieve-notify-xmpp-06.txt
	Pages           : 11
	Date            : 2007-11-07

This document describes a profile of the Sieve extension for
notifications, to allow notifications to be sent over the Extensible
Messaging and Presence Protocol (XMPP), also known as Jabber.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-xmpp-06.txt

To remove yourself from the I-D Announcement list, send a message to
[email-masked] with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-sieve-notify-xmpp-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-notify-xmpp-06.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email-masked]"

Content-Type: text/plain
Content-ID:     <[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-notify-xmpp-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-notify-xmpp-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2007-11-07113317.I-D\@ietf.org>

--OtherAccess--

--NextPart--

To: [email-masked]
Cc: [email-masked], [email-masked]
From: IETF I-D Submission Tool <[email-masked]>
Subject: New Version Notification for draft-ietf-sieve-notify-xmpp-06 
Date: Wed, 07 Nov 2007 11:33:19 -0500
Sender: [email-masked]

A new version of I-D, draft-ietf-sieve-notify-xmpp-06.txt has been successfuly submitted by Peter Saint-Andre and posted to the IETF repository.

Filename:	 draft-ietf-sieve-notify-xmpp
Revision:	 06
Title:		 Sieve Notification Mechanism: xmpp
Creation_date:	 2007-11-07
WG ID:		 sieve
Number_of_pages: 11

Abstract:
This document describes a profile of the Sieve extension for
notifications, to allow notifications to be sent over the Extensible
Messaging and Presence Protocol (XMPP), also known as Jabber.

The IETF Secretariat.

Cc: Ned Freed <[email-masked]>, Srinivas Saisatish Vedam <[email-masked]>, [email-masked]
Date: Fri, 02 Nov 2007 07:50:12 -0700 (PDT)
From: Ned Freed <[email-masked]>
Subject: Re: About draft-freed-sieve-in-xml-00
To: Stephane Bortzmeyer <[email-masked]>
Sender: [email-masked]

> I like your I-D about Sieve in XML and find it is a good idea.

THanks!

> I have two remarks (not very important).

> First, why did you choose the W3C Schema language instead of RelaxNG?
> I understand it may be a matter of taste, but I'm curious.

I'm much more familiar with W3C Schema. Time permitting we plan to add
a RelaxNG definition to the document.

> Second, to represent Sieve comments, you use XML comments. But a
> conforming XML parser MAY ignore comments so there is a risk that
> round-trip conversion may lose comments. Moreover, your schema (and
> the associated XSL script) forbids to put comments intended for the XML
> version only such as:

> <!-- Produced by sieve2xml on 2007-11-02. Do not edit. -->

> Such comments would be translated back to Sieve, which would be
> unfortunate.

> I suggest instead to create an element <sieve-comments> to store them.

Hmm, good point. A comment element shouldn't be hard to add and use.

				Ned

Date: Fri, 2 Nov 2007 09:25:58 +0100
From: Stephane Bortzmeyer <[email-masked]>
To: Ned Freed <[email-masked]>, Srinivas Saisatish Vedam <[email-masked]>
Cc: [email-masked]
Subject: About draft-freed-sieve-in-xml-00
Sender: [email-masked]

I like your I-D about Sieve in XML and find it is a good idea.

I have two remarks (not very important).

First, why did you choose the W3C Schema language instead of RelaxNG?
I understand it may be a matter of taste, but I'm curious.

Second, to represent Sieve comments, you use XML comments. But a
conforming XML parser MAY ignore comments so there is a risk that
round-trip conversion may lose comments. Moreover, your schema (and
the associated XSL script) forbids to put comments intended for the XML
version only such as:

<!-- Produced by sieve2xml on 2007-11-02. Do not edit. -->

Such comments would be translated back to Sieve, which would be
unfortunate.

I suggest instead to create an element <sieve-comments> to store them.