Changeset 11129

Show
Ignore:
Timestamp:
08/12/2008 09:23:42 PM (4 months ago)
Author:
dave
Message:

Make it obvious from the first mention that wildcards are not a solution
rather than waiting until after describing wildcards only to shoot them down.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • dotorg/trunk/html/beps/bep_0022.rst

    r11122 r11129  
    1919With this extension, BitTorrent clients are able to discover a tracker 
    2020nearby on the network, and via this tracker discover nearby caches or 
    21 peers.  A cache is simply a fast peer in the middle of the network. It 
     21peers.  A cache may simply be a fast peer in the middle of the network. It 
    2222might also have substantial disk space. The client communicates with a 
    2323cache using the normal BitTorrent protocol. 
     
    4444BEP. 
    4545 
     46Extensions to the BitTorrent wireline protocol to delegate seeding 
     47or improve cache performance are beyond the scope of this BEP.  
    4648 
    4749The Discovery Mechanism 
     
    98100The domain name returned from the reverse DNS lookup is specific to 
    99101the querying host.  In the naive implementation in DNS, there would be 
    100 one SRV resource record for every querying host.  The most obvious 
    101 solution is to use a wildcard of the form:: 
     102one SRV resource record for every querying host.  A natural but 
     103incorrect solution is to use a wildcard of the form:: 
    102104 
    103105  *.pacbell.net 
    104106 
    105 However, if wildcards are implemented according to the algorithm in 
    106 section 4.3.2 in [#RFC-1034]_ then all subdomains of pacbell.net that 
    107 do not have an exact label match will match the wildcard.  Thus, 
     107If wildcards are implemented according to the algorithm in section 
     1084.3.2 in [#RFC-1034]_ then all subdomains of pacbell.net that do not 
     109have an exact label match will match the wildcard.  Thus, 
    108110 
    109111:: 
     
    123125implemented with BIND 9.4.1. 
    124126 
    125 The natural solution would be to specify domain names of the type 
     127Another natural but incorrect solution is to specify domain names of 
     128the type 
    126129 
    127130:: 
     
    157160:: 
    158161 
    159   _bittorrent-tracker.dsl.pltn13.pacbell.net 
     162  _bittorrent-tracker._tcp.dsl.pltn13.pacbell.net 
    160163 
    161164and then 
     
    163166:: 
    164167 
    165   _bittorrent-tracker.pltn13.pacbell.net 
     168  _bittorrent-tracker._tcp.pltn13.pacbell.net 
    166169 
    167170The search removes one label at a time terminating when one or more