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
        
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

滥用报告格式(ARF)报告中的源端口

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.

本文档定义了用于滥用报告格式(ARF)报告的附加标题字段,以允许识别滥用事件中涉及的连接的源端口。

This document updates RFC 6591.

本文件更新了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.

本文件是互联网工程任务组(IETF)的产品。它代表了IETF社区的共识。它已经接受了公众审查,并已被互联网工程指导小组(IESG)批准出版。有关互联网标准的更多信息,请参见RFC 5741第2节。

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.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息,请访问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.

版权所有(c)2012 IETF信托基金和确定为文件作者的人员。版权所有。

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.

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件,因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本,并提供简化BSD许可证中所述的无担保。

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 ....................................................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
1. 介绍

[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.

[ARF]定义了滥用报告格式,这是一种用于电子邮件反馈报告的可扩展消息格式。这些报告用于报告电子邮件滥用事件。ARF由[AUTHFAILURE-REPORT]扩展,以允许报告电子邮件身份验证失败。这些规范提供了要包含在报告中的源IP地址。如[LOG]中所述,如果要明确识别滥用来源,IP地址共享技术的部署要求在报告中包含源端口值。

This document defines an ARF reporting field to contain this information and provides guidance for its use.

本文件定义了包含此信息的ARF报告字段,并为其使用提供了指导。

2. Keywords
2. 关键词

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
3. 源端口字段定义

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.

定义了一个称为“源端口”的新ARF头字段。当在报告中出现时,它必须包含报告消息来源的TCP连接的客户端端口,对应于包含同一连接的客户端地址的“源IP”字段,从而完全描述滥用事件的来源。

Per, [ABNF], the formal syntax is:

根据[ABNF],形式语法为:

     source-port = "Source-Port:" [CFWS] 1*5DIGIT [CFWS] CRLF
        
     source-port = "Source-Port:" [CFWS] 1*5DIGIT [CFWS] CRLF
        

"CFWS", which represents email-style comments or folding white space, is imported from [MAIL].

“CFWS”表示电子邮件样式的注释或折叠空白,从[MAIL]导入。

When any report is generated that includes the "Source-IP" field (see Section 3.2 of [ARF]), this field SHOULD also be present, unless the port number is unavailable.

生成包含“源IP”字段的任何报告时(参见[ARF]第3.2节),该字段也应存在,除非端口号不可用。

Use of this field is RECOMMENDED for reports generated per [AUTHFAILURE-REPORT] (see Section 3.1 of that document).

建议根据[AUTHFAILURE-REPORT]生成的报告使用此字段(参见该文档的第3.1节)。

4. Time Accuracy
4. 时间精度

[LOG] underscores the importance of accurate clocks when generating reports that include source port information because of the fact that source ports can be recycled very quickly in Internet Service Provider environments. The same considerations described there apply here.

[LOG]强调了在生成包含源端口信息的报告时精确时钟的重要性,因为在Internet服务提供商环境中,源端口可以很快回收。此处所述的注意事项同样适用。

Report generators that include an Arrival-Date report field MAY choose to express the value of that date in Universal Coordinated Time (UTC) to enable simpler correlation with local records at sites that are following the provisions of [LOG].

包含到达日期报告字段的报告生成器可以选择以世界协调时间(UTC)表示该日期的值,以便与遵守[LOG]规定的现场的本地记录进行更简单的关联。

5. IANA Considerations
5. IANA考虑

IANA has added the following entry to the "Feedback Report Header Fields" registry:

IANA已将以下条目添加到“反馈报告标题字段”注册表中:

Field Name: Source-Port

字段名称:源端口

Description: TCP source port from which the original message was received

描述:从中接收原始消息的TCP源端口

Multiple Appearances: No

多次出现:否

Related "Feedback-Type": any

相关“反馈类型”:任何

Reference: [RFC6692]

参考文献:[RFC6692]

Status: current

状态:当前

6. Security Considerations
6. 安全考虑

This extension introduces no new security considerations not already covered in [ARF].

此扩展没有引入[ARF]中尚未涉及的新安全注意事项。

Some security considerations related to the general topic of source port logging can be found in [LOG].

与源端口日志记录的一般主题相关的一些安全注意事项可以在[LOG]中找到。

7. References
7. 工具书类
7.1. Normative References
7.1. 规范性引用文件

[ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.

[ABNF]Crocker,D.和P.Overell,“语法规范的扩充BNF:ABNF”,STD 68,RFC 5234,2008年1月。

[ARF] Shafranovich, Y., Levine, J., and M. Kucherawy, "An Extensible Format for Email Feedback Reports", RFC 5965, August 2010.

[ARF]Shafranovich,Y.,Levine,J.,和M.Kucherawy,“电子邮件反馈报告的可扩展格式”,RFC 59652010年8月。

[AUTHFAILURE-REPORT] Fontana, H., "Authentication Failure Reporting Using the Abuse Reporting Format", RFC 6591, April 2012.

[AUTHFAILURE-REPORT]Fontana,H.,“使用滥用报告格式的认证失败报告”,RFC 65912012年4月。

[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.

[关键词]Bradner,S.,“RFC中用于表示需求水平的关键词”,BCP 14,RFC 2119,1997年3月。

[MAIL] Resnick, P., Ed., "Internet Message Format", RFC 5322, October 2008.

[邮件]Resnick,P.,Ed.,“互联网信息格式”,RFC5322,2008年10月。

7.2. Informative References
7.2. 资料性引用

[LOG] Durand, A., Gashinsky, I., Lee, D., and S. Sheppard, "Logging Recommendations for Internet-Facing Servers", BCP 162, RFC 6302, June 2011.

[LOG]Durand,A.,Gashinsky,I.,Lee,D.,和S.Sheppard,“面向互联网服务器的日志记录建议”,BCP 162,RFC 6302,2011年6月。

Appendix A. Acknowledgements
附录A.确认书

The authors wish to acknowledge the following for their review and constructive criticism of this proposal: Steve Atkins, Scott Kitterman, John Levine, and Doug Otis.

作者希望感谢以下对本提案的审查和建设性批评:史蒂夫·阿特金斯、斯科特·基特曼、约翰·莱文和道格·奥蒂斯。

The idea for this work originated within the Messaging Anti-Abuse Working Group (MAAWG).

这项工作的想法起源于反滥用信息工作组(MAAWG)。

Authors' Addresses

作者地址

Richard Clayton University of Cambridge Computer Laboratory JJ Thomson Avenue Cambridge CB3 0FD United Kingdom

李察克莱顿剑桥大学计算机实验室JJ汤姆逊大道剑桥CB3 0FD英国

   Phone: +44 1223 763570
   EMail: richard.clayton@cl.cam.ac.uk
        
   Phone: +44 1223 763570
   EMail: richard.clayton@cl.cam.ac.uk
        

Murray S. Kucherawy Cloudmark, Inc. 128 King St., 2nd Floor San Francisco, CA 94107 US

MurayS.KuCaWaWy CuldMax公司,128国王圣,第二楼旧金山,CA 94107美国

   Phone: +1 415 946 3800
   EMail: superuser@gmail.com
        
   Phone: +1 415 946 3800
   EMail: superuser@gmail.com