Changeset 11028

Show
Ignore:
Timestamp:
02/27/2008 02:48:10 PM (5 months ago)
Author:
dave
Message:

add reference in index to peer id conventions bep.

Location:
dotorg/trunk/html/beps
Files:
2 modified

Legend:

Unmodified
Added
Removed

  • dotorg/trunk/html/beps/bep_0000.rst

    r11025 r11028  
    4444|18|       :raw-html:`<A HREF="bep_0018.html">Search Engine Specification</A>` 
    4545|19|       :raw-html:`<A HREF="bep_0019.html">HTTP/FTP Seeding (GetRight-style) </A>` 
     46|20|       :raw-html:`<A HREF="bep_0020.html">Peer ID Conventions</A>` 
    4647|1000|     :raw-html:`<A HREF="bep_1000.html">Pending Standards Track Documents</A>` 
    4748======     =================== 

  • dotorg/trunk/html/beps/bep_0020.rst

    r11027 r11028  
    1616followed by version number represented by ascii digits with major, 
    1717minor and tiny versions separated by dashes.  Examples include 
    18 `M4-3-6--' or 'M4-20-8-' for versions 4.3.6 and 4.20.8.  The remaining 
     18``M4-3-6--`` or ``M4-20-8-`` for versions 4.3.6 and 4.20.8.  The remaining 
    1919bytes in the peer id are random.  The following list was originally 
    20 derived from [#theory]. 
     20derived from [#theory]_. 
    2121 
    2222A number of clients begin the peer id with a dash followed by two 
    … …  
    2525bytes are random.  An example is ``-AZ2060-``. 
    2626 
    27 Known clients that uses this encoding style are:: 
     27Known clients that use this encoding style are 
     28 
     29:: 
    2830 
    2931     'AG' - Ares 
    … …  
    8789     'ZT' - ZipTorrent  
    8890 
    89 Clients which have been seen in the wild and need to be identified: 
     91The following clients have been seen in the wild and need to be identified:: 
    9092 
    9193     'BD' (example: -BD0300-) 
    … …  
    105107 
    106108As with other peer id formats, the remanining bytes are random.  There 
    107 are significant deviations from this explained here [#shad0w]. 
     109are significant deviations from this explained here [#shad0w]_. 
    108110 
    109 Known clients that uses this encoding style are: 
     111Known clients that uses this encoding style are:: 
    110112 
    111     * 'A' - ABC 
    112     * 'O' - Osprey Permaseed 
    113     * 'Q' - BTQueue 
    114     * 'R' - Tribler 
    115     * 'S' - Shadow's client 
    116     * 'T' - BitTornado 
    117     * 'U' - UPnP NAT Bit Torrent  
     113    'A' - ABC 
     114    'O' - Osprey Permaseed 
     115    'Q' - BTQueue 
     116    'R' - Tribler 
     117    'S' - Shadow's client 
     118    'T' - BitTornado 
     119    'U' - UPnP NAT Bit Torrent  
    118120 
    119121BitComet produces peer ids that consists of four ASCII characters 
    … …  
    158160BitSpirit has several modes for its peer ID. In one mode it reads the 
    159161ID of its peer and reconnects using the first eight bytes as a basis 
    160 for its own ID. Its real ID appears to use ``\0\3BS`` (C notation) as 
    161 the first four bytes for version 3.x and ``\0\2BS`` for version 2.x. In 
     162for its own ID. Its real ID appears to use ``\\0\\3BS`` (C notation) as 
     163the first four bytes for version 3.x and ``\\0\\2BS`` for version 2.x. In 
    162164all modes the ID may end in ``UDP0``. 
    163165