Opened 11 years ago
Closed 10 years ago
#313 closed design (fixed)
SHOULD and MAY review in p6
Reported by: | mnot@… | Owned by: | draft-ietf-httpbis-p6-cache@… |
---|---|---|---|
Priority: | normal | Milestone: | 17 |
Component: | p6-cache | Severity: | Active WG Document |
Keywords: | Cc: |
Description
Design implications of #271 tracked here.
Thread starts at <http://www.w3.org/mid/90400372-C89F-4E9C-92F6-D8F1A6AAD631@mnot.net>
Change History (4)
comment:1 Changed 11 years ago by mnot@…
comment:2 Changed 11 years ago by mnot@…
- Milestone changed from unassigned to 17
- Resolution set to incorporated
- Status changed from new to closed
comment:3 Changed 10 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:4 Changed 10 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
From [1433]:
Turn non-requirement SHOULDs and MAYs into prose; strengthen some obvious candidates into MUST, as per discussion. See #313