9c19401cb33313a7518ded15ee2941ec99f01f77
Frequently-Asked-Questions.md
... | ... | @@ -27,4 +27,9 @@ Another issue with the private ASN range 64512-65534: other projects are also us |
27 | 27 | |
28 | 28 | Fortunately, [RFC6996](http://tools.ietf.org/html/rfc6996) defines a new private ASN range: 4200000000-4294967294. Given the size of this range, there is little chance of running into a conflict. |
29 | 29 | |
30 | -dn42 is now using the **4242420000-4242429999** range for new allocations. |
|
30 | +dn42 is now using the **4242420000-4242429999** range for new allocations. This range is further subdivided: |
|
31 | +* **4242420000-4242423999** for end-users allocations |
|
32 | +* **4242424000-4242426999** reserved for future use |
|
33 | +* **4242427000-4242429999** for sub-allocations |
|
34 | + |
|
35 | +If you are running a project similar to dn42, please use another range of ASN. The "sub-allocations" range is meant for dn42 users willing to have administrative control over a small, consecutive range of ASN (e.g. to use them directly or to distribute them). |
|
... | ... | \ No newline at end of file |