Show
Ignore:
Timestamp:
05/20/2008 06:39:19 PM (5 months ago)
Author:
dave
Message:

updated html

Files:
1 modified

Legend:

Unmodified
Added
Removed

  • dotorg/trunk/html/beps/bep_0004.html

    r11040 r11092  
    4141<tr class="field"><th class="field-name">Version:</th><td class="field-body">11031</td> 
    4242</tr> 
    43 <tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference external" href="http://svn.bittorrent.org/trac/browser/dotorg/trunk/html/beps/bep_0004.rst">2008-02-28 16:43:58 -0800 (Thu, 28 Feb 2008)</a></td> 
     43<tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference external" href="http://bittorrent.org/trac/browser/dotorg/trunk/html/beps/bep_0004.rst">2008-02-28 16:43:58 -0800 (Thu, 28 Feb 2008)</a></td> 
    4444</tr> 
    4545<tr class="field"><th class="field-name">Author:</th><td class="field-body">David Harrison &lt;dave&#32;&#97;t&#32;bittorrent.com&gt;</td> 
    … …  
    74740x80  Azureus Messaging Protocol 
    7575 
     76reserved[2] 
     770x08  BitTorrent Location-aware Protocol (no known implementations) 
     78 
    7679reserved[5] 
    77800x10  LTEP (Libtorrent Extension Protocol) 
     810x02  Extension Negotiation Protocol 
     820x01  Extension Negotiation Protocol 
    7883 
    7984reserved[7] 
    80850x01  BitTorrent DHT 
     860x02  XBT Peer Exchange 
    81870x04  suggest, haveall, havenone, reject request, and allow fast extensions 
     880x08  NAT Traversal 
    8289</pre> 
     90<p>There are known collisions.</p> 
     91<blockquote> 
     92<p>reserved[0] 
     930xFF  BitComet Extension Protocol</p> 
     94<p>reserved[1] 
     950xFF  BitComet Extension Protocol</p> 
     96<p>reserved[7] 
     970x01  XBT Metadata Exchange (implemented only in XBT)</p> 
     98</blockquote> 
     99<p>It is recommended that further extensions use LTEP [#BEP-]_.  With 
     100LTEP, extension bit collisions become impossible since no new 
     101extension bits are allocated.  With LTEP, message ID collisions also 
     102become impossible because message IDs are allocated on demand at the 
     103beginning of the connection.  Extension <em>name</em> collisions become 
     104possible, but the probability is much less likely.</p> 
    83105</div> 
    84106<div class="section" id="reserved-message-ids">