Info on LS2 encryption key selection

i2p2www/pages/site/docs/how/network-database.html

@@ -268,7 +268,7 @@ This is the only planned use for that signing key, so it is currently unused.
 {%- endtrans %}</p>
 
 
-<h3 id="encrypted">LeaseSet2 (LS2)</h3>
+<h3 id="ls2">LeaseSet2 (LS2)</h3>
 <p>{% trans -%}
 As of release 0.9.38, floodfills support a new LeaseSet2 structure.
 This structure is very similar to the old LeaseSet structure, and serves the same purpose.
@@ -279,7 +279,7 @@ See proposal 123 for details.
 {%- endtrans %}</p>
 
 
-<h3 id="encrypted">Meta LeaseSet (LS2)</h3>
+<h3 id="meta">Meta LeaseSet (LS2)</h3>
 <p>{% trans -%}
 As of release 0.9.38, floodfills support a new Meta LeaseSet structure.
 This structure provides a tree-like structure in the DHT, to refer to other LeaseSets.
@@ -309,7 +309,7 @@ research whether the user interface and implementation of encrypted LeaseSets co
 {%- endtrans %}</p>
 
 
-<h3 id="encrypted">{% trans %}Encrypted LeaseSets{% endtrans %} (LS2)</h3>
+<h3 id="encrypted2">{% trans %}Encrypted LeaseSets{% endtrans %} (LS2)</h3>
 <p>{% trans -%}
 As of release 0.9.38, floodfills support a new, EncryptedLeaseSet structure.
 The Destination is hidden, and only a blinded public key and an expiration
@@ -330,9 +330,22 @@ For EncryptedLeaseSet and MetaLeaseSet, the expiration may vary,
 and maximum expiration may be enforced, to be determined.
 {%- endtrans %}</p>
 
+
 <h3>{% trans %}LeaseSet Persistent Storage{% endtrans %}</h3>
 <p>{% trans -%}
-There is no persistent storage of LeaseSet data since they expire so quickly.
+No persistent storage of LeaseSet data is required, since they expire so quickly.
+Howewver, persistent storage of EncryptedLeaseSet and MetaLeaseSet data
+with long expirations may be advisable.
+{%- endtrans %}</p>
+
+
+<h3 id="ls2keys">{% trans %}Encryption Key Selection{% endtrans %} (LS2)</h3>
+<p>{% trans -%}
+LeaseSet2 may contain multiple encryption keys.
+The keys are in order of server preference, most-preferred first.
+Default client behavior is to select the first key with
+a supported encryption type. Clients may use other selection algorithms
+based on encryption support, relative performance, and other factors.
 {%- endtrans %}</p>
 
 

i2p2www/spec/proposals/123-new-netdb-entries.rst

@@ -5,7 +5,7 @@ New netDB Entries
     :author: zzz, str4d, orignal
     :created: 2016-01-16
     :thread: http://zzz.i2p/topics/2051
-    :lastupdated: 2019-01-25
+    :lastupdated: 2019-01-27
     :status: Open
     :supercedes: 110, 120, 121, 122
 
@@ -413,6 +413,11 @@ Notes
 - If we ever implement revocation, we can do it with an expires field of zero,
   or zero leases, or both. No need for a separate revocation key.
 
+- Encryption keys are in order of server preference, most-preferred first.
+  Default client behavior is to select the first key with
+  a supported encryption type. Clients may use other selection algorithms
+  based on encryption support, relative performance, and other factors.
+
 
 Encrypted LS2
 -------------