Review of existing standards and their applicability

From Web of Things Community Group


W3C is responsible for many standards relevant to the Web of Things, e.g. HTML, XML, scripting APIs, and work related to rich descriptions.

insert bullet list of areas here


ITU-T SG13 Q.12

Recommendation ITU-T Y.2063 provides a framework of the web of things (WoT). As the use of various devices has become so widespread, it is difficult to access data on these devices in a unified way. The WoT allows physical devices to be accessed as resources of both the web and services/applications based upon a web-based service environment, as well as through legacy telecommunications.

This Recommendation describes the overview of the WoT and identifies the requirements to support the WoT. In addition, this Recommendation specifies the functional architecture including a deployment model for the WoT



The HyperText Transfer Protocol (HTTP) is the mainstay of the Web for accessing resources made available by servers. It is currently defined by RFC 2616 and provides a request/response protocol over TCP/IP. HTTP can be used together with XML or JSON for transferring structured data. Representational state transfer (REST) is a set of principles that can be applied to create lightweight services implemented on top of HTTP.


The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as 6LoWPAN often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.

CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead and simplicity for constrained environments.

IETF Home Networking WG (HomeNet)

This working group focuses on the evolving networking technology within and among relatively small "residential home" networks. Current home networks are largely IPv4 based, however, this is expected to change and IPv6 home networks are expected to include several subnets, e.g. to facilitate private and guest networks, heterogeneous link layers, and smart grid components, and have enough address space available to allow every device to have a globally unique address. More details are given in the following Internet Draft:


  • ETSI TS 102 689: "Machine-to-Machine communications (M2M); M2M service requirements"
  • ETSI TS 102 690: "Machine-to-Machine communications (M2M); M2M functional architecture".
  • ETSI TR 102 691: "Machine-to-Machine communications (M2M); Smart Metering Use Cases".
  • ETSI TR 102 732: "Machine to Machine Communications (M2M); Use cases of M2M applications for eHealth".
  • ETSI TR 102 897: "Machine to Machine Communications (M2M); Use cases of M2M applications for City Automation".
  • ETSI TR 102 875: "Access, Terminals, Transmission and Multiplexing (ATTM); Study of European requirements for Virtual Noise for ADSL2, ADSL2plus and VDSL2".
  • ETSI TR 102 898: "Machine to Machine Communications (M2M); Use cases of Automotive Applications in M2M capable networks".