idnits 2.17.1 draft-kucherawy-marf-source-ports-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 7, 2012) is 4372 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'CFWS' is mentioned on line 94, but not defined Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Individual submission R. Clayton 3 Internet-Draft University of Cambridge 4 Updates: 5965, 6591 (if approved) M. Kucherawy 5 Intended status: Standards Track Cloudmark, Inc. 6 Expires: November 8, 2012 May 7, 2012 8 Source Ports in ARF Reports 9 draft-kucherawy-marf-source-ports-03 11 Abstract 13 This document defines an additional header field for use in Abuse 14 Reporting Format reports to permit the identification of the source 15 port of the connection involved in an abuse incident. 17 This document updates RFC5965 and RFC6591. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on November 8, 2012. 36 Copyright Notice 38 Copyright (c) 2012 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Source-Port Field Definition . . . . . . . . . . . . . . . . . 3 56 4. Time Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 58 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 59 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 7.1. Normative References . . . . . . . . . . . . . . . . . . . 4 61 7.2. Informative References . . . . . . . . . . . . . . . . . . 5 62 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 5 64 1. Introduction 66 [ARF] defined the Abuse Reporting Format, an extensible message 67 format for Email Feedback Reports. These reports are used to report 68 incidents of email abuse. ARF was extended by [AUTHFAILURE-REPORT] 69 to enable reporting of email authentication failures. These 70 specifications provided for the source IP address to be included in a 71 report. As explained in [LOG], the deployment of IP address sharing 72 techniques requires the source port values to be included in reports 73 if unambiguous identification of the origin of abuse is to be 74 achieved. 76 This document defines an ARF reporting field to contain this 77 information and provides guidance for its use. 79 2. Keywords 81 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 82 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 83 document are to be interpreted as described in [KEYWORDS]. 85 3. Source-Port Field Definition 87 A new ARF header field called "Source-Port" is defined. When present 88 in a report, it MUST contain the TCP source port matching the 89 "Source-IP" field in the same report, thereby describing completely 90 the origin of the abuse incident. 92 Per, [ABNF], the formal syntax is: 94 source-port = "Source-Port:" [CFWS] 1*DIGIT [CFWS] CRLF 96 "CFWS" is imported from [MAIL]. 98 When any report is generated that includes the "Source-IP" reporting 99 field (see Section 3.2 of [ARF]), this field SHOULD also be present, 100 unless the port number is unavailable. 102 Use of this field is RECOMMENED for reports generated per 103 [AUTHFAILURE-REPORT] (see Section 3.1 of that document). 105 4. Time Accuracy 107 [LOG] underscores the importance of accurate clocks when generating 108 reports that include source port information because of the fact that 109 source ports can be recycled very quickly in Internet Service 110 Provider environments. The same considerations described there apply 111 here. 113 Report generators that include an Arrival-Date report field MAY 114 choose to express the value of that date in Universal Coordinated 115 Time (UTC) to enable simpler correlation with local records at sites 116 that are following the provisions of [LOG]. 118 5. IANA Considerations 120 IANA is requested to add the following entry to the Feedback Report 121 Header Fields registry: 123 Field Name: Source-Port 125 Description: TCP source port from which the reported connection 126 originated 128 Multiple Appearances: No 130 Related Feedback-Type: any 132 Reference: [this document] 134 Status: current 136 6. Security Considerations 138 This extension introduces no new security considerations not already 139 covered in [ARF]. 141 Some security considerations related to the general topic of source 142 port logging can be found in [LOG]. 144 7. References 146 7.1. Normative References 148 [ABNF] Crocker, D. and P. Overell, "Augmented BNF for 149 Syntax Specifications: ABNF", STD 68, RFC 5234, 150 January 2008. 152 [ARF] Shafranovich, Y., Levine, J., and M. Kucherawy, 153 "An Extensible Format for Email Feedback 154 Reports", RFC 5965, August 2010. 156 [AUTHFAILURE-REPORT] Fontana, H., "Authentication Failure Reporting 157 using the Abuse Report Format", RFC 6591, 158 April 2012. 160 [KEYWORDS] Bradner, S., "Key words for use in RFCs to 161 Indicate Requirement Levels", BCP 14, RFC 2119, 162 March 1997. 164 [MAIL] Resnick, P., Ed., "Internet Message Format", 165 RFC 5322, October 2008. 167 7.2. Informative References 169 [LOG] Durand, A., Gashinsky, I., Lee, D., and S. 170 Sheppard, "Logging Recommendations for 171 Internet-Facing Servers", RFC 6302, June 2011. 173 Appendix A. Acknowledgements 175 The authors wish to acknowledge the following for their review and 176 constructive criticism of this proposal: Steve Atkins, Scott 177 Kitterman, John Levine, and Doug Otis. 179 The idea for this work originated within the Messaging Anti-Abuse 180 Working Group (MAAWG). 182 Authors' Addresses 184 Richard Clayton 185 University of Cambridge 186 Computer Laboratory 187 JJ Thomson Avenue 188 Cambridge CB3 0FD 189 United Kingdom 191 Phone: +44 1223 763570 192 EMail: richard.clayton@cl.cam.ac.uk 194 Murray S. Kucherawy 195 Cloudmark, Inc. 196 128 King St., 2nd Floor 197 San Francisco, CA 94107 198 US 200 Phone: +1 415 946 3800 201 EMail: msk@cloudmark.com