A Reputation Query Protocol
RFC 7072
Document | Type | RFC - Proposed Standard (November 2013; No errata) | |
---|---|---|---|
Authors | Nathaniel Borenstein , Murray Kucherawy | ||
Last updated | 2015-10-14 | ||
Replaces | draft-kucherawy-reputation-query-http | ||
Stream | Internet Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized 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 7072 (Proposed Standard) | |
Action Holders |
(None)
|
||
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: 7072 Mimecast Category: Standards Track M. Kucherawy ISSN: 2070-1721 November 2013 A Reputation Query Protocol Abstract This document defines a mechanism to conduct queries for reputation information over the HyperText Transfer Protocol (HTTP) using JavaScript Object Notation (JSON) as the payload meta-format. 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/rfc7072. 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 7072 A Reputation Query Protocol November 2013 Table of Contents 1. Introduction ....................................................2 2. Terminology and Definitions .....................................2 2.1. Key Words ..................................................2 2.2. Other Definitions ..........................................3 3. Description .....................................................3 3.1. Overview ...................................................3 3.2. URI Template ...............................................3 3.3. Syntax .....................................................4 3.4. Response ...................................................6 3.5. Protocol Support ...........................................6 4. IANA Considerations .............................................7 5. Security Considerations .........................................7 6. References ......................................................8 6.1. Normative References .......................................8 6.2. Informative References .....................................8 Appendix A. Acknowledgements .......................................9 1. Introduction This document defines a method to query a reputation data service for information about an entity, using the HyperText Transfer Protocol (HTTP) as the transport mechanism and JSON as the payload meta- format. The mechanism is a two-stage query: 1. A client retrieves a template from a server that describes the construction of a Universal Resource Identifier (URI) that will be the actual query; 2. The client then uses the constructed URI to request the reputation data from the server. 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]. Borenstein & Kucherawy Standards Track [Page 2] RFC 7072 A Reputation Query Protocol November 2013 2.2. Other Definitions Other terms of importance in this document are defined in [RFC7070] and [RFC7071]. 3. Description 3.1. Overview The components to the question being asked are the following: o The subject of the query; o The name of the host, or the IP address, at which the reputation service is available; o The name of the reputation application, i.e., the context within which the subject is being evaluated; o Optionally, names of the specific reputation assertions or attributes that are being requested. There is no discovery protocol for finding reputation services. These are typically subscription services, negotiated between operators through some out-of-band method. Assertions are discussed in [RFC7071].Show full document text