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/
The addition of guarded fields
- Previous message (by thread): The addition of guarded fields
- Next message (by thread): The addition of guarded fields
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gilles Farrache
farrache at ccpnxt5.in2p3.fr
Tue Jul 27 13:50:16 CEST 1993
Marten, I think that the RIPE NCC have to split blocks. RIPE NCC is a neutral organisation that can do it without problems. If we do not agree on that, that means a very long procedure to update the guarded fields, and I believe that no service provider will want to rely on the efficiency of a NIC for its routing policy. So that mean that nobody will use those fields for routing, so the information may be completly out of date. But I agree with Blasco on one point, the maintainer of the block must be inform that the block has been splitted Gilles
- Previous message (by thread): The addition of guarded fields
- Next message (by thread): The addition of guarded fields
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]