<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.nir-saag-star" target="https://datatracker.ietf.org/doc/html/draft-nir-saag-star-01">
   <front>
      <title>Considerations For Using Short Term Certificates</title>
      <author initials="Y." surname="Nir" fullname="Yoav Nir">
         <organization>Dell EMC</organization>
      </author>
      <author initials="T." surname="Fossati" fullname="Thomas Fossati">
         <organization>Nokia</organization>
      </author>
      <author initials="Y." surname="Sheffer" fullname="Yaron Sheffer">
         <organization>Intuit</organization>
      </author>
      <author initials="T. T." surname="Eckert" fullname="Toerless Eckert">
         <organization>Huawei USA - Futurewei Technologies Inc.</organization>
      </author>
      <date month="March" day="5" year="2018" />
      <abstract>
	 <t>   Recently there has been renewed interest in an old idea: Issue
   certificates with short validity periods and forego revocation
   processing, reasoning that expiration is a sufficient replacement for
   revocation as long as that expiration is not too far off.

   This document covers considerations, both security and operational,
   for using such Short Term Auto Renewed (STAR) certificates for
   various scenarios where Using a revocation protocol is considered
   inappropriate.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-nir-saag-star-01" />
   
</reference>
