Re: [marf] WGLC starting for draft-ietf-marf-base-01
Alessandro Vesely <vesely@tana.it> Fri, 09 April 2010 18:02 UTC
Return-Path: <vesely@tana.it>
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 401E83A6862 for <marf@core3.amsl.com>; Fri, 9 Apr 2010 11:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.659
X-Spam-Level:
X-Spam-Status: No, score=-3.659 tagged_above=-999 required=5 tests=[AWL=1.060, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3SbQ5fG6oeM1 for <marf@core3.amsl.com>; Fri, 9 Apr 2010 11:02:03 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 84F203A6890 for <marf@ietf.org>; Fri, 9 Apr 2010 11:01:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tana.it; s=test; t=1270836110; bh=blxqXEjNX2VPaHCpk4HpNFAyx9tK3QuHITOi9N/vxf4=; l=1398; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=U54Z9/rXHlHuUJXamchHJdGz6h63cY3YbYeK4YaUkvyo5ltUZ8gKa3n0dDLXhmiBX q+PxE9Mste5M2RTJQKcZzp+Dh+DMkxdDrqf3nRzAOCoUjvKLt5LDBwkLIEdsHnGKen QMDvQuZ34SgOVfRXOlcdE4t/PgCGX64T5ppdoMjk=
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, 09 Apr 2010 20:01:50 +0200 id 00000000005DC035.000000004BBF6B8E.0000139F
Message-ID: <4BBF6B8D.1030901@tana.it>
Date: Fri, 09 Apr 2010 20:01:49 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: marf@ietf.org
References: <BB012BD379D7B046ABE1472D8093C61C01CF9478A6@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <BB012BD379D7B046ABE1472D8093C61C01CF9478A6@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [marf] WGLC starting for draft-ietf-marf-base-01
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: Fri, 09 Apr 2010 18:02:05 -0000
"Reported-Domain" is unspecified by design. Fine :-( However, it is not clear whether it may appear multiple times even if the report covers a single incident. As for using "Reported-URI" for the spamvertized mailbox, I just note that IODEF's draft-cain-post-inch-phishingextns (now in LC) calls that "Collection Site". The phrase "a URI to which the report recipient can go for further details", instead, suggests something like http://example.com/arf-generators/XYZ-v1.04b/meaning-of-fields.html I propose to replace that phrase with just "See next Section 3.4". (Will there be an applicability statement to clarify how meanings may be negotiated, eventually?) Section 7.3 still says "MAIL FROM:<>". See the end of http://www.ietf.org/mail-archive/web/marf/current/msg00641.html Should the security section mention that automatically forwarding an abuse report to the wrong party may leak sensible information, especially if the report had been inadvertently generated by a user? (The intro says something about supporting mail clients.) Should "http://www.mipassoc.org/arf/" in the examples be replaced with something with like the first http link above? (Should the spec RECOMMEND that the meaning of fields is stated that way?) In appendix B2, the Authentication-Results looks bogus. In addition, the caption says "Example 3" rather than 2.
- [marf] WGLC starting for draft-ietf-marf-base-01 Murray S. Kucherawy
- Re: [marf] WGLC starting for draft-ietf-marf-base… Alessandro Vesely
- Re: [marf] WGLC starting for draft-ietf-marf-base… J.D. Falk
- Re: [marf] WGLC starting for draft-ietf-marf-base… Yakov Shafranovich
- Re: [marf] WGLC starting for draft-ietf-marf-base… SM
- Re: [marf] WGLC starting for draft-ietf-marf-base… Alessandro Vesely
- Re: [marf] WGLC starting for draft-ietf-marf-base… Murray S. Kucherawy
- Re: [marf] WGLC starting for draft-ietf-marf-base… Murray S. Kucherawy
- Re: [marf] WGLC starting for draft-ietf-marf-base… Murray S. Kucherawy
- Re: [marf] WGLC starting for draft-ietf-marf-base… Murray S. Kucherawy
- Re: [marf] WGLC starting for draft-ietf-marf-base… Murray S. Kucherawy
- Re: [marf] WGLC starting for draft-ietf-marf-base… SM
- Re: [marf] WGLC starting for draft-ietf-marf-base… SM
- Re: [marf] WGLC starting for draft-ietf-marf-base… SM
- Re: [marf] WGLC starting for draft-ietf-marf-base… Murray S. Kucherawy
- Re: [marf] WGLC starting for draft-ietf-marf-base… J.D. Falk
- Re: [marf] WGLC starting for draft-ietf-marf-base… Shmuel Metz (Seymour J.)