P2P Protocol
From P2P Foundation
A proposal by Alex Rollin:
Contents |
P2P Protocol
P2P Protocol is the set of rules that members of a network must follow in order to be a member of that network.
P2P Protocol is built by peers who are members of a network. The protocol is for governing the network itself. Users who are members of the network have the ability to create and vote on the protocol.
Purpose of P2P Protocol
The purpose of protocol is whatever users choose to make it. Some of the paramount purposes are:
- Decide how membership of the network is achieved and maintained
- Protect the network from threats
- Acquire and manage network assets and resources
- Aid individuals or projects in the network
- Define how protocol is managed
Qualities of P2P Protocol
Managed by Peers
Peers are equals in a network. Each one has the ability and access to influence another, and to manage P2P Protocol. Peers are equal in their ability to act within the network on the network. They may not have the same skills, hair color, amount of money in the bank, but each member of the network is allowed to participate in creating, managing, and destroying protocol. Every member is choosing to adopt the protocol of the network, and so they participate in managing it.
Of the Network, For the Network
P2P Protocol takes place in a network, and protocol that comes into being is protocol that is accepted by a very large majority of the users. As such, it is an inappropriate forum for personal justice or ideology. Protocol can be used to interdict in behavior on a case by case basis, but this is not generally recommended, and could be construed as a mis-use of network resources.
P2P Protocol is Written Collaboratively
Managing protocol is a process of discovery. Individuals make recommendations for protocol, and find out whether their preference is shared by the network.
Here's an example of how the collaboration might happen:
- Member A of the "Cat Network" writes a protocol that "All members must have dogs"
- Member B offers a competing protocol that "All members must like dogs"
- Member C offers a competing protocol that "All members must tolerate dogs"
- Each member contacts the other 15 members of the network and asks them their thoughts, and to vote on the protocol
- Member A changes their protocol to match Member B "All members must like dogs"
- Members vote and the protocol B leads with 9 votes, and C has 3
- After 60 days the protocol receives no additional votes and is retired.
- After 2 years is it revived, and position C wins 90% and carries into active protocol. (Position C requires no enforcement)
In this example we have several forms of collaboration:
- Members innovate and share their innovation with others
- Members discuss options with each other
- Members come up with additional proposals
- Members merge their positions
Protocol goes into effect because a large portion of the network agrees that the protocol is important, and because the protocol can be implemented by those who support the protocol.
Codify Good Behavior
Protocol should be written to codify attributes of the network. This is not the same as attributes of members of the network, as they are not the same thing. Members cannot and do not represent the network as a whole. Positive behavior is behavior that affirms the network's viability as a whole, and the behavior is that of the network, not the individuals who comprise the network.
A network might vote to make it mandatory that all members have cats. This may lead to the network voting to dissolve itself. In each case it is the members of the network that are voting, as well as setting the rules for how the votes are turned into sanctions, if necessary. It may be that it is important for the network that all members have cats, but this would be evaluated on terms that individuals understand. For example, is having cats ensuring that the network is able to access quality housing? If the network is a network of cat lovers, and doesn't care about housing, then this is obvious. The use of P2P Protocol assumes nothing about the purpose of the network save that members are participating voluntarily and can also vote with their feet by joining another network.
Writing protocol that outlines punishments is important, but writing protocol solely for the purpose of outlining negative actions in a network is less useful than writing protocol that outlines positive actions.
On Demand
Protocol can be created and destroyed as needed by a network. Bad or poorly written protocol can be scrapped. Old protocol can be replaced with new, or simply killed. New protocol can be created in response to a need and managed for as long as necessary.
Membership as Participation in Protocol
For organizations that operate as networks it is important to consider that the true definition of membership is simply the agreement by a member to follow the protocol of the network. In some cases this may come with monumental requirements, but it does not need to.
If networks are built with the idea that they interact with each other, it is possible that a string of networks might require ever increasing commitments for memberships.
Members that agree to participate in protocol are also agreeing to participate in the creation and destruction of protocol. Indeed, for a protocol driven network, this is quite possibly the most important task for any member of the network as this is the activity that preserves or changes the very definition of the network by protocol.
Conditions for Protocol
Protocol is written and managed for a purpose. Protocol defines the network, so at the very least, protocol ensures the continued existence of the network. Here are some additional conditions for protocol.
- Protocol must be understandable - or it won't gain traction with members
- Protocol must be attainable - or members won't vote for it
- Protocol must be enforceable - or it won't be implemented
- Protocol must be legal - or it will risk network assets
- Protocol must be transparent - it must be managed publicly so that the network can see how it is working, who it is affecting, and what the effects are
Enforcement of Protocol
Failure to follow the protocol results in a series of punishments that escalate from sanctions to the point of removing the user from the network through shunning.
Examples of P2P Protocol
There are many examples of protocols from the Information Technology world, but these are only partially relevant. In most technology context protocol has to do with the formatting of information. The formatting of the information allows the information to be consumed by a number of other nodes in a network. In our case, were an analogy to be made, it might be that the act of participating in the management of protocol is a bit like the special formatting that information undergoes in order to be part of the network. The nodes in the network are resources or other individuals, and the information is also like an individual. Again, though, protocol in the information world is different, and the analogy is a stretch.
Examples of P2P Protocol in A Cooperative Housing Project
Let's look at a cooperative housing project. Each member is an equal participant in the management of the common business for the project once they are members.
Existing Protocols
- You must apply to move into the housing project and to become a member.
- Once you live in the project you must pay rent
- Once you live in the project you must do 15 hours of service work each month on the project common areas
New Protocols
- Manage common area tasks on a website list
- House project meeting once monthly
- 10 hours of monthly service instead of 15
- Paint the ground floor hallway
Tools for Protocol Management
Depending on how large your organization is, you might be able to manage protocol with pen and paper. If your needs are more extensive you might consider a tool like Votorola.
