draft-ietf-repute-media-type-02.txt   draft-ietf-repute-media-type-03.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: October 8, 2012 Cloudmark Expires: December 30, 2012 June 28, 2012
April 6, 2012
A Media Type for Reputation Interchange A Media Type for Reputation Interchange
draft-ietf-repute-media-type-02 draft-ietf-repute-media-type-03
Abstract Abstract
This document defines a media type for exchanging reputation This document defines a media type for exchanging reputation
information about an arbitrary class of object. information about an arbitrary class of object.
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 32 skipping to change at page 1, line 31
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 October 8, 2012. This Internet-Draft will expire on December 30, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 19 skipping to change at page 2, line 19
2.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Other Definitions . . . . . . . . . . . . . . . . . . . . 3 2.2. Other Definitions . . . . . . . . . . . . . . . . . . . . 3
3. Description . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Description . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Reputon Keys . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Reputon Keys . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Reputon Structure . . . . . . . . . . . . . . . . . . . . 5 3.2. Reputon Structure . . . . . . . . . . . . . . . . . . . . 5
3.3. Example Reply . . . . . . . . . . . . . . . . . . . . . . 6 3.3. Example Reply . . . . . . . . . . . . . . . . . . . . . . 6
4. Scores . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Scores . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
5.1. application/reputon Media Type Registration . . . . . . . 8 5.1. application/reputon Media Type Registration . . . . . . . 8
5.2. Reputation Applications Registry . . . . . . . . . . . . . 9 5.2. Reputation Applications Registry . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11
7.2. Informative References . . . . . . . . . . . . . . . . . . 11 7.2. Informative References . . . . . . . . . . . . . . . . . . 11
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 12 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 12
Appendix B. Public Discussion . . . . . . . . . . . . . . . . . . 12 Appendix B. Public Discussion . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
This document defines a media type for use when answering a This document defines a media type for use when answering a
skipping to change at page 8, line 17 skipping to change at page 8, line 17
This document presents two actions for IANA, namely the creation of This document presents two actions for IANA, namely the creation of
the new media type "application/reputon+json" and the creation of a the new media type "application/reputon+json" and the creation of a
registry for reputation application types. Another document in this registry for reputation application types. Another document in this
series creates an initial registry entry for the latter. series creates an initial registry entry for the latter.
5.1. application/reputon Media Type Registration 5.1. application/reputon Media Type Registration
This section provides the media type registration application from This section provides the media type registration application from
[MIME-REG] for processing by IANA: [MIME-REG] for processing by IANA:
To: ietf-types@iana.org To: media-types@iana.org
Subject: Registration of media type application/reputon Subject: Registration of media type application/reputon
Type name: application Type name: application
Subtype name: reputon+json Subtype name: reputon+json
Required parameters: none Required parameters: none
Optional parameters: Optional parameters:
skipping to change at page 9, line 35 skipping to change at page 9, line 35
IANA is requested to create the "Reputation Applications" registry. IANA is requested to create the "Reputation Applications" registry.
This registry will contain names of applications used with the This registry will contain names of applications used with the
application/reputon+json media type (and other media types that carry application/reputon+json media type (and other media types that carry
reputons), as defined by this document. reputons), as defined by this document.
New registrations or updates MUST be published in accordance with the New registrations or updates MUST be published in accordance with the
"Specification Required" guidelines as described in "Specification Required" guidelines as described in
[IANA-CONSIDERATIONS]. [IANA-CONSIDERATIONS].
New registrations and updates MUST contain the following information: New registrations and updates are to contain the following
information:
1. Name of the application being registered or updated 1. Name of the application being registered or updated
2. Short description of the application (i.e., the class of entity 2. Short description of the application (i.e., the class of entity
about which it reports reputation data) about which it reports reputation data)
3. The document in which the application is defined 3. The document in which the application is defined
4. New or updated status, which MUST be one of: 4. New or updated status, which is to be one of:
current: The application is in current use current: The application is in current use
deprecated: The application is in current use but its use is deprecated: The application is in current use but its use is
discouraged discouraged
historic: The application is no longer in current use historic: The application is no longer in current use
5. A description of the subject of a query within this reputation, 5. A description of the subject of a query within this reputation,
and a legal syntax for the same and a legal syntax for the same
skipping to change at page 10, line 25 skipping to change at page 10, line 25
Status: (as above) Status: (as above)
Description: A short description of the purpose of this Description: A short description of the purpose of this
parameter parameter
Syntax: A reference to a description of valid syntax for the Syntax: A reference to a description of valid syntax for the
parameter's value parameter's value
Required: "yes" if the parameter is mandatory, "no" otherwise Required: "yes" if the parameter is mandatory, "no" otherwise
A document creating a reputation application MUST include: 7. A list of one or more assertions registered within this
application; each table entry is to include:
1. A list of one or more assertions registered within this
application; each table entry must include:
Name: Name of the assertion Name: Name of the assertion
Description: A short description of the assertion, with specific Description: A short description of the assertion, with specific
meanings for values of 0.0 and 1.0 meanings for values of 0.0 and 1.0
Scale: A short description of the scale used in computing the Scale: A short description of the scale used in computing the
value (see Section 4 of this document) value (see Section 4 of this document)
A document creating a reputation application MAY include: 8. An optional list of one or more response set extension keys for
use within this application; each table entry is to include:
1. A list of one or more response set extension keys for use within
this application; each table entry must include:
Name: Name of the extension key Name: Name of the extension key
Description: A short description of the key's intended meaning Description: A short description of the key's intended meaning
Syntax: A description of valid values that can appear associated Syntax: A description of valid values that can appear associated
with the key with the key
6. Security Considerations 6. Security Considerations
skipping to change at page 12, line 34 skipping to change at page 12, line 29
Nathaniel Borenstein Nathaniel Borenstein
Mimecast Mimecast
203 Crescent St., Suite 303 203 Crescent St., Suite 303
Waltham, MA 02453 Waltham, MA 02453
USA USA
Phone: +1 781 996 5340 Phone: +1 781 996 5340
Email: nsb@guppylake.com Email: nsb@guppylake.com
Murray S. Kucherawy Murray S. Kucherawy
Cloudmark 2063 42nd Avenue
128 King St., 2nd Floor San Francisco, CA 94116
San Francisco, CA 94107
USA USA
Phone: +1 415 946 3800 Email: superuser@gmail.com
Email: msk@cloudmark.com
 End of changes. 11 change blocks. 
19 lines changed or deleted 14 lines changed or added

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