HIPI » policy
This document is a work in progress. Most of it has been pulled straight from brismesh's standard policy. I need the executive to make modifications as needed.
MUCH WORK MUST BE DONE TO THIS PAGE! IT HASNT BEEN TOUCHED IN WELL OVER A YEAR!
Summary
- All nodes are public and accessible
- Traffic is transported "best effort"
- No carriage liability for routers
- No money is to be made through the network
Definitions
- The "rules" are the set of rules contained in this document.
- The "mesh" is the collection of nodes (interior or leaf nodes) linked together using free media (such as the 2.4GHz radio band) and open technologies (such as IEEE802.11b).
- An "internal network" is a network outside of the mesh (such as a private LAN, or the internet)
- A "leaf node" is a node with exactly one link to the mesh. It may be attached directly to one or more internal networks.
- An "interior node" is a node with two or more links to other nodes. It too may be attached to one or more internal networks.
- An "operator" is a person or group in a position to make changes, operational or technical modifications to a particular node or nodes, or to the published information about that node or nodes.
- An "owner" is a person or group in which ultimate responsibility of a node's operation lies.
- "Link establishment" is the short procedure that nodes undertake to establish a long-term connection between each other.
Rules
These were pulled straight from the sample one (David Leonard, May 2001).
- 1. Public access
Owners of a node agree that:
- An operator must make public sufficiently accurate configuration information for other nodes to commence link establishment with that node.
- Corrections to a published configuration must be made in a timely fashion by the operator.
- Configuration information of a node must include a bona fide contact method for the node's operator that does not make use of the mesh (e.g. telephone number)
- Nodes must immediately accept link establishments from unknown nodes.
- Nodes need not accept or maintain links to nodes that do not follow these rules.
- Awareness and discussion about mesh usage between the mesh users must be facilitated by node owners. The owners should encourage such communication.
Explanatory notes:
- Node operators may remain anonymous, but must be contactable.
- All information about a node's technical configuration ought to be made public, e.g. location, technology used, beam area, channels, hardware and software used, antenna information, traffic shaping
rules in use, etc.
- Users sending traffic into the mesh ought to be considerate of the other users of the mesh.
- 2. Best effort transport
Owners of a node agree that:
- An interior node must correctly route all packets within the mesh in a best effort fashion.
- Nodes must implement IPv6 and use the OSPF routing protocol.
- Nodes should not encrypt inter-node packets.
- Nodes should operate continuously.
- Nodes do not need to provide best effort routing for nodes that do not follow these rules.
Explanatory notes:
- Packet filtering between nodes must not occur.
- Individual nodes may "shape" traffic based on packet priority, quality or "type-of-service" fields; but not by other content semantics such as source or origin port, IP or MAC address.
- This rule only affects inter-node traffic; e.g. it does not prohibit packet filtering or shaping between a node and an it's associated internal network.
- In the case of abuse, auditing is preferred over suppression.
- Nodes need not route packets to their attached internal network(s).
- Encryption should be provided by applications, and not the network.
- 3. Carrier liability
- Owners of nodes (with or without attached internal networks) accept that owners of interior nodes have no liability for damage or loss caused by the traffic that they route between nodes within the mesh.
Explanatory notes:
- This rules is designed to permit interior node owners to route traffic within the mesh in good faith without fear of legal consequences of the foreign traffic that they pass.
- Liability relating to data routed between internal networks ought to be negotiated by the owners of the respectively attached nodes.
Times: DB-Connect 4ms; Initiailise 5ms; Menu 7ms; Total 24ms