Add Security Considerations section

[ioggstream]

I expect

• a Security Consideration section / document

Instead

• there is not
• some security hints are scattered throughout the document

See https://github.com/ietf-wg-httpapi/mediatypes/pull/49/files#diff-b22c3a369e1499074590046ad01b71334e21c491c64ccf045f8858e2d3036e56R543

cc: @darrelmiller

[MikeRalphson]

Link #3037

[handrews]

@OAI/tsc / @darrelmiller is this done? Should we add the currently-separate Security Considerations document into 3.0.4 and 3.1.1 as a section?

[ralfhandl]

Should we add the currently-separate Security Considerations document into 3.0.4 and 3.1.1 as a section?

Yes, please, and add links to corresponding specification sections to the text.

[miqui]

@ralfhandl , @handrews I would like to up vote Ralf's suggestion.

[handrews]

@ralfhandl @miqui I think the only reason this was ever a separate document is that we couldn't insert it into the published documents after the fact.

I agree that we should at least link it, but in most specifications (IETF, W3C, etc.) "Security Considerations" is a section in the document itself. So I'm asking if we should put it in 3.0.4 and 3.1.1 or if there is a reason to keep it separate.

[darrelmiller]

TDC consensus to move this content into the patch updates. Suggestion to add headings to make it clearer.

[handrews]

PR merged for 3.0.4 and ported to 3.1.1 via PR #3921!