Determine how bridge-pool assignments should work with BridgeDB's IPv6 and pluggable-transport extensions
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 legacy/trac#4097 (moved) (and legacy/trac#5027 (moved)) 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?