|author||pukkamustard <email@example.com>||2020-11-28 08:55:28 +0100|
|committer||pukkamustard <firstname.lastname@example.org>||2020-11-28 08:55:28 +0100|
eris.adoc: note on confidentiality
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/eris.adoc b/doc/eris.adoc
index 1056fb5..c754487 100644
@@ -24,7 +24,7 @@ However, naive content-addressing has certain drawbacks:
- Large content is stored as a large chunk of data. In order to optimize storage and network operations it is better to split up content into smaller uniformly sized blocks and reassemble blocks when needed.
- Confidentiality: Content is readable by all peers involved in transporting, caching and storing content.
-ERIS addresses these issues by splitting content into small uniformly sized and encrypted blocks.
+ERIS addresses these issues by splitting content into small uniformly sized and encrypted blocks. These blocks can be reassembled to the original content only with access to a short _read capability_, which can be encoded as an URN.
Encodings similar to ERIS are already widely-used in applications and protocols such as GNUNet (see <<_previous_work>>), BitTorrent <<BEP52>>, Freenet <<Freenet>> and others. However, they all use slightly different encodings that are tied to the respective protocols and applications. ERIS defines an encoding independant of any specific protocol or application and decouples content from transport and storage layers. ERIS may be seen as a modest step towards Information-Centric Networking <<RFC7927>>.
@@ -34,7 +34,8 @@ The objectives of ERIS are:
Availability :: Content encoded with ERIS can be easily replicated and cached.
Integrity :: Integrity of content can be verified efficiently.
-URN reference :: ERIS encoded content can be referrenced with a single URN.
+Confidentiality :: Encoded content can only be decoded with access to the read capability. Peers without access to the read capability can cache and transport individiual blocks without being able to read the content.
+URN reference :: ERIS encoded content can be referrenced with a single URN (the encoded read capability).
Storage efficiency :: ERIS can be used to encode small content (< 1 kibibyte) as well as large content (> many gibibyte) with reasonable storage overhead.
Simplicity :: The encoding should be as simple as possible in order to allow correct implementation on various platforms and in various languages.