Opened 7 years ago
Closed 6 years ago
#123 closed defect (wontfix)
log clients description too informal, incomplete
Reported by: | kent@… | Owned by: | draft-ietf-trans-rfc6962-bis@… |
---|---|---|---|
Priority: | major | Milestone: | review |
Component: | rfc6962-bis | Version: | |
Severity: | - | Keywords: | |
Cc: |
Description
Section 9 discusses log clients, but uses a lot of language that is not normative, e.g., “might perform” and “typical clients should [sic] function” and “somehow exchange STHs”. This section should be removed and a more thorough discussion of requirements provided in a set of separate documents, using appropriate standards language.
Change History (2)
comment:1 Changed 6 years ago by benl@…
- Milestone set to review
comment:2 Changed 6 years ago by paul@…
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
The point is that CT provides data you might choose to act on. This section describes some ways in which you can reliably get hold of the data you might choose to act on. It is intended to be informative and without it would make it substantially difficult for implementers to implement CT.
Suggest resolve wontfix.