A Reputation Response Set for Email Identifiers
RFC 7073
|
| Document |
Type |
|
RFC - Proposed Standard
(November 2013; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-kucherawy-reputation-vocab-identity
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Dave Crocker
|
|
Shepherd write-up |
|
Show
(last changed 2013-05-25)
|
| IESG |
IESG state |
|
RFC 7073 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Pete Resnick
|
|
IESG note |
|
Suggest reading -model first.
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) N. Borenstein
Request for Comments: 7073 Mimecast
Category: Standards Track M. Kucherawy
ISSN: 2070-1721 November 2013
A Reputation Response Set for Email Identifiers
Abstract
This document defines a response set for describing assertions a
reputation service provider can make about email identifiers, for use
in generating reputons.
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.
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/rfc7073.
Copyright Notice
Copyright (c) 2013 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.
Borenstein & Kucherawy Standards Track [Page 1]
RFC 7073 Email Identifiers Response Set November 2013
Table of Contents
1. Introduction ....................................................2
2. Terminology and Definitions .....................................2
2.1. Key Words ..................................................2
2.2. Email Definitions ..........................................2
2.3. Other Definitions ..........................................3
3. Discussion ......................................................3
3.1. Assertions .................................................3
3.2. Response Set Extensions ....................................4
3.3. Identifiers ................................................4
3.4. Query Extensions ...........................................5
4. IANA Considerations .............................................5
4.1. Registration of 'email-id' Reputation Application ..........5
5. Security Considerations .........................................6
6. References ......................................................7
6.1. Normative References .......................................7
6.2. Informative References .....................................7
Appendix A. Positive vs. Negative Assertions .......................8
Appendix B. Acknowledgments ........................................8
1. Introduction
This document specifies a response set for describing the reputation
of an email identifier. A "response set" in this context is defined
in [RFC7070] and is used to describe assertions a reputation service
provider can make about email identifiers as well as metadata that
can be included in such a reply beyond the base set specified there.
An atomic reputation response is called a "reputon", defined in
[RFC7071]. That document also defines a media type to contain a
reputon for transport, and creates a registry for reputation
applications and the interesting parameters of each.
2. Terminology and Definitions
This section defines terms used in the rest of the document.
2.1. Key Words
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].
Borenstein & Kucherawy Standards Track [Page 2]
RFC 7073 Email Identifiers Response Set November 2013
2.3. Other Definitions
Show full document text