[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:     
----------------------+-----------------------------------------------------
Changes (by karsten):

 * cc: asn, ln5 (added)


Comment:

 The current [https://metrics.torproject.org/formats.html#bridgepool
 assignments.log format] specifies three distributor rings where a bridge
 can only be contained in exactly one ring.  If the general assumption that
 a bridge is only distributed via email ''or'' https ''or'' neither of them
 (unallocated), we should be able to extend this format.

 The current format already allows assigning bridges to several subrings:

 {{{
 0103bb5b00ad3102b2dbafe9ce709a0a7c1060e4 https ring=2 port=443 flag=stable
 }}}

 We could add three new subrings for bridges that are blocked in certain
 countries (listing non-blocked might leave us with a quite long list) and
 are reachable via IPv4/v6 or via certain transports:

 {{{
 0103bb5b00ad3102b2dbafe9ce709a0a7c1060e4 https ring=2 port=443 flag=stable
 blocked=cn,ir ip=4,6 transport=or,obfs2
 }}}

 Note that I only made a guess how the ip and transport subrings could look
 like.  asn and ln5, please comment on the format there.

 In theory, any tool that parses assignment.log files should ignore the
 unknown subrings.  If not, we should fix the tools.

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