Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

General Comments #16

Open
DaveGFord opened this issue Aug 7, 2019 · 1 comment
Open

General Comments #16

DaveGFord opened this issue Aug 7, 2019 · 1 comment
Labels
feedback feedback on the guidelines.

Comments

@DaveGFord
Copy link

The Bulk Dataset via API indicates three (3) guidelines/considerations. One of which is “small datasets”. A lot of data requests call for larger segments of data, so I’d like to see a section reference larger datasets via API’s.

API Security section – Secure Data in Transit references enabling TLS version 1.2. I know last year(?) we had to upgrade due to TLS vulnerabilities and I think(?) we moved to TLS 1.2 however there’s a transcript collision (SLOTH) in 1.2. Should we be forward-looking and recommend the build of API’s that leverage TLS 1.3?

Other than that I think this is a very well written guide.

@ll911 ll911 added the feedback feedback on the guidelines. label Aug 9, 2019
@jeff-card
Copy link
Collaborator

Thank you for your comment! A peer review was held on August 9th and we have the following feedback:

We hope we’ve answered most of your feedback through the guidelines and these answers. With respect to TLS 1.3, this is preferred, but since there are still some limitations around use of TLS 1.3, the guideline’s wording will focus on using TLS 1.2 or newer versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback feedback on the guidelines.
Projects
None yet
Development

No branches or pull requests

3 participants