[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Captive-portals] The architecture requiring that the API be secure
Issue #6 in the architecture draft (https://github.com/capport-wg/architecture/issues/6)
was raised to point out that we should really mandate that the API be secure.
Basically, we want to make TLS a requirement, not a suggestion, so I've changed the
wording around TLS to reflect this. I also added a section to the security section
discussing the motivation behind the requirement.
I haven't submitted a new draft with these changes yet; they're still on github in a pull
Let me know if you have any comments or concerns.
This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is considered confidential, proprietary, sensitive and/or otherwise legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation.