<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.zhang-trans-ct-binary-codes" target="https://datatracker.ietf.org/doc/html/draft-zhang-trans-ct-binary-codes-04">
   <front>
      <title>CT for Binary Codes</title>
      <author initials="L." surname="Xia" fullname="Liang Xia">
         <organization>Huawei</organization>
      </author>
      <author initials="D." surname="Zhang" fullname="Dacheng Zhang">
         <organization>Huawei</organization>
      </author>
      <author initials="D. K." surname="Gillmor" fullname="Daniel Kahn Gillmor">
         <organization>CMRG</organization>
      </author>
      <author initials="B." surname="Sarikaya" fullname="Behcet Sarikaya">
         <organization>Huawei USA</organization>
      </author>
      <date month="March" day="6" year="2017" />
      <abstract>
	 <t>   This document proposes a solution extending the Certificate
   Transparency protocol [I-D.ietf-trans-rfc6962-bis] for transparently
   logging the software binary codes (BC)or its digest with their
   signature, to enable anyone to monitor and audit the software
   provider activity and notice the distribution of suspect software as
   well as to audit the BC logs themselves.  The solution is called
   &quot;Binary Transparency&quot; in this document.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-zhang-trans-ct-binary-codes-04" />
   
</reference>
