update dn42 communities

.drone.yml

@@ -19,7 +19,7 @@ steps:
     RSYNC_CHOWN: 81001:81001
     RSYNC_CHMOD: D2755,F644
   commands:
-   - /rsync.sh de-fra1,ca-bhs2 public/ apps/nginx/burble.dn42/
+   - /rsync.sh de-fra1,ca-bhs2,us-lax1 public/ apps/nginx/burble.dn42/
   when:
     branch: master
     event: push

content/network/communities.md

@@ -7,14 +7,19 @@ This page describes the use of BGP communities within the network.
 
 ## DN42 Communities
 
-[DN42 Communities](https://dn42.net/howto/Bird-communities) are applied both internally and externally, and are used to influence the [Routing Policy](/home/routing-policy).
+The [DN42 Route Origin Community](https://dn42.net/howto/Bird-communities) is applied both internally and externally, and is used to influence the [Routing Policy](/network/routing-policy).
+
+|Community  |Description|
+|:---|:---|
+|( 64511 : 40 < x < 54 ) &nbsp; | Route Origin |
+
+The other DN42 communities are not used in burble.dn42:
 
 |Community &nbsp;|Description|
 |:---|:---|
 |( 64511 : 0 < x < 21 )   &nbsp; | Max latency |
 |( 64511 : 20 < x < 30 ) &nbsp; | Min bandwidth |
 |( 64511 : 30 < x < 35 ) &nbsp; | Min encryption |
-|( 64511 : 40 < x < 54 ) &nbsp; | Route Origin |
 
 ## Well Known BGP Communities
 

content/network/peering.md

@@ -178,7 +178,8 @@ following features are supported:
 * Extended Next Hop - [RFC 5549](https://www.rfc-editor.org/info/rfc5549)
 * Extended Messages - [RFC 8654](https://www.rfc-editor.org/info/rfc8654)
 * DN42 Route Origin Authorisation (ROA - see below section on Route Filtering) 
-* DN42 [BGP communities](https://dn42.dev/howto/Bird-communities)
+* DN42 [Route Origin Community](https://dn42.dev/howto/Bird-communities)
+  * Note that DN42 latency, bandwidth and encryption communities are **not** supported.
 * burble.dn42 custom [large communities](/network/communities)
 * burble.dn42 [Routing Policy](/network/routing-policy)
 

content/network/routing-policy.md

@@ -9,12 +9,10 @@ With a global network and multiple peers, the burble.dn42 network typically has
 
 1. Direct routes for prefixes belonging to a peer should be given the highest priority.  
     - So that traffic to peer networks is routed over the burble.dn42 network directly to the peer and not via an external 3rd party
-3. Routes to the anycast prefixes should be prioritised through stable, low latency peers.  
-    - To ensure stability within the network and provide good routes for well known destinations (e.g. DNS and the DN42 wiki)
-5. Where prefixes are tagged with a DN42 region, they should be routed locally or within the burble.dn42 network.     
+2. Where prefixes are tagged with a DN42 region, they should be routed locally or within the burble.dn42 network.     
     - To avoid sending traffic across regions when this could have been avoided.  
     - The AS path length is also increased between regions to pursuade external routers to also prefer local hosts.
-7. Prioritise by shortest path, then lowest latency
+3. Prioritise by shortest path, then lowest latency
 
 ## Policy Implementation
 

content/services/public.md

@@ -69,11 +69,12 @@ In all cases, do not set the ping frequency to be higher than once a second.
 
 ### Speed Test Service
 
-A speed test service is available in France and Canada.<br/>
+A speed test service is available in France, Canada (East Coast) and US (LAX).<br/>
 Note that the service is currently available over IPv6 only at this time. 
 
 - France: [https://speedtest.fr-rbx1.burble.dn42](https://speedtest.fr-rbx1.burble.dn42)
 - Canada: [https://speedtest.ca-bhs2.burble.dn42](https://speedtest.ca-bhs2.burble.dn42)
+- US LAX: [https://speedtest.us-lax1.burble.dn42](https://speedtest.us-lax1.burble.dn42)
 
 {{<hint warning>}}
 If the service ends up loading or disrupting the rest of the network then I may end up