<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.zubov-snif" target="https://datatracker.ietf.org/doc/html/draft-zubov-snif-04">
   <front>
      <title>Deploying Publicly Trusted TLS Servers on IoT Devices Using SNI-based End-to-End TLS Forwarding (SNIF)</title>
      <author initials="J." surname="Zubov" fullname="Jim Zubov">
         <organization>VESvault Corp</organization>
      </author>
      <date month="February" day="16" year="2022" />
      <abstract>
	 <t>   This document proposes a solution, referred as SNIF, that provides
   the means for any Internet connected device to:

   *  allocate a globally unique anonymous hostname;

   *  obtain and maintain a publicly trusted X.509 certificate issued
      for the allocated hostname;

   *  accept incoming TLS connections on specific TCP ports of the
      allocated hostname from any TLS clients that are capable of
      sending Server Name Indication.

   The private key associated with the X.509 certificate is securely
   stored on the TLS terminating device, and is never exposed to any
   other party at any step of the process.

About This Document

   This note is to be removed before publishing as an RFC.

   Status information for this document may be found at
   https://datatracker.ietf.org/doc/draft-zubov-snif.

   Information can be found at https://snif.host.

   Source for this draft and an issue tracker can be found at
   https://github.com/vesvault/snif-i-d.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-zubov-snif-04" />
   
</reference>
