diff options
| author | Silvio Rhatto <rhatto@riseup.net> | 2010-01-25 17:03:35 -0200 |
|---|---|---|
| committer | Silvio Rhatto <rhatto@riseup.net> | 2010-01-25 17:03:35 -0200 |
| commit | 50cbee1e3788ce19366d16f35bb455e885e8326a (patch) | |
| tree | 478d43214befc6b85c88e0f7c5e81cb178862d41 | |
| parent | 6757b53cbcaa9d118261c356a85b4c517f90748c (diff) | |
| download | rsp-50cbee1e3788ce19366d16f35bb455e885e8326a.tar.gz rsp-50cbee1e3788ce19366d16f35bb455e885e8326a.tar.bz2 | |
Minor fix
| -rw-r--r-- | index.mdwn | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -120,7 +120,8 @@ This way, RSP metadata is encapsulated in resource packages that can be announce # Rulesets It is not strict builtin in the protocol but your group can also adopt internal rules regarding what goes at each layer. As an example, a group can adopt a data persistence rule such as data in a layer with a given level of security cannot be moved to a layer with a lower security level, except in cases it is temporarily or permanently declassified. -Implementation + +# Implementation The RSP implementation does not come directly from the protocol. It can be implemented several ways, like keeping tables or wiki pages with detailed information about each layer a given group (or groups) have, can offer or needs. You could even consider to write a script to keep this data updated, although this can be very difficult. One of the best ways to keep the metadata updated is through periodical audits in each layer. |