Opened 7 years ago
Closed 7 years ago
#74 closed defect (wontfix)
normative statement of TLS client behavior in Section 3
Reported by: | kent@… | Owned by: | draft-ietf-trans-rfc6962-bis@… |
---|---|---|---|
Priority: | blocker | Milestone: | review |
Component: | rfc6962-bis | Version: | |
Severity: | - | Keywords: | |
Cc: |
Description
Section 3 states:
A certificate not accompanied by an SCT (either for the end-entity certificate or for a name-constrained intermediate the end-entity certificate chains to) MUST NOT be considered compliant by TLS clients.
This is a normative statement about client behavior. Which is out of scope.
Change History (4)
comment:1 Changed 7 years ago by rob.stradling@…
- Component changed from client-behavior to rfc6962-bis
comment:2 Changed 7 years ago by benl@…
Describing how the protocol works from the client's POV is _not_ about client behaviour, it is about the client's understanding of the situation. How it behaves as a result of that understanding is behaviour.
I propose this should be closed "wontfix".
comment:3 Changed 7 years ago by rob.stradling@…
- Milestone set to review
Thanks Ben. Good point. I agree that WONTFIX makes sense.
comment:4 Changed 7 years ago by melinda.shore@…
- Resolution set to wontfix
- Status changed from new to closed
Changing component to rfc6962-bis, since this ticket requests text to be removed from that document.
Clearly the client-behavior document should make this normative statement about client behavior, but presumably there should be another ticket to track that.