Re: [apps-discuss] Spam reporting over IMAP

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 10 January 2012 19:31 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88FD621F8723 for <apps-discuss@ietfa.amsl.com>; Tue, 10 Jan 2012 11:31:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level:
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Nl5DFua3wK9 for <apps-discuss@ietfa.amsl.com>; Tue, 10 Jan 2012 11:31:30 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id BA57C21F86FF for <apps-discuss@ietf.org>; Tue, 10 Jan 2012 11:31:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1326223888; d=isode.com; s=selector; i=@isode.com; bh=SByEQ55Ur7HkSpYJpngBYTqFfM8+hb7nJnyqAG/Vsds=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=uwzn5u0iUGLQvvm3NJPmNEWrfF2yZZY0/wXyspXKugX2FGLGLQDgLNlNxRK40ZtU4Lk2m6 I1E5LIGdzOUf7oA76Fsx0cYqFBvqEV3Qx6RbAyrc90D99qSIhOr8lx0GkSxTlRZBqK3M3N yfmbn0wUBW+rVQUjf2O4yyxnn4zALUE=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <TwySDABOhVAS@rufus.isode.com>; Tue, 10 Jan 2012 19:31:28 +0000
Message-ID: <4F0C921C.8010402@isode.com>
Date: Tue, 10 Jan 2012 19:31:40 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
References: <F5833273385BB34F99288B3648C4F06F19C6C157A4@EXCH-C2.corp.cloudmark.com> <F0F3F170FC88900571B5E5E9@PST.JCK.COM> <F5833273385BB34F99288B3648C4F06F19C6C157C6@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F19C6C157C6@EXCH-C2.corp.cloudmark.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Spam reporting over IMAP
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jan 2012 19:31:30 -0000

On 09/01/2012 23:48, Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: John C Klensin [mailto:john-ietf@jck.com]
>> Sent: Monday, January 09, 2012 3:38 PM
>> To: Murray S. Kucherawy
>> Cc: apps-discuss@ietf.org
>> Subject: Re: [apps-discuss] Spam reporting over IMAP
>>
>> Conclusion:
>>
>> Not ready from prime time.  Not even ready for a careful and
>> comprehensive review.
>>
>> You asked.
> I did, and thanks for that.
>
> I think at this point perhaps a higher-level question is in order: Are we (either IETF in general, or APPSAWG specifically) interested in or willing to put time into developing this in conjunction with OMA?  Would this be something ultimately beneficial to have, and have it come from us?
>
> I suppose I'm also concerned with the idea of an external SDO, on getting a "no" from us, deciding they want to do this anyway so they publish their own (unsanctioned, of course) IMAP extension only to have it see some level of ubiquity as a result.  Indeed it may be possible that this is coming to us only because some OMA member organizations have already developed and are deploying this, at least experimentally.  There's friction between geopriv and OMA's LOC WG of this nature already which I'd just as soon resolve sooner rather than later somehow.
As an individual participant:
I don't think this is yet deployed, but there is a need in something 
like that and yes, there is a risk that OMA will do the job if IETF says 
"no", but does so badly. (Not a strong argument to do anything, but if 
we (IETF) want to help, I think we should.)

I am happy to work on something in this space. But I am not going to do 
that if nobody else is interested.
(I don't have an opinion yet on whether this belongs to APPSAWG, but I 
am happy to help out either way.)