Re: [marf] Benoit Claise's Discuss on draft-ietf-marf-as-14: (with DISCUSS and COMMENT)

Barry Leiba <barryleiba@computer.org> Wed, 25 April 2012 12:45 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: marf@ietfa.amsl.com
Delivered-To: marf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B33E921F8700; Wed, 25 Apr 2012 05:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level:
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 XFgERZhmITnn; Wed, 25 Apr 2012 05:45:28 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 09C2421F86C5; Wed, 25 Apr 2012 05:45:27 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so26955qcs.31 for <multiple recipients>; Wed, 25 Apr 2012 05:45:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=PJqg7v0UYaDNiT52q08BFzI13+gD/iHjJDOyxnHCbq4=; b=v4VXFdQSIwMlWvcxn+yDxvnj6r0uDDjNHIY+8Cmg/qTcDVA/m64AcZ+8vNVGaGC96M fxd2+EI96NpvkoFVbUZuQSEgPZ4qQjH6Vstz2aCbO0ZvY8y8IqrldS7uylm27GRJxgq+ Mo8DwTsZAccO+8NfQHhaHDaNmAjnTj3P8ItZOUjSV++lHHo3T9ZhaXnBq00uTXMdkKOM Qxq2ps3W9SQyWR+Rfs4g+BIjh88tw3e9/kAXjDGhPXkRRxKgHbxsZBRZNnBRaxP5mJrK Qu46JaDgFccD1AzgZWLRSUbsD0sSsC3yaCUErnMcNxkkeRslNl1p7laTX5euJrulO19k +ixQ==
MIME-Version: 1.0
Received: by 10.224.184.70 with SMTP id cj6mr1812270qab.77.1335357927600; Wed, 25 Apr 2012 05:45:27 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.229.220.19 with HTTP; Wed, 25 Apr 2012 05:45:27 -0700 (PDT)
In-Reply-To: <4F97EF53.9070408@cisco.com>
References: <20120423094450.10355.95358.idtracker@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392810193D@exch-mbx901.corp.cloudmark.com> <4F97CC0C.6010209@cisco.com> <CALaySJJmpyj-j=ybsLzwJdNHcYwgTOuhA+U4CezmRpx3TgLX+A@mail.gmail.com> <4F97EF53.9070408@cisco.com>
Date: Wed, 25 Apr 2012 08:45:27 -0400
X-Google-Sender-Auth: SF9gXjVhedbHlCeDqDQ9KN-ndDw
Message-ID: <CALaySJLRGU9rAXf81y6=ZmuAvnqTQnF1=OTMmdRWxANxu613sQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "draft-ietf-marf-as@tools.ietf.org" <draft-ietf-marf-as@tools.ietf.org>, "marf-chairs@tools.ietf.org" <marf-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "marf@ietf.org" <marf@ietf.org>
Subject: Re: [marf] Benoit Claise's Discuss on draft-ietf-marf-as-14: (with DISCUSS and COMMENT)
X-BeenThere: marf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Message Abuse Report Format working group discussion list <marf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 25 Apr 2012 12:45:29 -0000

>> Yes, 2.  But an AS doesn't necessarily (perhaps usually doesn't) cover
>> every use case.  Consider the greylisting document that's also on this
>> week's telechat: it's describing how to use SMTP for a specific use
>> case, to do a specific thing.  Many AS documents will be of that
>> nature, talking about certain use cases, but not every possible one.
>
> https://datatracker.ietf.org/doc/draft-ietf-appsawg-greylisting/ is
> different, as its scope is well defined, starting with the title: "Email
> Greylisting: An Applicability Statement for SMTP"
> On the other hand, "Creation and Use of Email Feedback Reports: An
> Applicability Statement for the Abuse Reporting Format (ARF)" points to a
> generic ARF application statement... which is not.

Hm.  This doesn't cover all use cases for ARF any more than
greylisting covers all use cases for SMTP, so I don't see the point.
But I'll leave it to Murray to respond further on this.  Maybe he has
some other thoughts.[1]

Barry

[1] Well, of course, he does... but I mean thoughts related to this point.