[domainrep] Charter adjustments

"Murray S. Kucherawy" <msk@cloudmark.com> Wed, 31 August 2011 05:30 UTC

Return-Path: <msk@cloudmark.com>
X-Original-To: domainrep@ietfa.amsl.com
Delivered-To: domainrep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8A921F8ADC for <domainrep@ietfa.amsl.com>; Tue, 30 Aug 2011 22:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.025
X-Spam-Level:
X-Spam-Status: No, score=-103.025 tagged_above=-999 required=5 tests=[AWL=-0.426, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wIO6qNEMoPtW for <domainrep@ietfa.amsl.com>; Tue, 30 Aug 2011 22:30:49 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id A5C4C21F8ACC for <domainrep@ietf.org>; Tue, 30 Aug 2011 22:30:46 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Tue, 30 Aug 2011 22:32:15 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "domainrep@ietf.org" <domainrep@ietf.org>
Date: Tue, 30 Aug 2011 22:32:14 -0700
Thread-Topic: Charter adjustments
Thread-Index: Acxnn1b0tDUGfuclRPu/ZtxAbur5XA==
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF9B6@EXCH-C2.corp.cloudmark.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [domainrep] Charter adjustments
X-BeenThere: domainrep@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 31 Aug 2011 05:30:50 -0000

After some review by our sponsoring AD, I've made a few tweaks in the proposed charter.  Please provide any comments you may have, even if it's just a "looks good", preferably sooner rather than later.  They are pretty minor, but having such feedback on the record will help move things along.

The full updated charter is still available at http://www.blackops.org/~msk/domainrep/repute-charter.txt; the diffs are below.

Absent any major problems, we should be on an IESG telechat and the main IETF mailing list fairly soon.

-MSK


--- repute-charter	2011/08/14 02:52:38	1.16
+++ repute-charter	2011/08/29 22:05:44
@@ -74,16 +74,19 @@
 
 	This working group will produce a set of documents defining and
 	illustrating the requirement and defining mechanisms to satisfy it.
-	Two mechanisms are proposed:
+	Two mechanisms are on the table:
 
 	* simple -- a reputation is expressed in a simple manner such as
-		an integer
+		an integer, provided via TXT records in the DNS
+		(see draft-kucherawy-reputation-query-dns)
 
 	* extended -- a response can contain more complex information
-		useful to an assessor
+		useful to an assessor, provided via an XML reply over HTTP
+		(see draft-kucherawy-reputation-query-http)
 
 	The mechanisms will be designed to be application-independent, and
-	portable between reputation providers.
+	portable between reputation providers.  The working group will
+	consider these and may develop both or decide only one is needed.
 
 	The group will also produce specifications for reporting reputation
 	data from end-points (usually end users, such as someone clicking @@ -128,6 +131,14 @@
 	  compute reputations.  These are part of a back-end system, usually
 	  proprietary, and not appropriate for specification as part of
 	  a query/reply framework and protocol.
+
+	The initial draft set:
+		draft-kucherawy-reputation-model
+		draft-kucherawy-reputation-media-type
+		draft-kucherawy-reputation-query-http
+		draft-kucherawy-reputation-query-dns
+		draft-kucherawy-reputation-query-udp
+		draft-kucherawy-reputation-vocab-identity
 
 Goals and Milestones:
 	Mar 2012:	Informational document, defining the problem space