diff options
| author | Nick Mathewson <nickm@torproject.org> | 2018-01-09 12:33:13 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2018-01-09 12:33:13 -0500 |
| commit | 8bc8bf05bb1a0cc6f70bf5b14e745c968d9083e4 (patch) | |
| tree | 55671de7959d54fa68d58f3e39071f0697e0eccb /proposals/285-utf-8.txt | |
| parent | 414df99cfacc6f573fbe47f3e1350eb8a0965889 (diff) | |
| download | torspec-8bc8bf05bb1a0cc6f70bf5b14e745c968d9083e4.tar.gz torspec-8bc8bf05bb1a0cc6f70bf5b14e745c968d9083e4.zip | |
Clarify 285 further.
Diffstat (limited to 'proposals/285-utf-8.txt')
| -rw-r--r-- | proposals/285-utf-8.txt | 13 |
1 files changed, 12 insertions, 1 deletions
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. + |