IEEE Std 2030.5 is designed to implement a REST architecture. It is built around the core actions of GET, HEAD, PUT, POST, and DELETE (as used in (Fielding [B3]), with the addition of a lightweight subscription mechanism as discussed in 8.7. Any application protocol that can implement a RESTful command set could likely be used with IEEE Std 2030.5, but Hypertext Transfer Protocol (HTTP) is a required baseline for interoperable IEEE 2030.5 implementations. HTTP utilizes Transmission Control Protocol (TCP) as its transport protocol. As a result, TCP manages the session providing delivery assurance and windowing.
IEEE 2030.5 servers and clients SHALL be compliant with IETF RFC 7230, IETF RFC 7231, IETF RFC 7232, IETF RFC 7233, IETF RFC 7234, and IETF RFC 7235.