[domainrep] Review of: draft-ietf-repute-media-type-07

Dave Crocker <dcrocker@gmail.com> Mon, 20 May 2013 02:45 UTC

Return-Path: <dcrocker@gmail.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 953D221F8F12 for <domainrep@ietfa.amsl.com>; Sun, 19 May 2013 19:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 xjsKQqmBVpSw for <domainrep@ietfa.amsl.com>; Sun, 19 May 2013 19:45:14 -0700 (PDT)
Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by ietfa.amsl.com (Postfix) with ESMTP id 0BA2121F8F20 for <domainrep@ietf.org>; Sun, 19 May 2013 19:45:13 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id i10so7229533oag.29 for <domainrep@ietf.org>; Sun, 19 May 2013 19:45:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:content-type:content-transfer-encoding; bh=RcNSsdVh+qezumFtinYjT5AETpjXr8N891bN3rBCw2c=; b=Y1DVcJXLpi2G14V55V5fStyXbgRL1wWC67LHxQSrQJK+tHpMpJmvWjYMQMUUo+mq5x xjVHj9RLcYTiUt2U75Geh3zuTEItCAEzR49gcO6z17D1iacWS/7XbMGznLCviuPo5klc 22z+FNknfvk9fZ3rflboe4MxhLM3dcVUVXk71/KI9MgZOldkhEwpGzIn36CImdyHM8hv sNgZKJ0QL3/3NyjfU/Ug/Zh9AZ3VTEddaYLr9PYE/zqGgCgtADqgQDZj6n2xndcbNse2 4e6ibuklsgiv9U/CkvUxLJ5lafj6nT+aDkrXDszF6BzK36P63o9o6PR+YNXIrAr/tuRi 6aBA==
X-Received: by 10.182.153.67 with SMTP id ve3mr4789260obb.29.1369017913618; Sun, 19 May 2013 19:45:13 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net. [76.218.9.215]) by mx.google.com with ESMTPSA id jw8sm18447035obb.14.2013.05.19.19.45.11 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 May 2013 19:45:12 -0700 (PDT)
Message-ID: <51998E36.9030204@gmail.com>
Date: Sun, 19 May 2013 19:45:10 -0700
From: Dave Crocker <dcrocker@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: draft-ietf-repute-media-type.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "domainrep@ietf.org" <domainrep@ietf.org>
Subject: [domainrep] Review of: draft-ietf-repute-media-type-07
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: Mon, 20 May 2013 02:45:39 -0000

{ This review is provided as part of document shepherding. /d }



Review of:    A Media Type for Reputation Interchange
I-D:          draft-ietf-repute-media-type-07
Reviewed by:  D. Crocker
Review Date:  19 May 2013


Summary:

This document is part of a set that defines a mechanism for requesting 
and retrieving assessment-related information (reputation) concerning an 
object. The document defines the response side, in terms of content 
semantics and form, and MIME-based encoding.

The specification is usable in its current form.



Detailed Comments:

Only one, and it's probably ok to ignore it...

> 3.1.  Reputon Attributes
>
...
>    rater-authenticity:  The level of confidence that the rated identity
>       is genuine, expressed as a floating-point number between 0.0 and
>       1.0 inclusive.  "Genuine" here means the identity being rated is
>       legitimately associated with the real-world entity it represents.
>       For example, a rater might claim a value of 1.0 here if it is
>       certain the rated identity "example.com" is associated with The
>       Example Widget Co, Inc., because it is used in a context where
>       both authentication and authorization on the use of that domain
>       name are assured; the binding between the rated identity and the
>       real-world identity is well established.

Hmmm.  Arguably, example.com is merely an identifier, as is "Example 
Widget Co, Inc", and both are tied to the company the latter refers to. 
  I'm not sure how sensitive this mechanism is to the kind of linguistic 
precision this point implies.

Separately, it occurs to me that the response doesn't otherwise cite 
Example Widget Co, Inc.  If rater-authenticity is provided and its 
meaning concerns association with some real-world entity, would it help 
to specify that entity, similar to the form of what's done in the 
explanatory text here?  It's possible the answer is no, as in "the 
reader doesn't need to know the details about the real-world entity, but 
I, the rater, am confident this identifier is linked to them." My guess 
is that it's ok to leave this as it is now, and add in more if 
experience dictates it.



d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net