Re: [domainrep] I-D Action: draft-ietf-repute-media-type-03.txt

Guangqing Deng <dgq2011@gmail.com> Sun, 29 July 2012 13:18 UTC

Return-Path: <dgq2011@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 E90FA21F86B9 for <domainrep@ietfa.amsl.com>; Sun, 29 Jul 2012 06:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[AWL=1.137, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, 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 wz02luyD26YT for <domainrep@ietfa.amsl.com>; Sun, 29 Jul 2012 06:18:15 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id E83FA21F8646 for <domainrep@ietf.org>; Sun, 29 Jul 2012 06:18:14 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so8460816obb.31 for <domainrep@ietf.org>; Sun, 29 Jul 2012 06:18:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6RwglQd9vXpvSZ69nBe0nEofN++GSdWMj69xCtdxU40=; b=RC5q9zgA0xctj7IPC9XijhEZexEvwOB/gReQfD4xZk5FqYeFjlIKbHAy0HPZc00J8G oU7xH/YsNtrPcrAriPCaZf+y9Q/yxJEyiHGD7fJIjp3mpCnKEZudLDZNbHTMiLYHuUjE Ol/aMHrZLmSq+7E8z939DyeZHJipncKkeS3o6cXzVHmcvD+x2gTMtpG0iNEDo8NSdXSb HdzxoIe57oLQrKWgqzuq48peHTgMGz4HP/6XdnkfexGUAMM+O2y8RkKj4f6TXXs6Q1Jg Q9QO8OosRJ1wg5x6iijOI/sY9+m+haqrE/5B2F4RiKlKHsspxHYGeSqBB1LZ2CWNxyMz DAaA==
MIME-Version: 1.0
Received: by 10.50.10.201 with SMTP id k9mr6202092igb.28.1343567894245; Sun, 29 Jul 2012 06:18:14 -0700 (PDT)
Received: by 10.64.81.168 with HTTP; Sun, 29 Jul 2012 06:18:14 -0700 (PDT)
In-Reply-To: <50082D33.2020402@trustsphere.com>
References: <20120628212818.23353.18943.idtracker@ietfa.amsl.com> <CAL4OH3Q8jFss29Efzj891BO2tDL9z-OfqBudPucgamgDC3kjVw@mail.gmail.com> <CAL0qLwYfhpkfEYJ3q9_iJp8daDogRCNLfj9gF519C4rNYjmzjw@mail.gmail.com> <5007E047.8010306@trustsphere.com> <CAL4OH3RLGmMdoUDWf-b3hkMDLNWy7m-1+V-+h1W7MbNYPV4m9Q@mail.gmail.com> <50082D33.2020402@trustsphere.com>
Date: Sun, 29 Jul 2012 21:18:14 +0800
Message-ID: <CAL4OH3Tqmkp7Z56VBd250q=MMeQNrvO-J3s-xwc-BXUMwDASpA@mail.gmail.com>
From: Guangqing Deng <dgq2011@gmail.com>
To: Steve Allam <steve.allam@trustsphere.com>
Content-Type: multipart/alternative; boundary="14dae93403691171c804c5f7c7d4"
Cc: domainrep@ietf.org
Subject: Re: [domainrep] I-D Action: draft-ietf-repute-media-type-03.txt
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: Sun, 29 Jul 2012 13:18:18 -0000

Maybe it is worthy to take consideration of RATER-AUTHENTICITY whose value
range is also between 0.0 and 1.0. Users will be puzzled by a
RATER-AUTHENTICITY of 0.5, for they can’t determine the RATED is genuine or
not. It is better to send a clear indication to the users no matter what
they will do (but the recommendation is provided). So the
RATER-AUTHENTICITY item should also be either 0 or 1, no other
floating-point number between 0 and 1. Another issue that I am interested
in is how to compute the RATER-AUTHENTICITY? You know, the RATING is
computed from the collected data; is the RATER-AUTHENTICITY also computed
from that? Please forgive me if I miss something important.

2012/7/19 Steve Allam <steve.allam@trustsphere.com>

>
> It depends.
>
> If my assertion is "does this sender ALWAYS send good messages", the
> rating would be 1 or 0
> If my assertion is "what percentage of mail is good from this sender", the
> rating will be somewhere between 0 and 1
>
> Hence, the rating can be whatever the application author wants it to be,
> repute just provides the framework.
>
> Steve
>
>
>
> On 19/07/2012 16:43, 邓光青 wrote:
>
> Hi, folks, before mentioning the RATER, RATED and RATING, let’s look back:
> what should the judge do towards the suspect in court. Usually, the judge
> should sentence the suspect to be either guilty or innocent; no judge
> will sentence a suspect to be 50% guilty (or innocent)! To some extent, the
> role of RATER, RATED and RATING is similar to that of the judge, suspect
> and verdict, respectively. In my opinion, the RATER should have a clear
> position towards the RATED; so the RATING should be either 0 or 1, no
> other floating-point number between 0 and 1.
>
>
> 2012/7/19 Steve Allam <steve.allam@trustsphere.com>
>
>>  Hi,
>>
>> Maybe also worth pointing out that the reputation application that is
>> being used (ficticious in this case) would have its own description of how
>> it used the rating item, and how the number should be interpreted - in a
>> similar way to many anti-spam systems that provide a score, they normally
>> provide information on what different levels of that score mean and how you
>> might use them - as the user, you can then do whatever you like, but the
>> recommendations are provided.
>>
>> As a further example, in our reputation application, the RATING item in
>> the repute response will be either 0 or 1, never anything inbetween, as we
>> are simply returning a true or false - our documentation will detail how
>> you may wish to use the 0 or 1 as well.
>>
>> Regards,
>>
>> Steve
>>
>>
>>
>>
>> On 18/07/2012 18:37, Murray S. Kucherawy wrote:
>>
>>  On Wed, Jul 18, 2012 at 6:29 AM, 邓光青 <dgq2011@gmail.com> wrote:
>>
>>>
>>>   Consider this case:
>>>
>>> Content-type: application/reputon+json
>>>
>>> {
>>>
>>> "reputon":
>>>
>>> {
>>>
>>> "rater": "RatingsRUs.example.com",
>>>
>>> "rater-authenticity": 1.0,
>>>
>>> "assertion": "IS-GOOD",
>>>
>>> "rated": "Alex Rodriguez",
>>>
>>> "rating": 0.5,
>>>
>>> "sample-size": 50000
>>>
>>> }
>>>
>>> }
>>> …indicates that we are absolutely *sure* (1.0) that the entity "
>>> RatingsRUs.example.com" consolidated 50000 data points (perhaps from
>>> everyone in Yankee Stadium) and concluded that Alex Rodriguez may be *good*
>>> or be *bad* (0.5) at something. Besides, if "rater-authenticity" equals 0.5
>>> but "rating" equals 1.0, it is also very hard to understand.
>>>
>>
>>
>> I interpret that reply to mean, literally: RatingsRUs.example.comcollected 50,000 data points about Alex Rodriguez.  It is 100% certain that
>> "Alex Rodriguez" refers to a real thing.  The data collected indicates that
>> the claim "Alex Rodriguez is good" is 50% true.
>>
>> As a person reading this, I take that to mean he's not good but also not
>> bad at whatever the application space covers, or that it's 50% likely that
>> he's good.
>>
>> -MSK
>>
>>
>>   _______________________________________________
>> domainrep mailing listdomainrep@ietf.orghttps://www.ietf.org/mailman/listinfo/domainrep
>>
>>
>>
>>
>> _______________________________________________
>> domainrep mailing list
>> domainrep@ietf.org
>> https://www.ietf.org/mailman/listinfo/domainrep
>>
>>
>
>
> --
> Guangqing Deng
>
>
>


-- 
Guangqing Deng