
From wwwrun@rfc-editor.org  Mon Jun 25 10:32:41 2012
Return-Path: <wwwrun@rfc-editor.org>
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 BFBD821F853B; Mon, 25 Jun 2012 10:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.535
X-Spam-Level: 
X-Spam-Status: No, score=-104.535 tagged_above=-999 required=5 tests=[AWL=0.542, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, 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 ZAQuJXgL1MaN; Mon, 25 Jun 2012 10:32:41 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 1D67721F84E6; Mon, 25 Jun 2012 10:32:41 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 919E6B1E008; Mon, 25 Jun 2012 10:31:45 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120625173145.919E6B1E008@rfc-editor.org>
Date: Mon, 25 Jun 2012 10:31:45 -0700 (PDT)
Cc: marf@ietf.org, rfc-editor@rfc-editor.org
Subject: [marf] RFC 6650 on Creation and Use of Email Feedback Reports: An Applicability Statement for the Abuse Reporting Format (ARF)
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: Mon, 25 Jun 2012 17:32:41 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6650

        Title:      Creation and Use of Email 
                    Feedback Reports: An Applicability Statement for 
                    the Abuse Reporting Format (ARF) 
        Author:     J. Falk, M. Kucherawy, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2012
        Mailbox:    none, 
                    superuser@gmail.com
        Pages:      15
        Characters: 35273
        Updates:    RFC5965

        I-D Tag:    draft-ietf-marf-as-16.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6650.txt

RFC 5965 defines an extensible, machine-readable format intended for
mail operators to report feedback about received email to other
parties.  This applicability statement describes common methods for
utilizing this format for reporting both abuse and authentication
failure events.  Mailbox Providers of any size, mail-sending
entities, and end users can use these methods as a basis to create
procedures that best suit them.  Some related optional mechanisms are
also discussed.  [STANDARDS-TRACK]

This document is a product of the Messaging Abuse Reporting Format Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From wwwrun@rfc-editor.org  Mon Jun 25 10:44:44 2012
Return-Path: <wwwrun@rfc-editor.org>
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 275F211E8095; Mon, 25 Jun 2012 10:44:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.854
X-Spam-Level: 
X-Spam-Status: No, score=-101.854 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, 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 pLIwkLJoDSxM; Mon, 25 Jun 2012 10:44:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 9C46A11E8073; Mon, 25 Jun 2012 10:44:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id F0717B1E017; Mon, 25 Jun 2012 10:32:06 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120625173206.F0717B1E017@rfc-editor.org>
Date: Mon, 25 Jun 2012 10:32:06 -0700 (PDT)
Cc: marf@ietf.org, rfc-editor@rfc-editor.org
Subject: [marf] RFC 6652 on Sender Policy Framework (SPF) Authentication Failure Reporting Using the Abuse Reporting Format
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: Mon, 25 Jun 2012 17:44:44 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6652

        Title:      Sender Policy Framework (SPF) Authentication 
                    Failure Reporting Using the Abuse Reporting 
                    Format 
        Author:     S. Kitterman
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2012
        Mailbox:    scott@kitterman.com
        Pages:      8
        Characters: 15373
        Updates:    RFC4408

        I-D Tag:    draft-ietf-marf-spf-reporting-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6652.txt

This memo presents extensions to the Abuse Reporting Format (ARF) and
Sender Policy Framework (SPF) specifications to allow for detailed
reporting of message authentication failures in an on-demand fashion.

This memo updates RFC 4408 by providing an IANA registry for SPF
modifiers.  [STANDARDS-TRACK]

This document is a product of the Messaging Abuse Reporting Format Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From wwwrun@rfc-editor.org  Mon Jun 25 10:44:44 2012
Return-Path: <wwwrun@rfc-editor.org>
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 7B9C311E8073; Mon, 25 Jun 2012 10:44:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.858
X-Spam-Level: 
X-Spam-Status: No, score=-101.858 tagged_above=-999 required=5 tests=[AWL=0.142, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, 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 Ei3jjgS7wMmW; Mon, 25 Jun 2012 10:44:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id E0AB711E8091; Mon, 25 Jun 2012 10:44:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C4965B1E008; Mon, 25 Jun 2012 10:31:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120625173155.C4965B1E008@rfc-editor.org>
Date: Mon, 25 Jun 2012 10:31:55 -0700 (PDT)
Cc: marf@ietf.org, rfc-editor@rfc-editor.org
Subject: [marf] RFC 6651 on Extensions to DomainKeys Identified Mail (DKIM) for Failure Reporting
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: Mon, 25 Jun 2012 17:44:44 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6651

        Title:      Extensions to DomainKeys Identified Mail 
                    (DKIM) for Failure Reporting 
        Author:     M. Kucherawy
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2012
        Mailbox:    superuser@gmail.com
        Pages:      18
        Characters: 35028
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-marf-dkim-reporting-16.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6651.txt

This document presents extensions to the DomainKeys Identified Mail
(DKIM) specification to allow for detailed reporting of message
authentication failures in an on-demand fashion.  [STANDARDS-TRACK]

This document is a product of the Messaging Abuse Reporting Format Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From iesg-secretary@ietf.org  Tue Jun 26 10:06:39 2012
Return-Path: <iesg-secretary@ietf.org>
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 3C72A21F85FB; Tue, 26 Jun 2012 10:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, 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 9SS+rAPjHBkE; Tue, 26 Jun 2012 10:06:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9F3521F85F0; Tue, 26 Jun 2012 10:06:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.21
Message-ID: <20120626170638.10365.81623.idtracker@ietfa.amsl.com>
Date: Tue, 26 Jun 2012 10:06:38 -0700
Cc: marf@ietf.org
Subject: [marf] WG Action: Conclusion of Messaging Abuse Reporting Format (marf)
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: Tue, 26 Jun 2012 17:06:39 -0000

The Messaging Abuse Reporting Format (marf) Working Group in the =

Applications Area has concluded. The IESG contact persons are Barry =

Leiba and Pete Resnick.

The RFC Editor has published the final MARF documents, and the working
group has finished its work and is now closing. The Applications ADs
thank the anti-abuse community for its work in producing Abuse
Reporting Format standards and related information. Special
posthumous thanks go to the late JD Falk, who worked on his
contributions through periods of hospitalization.

The mailing list <marf@ietf.org> will remain open for related discussions.

From sm@resistor.net  Tue Jun 26 11:26:05 2012
Return-Path: <sm@resistor.net>
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 647CA21F85AD for <marf@ietfa.amsl.com>; Tue, 26 Jun 2012 11:26:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, 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 iZ3BYus7UODK for <marf@ietfa.amsl.com>; Tue, 26 Jun 2012 11:26:02 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 750AF21F85AA for <marf@ietf.org>; Tue, 26 Jun 2012 11:26:02 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5QIPtSu014295; Tue, 26 Jun 2012 11:25:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1340735160; i=@resistor.net; bh=NKoRmgz83H9mAb+dBBV6BP5Ot3jIaFerIePcDbLh0CE=; h=Date:To:From:Subject:Cc; b=phc/ygLRSo4G0RaV5FOn3BxeWgkFS6PcR37T7sOffB88dzrmeoK6vs5+mDMvFD1yu 2ckvTLhA9auZbPFyxxLhFT9K64bUOQ388BG/f1oW17AUKB9c4oi10bxF4sSJx/z9Ss txIUYQM0JC6zvItUwUI7eZ9tCOJXo7/qIbTld0VQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1340735160; i=@resistor.net; bh=NKoRmgz83H9mAb+dBBV6BP5Ot3jIaFerIePcDbLh0CE=; h=Date:To:From:Subject:Cc; b=INXBIh9ZreR2l6a1G5C8uyNG6Ih5eHkgYjWMrh40CFM722NGa06V47OckJXuos5xS sl22m72WCs6FoDe699zTjK7ZOEIhs0u2zOhsiVCW3zYWsJihklxJAOIRTmITP2VB7I Qy+Ldrko2yQBWHbM9u5pRplsMs+KBmL4czQJvy5I=
Message-Id: <6.2.5.6.2.20120626111934.0a7de9f0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 26 Jun 2012 11:25:23 -0700
To: "Murray S. Kucherawy" <superuser@gmail.com>
From: SM <sm@resistor.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: marf@ietf.org
Subject: [marf] IANA Modifier Names registry
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: Tue, 26 Jun 2012 18:26:05 -0000

Hi Murray,

I noticed that the IANA Modifier Names (SPF) registry references 
draft-ietf-marf-spf-reporting-10.  Shouldn't that be updated to RFC 6652?

Regards,
-sm


From superuser@gmail.com  Tue Jun 26 13:00:28 2012
Return-Path: <superuser@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 A20B221F85E6 for <marf@ietfa.amsl.com>; Tue, 26 Jun 2012 13:00:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.454
X-Spam-Level: 
X-Spam-Status: No, score=-3.454 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 z8tmBViMnA9O for <marf@ietfa.amsl.com>; Tue, 26 Jun 2012 13:00:27 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 999B721F85DF for <marf@ietf.org>; Tue, 26 Jun 2012 13:00:26 -0700 (PDT)
Received: by bkty8 with SMTP id y8so352870bkt.31 for <marf@ietf.org>; Tue, 26 Jun 2012 13:00:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FJGphzUuTCgUuYtnjxsSe/8pmMBoODEYFzKn3B8LfSM=; b=U2aJkUaM1QJuly9hn1GDGAgfiM4bKYOJNFmU/BVudgWZcysEYxR2UPNc5MCOg7ktOF iOKqx2gKJqgfVMSgIyzJ1i0LXESNRslYD1xA+KI1CZJiw6GqDZ7TF/P4SSYpYXrBqoae QK6TmFk31QOFw744NroiDijZbXRMLlgeiUpomG1awd06jd7fl9xkcJ/v5UXZzNI/w0nk 6TJ2ZHcA47dh6hm39TK/VaI/HxEEBPpRM8LkkdXdLInpiVL34XNEx4hmS/FP3g5/T3PT uVdzlCbcCEuAen8eHL95OrVV9IcPPJq6N6I0Dx1sv4kIP9W1E0/GO569qmU6diENXX7r +alg==
MIME-Version: 1.0
Received: by 10.152.104.171 with SMTP id gf11mr17679672lab.5.1340740825044; Tue, 26 Jun 2012 13:00:25 -0700 (PDT)
Received: by 10.112.89.3 with HTTP; Tue, 26 Jun 2012 13:00:24 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120626111934.0a7de9f0@elandnews.com>
References: <6.2.5.6.2.20120626111934.0a7de9f0@elandnews.com>
Date: Tue, 26 Jun 2012 13:00:24 -0700
Message-ID: <CAL0qLwYgDZ1CpN=E83D6F9_KcBkEVZXqMVVSiEwh54wYC57JAQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=f46d04083de79cd7ba04c3658c3a
Cc: marf@ietf.org
Subject: Re: [marf] IANA Modifier Names registry
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: Tue, 26 Jun 2012 20:00:28 -0000

--f46d04083de79cd7ba04c3658c3a
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 26, 2012 at 11:25 AM, SM <sm@resistor.net> wrote:

> Hi Murray,
>
> I noticed that the IANA Modifier Names (SPF) registry references
> draft-ietf-marf-spf-reporting-**10.  Shouldn't that be updated to RFC
> 6652?
>
>
I imagine if IANA doesn't do that on its own in the next couple of days,
someone should drop them a note.

-MSK

--f46d04083de79cd7ba04c3658c3a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 26, 2012 at 11:25 AM, SM <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:sm@resistor.net" target=3D"_blank">sm@resistor.net</a>&gt;</span> wrote:<=
br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Murray,<br>
<br>
I noticed that the IANA Modifier Names (SPF) registry references draft-ietf=
-marf-spf-reporting-<u></u>10. =A0Shouldn&#39;t that be updated to RFC 6652=
?<br>
<br></blockquote><div><br>I imagine if IANA doesn&#39;t do that on its own =
in the next couple of days, someone should drop them a note.<br><br>-MSK <b=
r></div></div><br>

--f46d04083de79cd7ba04c3658c3a--
