Tied to domains, but you still have a good point. Try getting a cert for "foo.myhouse.lan" (and that ignores complications of coordinating hostnames of embedde

Tied to domains, but you still have a good point. Try getting a cert for "foo.myhouse.lan" (and that ignores complications of coordinating hostnames of embedded device ahead of time). On a manged corporate intranet, Active Directory can push out a new CA and your computer trust whatever certs the local IT department wants to cook up, but it breaks down with a BYOD office or SOHO lan. I manage a few intranet websites, this encryption requirement basically kills any interest I had in experimenting with HTTP/2 which was already miniscule. I'm not seeing the use case for HTTP/2 unless you're already all-https or in the Top N websites and want to slim down bandwidth use.