[tor-bugs] #5935 [BridgeDB]: Determine how bridge-pool assignments should work with BridgeDB's IPv6 and pluggable-transport extensions

[Tor Bug Tracker & Wiki]

#5935: Determine how bridge-pool assignments should work with BridgeDB's IPv6 and
pluggable-transport extensions
----------------------+-----------------------------------------------------
 Reporter:  aagbsn    |          Owner:     
     Type:  defect    |         Status:  new
 Priority:  normal    |      Milestone:     
Component:  BridgeDB  |        Version:     
 Keywords:            |         Parent:     
   Points:            |   Actualpoints:     
----------------------+-----------------------------------------------------
 Extensions #4097, #5027 sort bridges into sub-rings determined by a set of
 filters. #4568 (pluggable transports) will function similarly.

 e.g. A bridge request that specifies ipv6 address, or bridges not blocked
 in a given country, or bridges with a specified pluggable transport type,
 or even some combination of the above.

 The changes in #4097 (and #5027) cause BridgeDB to write all the
 assignments including subrings -- which are named by the set of applied
 filters -- into the assignments.log. This seems to confuse the bridge-
 assignments script(s) that Karsten runs.

 A bridge may be present in several different sub-rings, because it matches
 several filters (i.e. a bridge may be in a ring of ipv6 bridges as well as
 another ring of bridges not blocked in iran, and another ring of bridges
 with ipv6 addresses and not blocked in iran)

 We need to figure out what the bridge assignments.log should look like,
 and whether/how the scripts that parse this file should be updated.

 Karsten, what are your thoughts/questions?

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