>>>>> "VD" == Viktor Dukhovni <[email protected]> writes:
VD> I was thinking of multiplexing by port, rather than URI. I got that. But what if the MXs already run something on port 443? If the GET/POST path can be specified, the existing web server can proxy to the MTA's port. Otherwise the MTA would have to proxy anything which it doesn't handle. Of course, with ipv6 there are always enough addresses to put the other 443 service(s) on their own ip. So it is a short-term issue. And it may take longer for something like this widely to deploy than it will for v6 to displace v4 w/in the subset of sites which would use it. So it may not be worth worry. Otherwise, I like the idea. Either way, it would be cool for such a service to provide gpg keyids, too. So the reply should include for each line a token specifying which kind of key (smime, gpg, future) that line matches. -JimC -- James Cloos <[email protected]> OpenPGP: 0x997A9F17ED7DAEA6 _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
