Re: Last Call: <draft-ietf-repute-media-type-10.txt> (A Media Type for Reputation Interchange) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



At 07:44 15-08-2013, The IESG wrote:
The IESG has received a request from the Reputation Services WG (repute)
to consider the following document:
- 'A Media Type for Reputation Interchange'
  <draft-ietf-repute-media-type-10.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@xxxxxxxx mailing lists by 2013-08-29. Exceptionally, comments may be

From Section 3.1:

   "expires:  A timestamp indicating a time beyond which the score
      reported is likely not to be valid.  Expressed as the number of
      seconds since January 1, 1970 00:00 UTC.  See Section 5 for
      discussion."

And Section 5:

  'A reputon can contain an "expires" field indicating a timestamp after
   which the client SHOULD NOT use the rating it contains, and SHOULD'

The "expires" field uses "HTTP-date". It is easier to code for one timestamp format instead of two (see Unix timestamp in Section 3.1).

In Section 3.1:

  "An application service provider might operate with an enhanced form
   of common services, which might in turn prompt development and
   reporting of specialized reputation information."

I don't see anything actionable in the above.

Why was "specification required" chosen for the Reputation Applications Registry?

Regards,
-sm









[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]