+1 to CoAP, cause MQTT is an insecure hack.
2. Bootstrapping this will require a substantial number of hardware vendors to sign on, both at the edge and at the hub layers. IMHO this is why Google Weave [1] never took off in it's original incarnation. Bootstrapping this like they did with web stuff isn't enough, because this isn't the web.
+1 Check out Oauth.
3. Devices are only part of the problem: We need a software services layer, too. Think time services, IFTTT-like orchestrators, media services, etc.
Sounds to me like a good start up proposition!
4. JSON is a non-starter long-term: it sucks for small devices. They need a binary format that is easy to parse.
RFC7049
5. Request-Response isn't the right pattern for most use cases.
-1 Wrong.
6. The Property/Action/Event concept is a solid start.
W3C WoT Thing Description.
7. For the love of everything holy, add versioning!
+1