REPUTE Working Group                                       N. Borenstein
Internet-Draft                                                  Mimecast
Intended status: Standards Track                            M. Kucherawy
Expires: May 22, June 18, 2012                                         Cloudmark
                                                       November 19,
                                                       December 16, 2011

             A Reputation Vocabulary for Email Identities
                 draft-ietf-repute-email-identifiers-00 Identifiers
                 draft-ietf-repute-email-identifiers-01

Abstract

   This document defines a vocabulary for describing email identities identifiers
   (typically authors or signers) with the application/reputon media
   type.

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 May 22, June 18, 2012.

Copyright Notice

   Copyright (c) 2011 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Terminology and Definitions . . . . . . . . . . . . . . . . . . 3
     2.1.  Keywords  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     2.2.  Email Definitions . . . . . . . . . . . . . . . . . . . . . 3
     2.3.  Other Definitions . . . . . . . . . . . . . . . . . . . . . 3
   3.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . . . 3
     3.1.  Assertions  . . . . . . . . . . . . . . . . . . . . . . . . 3
     3.2.  Vocabulary Extensions . . . . . . . . . . . . . . . . . . . 4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
     4.1.  Registration of 'email-id' Reputation Application . . . . . 5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   6.  Informative References  . . . . . . . . . . . . . . . . . . . . 5
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . . . 6
   Appendix B.  Public Discussion  . . . . . . . . . . . . . . . . . . 6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 6

1.  Introduction

   This memo defines a "vocabulary" for describing reputation of an
   email identity. identifier.  A "vocabulary" in this context is defined in
   [RFCxxxx] and is used to describe assertions a reputation service
   provider can make about email identities identifiers as well as meta-data that
   can be included in such a reply beyond the base set specified there.

2.  Terminology and Definitions

   This section defines terms used in the rest of the document.

2.1.  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].

2.2.  Email Definitions

   Commonly used definitions describing entities in the email
   architecture are defined and discussed in [EMAIL-ARCH].

2.3.  Other Definitions

   Other terms of importance in this memo are defined in RFCxxxx, the
   base memo in this document series.

3.  Discussion

   The expression of reputation about an email identity identifier requires
   extensions of the base set defined in [RFCxxxx].  This memo defines
   and registers some common assertions about an entity found in a piece
   of [MAIL].

3.1.  Assertions

   The "email-id" reputation application recognizes the following
   assertions:

   PERPETRATES-FRAUD:

   FRAUD:  The subject identity identifier is associated with sending or handling
      of fraudulent email

   SENDS-MALWARE:

   MALWARE:  The subject identity identifier is associated with the sending or relaying
      handling of malware via email

   SENDS-SPAM:

   SPAM:  The subject identity identifier is associated with sending or handling
      of unwanted bulk email

   SENDS-TO-INVALID-RECIPIENTS:

   INVALID-RECIPIENTS:  The subject identifier is associated with
      delivery attempts to nonexistent recipients

   For all assertions, the RATING scale is linear: A value of 0.0 means
   there is no data to support the assertion, a value of 1.0 means all
   accumulated data support the assertion, and the intervening values
   have a linear relationship (i.e., a score of "x" is twice as strong
   of an assertion as a value of "x/2").

3.2.  Vocabulary Extensions

   The "email-id" reputation application recognizes the following
   OPTIONAL extensions to the basic vocabulary defined in [RFCxxxx]:

   IDENTITY:  A token indicating the source of the identity; identifier; that is,
      where the subject identity identifier was found in the message.  This MUST
      be one of:

      DKIM:  The signing domain, i.e. the value of the "d=" tag, found
         on a valid [DKIM] signature in the message

      IPV4:  The IPv4 address of the client

      IPV6:  The IPv6 address of the client

      RFC5321.MAILFROM:  The RFC5321.MailFrom value of the envelope of a
         message of the message (see [SMTP])

      RFC5322.FROM:  The RFC5322.From field of the message (see [MAIL])

      SPF:  The identity domain name portion of the identifier (RFC5321.MailFrom
         or RFC5321.Helo) verified by [SPF])

   RATE:  A token that recommends an overall message acceptance rate for
      the subject domain.  This is expected to be a value tailored to
      the requesting agent; for example, the reputation service would
      use this to indicate that, based on the data reported by the
      requesting agent, the service recommends a particular message
      limit for that agent.  The value is an unsigned decimal value.

   SOURCES:  A token relating a count of the number of sources of data
      that contributed to the reported reputation.  This is in contrast
      to the SAMPLE-SIZE parameter, which indicates the total number of
      reports across all reporting sources.

   A reply that does not contain the IDENTITY or SOURCES extensions is
   making a non-specific statement about how the reputation returned was
   developed.  A client may use or ignore such a reply at its
   discretion.

4.  IANA Considerations

   This memo presents one action for IANA, namely the registraton of the
   reputation application "email-id".

4.1.  Registration of 'email-id' Reputation Application

   This section registers the "email-id" reputation application, as
   defined in [RFCxxxx+1].  The registration parameters are as folows:

   o  Application name: email-id

   o  Short description: Evaluates DNS domain names found in email
      identities
      identifiers

   o  Defining document: [this memo]

   o  Status: current

   o  Application-specific query parameters:

      subject:  (current) identifies specifies the subject of the reputation query;
         in this case, it is the email identity identifier whose reputation is
         requested

5.  Security Considerations

   This memo describes security considerations introduced by the
   reputation application and vocabulary defined here.

   [TBD]

6.  Informative References

   [DKIM]     Crocker, D., Ed., Hansen, T., Ed., and M. Kucherawy, Ed.,
              "DomainKeys Identified Mail (DKIM) Signatures", RFC 6376,
              September 2011.

   [EMAIL-ARCH]
              Crocker, D., "Internet Mail Architecture", RFC 5598,
              July 2009.

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

   [SMTP]     Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,
              October 2008.

   [SPF]      Wong, M. and W. Schlitt, "Sender Policy Framework (SPF)
              for Authorizing Use of Domains in E-Mail, Version 1",
              RFC 4408, April 2006.

Appendix A.  Acknowledgments

   The authors wish to acknowledge the contributions of the following to
   this specification: Scott Kitterman, John Levine, Doug Otis, and
   David F. Skoll.

Appendix B.  Public Discussion

   Public discussion of this suite of memos takes place on the
   domainrep@ietf.org mailing list.  See
   https://www.ietf.org/mailman/listinfo/domainrep.

Authors' Addresses

   Nathaniel Borenstein
   Mimecast
   203 Crescent St., Suite 303
   Waltham, MA  02453
   USA

   Phone: +1 781 996 5340
   Email: nsb@guppylake.com
   Murray S. Kucherawy
   Cloudmark
   128 King St., 2nd Floor
   San Francisco, CA  94107
   USA

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