|
Size: 2196
Comment:
|
Size: 2585
Comment: point node map link to the node map
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| Line 5: | Line 6: |
|
* Must be listed on the [http://maps.personaltelco.net/ node map]. -- 20060222 is this really a requirement anymore? Should it instead be the NetworkAddressAllocations listing? |
* Must be listed on the [http://map.personaltelco.net/ node map]. * 20060222 is this really a requirement anymore? Should it instead be the NetworkAddressAllocations listing? * 2006.05.27: That change sounds reasonable to me. (- KeeganQuinn) |
| Line 8: | Line 10: |
| * -- ''added 20030611'' |
* ''added 20030611'' |
| Line 13: | Line 16: |
|
* 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. -- 20060222 Proposed change "or www.personaltelco.net/identifier where the identifier is the node name, number or other description." |
* 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://map.personaltelco.net/ node map]). ESSID '''MUST''' be all lower case. * 20060222 Proposed change "or www.personaltelco.net/identifier where the identifier is the node name, number or other description." * 2006.05.27: Who proposes this change? (- KeeganQuinn) * 2006.05.27: I think that we should generally not encourage people to use any ESSID other than ''www.personaltelco.net'' unless they have a '''very good reason''' to do so. I guess that would be a '''SHOULD''' directive. (- KeeganQuinn) |
| Line 19: | Line 24: |
| Line 25: | Line 31: |
| Line 26: | Line 33: |
| Line 30: | Line 38: |
|
Are we/did we adopt the [http://www.freenetworks.org/peering.html Freenetworks Peering Agreement]? Yes, summer of 2004 after the Freenetworks summit. |
Are we/did we adopt the [http://www.freenetworks.org/peering.html FreeNetworks Peering Agreement]? Yes, summer of 2004 after the FreeNetworks summit. |
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://map.personaltelco.net/ node map].
20060222 is this really a requirement anymore? Should it instead be the NetworkAddressAllocations listing?
2006.05.27: That change sounds reasonable to me. (- KeeganQuinn)
- 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://map.personaltelco.net/ node map]). ESSID MUST be all lower case.
- 20060222 Proposed change "or www.personaltelco.net/identifier where the identifier is the node name, number or other description."
2006.05.27: Who proposes this change? (- KeeganQuinn)
2006.05.27: I think that we should generally not encourage people to use any ESSID other than www.personaltelco.net unless they have a very good reason to do so. I guess that would be a SHOULD directive. (- KeeganQuinn)
- 20060222 Proposed change "or www.personaltelco.net/identifier where the identifier is the node name, number or other description."
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 [http://www.freenetworks.org/ FreeNetworks Peer Agreement].
MUST, SHOULD, etc. directives as defined in RFC: http://www.faqs.org/rfcs/rfc2119.html -RossOlson
Are we/did we adopt the [http://www.freenetworks.org/peering.html FreeNetworks Peering Agreement]? Yes, summer of 2004 after the FreeNetworks summit.