RE: Pushing the current CR for TPE for REComenndation in 2017

Hi Matthias,

 
Could you please reitterate what the group's exit criteria are in terms of the W3C process and the number of implementations?

 
Rob

—
PGP fingerprint: 704F 4955 F7E3 044E 4084 19E2 2844 CDDC A655 DB3C [public_key]

PGP verification is published in DNS which is secured by DNSSEC [rob._pka.blaeu.com]

 
 
 
-----Original message-----
From: Matthias Schunter (Intel Corporation)
Sent: Tuesday, November 7 2017, 9:55 am
To: public-tracking@w3.org (public-tracking@w3.org)
Subject: Pushing the current CR for TPE for REComenndation in 2017
 
Dear TPWG,


in our call yesterday, we decided that we should push the current
unmodified CR towards REC while working on the purposes for the next
release of the TPE standard.

Our charter ends in December and this is the deadline for finishing the
Recommendation.

For getting to REC, we need implementation reports. I currently see four

implementation that were promises:
- Mike's browser plugin (client-side)
- Mike's server extensions (server side)
- The TPE-enhanced  privacy badger  (client side)
- A case study by Deutsche Telekom (client + server)

Did I miss any ongoing effort? Would anyone else have interest and
resources to validate our standard by implementing (parts of) it?

We would need these implementation reports latest by mid December.

Could each of you provide an update to the group?


Regards,
 matthias