[tor-commits] [torspec/master] Clarify 285 further.

[nickm@xxxxxxxxxxxxxx]

commit 8bc8bf05bb1a0cc6f70bf5b14e745c968d9083e4
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date:   Tue Jan 9 12:33:13 2018 -0500

    Clarify 285 further.
---
 proposals/285-utf-8.txt | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/proposals/285-utf-8.txt b/proposals/285-utf-8.txt
index a7f4626..6521e03 100644
--- a/proposals/285-utf-8.txt
+++ b/proposals/285-utf-8.txt
@@ -22,6 +22,8 @@ Status: Open
    So, in this proposal, we describe a migration path to having all
    directory documents be fully UTF-8.
 
+   (See 2.3 below for a discussion of what exactly we mean by "non-UTF-8".)
+
 2. Proposal
 
    First, we should have Tor relays reject ContactInfo lines (and any
@@ -58,12 +60,21 @@ Status: Open
    the "reject-encrypted-non-utf-8" parameter, that parameter can be set
    to 1.
 
-2.2. Which UTF-8 exactly?
+2.2. Bridge descriptors
+
+   Since clients download bridge descriptors directly from the bridges, they
+   also need a two-phase plan as for hidden service descriptors above.  Here
+   we take the same approach as in section 2.1 above, except using the
+   parameter "reject-bridge-descriptor-non-utf-8".
+
+2.3. Which UTF-8 exactly?
 
    We define the allowable set of UTF-8 as:
       * Encoding the codepoints U+01 through U+10FFFF,
       * but excluding the codepoints U+D800 through U+DFFF,
       * each encoded with the shortest possible encoding.
+      * without any BOM.
+
 
 
 

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits