[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-380) Insert a section in protocol (and similar in JSON and ATOM) named 'Security Considerations' (before 'Conformance')
[ http://tools.oasis-open.org/issues/browse/ODATA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Drees updated ODATA-380:
-------------------------------
Resolution:
https://www.oasis-open.org/committees/download.php/49275/odata-v4.0-wd02-part1-protocol-2013-05-21.docx
https://www.oasis-open.org/committees/download.php/49273/odata-atom-format-v4.0-wd02-2013-05-21.docx
https://www.oasis-open.org/committees/download.php/49274/odata-json-format-v4.0-wd02-2013-05-21.docx
Accepted: https://www.oasis-open.org/committees/download.php/49557/odata-meeting-41_on-20130613_14-F2F-minutes.html#odata-380
was:
https://www.oasis-open.org/committees/download.php/49275/odata-v4.0-wd02-part1-protocol-2013-05-21.docx
https://www.oasis-open.org/committees/download.php/49273/odata-atom-format-v4.0-wd02-2013-05-21.docx
https://www.oasis-open.org/committees/download.php/49274/odata-json-format-v4.0-wd02-2013-05-21.docx
> Insert a section in protocol (and similar in JSON and ATOM) named 'Security Considerations' (before 'Conformance')
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ODATA-380
> URL: http://tools.oasis-open.org/issues/browse/ODATA-380
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData ATOM Format , OData JSON Format, OData Protocol
> Affects Versions: V4.0_CSD01
> Environment: [Applied]
> Reporter: Stefan Drees
> Assignee: Stefan Drees
> Fix For: V4.0_CSD02
>
>
> We have some spurious overlaps with security considerations but are remarkably silent about it as a whole, when considereing, that we suggest opening up the silos of data. Although we rely on other protocols that handle transport and security, we should follow the role model of IETF in enforcing a security considerations section in each I-D. It should be quite cheap as we can refer to the security considerations of the underlying protocols (HTTP has some elaboratesubsections on this)
> This started from discussions and comments on ODATA-301 but to the reporter also seems like a very natural, reasonable and "expected" thing to be provided by the TC and inside the work products.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]