title: How does TLS Channel ID guarantee client authenticity?
body: <p>I've read <a href="https://datatracker.ietf.org/doc/html/draft-balfanz-tls-channelid-00" rel="nofollow noreferrer">RFC draft</a> for Channel ID. I've also read the earlier <a href="https://datatracker.ietf.org/doc/html/draft-balfanz-tls-obc-01" rel="nofollow noreferrer">draft for OBC's</a>, but I'm a little slow to follow. I understand that Google has implemented a new extension based on their earlier Channel ID work. I'm curious to learn what the benefits are and how they are accomplished, but I can't seem to find much detail on the topic from a systems perspective (I'm not a crypto man).</p>
  <p>How does Channel ID guarantee the authenticity of a client machine in a SSL session?</p>