|
Size: 1158
Comment:
|
Size: 1795
Comment: Recommendation for RFC style Must/Shoulds etc.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
|
* Must be on most of the time. * -- ''added by LonnieWormley 20030611'' |
|
| Line 10: | Line 12: |
|
* 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]). * The network must provide free and open access (blocking port 25?) to the internet or the "wireless cloud". * Must display the AcceptableUseAgreement, ideally it should run a CaptivePortal with the NodeSplashPages. * Must run a DHCP server. |
* 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]). 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 board of advisors.)]] and zero cost access to the internet and/or the "wireless cloud". * Ideally it should run a CaptivePortal with the NodeSplashPages and display the AcceptableUseAgreement. * Must serve IP addresses to clients via DHCP or IPv6 autoconfiguration. * Must be accessible from a public space (ie. can't require trespass or breaking and entering to get a usable signal). |
| Line 15: | Line 18: |
| '''Repeater Node'''' | '''Repeater Node''' |
| Line 18: | Line 21: |
| * Must provide free peering and transit. Possibly along the terms of the PicoPeer [http://www.picopeer.net/wiki/index.php/PicoPeeringAgreement agreement]. |
* Must provide free peering and transit along the terms of the PicoPeer [http://www.picopeer.net/wiki/index.php/PicoPeeringAgreement agreement]. ---- Document Recommendation: Consider attaching MUST, SHOULD, etc. directives as they are used in RFCs: http://www.faqs.org/rfcs/rfc2119.html -RossOlson (I would but I'm not sure what the other members have in mind.) |
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 by LonnieWormley 20030611
Gateway Node
Must provide an AccessPoint (ie. run in InfrastructureMode) and may not restrict access via ["WEP"], ["802.1x"] or any other mechanism.
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]). 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 board of advisors.) and zero cost access to the internet and/or the "wireless cloud".
Ideally it should run a CaptivePortal with the NodeSplashPages and display the AcceptableUseAgreement.
- Must serve IP addresses to clients via DHCP or IPv6 autoconfiguration.
- Must be accessible from a public space (ie. can't require trespass or breaking and entering to get a usable signal).
Repeater Node
- Must connect at least two other repeater or gateway nodes together.
Must provide free peering and transit along the terms of the PicoPeer [http://www.picopeer.net/wiki/index.php/PicoPeeringAgreement agreement].
Document Recommendation: Consider attaching MUST, SHOULD, etc. directives as they are used in RFCs: http://www.faqs.org/rfcs/rfc2119.html -RossOlson (I would but I'm not sure what the other members have in mind.)