%% You should probably cite draft-nichols-iotops-defined-trust-transport-07 instead of this revision. @techreport{nichols-iotops-defined-trust-transport-02, number = {draft-nichols-iotops-defined-trust-transport-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-nichols-iotops-defined-trust-transport/02/}, author = {Kathleen Nichols and Van Jacobson and Randy King}, title = {{Defined-Trust Transport (DeftT) Protocol for Limited Domains}}, pagetotal = 62, year = 2023, month = sep, day = 27, abstract = {This document describes a broadcast-oriented, many-to-many Defined- trust Transport (DeftT) framework 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's communication model is one of synchronized collections of secured information rather than one-to- one optionally secured connections. DeftT is part of a Defined-trust Communications approach with a specific example implementation available. Combined with IPv6 multicast and modern hardware-based methods for securing keys and code, it provides an easy to use foundation for secure and efficient communications in Limited Domains (RFC8799), in particular for Operational Technology (OT) networks.}, }