← Revision 12 as of 2003-06-11 09:43:04
Size: 1804
Comment: Clean up regarding MUST/SHOULD, etc.
|
← Revision 13 as of 2005-01-20 17:37:21 →
Size: 1769
Comment: repointed Pico Peer link to a valid page.
|
Deletions are marked like this. | Additions are marked like this. |
Line 21: | Line 21: |
* The Node '''MUST''' provide free peering and transit along the terms of the PicoPeer [http://www.picopeer.net/wiki/index.php/PicoPeeringAgreement agreement]. | * The Node '''MUST''' provide free peering and transit along the terms of the PicoPeer [http://www.picopeer.net/ agreement]. |
Here is the list of criteria which a node needs to meet in order to be an official PersonalTelco node. See NodeTypes for a list of all the different types of nodes:
All Nodes
Must be listed on the [http://maps.personaltelco.net/ node map].
- Must be on most of the time.
-- added 20030611
Gateway Node
The Node MUST provide an AccessPoint (ie. run in InfrastructureMode) and MUST NOT restrict access via ["WEP"], ["802.1x"] or any other mechanism.
The AccessPoint MUST broadcast its ["ESSID"] and have it set to www.personaltelco.net or www.personaltelco.net/nodeXXX (where XXX is the number from the [http://maps.personaltelco.net/ node map]). ESSID MUST be all lower case.
The Network MUST provide open FootNote(The exact definition of "open" is left to the owners imagination, however if there is any debate the final determination lies with the BoardOfDirectors.) and zero cost access to the internet and/or the "wireless cloud".
The AccessPoint The Node MUST serve IP addresses to clients via DHCP or IPv6 autoconfiguration.
The AccessPoint MUST be accessible from a public space (ie. can't require trespass or breaking and entering to get a usable signal).
The Node SHOULD run a CaptivePortal with the NodeSplashPages and display the AcceptableUseAgreement.
Repeater Node
The Node MUST connect at least two other repeater or gateway nodes together.
The Node MUST provide free peering and transit along the terms of the PicoPeer [http://www.picopeer.net/ agreement].
MUST, SHOULD, etc. directives as defined in RFC: http://www.faqs.org/rfcs/rfc2119.html -RossOlson