Re: Problems with RIPE210

[Daniel Karrenberg <]

At 12:54 PM 6/28/00, Randy Bush wrote:
> > specpref:     193.0.14.0/24
> > type:         DNS ROOT
> > descr:        K Root Server
> > admin-c:      DK58
> >
> > ...
> >
> > DNS ROOT
> > DNS TLD
> > WHOIS TLD
> > WHOIS ADDRESS
> > OTHER
>
> LONGEST ALLOC PREFIX, under rir control, would address the discussions of
> automatic generation of prefix length filters.
I had thoght about that. In the RIPE database context this is more properly
addressed by an atttribute of the corresponding inetnum object, e.g something
like:

inetnum:     217.0.0.0 - 217.255.255.255
netname:     EU-ZZ-217
descr:       RIPE NCC
descr:       European Regional Registry
country:     EU
admin-c:     NN32-RIPE
tech-c:      CREW-RIPE
tech-c:      OPS4-RIPE
status:      ALLOCATED UNSPECIFIED
mnt-by:      RIPE-NCC-HM-MNT
mnt-lower:   RIPE-NCC-HM-MNT
min-alloc:   /20                                  <============
changed:     hostmaster@localhost 20000602
changed:     hostmaster@localhost 20000615
source:      RIPE




> apologies, but the semantics of the two WHOIS entries are not obvious to me
> from the syntax.
Prefixes in which there are whois servers serving information about address
allocations by RIRs (ADDRESS) or TLD name delegations (DNS). Rationale:
When diagnosing network problems either of these are often needed, so they
should remain reachable.



> and i am willing to _help_ with a document.
Thanks. You'll get at least to proofread it if and when it is written.

Daniel