Re: [marf] Abuse reporting, was draft-jdfalk-marf-as

Alessandro Vesely <vesely@tana.it> Fri, 01 July 2011 09:05 UTC

Return-Path: <vesely@tana.it>
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 20E8521F88C2 for <marf@ietfa.amsl.com>; Fri, 1 Jul 2011 02:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.032
X-Spam-Level:
X-Spam-Status: No, score=-5.032 tagged_above=-999 required=5 tests=[AWL=-0.313, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9wYT6Wc6Nqqt for <marf@ietfa.amsl.com>; Fri, 1 Jul 2011 02:05:28 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 023E221F88C3 for <marf@ietf.org>; Fri, 1 Jul 2011 02:05:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1309511126; bh=gI5FY+StetDs/8mI250ZH+ZkxeeuyVkLstiqwnH4Q9I=; l=2268; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=Qusz4lKWiQeQYX9ck4X2BoD2hnFNa5zzEp9gEq7eeNtlhnskgjFrM6+QDJix2VZC4 dOEJNzZ2pYPoJZmSYVk4fwQgnWoy86y3WMzg6byQjZSDaToih8xaLXigt4H4ePAmMB ohZju3sLc2LFeVgmItBsEPTEilYSo93FzPdQv2qs=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Fri, 01 Jul 2011 11:05:26 +0200 id 00000000005DC039.000000004E0D8DD6.00002CF1
Message-ID: <4E0D8DD6.3030501@tana.it>
Date: Fri, 01 Jul 2011 11:05:26 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: marf@ietf.org
References: <20110623192929.13813.qmail@joyce.lan> <4E04B896.5010604@tana.it> <F5833273385BB34F99288B3648C4F06F134EBC4AB8@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC4AB8@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: [marf] Abuse reporting, was draft-jdfalk-marf-as
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: Fri, 01 Jul 2011 09:05:29 -0000

On 29/Jun/11 19:42, Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: ietf.org On Behalf Of Alessandro Vesely
>> 
>> I think a document is needed in order to state the "obvious" facts
>> that RIRs don't have the scope for discussing.  Since JD said it
>> cannot be part of the FBL AS, we'd probably better write a new one.
>> 
>> Is it possible to do so?
> 
> We'd have to recharter to do it.  For now if you want to get
> started, post it as an individual submission, and later we can
> consider rechartering to take it on.

Hm, the charter provides for an "ARF guidelines document".  Couldn't
this non-FBL guidelines be considered a part of a multi-part document,
together with the FBL AS, the cfblbcp, and the redaction docs?
Anyway, I'll try and post an individual submission if you think that's
the right thing to do.

> Also, John pointed you at the WEIRDS pre-working-group list.  ICANN
> people approached me about starting that effort up, and right now
> they're exploring requirements.  There will probably be a bar BoF
> at the Quebec City conference next month followed by a lobby to
> create a working group later on once they get some momentum going.

Hmm, the concluded Web Elucidation of Internet-Related Developments
has nothing to do with this, has it?  IETF's "concluded" page also
mentions a Whois and Network Information Lookup Service concerned with
a historical son-of-WHOIS protocol...

> It's true that any standard we produce won't compel a WHOIS
> provider to give out information it doesn't want to make available,
> but ICANN does have a little more stomping power on registrars than
> the IETF does.

It seems ARIN, APNIC, LACNIC, and RIPE already have abuse team
contacts, and are possibly adjusting related procedures, such as
removing query rate limits.  AfriNIC is apparently discussing that.

It is still unclear who should do what in this evolving scenario.
There are lots of web pages entitled something like How To Complain To
The Spammer's Provider, most of which are reminiscent of a time when
there were no means to automate abuse reporting.  Updating such
documentation is clearly out of WHOIS providers' scope.

What is this WG's opinion about such an additional document?