[1] draft-balfanz-tls-obc-01 - TLS Origin-Bound Certificates ( ( 版)) <http://tools.ietf.org/html/draft-balfanz-tls-obc-01>
[2] draft-balfanz-tls-channelid-01 - Transport Layer Security (TLS) Channel IDs ( 版) <http://tools.ietf.org/html/draft-balfanz-tls-channelid-01>
[3] Origin-Bound Certificates - BrowserAuth.net ( 版) <http://www.browserauth.net/origin-bound-certificates>
[4] balfanz/tls-obc-spec ( 版) <https://github.com/balfanz/tls-obc-spec>
[5] ( 版) <https://www.usenix.org/system/files/conference/usenixsecurity12/sec12-final162.pdf>
[6] [TLS] Update on Origin-Bound Certificates: Now called "Channel ID" ( ()) <https://www.ietf.org/mail-archive/web/tls/current/msg09042.html>
As you might have noticed, I have let the TLS-Origin-Bound Certificates (TLS-OBC: http://tools.ietf.org/id/draft-balfanz-tls-obc-01.txt) draft expire. The reason for this is that we (i.e., Google) had implemented TLS-OBC as described in the draft (in Chrome and server-side), and we weren't too happy with it. There were a few of problems:
[7] draft-balfanz-tls-channelid-01 - Transport Layer Security (TLS) Channel IDs ( ()) <https://tools.ietf.org/html/draft-balfanz-tls-channelid-01>
[8] Stub for w3c/webappsec-clear-site-data#2. (mikewest著, ) <https://github.com/w3c/webappsec-clear-site-data/commit/5724b15c8a31fc89d73823e4981b4619afabc4cc>