Source Ports in Abuse Reporting Format (ARF) Reports
RFC 6692
| Document | Type |
RFC - Proposed Standard
(July 2012; No errata)
Updates RFC 6591
Was draft-kucherawy-marf-source-ports (individual in app area)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6692 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Barry Leiba | ||
| IESG note | The document shepherd is John Levine <johnl@iecc.com>. | ||
| Send notices to | johnl@iecc.com | ||
Internet Engineering Task Force (IETF) R. Clayton
Request for Comments: 6692 University of Cambridge
Updates: 6591 M. Kucherawy
Category: Standards Track Cloudmark, Inc.
ISSN: 2070-1721 July 2012
Source Ports in Abuse Reporting Format (ARF) Reports
Abstract
This document defines an additional header field for use in Abuse
Reporting Format (ARF) reports to permit the identification of the
source port of the connection involved in an abuse incident.
This document updates RFC 6591.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6692.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Clayton & Kucherawy Standards Track [Page 1]
RFC 6692 ARF Source Ports July 2012
Table of Contents
1. Introduction ....................................................2
2. Keywords ........................................................2
3. Source-Port Field Definition ....................................2
4. Time Accuracy ...................................................3
5. IANA Considerations .............................................3
6. Security Considerations .........................................3
7. References ......................................................4
7.1. Normative References .......................................4
7.2. Informative References .....................................4
Appendix A. Acknowledgements .......................................5
1. Introduction
[ARF] defined the Abuse Reporting Format, an extensible message
format for Email Feedback Reports. These reports are used to report
incidents of email abuse. ARF was extended by [AUTHFAILURE-REPORT]
to enable the reporting of email authentication failures. These
specifications provided for the source IP address to be included in a
report. As explained in [LOG], the deployment of IP address sharing
techniques requires the source port values to be included in reports
if unambiguous identification of the origin of abuse is to be
achieved.
This document defines an ARF reporting field to contain this
information and provides guidance for its use.
2. Keywords
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [KEYWORDS].
3. Source-Port Field Definition
A new ARF header field called "Source-Port" is defined. When present
in a report, it MUST contain the client port of the TCP connection
from which the reported message originated, corresponding to the
"Source-IP" field that contains the client address of that same
connection, thereby describing completely the origin of the abuse
incident.
Per, [ABNF], the formal syntax is:
source-port = "Source-Port:" [CFWS] 1*5DIGIT [CFWS] CRLF
Clayton & Kucherawy Standards Track [Page 2]
RFC 6692 ARF Source Ports July 2012
"CFWS", which represents email-style comments or folding white space,
is imported from [MAIL].
When any report is generated that includes the "Source-IP" field (see
Show full document text