[PING] privacy at IETF hackathon


If you are coming to IETF 101 in London, please consider signing up for the hackathon to work on privacy and/or other projects of public interest.

To get things started, Mallory Knodel (Article 19), Joe Hall, DKG and I put together some potential topics (see the wiki):

* HTTP status code 451 - this would involve further refining of software and services that the group worked on in 2017 around HTTP status code 451

* Measuring leakage from IoT with a MITM proxy - essentially creating a process and document that network researchers can use to sniff the traffic of IoT devices they have control over (this would be sort of like a generic guide to consentual network inspection).

* WebRTC Apple discoverability, IP route leaks - apparently Safari has a clever method of blocking WebRTC private address leakage, can we hack on that?

* Web protocol privacy considerations - an opportunity to spend some intensive time on our annotated privacy questionnaire

* Privacy impact assessment tool on RFCs - can we build a tool that could spot potential privacy issues with RFCs?

Also, if you have other ideas, please share them here or add them to the wiki.

Looking forward to seeing you in London. 

Information about the IETF Hackathon: https://www.ietf.org/how/runningcode/hackathons/101-hackathon/
IETF Hackathon wiki: https://trac.ietf.org/trac/ietf/meeting/wiki/101hackathon


Received on Thursday, 8 March 2018 01:17:11 UTC