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]/

New nsf.db in RIPE database format

Previous message (by thread): Operational Contacts
Next message (by thread): New nsf.db in RIPE database format

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Stefan Fassbender +49 2241 14 3180 stf at easi.net
Thu Oct 22 20:42:57 CET 1992

Hi,

what about keeping the infos out of
  nis.nsf.net: nsfnet/announced.networks/country.now
  nis.nsf.net: nsfnet/announced.networks/country3.now
somewhere on ftp.ripe.net.

Those files provide the most useful information about NSFNET
networks (at least for my administrative needs), ie they show
the countries and the NSFNET announcements and they are up-to-date.

What about converting them into the RIPE database format with 
the tags *in: *na: *cy: *ni: *ch: *so: and storing them as:
  ftp.ripe.net: ripe/dbase/nsf-t1.db
  ftp.ripe.net: ripe/dbase/nsf-t3.db

or better to merge them into one database called:
  ftp.ripe.net: ripe/dbase/nsf.db

with such entries:
  *in: 132.165.0.0
  *na: CEA-SIEGE
  *cy: FR
  *n1: 1=590 14=750 15=756 20=1800
  *n3: 1=1800
  *ch: 910503 Merit
  *so: NSF

This (small) database might replace the usually out-of-date nsfnets.db.
(We could provide a gawk-script for the conversion)

Any comments?

-stefan-

Previous message (by thread): Operational Contacts
Next message (by thread): New nsf.db in RIPE database format

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]