This is a list of technical and operational standards that BC Wireless nodes should adhere to.
This document uses terms outlined in RFC2119
Network Naming
Community Network Nodes
Community Network Nodes operated by members of the Society should follow this naming convention:
SSID Template |
Description |
BCWNS-Public-NodeName |
Public/non secured (captive portal) Wireless Access |
BCWNS-NodeName |
Public/secured (WPA/EAP) Wireless Access |
Society Network Nodes
Society Network Nodes operated by BCWNS are named:
SSID Template |
Description |
www.bcwireless.net |
Wireless Access |
Others
We suggest that nodes that are not BC Wireless, but are public in general should use either the WarChalking symbol )(, or state that the node is open (ie: including the word "public").
Network Peering
- The node MUST NOT explicitly prohibit the use of IPSEC, GRE or protocols and ports used by OpenVPN.
Regulatory
The node MUST operate within safe and regulated power restricted as outlined in the Regulatory section.
Access to non-free networks
The node SHOULD use an authentication system such as a CaptivePortal or VirtualPrivateNetwork
- The authentication system MAY authenticate from the BC Wireless Community Access service so as to provide uniform access to all BC Wireless members.
- The authentication system SHOULD enforce an acceptable use policy.
