On 10/21/15 8:13 AM, Benjamin Kaduk wrote: > I don't think that's quite the point I was trying to make. HTTPS is > HTTP layered on top of TLS, yes, but in order for there to be a > separation of layers, TLS should not include any data structures that > are only useful for the HTTPS case. This document seems to add a field > to TLS that is only used in the HTTPS use case, which seems like a > layering violation to me.
In fairness you can express all sorts of endpoint addresses as URLs, not just http. That said I agree that this is not an attractive proposal - the performance improvement over existing redirect models is marginal, there may be some unpleasant middlebox interactions, and it would require API changes. The cost/benefit tradeoff isn't favorable, on balance. Melinda -- Melinda Shore No Mountain Software melinda.sh...@nomountain.net "Software longa, hardware brevis." _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
