On 4/28/2017 1:37 PM, Ilari Liusvaara wrote: >> The key, however, is that this proposal is really redefining HTTP ports >> 80 and 443 (if that's the direction you go), and you need to get >> consensus on that. It's not enough to simply say "we want to do it and >> it works as currently specd". > The properties this draft exploits for detection are completely > fundamential to HTTP/1.x and HTTP/2. There is no way anything that > breaks those properties can be deployed on mass scale without a new > ALPN, which should be ample warning to the server that new things > are going on.
All I'm asking is that this doc makes it very clear that it intends to redefine the services on ports 80 and/or 443, if that's the way you go. I'll leave it to others to decide whether that's a good idea or not. Joe
_______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
