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/dns-wg@ripe.net/
A proposal about hostcount and DNS
- Previous message (by thread): A proposal about hostcount and DNS
- Next message (by thread): A proposal about hostcount and DNS
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piet Beertema
Piet.Beertema at cwi.nl
Fri Jun 13 11:35:22 CEST 1997
What we might want to think about is *if* it is useful to come
up with some recommendations (RIPE-Document? BCP?) as to the
*access* to that ionformation from the sites in the network
which perform the tree walk. E.g. things like refusing zone
transfers, address filters, and the like.
I don't think it's up to RIPE or any other outsider to
make any recommendations for a company's or institute's
policy regarding access to its nameservers (other than
the normal access needed to make the service work for
purpose it's meant for).
Personally, I don't see a need to do some fancy new stuff, which
would simply replace one educated guess with a different one, and
at the same time would be open to "bending", like freely configurable
meta entries.
Fully agreed.
I don't think that it is reasonable for the RIPE-NCC or the RIPE
Community as a whole, to try to perform - or even support - any
particular interpretation of data!
Right!
When and if there is a need for such activities, I'd propose to
leave that to commercial entities.
In that case it is extremely likely that the number of
sites that close their nameservers for zone transfers
will grow immensely.
Piet
- Previous message (by thread): A proposal about hostcount and DNS
- Next message (by thread): A proposal about hostcount and DNS
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]