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] Proposed change 2003.2: removal of cross notifications

Previous message (by thread): [db-wg] Proposed change 2003.1: notification for more-specific
Next message (by thread): [db-wg] Proposed change 2003.3: "reclaim:"-like functionality

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Shane Kerr shane at ripe.net
Tue Mar 4 15:50:02 CET 2003

Colleagues,

This is one of a number of proposed changes to the way the RIPE
Database works.  These are changes that are intended to make the
database work more consistently, as well as provide an increased level
of security and control to users.

Please have a look, and discuss it here.


[2003.2] Removal of cross notifications in the routing registry
---------------------------------------------------------------

Proposal:

Deprecate cross notifications.  This means removing "cross-mnt:" and
"cross-nfy:" attributes from aut-num or route objects with them (150
and 555 of each, respectively).

Motivation:

Currently cross notifications provide a redundant facility now fully
implemented by RPSL authorisation.

Also, current implementation sends notifications to every possible
overlapping route (-L + -M), which is not very consistent with RPSL
hierarchical authorisation scheme.


-- 
Shane Kerr
RIPE NCC

Previous message (by thread): [db-wg] Proposed change 2003.1: notification for more-specific
Next message (by thread): [db-wg] Proposed change 2003.3: "reclaim:"-like functionality

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]