This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] RIPE NCC to remove mnt-lower RIPE-NCC-END-MNT from ASSIGNED PI objects
- Previous message (by thread): [db-wg] RIPE NCC to remove mnt-lower RIPE-NCC-END-MNT from ASSIGNED PI objects
- Next message (by thread): [db-wg] RIPE NCC to remove mnt-lower RIPE-NCC-END-MNT from ASSIGNED PI objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Bruijnzeels
tim at ripe.net
Wed Feb 25 17:21:00 CET 2015
Hi Marco, WG, On 25 Feb 2015, at 13:27, Marco d'Itri <md at Linux.IT> wrote: > On Feb 25, Tim Bruijnzeels <tim at ripe.net> wrote: > >> Please let us know if you have any questions or comments. > Good idea. Is the up to date business logic of the database available > somewhere? The business logic is how we typically implement RIPE policy restrictions on the RIPE database. These restrictions are documented in RIPE policy documents and implementation plans. We understand that this means that the documentation can be somewhat implicit and scattered. Providing a central overview of these rules, the restrictions and reasons (references to policy), in the RIPE database documentation itself was already on our radar, albeit not with the highest priority. If you and the WG indicate that they value having this soon though, we are happy to give this more priority. Regards, Tim Bruijnzeels
- Previous message (by thread): [db-wg] RIPE NCC to remove mnt-lower RIPE-NCC-END-MNT from ASSIGNED PI objects
- Next message (by thread): [db-wg] RIPE NCC to remove mnt-lower RIPE-NCC-END-MNT from ASSIGNED PI objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]