Opened 15 years ago

Closed 14 years ago

#41 closed design (fixed)

Security Considerations

Reported by: mnot@… Owned by:
Priority: Milestone: unassigned
Component: non-specific Severity:
Keywords: Cc:


What work needs to be done to the Security Considerations section

of RFC2616 to allow publication of a revision? E.g., does HTTP need to specify a Mandatory To Implement mechanism?

Change History (3)

comment:1 Changed 15 years ago by mnot@…

  • Component set to non-specific
  • Milestone set to unassigned

comment:2 Changed 15 years ago by mnot@…

  • version set to 00-draft

comment:3 Changed 14 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from new to closed

Satisfied by the security properties document (not done yet, but chartered).

Note: See TracTickets for help on using tickets.