idnits 2.17.1 draft-kucherawy-marf-source-ports-01.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 (April 18, 2012) is 4391 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 93, 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: October 20, 2012 April 18, 2012 8 Source Ports in ARF Reports 9 draft-kucherawy-marf-source-ports-01 11 Abstract 13 This document registers 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 memo 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 October 20, 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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 57 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 58 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 60 6.2. Informative References . . . . . . . . . . . . . . . . . . 4 61 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 5 63 1. Introduction 65 [ARF] defined the Abuse Reporting Format, a new header message format 66 for use in reporting incidents of email abuse. It was extended by 67 [I-D.IETF-MARF-AUTHFAILURE-REPORT] to enable reporting of email 68 authentication failures. Although those specifications gave the 69 capability to include the source IP address in the report, the source 70 port was not included. As explained in [LOG], the deployment of IP 71 sharing techniques means it can now be essential to include source 72 port values in reports if unambiguous identification of the origin of 73 abuse is to be achieved. 75 Accordingly, this memo registers an ARF reporting field to contain 76 this information and provides guidance for its use. 78 2. Keywords 80 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 81 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 82 document are to be interpreted as described in [KEYWORDS]. 84 3. Source-Port Field Definition 86 A new ARF reporting field called "Source-Port" is defined. When 87 present in a report, it MUST contain the TCP or UDP source port 88 matching the "Source-IP" field in the same report, thereby describing 89 completely the origin of the abuse incident. 91 Per, [ABNF], the formal syntax is: 93 source-port = "Source-Port:" [CFWS] 1*DIGIT [CFWS] CRLF 95 "CFWS" is imported from [MAIL]. 97 When any report is generated that includes the "Source-IP" reporting 98 field, this field SHOULD also be present. 100 4. IANA Considerations 102 IANA is requested to add the following entry to the Feedback Report 103 Header Fields registry: 105 Field Name: Source-Port 107 Description: TCP or UDP source port from which the reported 108 connection originated 110 Multiple Appearances: No 112 Related Feedback-Type: any 114 Reference: [this memo] 116 Status: current 118 5. Security Considerations 120 This extension introduces no new security considerations not already 121 covered in [ARF]. 123 6. References 125 6.1. Normative References 127 [ABNF] Crocker, D. and P. Overell, 128 "Augmented BNF for Syntax 129 Specifications: ABNF", STD 68, 130 RFC 5234, January 2008. 132 [ARF] Shafranovich, Y., Levine, J., and 133 M. Kucherawy, "An Extensible 134 Format for Email Feedback 135 Reports", RFC 5965, August 2010. 137 [I-D.IETF-MARF-AUTHFAILURE-REPORT] Fontana, H., "Authentication 138 Failure Reporting using the Abuse 139 Report Format", I-D draft-ietf- 140 marf-authfailure-report, 141 January 2012. 143 [KEYWORDS] Bradner, S., "Key words for use 144 in RFCs to Indicate Requirement 145 Levels", BCP 14, RFC 2119, 146 March 1997. 148 [MAIL] Resnick, P., Ed., "Internet 149 Message Format", RFC 5322, 150 October 2008. 152 6.2. Informative References 154 [LOG] Durand, A., Gashinsky, I., Lee, 155 D., and S. Sheppard, "Logging 156 Recommendations for Internet- 157 Facing Servers", RFC 6302, 158 June 2011. 160 Appendix A. Acknowledgements 162 The authors wish to acknowledge the following for their review and 163 constructive criticism of this proposal: (names) 165 The idea for this work originated within the Messaging Anti-Abuse 166 Working Group (MAAWG). 168 Authors' Addresses 170 Richard Clayton 171 University of Cambridge 172 Computer Laboratory 173 JJ Thomson Avenue 174 Cambridge CB3 0FD 175 United Kingdom 177 Phone: +44 1223 763570 178 EMail: richard.clayton@cl.cam.ac.uk 180 Murray S. Kucherawy 181 Cloudmark, Inc. 182 128 King St., 2nd Floor 183 San Francisco, CA 94107 184 US 186 Phone: +1 415 946 3800 187 EMail: msk@cloudmark.com