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]/
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 ]
Marten Terpstra
Marten.Terpstra at ripe.net
Tue Jul 27 13:32:34 CEST 1993
Dave Morton <Dave.Morton at ecrc.de> writes * Marten, * No big help I know - this looks messy and a real nasty can of * worms. Mabye the db needs a whole new type of object for these * damm blocks, other than that I don't see any real way out ! ? * Dave Maybe you are right, but right now I would not have any idea how to do so. If have even been thinking of putting all the guarded fields in some other object, which has just the network number and the guarded fields, and no other information. by querying the database one would get the normal output and an extra object with the network number and all its guarded values. In this extra object, no blocks would be allowed ... -Marten PS CCed to routing and db-wg, because this may be a solution.
- 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 ]