Opened 6 years ago

Last modified 6 years ago

#148 new defect

Architecture document: Spelling/improvements to Introduction

Reported by: eranm@… Owned by: draft-ietf-trans-threat-analysis@…
Priority: major Milestone:
Component: threat-analysis Version:
Severity: - Keywords:
Cc:

Description

In section 1:
onlogs -> on logs
repeatedlymisbehave -> repeatedly misbehave.

I also propose changing 'repeatedly misbehave' to 'grossly misbehave' (or something else to indicate particularly bad misbehaviour).
A log may misbehave multiple times (multiple, minor infractions, e.g. by missing it's MMD by a bit) but still be used by browsers. On the contrary, a log may be disqualified after grossly misbehaving once (e.g. by not including an entry).

Change History (1)

comment:1 Changed 6 years ago by kent@…

I have revised the text to be:
In turn, the Monitors and Browser Vendors are expected to cease relying on logs that repeatedly misbehave in a fashion indicative of malice. (Ultimately, what constitutes malicious misbehavior will be determined by Monitors and Browser Vendors, and thus is outside the scope of this document.)

Note: See TracTickets for help on using tickets.