Source Ports in ARF Reports
draft-kucherawy-marf-source-ports-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in app area)
Authors Richard Clayton , Murray Kucherawy 
Last updated 2012-05-07 (latest revision 2012-04-18)
Stream Internet Engineering Task Force (IETF)
Formats plain text pdf htmlized bibtex
Reviews
Stream WG state (None)
Document shepherd None
IESG IESG state AD Evaluation
Consensus Boilerplate Unknown
Telechat date
Responsible AD Barry Leiba
IESG note The document shepherd is John Levine <johnl@iecc.com>.
Send notices to richard.clayton@cl.cam.ac.uk, msk@cloudmark.com, draft-kucherawy-marf-source-ports@tools.ietf.org, johnl@iecc.com
Individual submission                                         R. Clayton
Internet-Draft                                   University of Cambridge
Updates: 5965, 6591 (if approved)                           M. Kucherawy
Intended status: Standards Track                         Cloudmark, Inc.
Expires: October 20, 2012                                 April 18, 2012

                      Source Ports in ARF Reports
                  draft-kucherawy-marf-source-ports-02

Abstract

   This document registers an additional header field for use in Abuse
   Reporting Format reports to permit the identification of the source
   port of the connection involved in an abuse incident.

   This memo updates RFC5965 and RFC6591.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 20, 2012.

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

Clayton & Kucherawy     Expires October 20, 2012                [Page 1]
Internet-Draft              ARF Source Ports                  April 2012

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Keywords  . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Source-Port Field Definition  . . . . . . . . . . . . . . . . . 3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 4
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 4
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . . . 4

Clayton & Kucherawy     Expires October 20, 2012                [Page 2]
Internet-Draft              ARF Source Ports                  April 2012

1.  Introduction

   [ARF] defined the Abuse Reporting Format, a new header message format
   for use in reporting incidents of email abuse.  It was extended by
   [AUTHFAILURE-REPORT] to enable reporting of email authentication
   failures.  Although those specifications gave the capability to
   include the source IP address in the report, the source port was not
   included.  As explained in [LOG], the deployment of IP sharing
   techniques means it can now be essential to include source port
   values in reports if unambiguous identification of the origin of
   abuse is to be achieved.

   Accordingly, this memo registers 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 reporting field called "Source-Port" is defined.  When
   present in a report, it MUST contain the TCP or UDP source port
   matching the "Source-IP" field in the same report, thereby describing
   completely the origin of the abuse incident.

   Per, [ABNF], the formal syntax is:

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

   "CFWS" is imported from [MAIL].

   When any report is generated that includes the "Source-IP" reporting
   field, this field SHOULD also be present.

4.  IANA Considerations

   IANA is requested to add the following entry to the Feedback Report
   Header Fields registry:

   Field Name:  Source-Port

   Description:  TCP or UDP source port from which the reported
      connection originated

Clayton & Kucherawy     Expires October 20, 2012                [Page 3]
Internet-Draft              ARF Source Ports                  April 2012

   Multiple Appearances:  No

   Related Feedback-Type:  any

   Reference:  [this memo]

   Status:  current

5.  Security Considerations

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

6.  References

6.1.  Normative References

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

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

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

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

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

6.2.  Informative References

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

Appendix A.  Acknowledgements

   The authors wish to acknowledge the following for their review and
   constructive criticism of this proposal: (names)

   The idea for this work originated within the Messaging Anti-Abuse

Clayton & Kucherawy     Expires October 20, 2012                [Page 4]
Internet-Draft              ARF Source Ports                  April 2012

   Working Group (MAAWG).

Authors' Addresses

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

   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

   Phone: +1 415 946 3800
   EMail: msk@cloudmark.com

Clayton & Kucherawy     Expires October 20, 2012                [Page 5]