<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.kwatsen-netconf-voucher" target="https://datatracker.ietf.org/doc/html/draft-kwatsen-netconf-voucher-00">
   <front>
      <title>Voucher and Voucher Revocation Profiles for Bootstrapping Protocols</title>
      <author initials="K." surname="Watsen" fullname="Kent Watsen">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="M." surname="Richardson" fullname="Michael Richardson">
         <organization>SSW</organization>
      </author>
      <author initials="M." surname="Pritikin" fullname="Max Pritikin">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="T. T." surname="Eckert" fullname="Toerless Eckert">
         <organization>Cisco Systems</organization>
      </author>
      <date month="October" day="31" year="2016" />
      <abstract>
	 <t>   This memo defines the two artifacts &quot;voucher&quot; and &quot;voucher-
   revocation&quot;, which are YANG-defined structures that have been signed
   by a TBD algorithm.

   The voucher artifact is generated by the device&#x27;s manufacture or
   delegate.  The voucher&#x27;s purpose is to securely assign one or more
   devices to an owner.  The voucher informs each device which entity it
   should consider to be its owner.

   The voucher revocation artifact is used by the manufacturer or
   delegate (i.e.  the issuer of the voucher) to revoke vouchers, if
   ever necessary.  The voucher revocation format defined herein
   supports both issuer-wide and voucher-specific constructs, enabling
   usage flexibility.

   For both artifacts, this memo only defines the artifact, leaving it
   to future work to describe specialized protocols for accessing them.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-kwatsen-netconf-voucher-00" />
   
</reference>
