Policies.md
... ...
@@ -30,17 +30,17 @@ Another option would be to signal opt-outs via the wiki:
30 30
| `EXAMPLE-MNT` | 172.0.0.1/24 | Yes |
31 31
32 32
33
-## Registry cleanup process
34
-This process is used to remove inactive objects based on MRT data and the git commit history.
35
-The process is to be executed on a regular basis (yearly).
33
+## Registry cleanup
36 34
37 35
A maintainer is classified as "inactive" if the following conditions have been fulfilled:
38 36
1. All of the ASNs the maintainer has been directly or indirectly associated with (in any way and by following all references, whether through mnt-by, admin-c, tech-c, etc. or through an ORG) have not been observed originating any prefix in the global routing table at any point within the last three years. (Determined by analyzing the daily MRT RIB dumps provided by the DN42 Global Route collector.)
39
-2. The maintainer has not edited any of the ASNs they are associated with in the registry within the last three years. (Determined by analyzing the git commit history.)
37
+2. The maintainer has not edited any of the ASN objects they are associated with in the registry within the last three years. (Determined by analyzing the git commit history.)
40 38
41 39
Maintainers that are not affiliated with an ASN (whether directly or indirectly or through other maintainers) are also considered inactive regardless of whether they fulfill the above conditions.
40
+A maintainer may also ask to opt out from a cleanup operation.
42 41
43 42
### Process
43
+The process is to be executed on a regular basis (yearly).
44 44
45 45
Using **registry_wizard (written for v0.4.12)**:
46 46