[domainrep] RFC 7070 on An Architecture for Reputation Reporting
rfc-editor@rfc-editor.org Fri, 22 November 2013 16:45 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: domainrep@ietfa.amsl.com
Delivered-To: domainrep@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A358E1ADF72; Fri, 22 Nov 2013 08:45:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level:
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ctx5u-xabdzr; Fri, 22 Nov 2013 08:45:48 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id D32301ADBE5; Fri, 22 Nov 2013 08:45:48 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2130175E001; Fri, 22 Nov 2013 08:35:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20131122163516.2130175E001@rfc-editor.org>
Date: Fri, 22 Nov 2013 08:35:16 -0800
Cc: drafts-update-ref@iana.org, domainrep@ietf.org, rfc-editor@rfc-editor.org
Subject: [domainrep] RFC 7070 on An Architecture for Reputation Reporting
X-BeenThere: domainrep@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Domain Reputation discussion list <domainrep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/domainrep>, <mailto:domainrep-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/domainrep/>
List-Post: <mailto:domainrep@ietf.org>
List-Help: <mailto:domainrep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/domainrep>, <mailto:domainrep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Nov 2013 16:45:50 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7070
Title: An Architecture for Reputation Reporting
Author: N. Borenstein, M. Kucherawy
Status: Standards Track
Stream: IETF
Date: November 2013
Mailbox: nsb@guppylake.com,
superuser@gmail.com
Pages: 14
Characters: 32262
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-repute-model-10.txt
URL: http://www.rfc-editor.org/rfc/rfc7070.txt
This document describes a general architecture for a reputation-based
service, allowing one to request reputation-related data over the
Internet, where "reputation" refers to predictions or expectations
about an entity or an identifier such as a domain name. The document
roughly follows the recommendations of RFC 4101 for describing a
protocol model.
This document is a product of the Reputation Services Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC