<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.pritikin-anima-bootstrapping-keyinfra" target="https://datatracker.ietf.org/doc/html/draft-pritikin-anima-bootstrapping-keyinfra-02">
   <front>
      <title>Bootstrapping Key Infrastructures</title>
      <author initials="M." surname="Pritikin" fullname="Max Pritikin">
         <organization>Cisco</organization>
      </author>
      <author initials="M." surname="Richardson" fullname="Michael Richardson">
         <organization>SSW</organization>
      </author>
      <author initials="M. H." surname="Behringer" fullname="Michael H. Behringer">
         <organization>Cisco</organization>
      </author>
      <author initials="S." surname="Bjarnason" fullname="Steinthor Bjarnason">
         <organization>Cisco</organization>
      </author>
      <date month="July" day="6" year="2015" />
      <abstract>
	 <t>   This document specifies automated bootstrapping of an key
   infrastructure using vendor installed IEEE 802.1AR manufacturing
   installed certificates, in combination with a vendor based service on
   the Internet.  Before being authenticated, a new device has only
   link-local connectivity, and does not require a routable address.
   When a vendor provides an Internet based service, devices can be
   forced to join only specific domains but for constrained environments
   we describe a variety of options that allow bootstrapping to proceed.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-pritikin-anima-bootstrapping-keyinfra-02" />
   
</reference>
