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] irt object useless
- Previous message (by thread): [db-wg] irt object useless
- Next message (by thread): [db-wg] irt object useless
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Fri May 27 22:05:34 CEST 2005
Hi, On Fri, May 27, 2005 at 07:51:31PM +0200, Marco d'Itri wrote: > > As I don't see any more comments on this, have we already reached consensus? > Hiding more-specific objects by default is such a major change that I > do not think it can be deployed after a discussion among just three or > four people. Nobody wants to hide more-specifics. The goal is to show the inetnum: object (as before) and, in addition to that, the most-specific available irt: object. *In the default response*. So if the inetnum: has its own mnt-irt: then show it, but if there is only one for the encompassing /16 (or whatever), then show the "parent" irt: - otherweise irt: is pretty useless. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 71007 (66629) SpaceNet AG Mail: netmaster at Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 D- 80807 Muenchen Fax : +49-89-32356-234
- Previous message (by thread): [db-wg] irt object useless
- Next message (by thread): [db-wg] irt object useless
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]