Security for Low-Latency Group Communication
draft-somaraju-ace-multicast-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Abhinav Somaraju , Sandeep S. Kumar , Hannes Tschofenig , Walter Werner | ||
| Last updated | 2016-07-21 (Latest revision 2016-01-15) | ||
| Replaced by | draft-tschofenig-ace-group-communication-security | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Some Internet of Things application domains, such as lighting, have strict requirements on latency for group communication. From a user experience point of view latency less than 200 ms is necessary from an action triggered by a user to the visible effects. This draft describes procedures for authorization, key management, and securing group messages within a low latency application domain with a special emphasis on lighting systems. We specify the usage of object security at the application layer for group communication and assume that CoAP is used as the application layer protocol.
Authors
Abhinav Somaraju
Sandeep S. Kumar
Hannes Tschofenig
Walter Werner
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)