BEP: | 0 |
---|---|
Title: | Index of BitTorrent Enhancement Proposals |
Version: | cc019ba660805f441593d565cd930a4d1f4ae471 |
Last-Modified: | Fri Jul 20 09:34:18 2018 -0700 |
Author: | David Harrison <dave@bittorrent.com> |
Status: | Active |
Type: | Process |
Created: | 10-Jan-2008 |
Post-History: | Oct 13, 2012: updated link to document repository |
The BitTorrent Community Forum coordinates the development of the BitTorrent protocol suite and its reference implementation. It is the wish of Bram Cohen that the BitTorrent mainline python implementation remain open source and that the protocol development process be modelled after the Python Enhancement Proposal (PEP) process [1].
This document indexes all BitTorrent Enhancement Proposals (BEPs). When a new proposal is submitted, one of the BitTorrent.org editors assigns a BEP number and updates this index appropriately. Each document has a number that never changes and the history of the document is maintained in git [2].
These BEPs describe mechanisms that have been deployed in one or more BitTorrent implementations and have proven useful. They may require minor revisions. They await the blessing of the BDFL before they can be considered Final.
The following BEPs are under consideration for standardization.
The editor(s) deem that the following BEPs are not progressing toward standardization, but they have not yet been withdrawn.
Num | Title |
---|---|
8 | Tracker Peer Obfuscation |
18 | Search Engine Specification |
22 | BitTorrent Local Tracker Discovery Protocol |
26 | Zeroconf Peer Advertising and Discovery |
28 | Tracker exchange |
At this time, no BEPs have been withdrawn.
At this time, no BEPs have been rejected.
[1] | http://www.python.org/dev/peps/ |
[2] | https://github.com/bittorrent/bittorrent.org |