howto/Getting-started.md
... ...
@@ -116,7 +116,30 @@ mnt-by: EXAMPLE-MNT
116 116
117 117
### Register a network prefix
118 118
119
-To register an IPv4 network prefix, simply create an `inetnum` object.
119
+#### IPv6
120
+
121
+To register an [IPv6 prefix](/FAQ#frequently-asked-questions_what-about-ipv6-in-dn42), you can create an `inet6num` object. A single /48 allocation in [ULA space](https://www.sixxs.net/tools/grh/ula/) will likely provide more than enough room for all devices you will ever connect. Some people use “vanity” prefixes like fd42:_xyz_::/48 instead of the fully standard-conformant pseudorandom ones.
122
+
123
+[Unique Local IPv6 Generator](http://unique-local-ipv6.com/)
124
+
125
+example: data/inet6num/fd42:4992:6a6d::_48
126
+```
127
+inet6num: fd42:4992:6a6d:0000:0000:0000:0000:0000 - fd42:4992:6a6d:ffff:ffff:ffff:ffff:ffff
128
+cidr: fd42:4992:6a6d::/48
129
+netname: EVE-NETWORK
130
+descr: Network of eve
131
+country: DE
132
+admin-c: MIC92-DN42
133
+tech-c: MIC92-DN42
134
+mnt-by: MIC92-MNT
135
+nserver: ns1.evenet.dn42
136
+nserver: ns2.evenet.dn42
137
+status: ASSIGNED
138
+```
139
+
140
+#### IPv4 (Legacy)
141
+
142
+If you also want to register an IPv4 network prefix, simply create an `inetnum` object.
120 143
121 144
You may choose your network prefix in one of the currently open netblocks. You can get a list of unassigned subnets on the following sites, please mind the allocation guideline below.
122 145
... ...
@@ -141,25 +164,6 @@ To register for example 172.20.150.0/27, you need to fill in 172.20.150.0-172.20
141 164
142 165
**Note:** Reverse DNS works with _any_ prefix length, as long as your [recursive nameserver](/services/DNS) supports [RFC 2317](https://www.ietf.org/rfc/rfc2317.txt). Don't go for a /24 _just to have RDNS_.
143 166
144
-If you want to register an [IPv6 prefix](/FAQ#frequently-asked-questions_what-about-ipv6-in-dn42), you can create an `inet6num` object. A single /48 allocation in [ULA space](https://www.sixxs.net/tools/grh/ula/) will likely provide more than enough room for all devices you will ever connect. Some people use “vanity” prefixes like fd42:_xyz_::/48 instead of the fully standard-conformant pseudorandom ones.
145
-
146
-[Unique Local IPv6 Generator](http://unique-local-ipv6.com/)
147
-
148
-example: data/inet6num/fd42:4992:6a6d::_48
149
-```
150
-inet6num: fd42:4992:6a6d:0000:0000:0000:0000:0000 - fd42:4992:6a6d:ffff:ffff:ffff:ffff:ffff
151
-cidr: fd42:4992:6a6d::/48
152
-netname: EVE-NETWORK
153
-descr: Network of eve
154
-country: DE
155
-admin-c: MIC92-DN42
156
-tech-c: MIC92-DN42
157
-mnt-by: MIC92-MNT
158
-nserver: ns1.evenet.dn42
159
-nserver: ns2.evenet.dn42
160
-status: ASSIGNED
161
-```
162
-
163 167
example: data/inetnum/172.23.75.0_24
164 168
```
165 169
inetnum: 172.23.75.0 - 172.23.75.255
... ...
@@ -175,7 +179,7 @@ status: ASSIGNED
175 179
176 180
#### Create route objects
177 181
178
-If you plan to announce your prefixes in dn42, which you probably want in most cases, you will also need to create a `route` object for ipv4 prefixes and a `route6` object for ipv6 prefixes. This information is used for ROA checks (route origin authorization). If you skip this step, your network will probably get filtered by some peers. Many people enforce ROA checks to prevent (accidental) hijacking of other people's prefixes.
182
+If you plan to announce your prefixes in dn42, which you probably want in most cases, you will also need to create a `route6` object for ipv6 prefixes and a `route` object for ipv4 prefixes. This information is used for Route Origin Authorization (ROA) checks. If you skip this step, your network will probably get filtered by most major peers. Checking ROA will prevent (accidental) hijacking of other people's prefixes.
179 183
180 184
example: data/route6/fd42:4992:6a6d::_48
181 185
```