Problem Statement and Requirements for the Operation and Control Networks (OCNs)
draft-tf-ocn-ps-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tooba Faisal , Diego Lopez , Jose A. Ordonez-Lucena , Kiran Makhijani | ||
| Last updated | 2023-01-03 (Latest revision 2022-07-02) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
The emergence of applications based on machine-to-machine communications require control systems to be extended beyond their closed environments. Specifically, autonomous systems that bring about physical and mechanical changes to an environment, heavily rely on their remote operations and control. This document provides an overview of the issues associated with the communications in the control systems to support network-based operations in a generic manner at any-scale environments. The term Operations and Control networks (OCN) is used to describe the common characteristics emerging from the requirements for such control systems. The OCNs are technology-agnostic concept. This document aims to discuss the requirements for establishing common interfaces and functions.
Authors
Tooba Faisal
Diego Lopez
Jose A. Ordonez-Lucena
Kiran Makhijani
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)