We've been allocated an IPv6 RIR assignment (2001:67c:930::/48) for Wikidough (. There are several steps required to complete the process. Eventual deployment will be on a POP by POP basis, starting with esams.
[] **Assign the global Anycast IPv6 address for Wikidough**
I would suggest assigning a /64 prefix for Wikidough and choosing the /128 from that.
We could use the very first /64, and then the first IP from that.
```
2001:67c:930::/64 - Prefix
2001:67c:930::1/128 - Anycast IP
```
Personally I'd probably skip the first /64, to keep the /48 and /64 visually distinct in the routing table. But it doesn't really make a difference (that's just old neteng thinking, and we're being replaced by robots anyway!)
Perhaps:
```
2001:67c:930:100::/64 - Prefix
2001:67c:930:100::1/128 - Anycast IP
```
[] **2. Enable IPv6 support in Wikidough's anycast configuration**
[] **3. Configure VM to CR BGP Sessions**
We need to configure the VMs running the Wikidough service to announce the newly assigned /128 address, and configure the CR routers to form a BGP adjacency with them.
When that is complete we can test that things are working locally at that POP before proceeding.
[] **4. Configure CR aggregate route**
We need to add the /48 to the list of aggregate prefixes on each CR. This will generate the /48 in BGP if any contributing routes are present, which in turn will be announced upstream.
Transits will likely need manual engagement before they'll update their filters and allow the route.
[] **5. Update AAAA records for Wikidough**