<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-anima-rfc8366bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-anima-rfc8366bis-14">
   <front>
      <title>A Voucher Artifact for Bootstrapping Protocols</title>
      <author initials="K." surname="Watsen" fullname="Kent Watsen">
         <organization>Watsen Networks</organization>
      </author>
      <author initials="M." surname="Richardson" fullname="Michael Richardson">
         <organization>Sandelman Software</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>Futurewei Technologies Inc.</organization>
      </author>
      <author initials="Q." surname="Ma" fullname="Qiufang Ma">
         <organization>Huawei</organization>
      </author>
      <date month="April" day="1" year="2025" />
      <abstract>
	 <t>   This document defines a strategy to securely assign a Pledge to an
   owner using an artifact signed, directly or indirectly, by the
   Pledge&#x27;s manufacturer.  This artifact is known as a &quot;voucher&quot;.

   This document defines an artifact format as a YANG-defined JSON or
   CBOR document that has been signed using a variety of cryptographic
   systems.

   The voucher artifact is normally generated by the Pledge&#x27;s
   manufacturer (i.e., the Manufacturer Authorized Signing Authority
   (MASA)).

   This document updates RFC8366, includes a number of desired
   extensions into the YANG.  The voucher request defined in RFC8995 is
   also now included in this document, as well as other YANG extensions
   needed for variants of BRSKI/RFC8995.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-anima-rfc8366bis-14" />
   
</reference>
