|
8
|
1 AnoNet Resource Database
|
|
|
2
|
|
|
3 as => list of ASNs with owners
|
|
|
4 dom => list of domains with owners and nameservers
|
|
|
5 ip => list of direct IP assignments with owners and nameservers
|
|
|
6 usr => list of users with useful information
|
|
|
7
|
|
|
8 The domains are organized by TLD, making it easy to split TLDs off onto
|
|
|
9 separate TLD servers, if that ever proves to be useful.
|
|
|
10
|
|
|
11 The IP claims are classful, the rationale being that reverse DNS is
|
|
|
12 classful anyway, and so trying to split delegations and rDNS on different
|
|
|
13 boundries is just an easy way of adding nnnecessary complexity. If you
|
|
|
14 want less than a class C, you should just take a full class C and share
|
|
|
15 it with your friends. If you want a /23, just take 2 adjacent /24s.
|
|
|
16 (Remember, your rDNS for the two blocks will have to be separate anyway.)
|
|
|
17
|
|
|
18 If anybody wants IPv6, just add an ip6 directory (again, with
|
|
|
19 subdirectories split according to rDNS rules).
|
|
|
20
|
|
|
21 The user directory is intended to facilitate contact between users.
|
|
|
22 Its original purpose was to maintain git URLs directly in the database
|
|
|
23 (makes automated git peering dead simple), but it's useful for far more.
|
|
|
24 Feel free to add arbitrary fields for users, but it may be wise to use an
|
|
|
25 "x-" prefix if you're not sure about the best name for some field.
|
