<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.wing-settle-requirements" target="https://datatracker.ietf.org/doc/html/draft-wing-settle-requirements-00">
   <front>
      <title>Requirements for HTTPS for Local Domains</title>
      <author initials="D." surname="Wing" fullname="Dan Wing">
         <organization>Cloud Software Group, Inc.</organization>
      </author>
      <author initials="E." surname="Nygren" fullname="Erik Nygren">
         <organization>Akamai Technologies</organization>
      </author>
      <author initials="M." surname="Richardson" fullname="Michael Richardson">
         <organization>Sandelman Software Works</organization>
      </author>
      <date month="March" day="3" year="2025" />
      <abstract>
	 <t>   When connecting to servers on their local network, users are
   surprised to encounter user interfaces that display errors, show
   insecure connections, and block some HTTP features when missing a
   secure context.  However, obtaining PKIX certificates for those
   servers is difficult for a variety of reasons.

   This document explores requirements for authenticating local servers.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-wing-settle-requirements-00" />
   
</reference>
