In article <[email protected]> you write: >On Fri, Dec 12, 2014 at 05:50:10PM -0500, James Cloos wrote: > >> VD> of the protocol. >> >> The only issue with using SRV is that the http GET path would have to be >> standardized, which could be an pain if the advertized MXs already serve >> https for something else. > >I was thinking of multiplexing by port, rather than URI. So that >the service in question really could be a light-weight HTTPS server >add-on to an MTA, rather than an HTTP application in a general >purpose HTTPS server.
Before we go too far down this road, we might check with some people who run large mail systems and ask how likely they are to spin up an all new address verification server. It doesn't seem very likely to me. The DNS has its faults, but it has the great advantage of already existing. R's, John _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
