< draft-ietf-repute-email-identifiers-07.txt   draft-ietf-repute-email-identifiers-08.txt >
REPUTE Working Group N. Borenstein REPUTE Working Group N. Borenstein
Internet-Draft Mimecast Internet-Draft Mimecast
Intended status: Standards Track M. Kucherawy Intended status: Standards Track M. Kucherawy
Expires: November 21, 2013 May 20, 2013 Expires: December 8, 2013 June 6, 2013
A Reputation Response Set for Email Identifiers A Reputation Response Set for Email Identifiers
draft-ietf-repute-email-identifiers-07 draft-ietf-repute-email-identifiers-08
Abstract Abstract
This document defines a response set for describing assertions a This document defines a response set for describing assertions a
reputation service provider can make about email identifers, for use reputation service provider can make about email identifers, for use
in generating reputons. in generating reputons.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 21, 2013. This Internet-Draft will expire on December 8, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 13 skipping to change at page 2, line 13
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Definitions . . . . . . . . . . . . . . . . . . 3 2. Terminology and Definitions . . . . . . . . . . . . . . . . . . 3
2.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Email Definitions . . . . . . . . . . . . . . . . . . . . . 3 2.2. Email Definitions . . . . . . . . . . . . . . . . . . . . . 3
2.3. Other Definitions . . . . . . . . . . . . . . . . . . . . . 3 2.3. Other Definitions . . . . . . . . . . . . . . . . . . . . . 3
3. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Assertions . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Assertions . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Response Set Extensions . . . . . . . . . . . . . . . . . . 4 3.2. Response Set Extensions . . . . . . . . . . . . . . . . . . 4
3.3. Query Extensions . . . . . . . . . . . . . . . . . . . . . 5 3.3. Query Extensions . . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Registration of 'email-id' Reputation Application . . . . . 5 4.1. Registration of 'email-id' Reputation Application . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6
6.2. Informative References . . . . . . . . . . . . . . . . . . 7 6.2. Informative References . . . . . . . . . . . . . . . . . . 7
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 7 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 7
Appendix B. Public Discussion . . . . . . . . . . . . . . . . . . 8 Appendix B. Public Discussion . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
This document specifies a response set for describing reputation of This document specifies a response set for describing reputation of
an email identifier. A "response set" in this context is defined in an email identifier. A "response set" in this context is defined in
[I-D.REPUTE-MODEL] and is used to describe assertions a reputation [I-D.REPUTE-MODEL] and is used to describe assertions a reputation
service provider can make about email identifiers as well as meta- service provider can make about email identifiers as well as meta-
data that can be included in such a reply beyond the base set data that can be included in such a reply beyond the base set
specified there. specified there.
An atomic reputation response is called a "reputon", also defined in An atomic reputation response is called a "reputon", defined in
that document. [I-D.REPUTE-MEDIA-TYPE]. That document also defines a media type to
contain a reputon for transport, and also creates a registry for
[I-D.REPUTE-MEDIA-TYPE] defines a media type to contain a reputon for reputation applications and the interesting parameters of each.
transport, and also creates a registry for reputation applications
and the interesting parameters of each.
2. Terminology and Definitions 2. Terminology and Definitions
This section defines terms used in the rest of the document. This section defines terms used in the rest of the document.
2.1. Key Words 2.1. Key Words
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [KEYWORDS]. document are to be interpreted as described in [KEYWORDS].
 End of changes. 6 change blocks. 
12 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/