[tor-bugs] #29206 [Circumvention/Snowflake]: New design for client -- server protocol for Snowflake

[Tor Bug Tracker & Wiki]

#29206: New design for client -- server protocol for Snowflake
-------------------------------------------------+-------------------------
 Reporter:  cohosh                               |          Owner:  cohosh
     Type:  task                                 |         Status:
                                                 |  needs_revision
 Priority:  Medium                               |      Milestone:
Component:  Circumvention/Snowflake              |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  ex-sponsor-19, anti-censorship-      |  Actual Points:
  roadmap                                        |
Parent ID:                                       |         Points:  6
 Reviewer:  dcf                                  |        Sponsor:
                                                 |  Sponsor28-must
-------------------------------------------------+-------------------------

Comment (by dcf):

 I'm thinking one other field that will be required is some kind of session
 ID, to enable the server to associate connections that come in via
 different proxies. meek has something like this, to link up separate HTTP
 requests:
  * https://gitweb.torproject.org/pluggable-transports/meek.git/tree/meek-
 server/meek-server.go?h=0.33#n147
  * [[doc/AChildsGardenOfPluggableTransports#meektransportlayer]]
 QUIC uses a Connection ID that is just a random string generated by the
 initiator.
  * https://quicwg.org/base-drafts/draft-ietf-quic-
 invariants.html#rfc.section.4.3
  * https://tools.ietf.org/html/draft-ietf-quic-transport-20#section-5.2

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29206#comment:20>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online