Defined-Trust Transport (DeftT) Protocol for Limited Domains
draft-nichols-tsv-defined-trust-transport-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Kathleen Nichols , Van Jacobson , Randy King | ||
| Last updated | 2022-07-11 | ||
| Replaced by | draft-nichols-iotops-defined-trust-transport | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-nichols-iotops-defined-trust-transport | |
| 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
This document describes a broadcast-friendly, many-to-many Defined- trust Transport (DeftT) that makes it simple to express and enforce application and deployment specific integrity, authentication, access control and behavior constraints directly in the protocol stack. DeftT combined with IPv6 multicast and modern hardware-based methods for securing keys and code provides an easy to use foundation for secure and efficient communications in Limited Domains (RFC8799), in particular for Operational Technology (OT) networks.
Authors
Kathleen Nichols
Van Jacobson
Randy King
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)