================================================================
#tor-meeting: prop#285 utf-8 in directory documents, 12 Feb 2018
================================================================


Meeting started by teor at 21:04:51 UTC. The full logs are available at
http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-02-12-21.04.log.html
.



Meeting summary
---------------
* ACTION: use "Unicode Scalar" to describe the set of code points in
  section "Which UTF-8 exactly?"  (teor, 21:17:54)
* ACTION: Since we exclude 0x00 (nul), note this difference from Rust
  (teor, 21:20:00)
* ACTION: Since we exclude byte order marks, note this difference from
  Rust  (teor, 21:20:23)
* ACTION: Reference Rust definition of char at
  https://doc.rust-lang.org/1.0.0/unicode/char/  (teor, 21:20:58)
* LINK: https://en.wikipedia.org/wiki/UTF-8#Byte_order_mark   (teor,
  21:23:35)
* ACTION: reference RFC 3629 section 6 to forbid the BOM
  https://tools.ietf.org/html/rfc3629#section-6  (teor, 21:33:02)
* ACTION: update dir-spec.txt to define contact as excluding NUL and NL
  (teor, 21:38:57)
* ACTION: update dir-spec.txt to define platform as ASCII?  (teor,
  21:39:18)
* ACTION: require directory document keywords to be ASCII to avoid
  confusion attacks  (teor, 21:49:13)
* ACTION: specify that unicode newlines are not valid dir-spec NLs
  (teor, 21:51:36)
* ACTION: email relay and bridge operators with non-UTF-8 in their
  contact info  (teor, 21:56:38)

Meeting ended at 21:59:18 UTC.




Action Items
------------
* use "Unicode Scalar" to describe the set of code points in section
  "Which UTF-8 exactly?"
* Since we exclude 0x00 (nul), note this difference from Rust
* Since we exclude byte order marks, note this difference from Rust
* Reference Rust definition of char at
  https://doc.rust-lang.org/1.0.0/unicode/char/
* reference RFC 3629 section 6 to forbid the BOM
  https://tools.ietf.org/html/rfc3629#section-6
* update dir-spec.txt to define contact as excluding NUL and NL
* update dir-spec.txt to define platform as ASCII?
* require directory document keywords to be ASCII to avoid confusion
  attacks
* specify that unicode newlines are not valid dir-spec NLs
* email relay and bridge operators with non-UTF-8 in their contact info




Action Items, by person
-----------------------
* **UNASSIGNED**
  * use "Unicode Scalar" to describe the set of code points in section
    "Which UTF-8 exactly?"
  * Since we exclude 0x00 (nul), note this difference from Rust
  * Since we exclude byte order marks, note this difference from Rust
  * Reference Rust definition of char at
    https://doc.rust-lang.org/1.0.0/unicode/char/
  * reference RFC 3629 section 6 to forbid the BOM
    https://tools.ietf.org/html/rfc3629#section-6
  * update dir-spec.txt to define contact as excluding NUL and NL
  * update dir-spec.txt to define platform as ASCII?
  * require directory document keywords to be ASCII to avoid confusion
    attacks
  * specify that unicode newlines are not valid dir-spec NLs
  * email relay and bridge operators with non-UTF-8 in their contact
    info




People Present (lines said)
---------------------------
* teor (64)
* nickm (54)
* isis (17)
* Samdney (3)
* MeetBot (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot