the Description and Definition for Atomic Security Functions
draft-chen-atomized-security-functions-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Meiling Chen , Li Su | ||
| Last updated | 2023-04-10 (Latest revision 2022-10-07) | ||
| 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
At present, many security products are deployed in the network, and the security functions of security products overlap. Atomized security function refers to the smallest representation unit of security function, which cannot be split again and can be implemented by independent code. Atomized security functions can quickly and effectively assemble security capabilities and provide security services. It no longer takes security products as the unit, but atomic security functions as the basic unit, by reorganize and define the security functions supported by existing network devices then provide guidance for secure routing, finally, each security function will be uniformly coded.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)