Changeset 10491

Timestamp:

01/31/08 02:51:01 (2 years ago)

Author:

dave

Message:

Use bep_0000.html as the developer home page.

We can change this later.

Some rstification of beps.

Location:

dotorg/trunk/html

Files:

• beps/bep_0000.rst (modified) (2 diffs)
• beps/bep_0007.rst (modified) (3 diffs)
• developer.html (deleted)
• donate.html (modified) (1 diff)
• index.html (modified) (2 diffs)

dotorg/trunk/html/beps/bep_0000.rst

@@ -1 @@
-:BEP: 0
-:Title: Index of BitTorrent Enhancement Proposals 
-:Version: 1
-:Last-Modified: 11-Jan-2008
-:Author:  David Harrison
-:Status:  Active
-:Type:    Process
-:Created: 10-Jan-2008
-:Post-History:
+BEP: 0
+Title: Index of BitTorrent Enhancement Proposals 
+Version: 1
+Last-Modified: 11-Jan-2008
+Author:  David Harrison
+Status:  Active
+Type:    Process
+Created: 10-Jan-2008
+Post-History:
 
 The BitTorrent Community Forum coordinates the development of the
@@ -52 +52 @@
 .. _8: bep_0008.html
 .. _9: bep_0009.html
-
+.. _10: bep_0010.html
+.. _11: bep_0011.html

dotorg/trunk/html/beps/bep_0007.rst

@@ -219 +219 @@
 secret.
 
+- any peer that reports a sha_ih is assumed to implement protocol encryption.
+- tracker OPTIONALLY includes a ``flags`` key that contains one byte per
+  peer in the reported peer list.  The first bit of each byte specifies
+  whether the peer support protocol encryption. (How do we protect
+  the flags field from modification?)
+- if no flags field is present then all peers should be assumed to support protocol encryption
+- if a flags field is present then those peers that support protocol
+  a 
+
 rationale
 ---------
@@ -232 +241 @@
 connections.
 
-This hardware was presumably deployed to get around BitTorrent
-protocol encryption, because BitTorrent protocol encryption increases
-the difficulty of identifying BitTorrent traffic based on the bytes
-transferred in a peer-to-peer connection.
+This hardware was presumably deployed to get around `BitTorrent
+Protocol Encryption`_.  Peers implementing BitTorrent Protocol
+Encryption obfuscate peer-to-peer connections by employing RC4
+encryption on every byte from the first byte transferred. BitTorrent
+Protocol Encryption thus increases the difficulty for a device
+observing passing packets to identify BitTorrent peer-to-peer
+connections.
 
 By using the SHA-1 of the infohash, the tracker is able to identify
@@ -327 +339 @@
 .. __: mailto:greg@bittorrent.com
 .. __: mailto:tony@ciani.phy.uic.edu 
-
+.. _`RFC 2119`: http://tools.ietf.org/html/rfc2119
+.. _`BitTorrent Protocol Encryption`: http://www.bittorrent.org/beps/bep_0013.html
+

dotorg/trunk/html/donate.html

@@ -17 +17 @@
   <li><a href="index.html">Home</a></li>
   <li><a href="introduction.html">For Users</a></li>
-  <li><a href="developer.html">For Developers</a></li>
+  <li><a href="beps/bep-0000.html">For Developers</a></li>
   <li><a href="donate.html">Donate!</a></li>
 </ul>

dotorg/trunk/html/index.html

@@ -17 +17 @@
 <li><span>Home</span></li>
 <li><a href="./introduction.html">For Users</a></li>
-<li><a href="./developer.html">For Developers</a></li>
+<li><a href="./beps/bep-0000.html">For Developers</a></li>
 <!-- <li><a href="./blog.html">Blog</a></li> -->
 <li><a href="./donate.html">Donate!</a></li>
@@ -35 +35 @@
 <h2>For Developers</h2>
 <ul>
-<li><a href="./ipv6_tracker_extension.html">IPv6 Tracker Extension Proposal</a></li>
-<li><a href="./fast_extensions.html">Fast Protocol Extensions</a></li>
-<li><a href="./protocol.html">BitTorrent Protocol Specification</a></li>
-<li><a href="./developer.html">For Developers (including more proposals) </a></li>
+<li><a href="./beps/bep_0000.html"> Proposed Standards Process  </a></li>
+<li><a href="./beps/bep_0006.html"> IPv6 Tracker Extension Proposal</a></li>
+<li><a href="./protocol.html"> BitTorrent Protocol Specification</a></li>
 </ul>
 </div>