howto/Address-Space.md
... ...
@@ -1,4 +1,4 @@
1
-DN42 uses network addresses in the [rfc1918](https://tools.ietf.org/html/rfc1918) and [ULA](https://tools.ietf.org/html/rfc4193) ranges. These are described in detail in the sections below.
1
+DN42 uses network addresses in the [rfc1918](https://tools.ietf.org/html/rfc1918) and [ULA](https://tools.ietf.org/html/rfc4193) ranges. These are described in detail within the sections below.
2 2
3 3
The [DN42 registry](https://git.dn42.us/dn42/registry) is the authoritative source of information on address space assignment. Within the registry, the DN42 address space is divided in to blocks based on _policies_ that define how the addresses may be used. Policies are defined in `inetnum` and `inet6num` objects and can be:
4 4
... ...
@@ -7,6 +7,12 @@ The [DN42 registry](https://git.dn42.us/dn42/registry) is the authoritative sour
7 7
- **reserved** - these ranges are reserved for future use
8 8
- **ask** - these ranges are for specific uses, please ask on the mailing list before requesting assignments
9 9
10
+A simple way to see all the active policies in the registry is to search the registry content for policy attributes:
11
+
12
+```sh
13
+grep -r ^policy data/inet{,6}num/
14
+```
15
+
10 16
The [filter.txt](https://git.dn42.us/dn42/registry/src/master/data/filter.txt) and [filter6.txt](https://git.dn42.us/dn42/registry/src/master/data/filter6.txt) files within the registry detail the network wide constraints on what address ranges are in use together with the global limits on what can be announced.
11 17
12 18
`inetnum` and `inet6num` objects within the registry are used to describe the allocation of address space to users. `route` and `route6` objects in the registry are used to validate routing announcements through [ROA](https://wiki.dn42/howto/Bird#route-origin-authorization).
... ...
@@ -17,7 +23,7 @@ Globally routable prefixes are not supported in DN42; they are denied via the re
17 23
18 24
# IPv6 Address Space
19 25
20
-DN42 uses the fd00::/8 ULA range for IPv6 addresses; the whole fd00::/8 block has an open policy and users are free to request any prefix in this range, that is not already allocated.
26
+DN42 uses the fd00::/8 ULA range for IPv6 addresses. Apart from a block of addresses reserved for anycast (fd42:d42:d42::/48), the whole fd00::/8 block has an open policy and users are free to request any prefix in this range, that is not already allocated.
21 27
22 28
**The DN42 registry is not authoritative for the fd00::/8 range**
23 29
... ...
@@ -25,7 +31,7 @@ DN42 is interconnected with other networks, like icvpn, which also use the same
25 31
26 32
# IPv4 Address Space
27 33
28
-DN42 uses the 172.20.0.0/14 range for IPv4 addresses. As with the public internet, IPv4 space is limited and users are encouraged to conserve space where possible.
34
+DN42 uses the 172.20.0.0/14 range for IPv4 addresses. As with the public internet, IPv4 space is more limited and users are encouraged to conserve space where possible. Any requests for assignments larger than /24 must provide justification.
29 35
30 36
Unlike the IPv6 address space, the DN42 IPv4 space is not fully open for assignment to users; some ranges are intended for specific uses and other ranges are reserved. See the policy section, below. Users should always check the policy in the registry before requesting a prefix to be assigned.
31 37
... ...
@@ -35,7 +41,7 @@ There are other IPv4 ranges in use within DN42 related to the affiliate networks
35 41
36 42
The diagram below shows the allocation policies for the DN42 address space.
37 43
38
-... image ...
44
+![Policy Map Image](images/PolicyMap.png)
39 45
40 46
Specific policy restrictions:
41 47
... ...
@@ -46,5 +52,6 @@ Specific policy restrictions:
46 52
| 172.20.64.0/18 | Reserved for allocations larger than /23, up to /21 |
47 53
| 172.22.0.0/18 | Reserved for allocations of /24 or larger, up to /21 |
48 54
| 172.23.16.0/21 | Closed to new allocations |
55
+| 172.21.0.0/18<br/>172.21.128.0/17<br/>172.22.192.0/18 | Reserved for future use |
49 56
50 57