SIEVE WG minutes - Quebec, Jul. 2011

Intro from chairs wrt document status: four RFCs published, one draft in WG last call.

Include discussion. WG LC complete. Minor changes being worked on. Will send to IESG as soon as new draft is posted.

IMAP-SIEVE. Some new reviews in. Comments to be incorporated.Still need review from Ned. Question: do we need two separate capabilities? Barry suggests using same string - will do that if no comments. Interaction with metadata issue: name of script in metadata can point to external or another metadata item. Ned suggests using full URI. Chris: must be able to interoperate with ManageSIEVE. Does include also need to reference by URI? Keep names the same in ManageSIEVE and IMAP - implementations ought to be able to do that with the same backend store - allows referring to them as simple names. IMAP server would need to advertise what its ManageSIEVE server is. Still need to discuss this more on the mailing list.

Convert. Just got some reviews and comments will be addressed. Now has a separate convert action. Do we need a way to discover available conversions? Put conversion list in ManageSIEVE? More reviews needed.

Notify SIP: Addressed latest reviews. Last issue: in SIEVE notify the URI scheme identifies the notification scheme, but sip allows for a bunch of other URIs, e.g.: tel:. It is probably OK for us to just stick with sip/sips for now. Again reviews needed.

ManageSIEVE quota: proposal to add quota check error codes into ManageSIEVE. Will quota for mail store and sieve scripts be different? One implementation uses different quotas. Other implementations might want a "global" quota for all a user's data. Might need two separate codes to distinguish sieve over quota vs all stuff over quota.

WG Futures: have various incomplete items. AD: we also have a burst of energy when we meet, but items sitting on the floor never seem to be picked up. AD: lets finish the active items, and if others aren't being done, then we drop them. Chair proposal: finish work on active documents, then see if there is any new work to be done and determine whether to shut down WG. ManageSIEVE quota could go as individual - no adoption of it now. AD: for non-active items - effectively decided to remove from charter. No objections in the room to the plan.