Changeset 10807

Show
Ignore:
Timestamp:
02/14/08 23:34:56 (2 years ago)
Author:
dave
Message:

some word smithing

Files:
1 modified

Legend:

Unmodified
Added
Removed

  • dotorg/trunk_fixed/html/beps/bep_0008.rst

    r10762 r10807  
    2727 
    2828When using this extension, instead of passing the ``info_hash`` parameter 
    29 to the tracker, an ``sha_ih`` is passed. 
     29to the tracker, a ``sha_ih`` is passed. 
    3030 
    3131The value of ``sha_ih`` MUST be the info-hash of the torrent, with a second 
    … …  
    4646================= 
    4747 
    48 If the tracker supports this extension, the response should be exactly the 
    49 same as if the ``info_hash`` was passed, except that any field that contains 
    50 peer information (such as ``peers``, ``peers6`` or any other field defined 
    51 by another extension) MUST be obfuscated as described in the next section. 
     48If the tracker supports this extension, the response should be exactly 
     49the same as if the ``info_hash`` had been passed, except that any 
     50field that contains peer information (such as ``peers``, ``peers6`` or 
     51any other field defined by another extension) MUST be obfuscated as 
     52described in the next section. 
    5253 
    5354There are additional parameters the tracker may OPTIONALLY return. 
    … …  
    5960We distinguish between the *tracker peer list* and the *returned peer 
    6061list*.  The *tracker peer list* contains the ip-port pairs of all 
    61 known peers in a given torrent, i.e., those peers that have reported to 
    62 the tracker that they are downloading or seeding a given file with a 
    63 given infohash.  The tracker may store this peer list however it 
    64 wishes.  The *returned peer list* contains a packed array of ip-port 
    65 pairs conforming to the BitTorrent protocol specification.  If the 
    66 swarm is sufficiently large then the returned ip-port pairs constitute 
    67 a subset of the ip-port pairs in the *tracker peer list*. 
     62known peers in a given torrent, i.e., those peers that have reported 
     63to the tracker that they are transferring the file with a given 
     64infohash.  The tracker may store this peer list however it wishes. 
     65The *returned peer list* contains a packed array of ip-port pairs 
     66conforming to the BitTorrent protocol specification.  If the swarm is 
     67sufficiently large then the returned ip-port pairs constitute a subset 
     68of the ip-port pairs in the *tracker peer list*. 
    6869 
    6970The returned peer list is encrypted using RC4-drop768 encryption using