Re: [marf] marf-base and OMA SpamRep convergence and OMA SpamRep comment
Yakov Shafranovich <yakov@shaftek.org> Sun, 01 August 2010 12:51 UTC
Return-Path: <yakov@shaftek.org>
X-Original-To: marf@core3.amsl.com
Delivered-To: marf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A542B3A6874 for <marf@core3.amsl.com>; Sun, 1 Aug 2010 05:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.253
X-Spam-Level: *
X-Spam-Status: No, score=1.253 tagged_above=-999 required=5 tests=[AWL=-2.968, BAYES_05=-1.11, DRUGS_MUSCLE=0.01, FM_FORGED_GMAIL=0.622, FRT_SOMA2=2.199, MANGLED_SOMA=2.5]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jCGlOrN7JJvN for <marf@core3.amsl.com>; Sun, 1 Aug 2010 05:51:38 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 07A103A6C31 for <marf@ietf.org>; Sun, 1 Aug 2010 05:49:57 -0700 (PDT)
Received: by eyb7 with SMTP id 7so1181208eyb.31 for <marf@ietf.org>; Sun, 01 Aug 2010 05:50:23 -0700 (PDT)
Received: by 10.213.16.144 with SMTP id o16mr2613935eba.62.1280667023237; Sun, 01 Aug 2010 05:50:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.47.67 with HTTP; Sun, 1 Aug 2010 05:50:03 -0700 (PDT)
In-Reply-To: <E41787825008234A9B8BB93D603C8B0F170405@bobo1.bobotek.net>
References: <BB012BD379D7B046ABE1472D8093C61C01F716664D@EXCH-C2.corp.cloudmark.com> <E41787825008234A9B8BB93D603C8B0F170405@bobo1.bobotek.net>
From: Yakov Shafranovich <yakov@shaftek.org>
Date: Sun, 01 Aug 2010 08:50:03 -0400
Message-ID: <AANLkTinyvdfVeXX4LHRytc63vnTkfm2Sg8V__04W0=nH@mail.gmail.com>
To: Alex Bobotek <alex@bobotek.net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: DAVID.K.SMITH@att.com, marf@ietf.org
Subject: Re: [marf] marf-base and OMA SpamRep convergence and OMA SpamRep comment
X-BeenThere: marf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Message Abuse Report Format working group discussion list <marf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/marf>, <mailto:marf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/marf>
List-Post: <mailto:marf@ietf.org>
List-Help: <mailto:marf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/marf>, <mailto:marf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Aug 2010 12:51:40 -0000
Alex, One comment on your slides: MARF does not support multiple messages explicitly because of RFC 3462. We had some preliminary discussions about that a while back but at the time it was determined that a separate standard would be needed for reporting aggregate data. There was an "Incidents" header which indicates multiple duplicate spam messages but only one message is actually included in the report. Regarding XML mapping, we should consider a more generic mechanism that maps SMTP and email to HTTP transport, as opposed to making a specific mapping for this. Some examples: http://www.openhealth.org/documents/xmtp.htm http://tools.ietf.org/html/draft-dusseault-httpmail-00 http://tools.ietf.org/html/draft-maes-lemonade-http-binding-04 There have also been attempts in the past to map between MMS/SMS and email: http://tools.ietf.org/html/rfc5442 http://tools.ietf.org/html/rfc4356 There is also some discussion about server to server notifications: http://tools.ietf.org/html/rfc5551 On Sun, Aug 1, 2010 at 1:57 AM, Alex Bobotek <alex@bobotek.net> wrote: > Here’s some more on Open Mobile Alliance’s(OMA’s) ‘SpamRep’ mobile spam > reporting draft standard. > > > > In the spirit of avoiding industry-fragmentation from competing > abuse-reporting standards, I put some thought into whether and how marf-base > and SpamRep might converge, particularly in the area of mobile abuse > reporting. “Towards Converged Message Abuse Reporting”, presented at > IETF78.MARF, identifies some key convergence issues along with a proposed > roadmap: http://www.ietf.org/proceedings/78/slides/marf-0.pdf. I’d like to > encourage any in MARF WG to explore and comment on this here in > marf@ietf.org. > > > > ------------------------------------ > > > > Also, as Murray posted, OMA’s SpamRep abuse reporting standard is now under > review. Here are some links and more information. The OMA documents are > public, however only OMA members can formally submit change requests; but of > course Murray and I (who are employed by OMA members and can submit change > requests) are interested in everyone’s comments. If your company is a > member, you can apply for a login (not needed to simply view docs) at > http://www.openmobilealliance.org . > > > > OMA has the concept of an “enabler.” The SpamRep enabler includes: > > > > · A draft technical specification: > http://member.openmobilealliance.org/ftp/Public_documents/COM/COM-SpamRep/Permanent_documents/OMA-AD-SpamRep-V1_0-20090911-D.zip > > · An XSD for the XML: > http://member.openmobilealliance.org/ftp/Public_documents/COM/COM-SpamRep/Permanent_documents/OMA-SUP-XSD_spam_rep-V1_0-20100707-D.zip > > · An architecture document: > http://member.openmobilealliance.org/ftp/Public_documents/COM/COM-SpamRep/Permanent_documents/OMA-AD-SpamRep-V1_0-20090911-D.zip > > · Test requirements: > http://member.openmobilealliance.org/ftp/Public_documents/COM/COM-SpamRep/Permanent_documents/OMA-ETR-SpamRep-V1_0-20100628-D.zip > > > > Regards, > > > > Alex Bobotek > > alex@bobotek.net > > > > > > > > From: marf-bounces@ietf.org [mailto:marf-bounces@ietf.org] On Behalf Of > Murray S. Kucherawy > Sent: Thursday, July 29, 2010 4:17 AM > To: 'marf@ietf.org' > Subject: [marf] OMA SpamRep document > > > > As was discussed in the MARF meeting this week, here’s a link to the OMA > SpamRep document’s current form. > > > > http://member.openmobilealliance.org/ftp/Public_documents/COM/COM-SpamRep/Permanent_documents/OMA-TS-SpamRep-V1_0-20100708-D.zip > > > > It is under what’s called Consistency Review, which is vaguely similar to a > combination of WGLC and IETF LC, so it’s late to be providing feedback to > them, but if you have something major you’d like to bring to their attention > you can send it to me or to Alex Bobotek (AT&T) who also presented this > week. > > > > You should certainly read this if you’re interested in participating in the > effort to work toward a merged format specification. > > > > -MSK > > _______________________________________________ > marf mailing list > marf@ietf.org > https://www.ietf.org/mailman/listinfo/marf > >
- [marf] OMA SpamRep document Murray S. Kucherawy
- Re: [marf] OMA SpamRep document John Levine
- [marf] marf-base and OMA SpamRep convergence and … Alex Bobotek
- Re: [marf] marf-base and OMA SpamRep convergence … Yakov Shafranovich