mtrp:security
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| mtrp:security [2026/06/10 13:25] – mosh | mtrp:security [2026/06/10 13:36] (current) – mosh | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | ===== 8.1 Purpose ===== | + | ===== 9.1 Purpose ===== |
| This document defines the current security posture and intended security boundaries of MTRP. | This document defines the current security posture and intended security boundaries of MTRP. | ||
| - | ===== 8.2 Design Intent ===== | + | ===== 9.2 Design Intent ===== |
| MTRP is intended to operate across a range of node classes, from constrained devices to more capable bridge or core nodes. | MTRP is intended to operate across a range of node classes, from constrained devices to more capable bridge or core nodes. | ||
| Line 16: | Line 16: | ||
| * trust policy | * trust policy | ||
| - | ===== 8.3 Security Capabilities ===== | + | ===== 9.3 Security Capabilities ===== |
| Security capability values indicate the forms of security a node or transport may support. | Security capability values indicate the forms of security a node or transport may support. | ||
| Line 28: | Line 28: | ||
| Capability signaling does not, by itself, guarantee that a given message was validated under that capability. It describes support and configuration context. | Capability signaling does not, by itself, guarantee that a given message was validated under that capability. It describes support and configuration context. | ||
| - | ===== 8.4 Network Separation ===== | + | ===== 9.4 Network Separation ===== |
| The network identifier remains useful even in secure deployments. | The network identifier remains useful even in secure deployments. | ||
| Line 36: | Line 36: | ||
| The network identifier is not, by itself, a security mechanism. | The network identifier is not, by itself, a security mechanism. | ||
| - | ===== 8.5 Constrained Security ===== | + | ===== 9.5 Constrained Security ===== |
| For constrained nodes, a reduced but practical security posture MAY be preferable to no security at all. | For constrained nodes, a reduced but practical security posture MAY be preferable to no security at all. | ||
| Line 46: | Line 46: | ||
| * compatibility with bridge-assisted architectures | * compatibility with bridge-assisted architectures | ||
| - | ===== 8.6 Trust Boundaries ===== | + | ===== 9.6 Trust Boundaries ===== |
| MTRP currently assumes relatively simple trust behavior. | MTRP currently assumes relatively simple trust behavior. | ||
| Line 58: | Line 58: | ||
| * secure group-delivery semantics | * secure group-delivery semantics | ||
| - | ===== 8.7 Future Direction ===== | + | ===== 9.7 Future Direction ===== |
| Likely future security work includes: | Likely future security work includes: | ||
/var/www/wiki.moshnetworks.com/data/attic/mtrp/security.1781097912.txt.gz · Last modified: by mosh