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/db-wg@ripe.net/

[db-wg] ad-hoc RIPE db-wg meeting at IETF93

Previous message (by thread): [db-wg] ad-hoc RIPE db-wg meeting at IETF93
Next message (by thread): [db-wg] NCC still enforcing descr: content

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

snash snash at arbor.net
Mon Jul 27 12:45:30 CEST 2015

Thanks to Job for reporting this discussion, so that it has reached the 
mailing list.

 > * Route object authorisation
 > - rv@ objects to allowing anybody to create a route-object with his
 > own origin asn.

Does this relate to our mailing list discussion about registering new 
OriginAS?
Can we please have some information about the nature of the objection?

Perhaps the reporting is abbreviated, but the proposal so far is NOT "to 
allowing anybody to create a route-object".
The registered "owner" of the address space is the only party entitled 
to add an authorised OriginAS.

If the objection stands, I think it is the first, so we really need to 
understand it better.

Steve Nash

Previous message (by thread): [db-wg] ad-hoc RIPE db-wg meeting at IETF93
Next message (by thread): [db-wg] NCC still enforcing descr: content

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

[ db-wg Archives ]