Address-Space.md
... ...
@@ -0,0 +1,57 @@
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
+
3
+The [DN42 registry](https://git.dn42.dev/dn42/registry) is the authoritative source of information on address space assignment. Within the registry, the DN42 address space is divided into blocks based on _policies_ that define how the addresses may be used. Policies are defined in `inetnum` and `inet6num` objects and can be:
4
+
5
+ - **open** - users may request prefixes in this range, subject to any constraints that are described in the `remark` attributes
6
+ - **closed** - these ranges cannot be assigned
7
+ - **reserved** - these ranges are reserved for future use
8
+ - **ask** - these ranges are for specific uses, please ask on the mailing list before requesting assignments
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
+
16
+The [filter.txt](https://git.dn42.dev/dn42/registry/src/master/data/filter.txt) and [filter6.txt](https://git.dn42.dev/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.
17
+
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](/howto/Bird2#route-origin-authorization).
19
+
20
+In addition to the native DN42 address ranges, the registry also contains allocations for the address space used by affiliate networks. These are updated by a regular [sync script](https://git.dn42.dev/dn42/registry-sync).
21
+
22
+Globally routable prefixes are not supported in DN42; they are denied via the registry filter{6,}.txt files and many networks will filter both announcements and traffic for prefixes that are outside of the allowable ranges.
23
+
24
+# IPv6 Address Space
25
+
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.
27
+
28
+**The DN42 registry is not authoritative for the fd00::/8 range**
29
+
30
+DN42 is interconnected with other networks, like icvpn, which also use the same ULA range and many users will also use this range for their own networks. A registration in the dn42 registry cannot prevent IPv6 conflicts, so a fully random prefix (see [RFC4193](https://tools.ietf.org/html/rfc4193)) is strongly recommended. If an address conflict is found, then needing to renumber your network is no fun.
31
+
32
+# IPv4 Address Space
33
+
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. A typical assignment in DN42 is a /27 and any requests for assignments larger than /24 must provide justification.
35
+
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.
37
+
38
+There are other IPv4 ranges in use within DN42 related to the affiliate networks, see the [filter.txt](https://git.dn42.dev/dn42/registry/src/master/data/filter.txt) file in the registry.
39
+
40
+## IPv4 Policies
41
+
42
+The diagram below shows the allocation policies for the DN42 address space.
43
+
44
+![Policy Map Image](/images/PolicyMap.png)
45
+
46
+Specific policy restrictions:
47
+
48
+| Prefix | Usage |
49
+|--------|-------|
50
+| 172.20.0.0/24<br/>172.21.0.0/24<br/>172.22.0.0/24<br/>172.23.0.0/24 | Reserved for anycast addresses |
51
+| 172.20.240.0/20<br/>172.22.240.0/20 | Reserved for transfer networks |
52
+| 172.20.64.0/18 | Reserved for allocations larger than /23, up to /21 |
53
+| 172.22.0.0/18 | Reserved for allocations of /24 or larger, up to /21 |
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 |
56
+
57
+
Links.md
... ...
@@ -1,29 +1,29 @@
1 1
This is a small list of links. Some of them are informative, some educational, some funny and some entertaining. You know a link you want to share? Then edit the page and add it!
2 2
3
+## Other Networks
3 4
[List of other Overlay Networks](/Other)
4 5
5
-Books:
6
+## Books
6 7
- [Computer Networks -Tanenbaum](https://github.com/gsahinpi/acm361/raw/master/Computer%20Networks%20-%20A%20Tanenbaum%20-%205th%20edition.pdf)
7 8
8
-Tutorials:
9
+## Tutorials
9 10
- [Multiple servers on dn42: iBGP and IGPs](https://jlu5.com/blog/dn42-multiple-servers-ibgp-igps)
10 11
- [Network Examples](https://github.com/knorrie/network-examples)
11 12
- [BGP Filter Guides](https://bgpfilterguide.nlnog.net/)
12 13
- [BGP4All workshops](https://www.bgp4all.com/pfs/workshops/start)
13 14
14
-Examples and Blogs:
15
+## Examples and Blogs
15 16
- [lantian's blog](https://lantian.pub/en/page/dn42/)
16 17
- [jlu5's dn42 config](https://github.com/jlu5/ansible-dn42)
17 18
18
-Videos:
19
-- English
19
+## Videos
20
+### English
20 21
- [BGP Tutorial Massimiliano Stucchi, Tom Smyth ](https://www.youtube.com/watch?v=oKyhrbG3sjI)
21 22
- [local-pref considered evil ](https://media.ccc.de/v/denog13-12617-local-pref-considered-evil)
22
-- German
23
+### German
23 24
- [Network / IP Basics OSI-Modell und Protokolle im Überblick](https://media.ccc.de/v/routingdays16-18-network_ip_basics)
24 25
- [iBGP Fundamentals BGP im internen Netzwerk.](https://media.ccc.de/v/routingdays16-14-ibgp_fundamentals)
25 26
- [(e)BGP Fundamentals Route selection, AS path, prefix, metrics and state machine](https://media.ccc.de/v/routingdays16-10-e_bgp_fundamentals)
26
-
27 27
28
-Funny:
28
+## Funny
29 29
- [ipv6bingo](https://ipv6bingo.com/)
_Sidebar.md
... ...
@@ -1,7 +1,7 @@
1 1
* [Home](/Home)
2 2
* [Getting Started](/howto/Getting-Started)
3 3
* [Registry Authentication](/howto/Registry-Authentication)
4
- * [Address Space](/howto/Address-Space)
4
+ * [Address Space](/Address-Space)
5 5
* [BGP communities](/howto/BGP-communities)
6 6
* [Interconnections](/Interconnections)
7 7
* [Policies](/Policies)
howto/Address-Space.md
... ...
@@ -1,57 +0,0 @@
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
-
3
-The [DN42 registry](https://git.dn42.dev/dn42/registry) is the authoritative source of information on address space assignment. Within the registry, the DN42 address space is divided into blocks based on _policies_ that define how the addresses may be used. Policies are defined in `inetnum` and `inet6num` objects and can be:
4
-
5
- - **open** - users may request prefixes in this range, subject to any constraints that are described in the `remark` attributes
6
- - **closed** - these ranges cannot be assigned
7
- - **reserved** - these ranges are reserved for future use
8
- - **ask** - these ranges are for specific uses, please ask on the mailing list before requesting assignments
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
-
16
-The [filter.txt](https://git.dn42.dev/dn42/registry/src/master/data/filter.txt) and [filter6.txt](https://git.dn42.dev/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.
17
-
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](/howto/Bird2#route-origin-authorization).
19
-
20
-In addition to the native DN42 address ranges, the registry also contains allocations for the address space used by affiliate networks. These are updated by a regular [sync script](https://git.dn42.dev/dn42/registry-sync).
21
-
22
-Globally routable prefixes are not supported in DN42; they are denied via the registry filter{6,}.txt files and many networks will filter both announcements and traffic for prefixes that are outside of the allowable ranges.
23
-
24
-# IPv6 Address Space
25
-
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.
27
-
28
-**The DN42 registry is not authoritative for the fd00::/8 range**
29
-
30
-DN42 is interconnected with other networks, like icvpn, which also use the same ULA range and many users will also use this range for their own networks. A registration in the dn42 registry cannot prevent IPv6 conflicts, so a fully random prefix (see [RFC4193](https://tools.ietf.org/html/rfc4193)) is strongly recommended. If an address conflict is found, then needing to renumber your network is no fun.
31
-
32
-# IPv4 Address Space
33
-
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. A typical assignment in DN42 is a /27 and any requests for assignments larger than /24 must provide justification.
35
-
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.
37
-
38
-There are other IPv4 ranges in use within DN42 related to the affiliate networks, see the [filter.txt](https://git.dn42.dev/dn42/registry/src/master/data/filter.txt) file in the registry.
39
-
40
-## IPv4 Policies
41
-
42
-The diagram below shows the allocation policies for the DN42 address space.
43
-
44
-![Policy Map Image](/howto/images/PolicyMap.png)
45
-
46
-Specific policy restrictions:
47
-
48
-| Prefix | Usage |
49
-|--------|-------|
50
-| 172.20.0.0/24<br/>172.21.0.0/24<br/>172.22.0.0/24<br/>172.23.0.0/24 | Reserved for anycast addresses |
51
-| 172.20.240.0/20<br/>172.22.240.0/20 | Reserved for transfer networks |
52
-| 172.20.64.0/18 | Reserved for allocations larger than /23, up to /21 |
53
-| 172.22.0.0/18 | Reserved for allocations of /24 or larger, up to /21 |
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 |
56
-
57
-
howto/images/PolicyMap.png
... ...
Binary files a/howto/images/PolicyMap.png and /dev/null differ
images/PolicyMap.png
... ...
Binary files /dev/null and b/images/PolicyMap.png differ
services/Whois.md
... ...
@@ -1,5 +1,5 @@
1 1
# Whois registry
2
-**aka** _The registry_ contains:
2
+The registry contains:
3 3
4 4
* AS numbers assignations
5 5
* Subnet assignations
... ...
@@ -13,11 +13,7 @@ dn42 uses some names and numbers, which are declared in the registry. Whenever
13 13
14 14
## Address space
15 15
16
-dn42 uses **172.20.0.0/14** for IPv4.
17
-
18
-For IPv6, we use ULA (that is, **fd00::/8**).
19
-
20
-See also the howto page covering the [DN42 address space](/howto/Address-Space).
16
+See the page covering the [dn42 address space](/Address-Space).
21 17
22 18
## AS numbers
23 19
... ...
@@ -32,9 +28,9 @@ Note that currently, most AS are using one of the legacy ASN range (and will pro
32 28
33 29
## DNS zones
34 30
35
-dn42 uses the `dn42.` TLD, which is not present in the root DNS zone of the ICANN-net. For details, see [DNS](/services/dns/Overview).
31
+dn42 uses the `dn42.` TLD, which is not present in the root DNS zone of the ICANN-net. For details, see [DNS](/services/dns/Overview).
36 32
37
-Note that other TLDs should also be usable from dn42, most notably from Freifunk and ChaosVPN. A tentative list is available at [External DNS](/services/dns/External-DNS).
33
+Note that other TLDs should also be usable from dn42, most notably from Freifunk and ChaosVPN. A list is available at [External DNS](/services/dns/External-DNS).
38 34
39 35
## Authentication
40 36