httpbis: Ticket #41: Security Considerations

Link:  http://trac.tools.ietf.org/wg/httpbis/trac/ticket/41

Component: non-specific

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?

Mails

• Closing i41: Security Considerations #41 Mark Nottingham (mnot@mnot.net) (2008-04-03)

History

: comment added; component, milestone set (Fri, 04 Jan 2008 06:11:53 GMT)

• component set to non-specific
• milestone set to unassigned

: comment added; version set (Fri, 04 Jan 2008 06:30:54 GMT)

• version set to 00-draft

: comment added; resolution set; status changed (Thu, 03 Apr 2008 02:19:59 GMT)

• status changed from new to closed.
• resolution set to fixed

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

Related Information

Issues List Index