RE: [db-wg] rpsl to arin format conversion
At 15:50 17/02/2004, Terry Ridder wrote:
On Tue, 17 Feb 2004, Wilfried Woeber wrote:
are there any software utilities available for converting from rpsl to 'arin' format?
Sorry, I don't have an answer, but rather a question:
why don"t you try to do it "the other way 'round", as RPSL is properly described in an RFC?
Wilfried.
arin's db contains the most records.
logically, it makes sense to convert the other rir dbs to arin format.
also converting from arin to rpsl would lose information which exists in arin's db.
Examples please, both syntax and semantics.
those helping with the research have a better understanding of arin format than rpsl.
-- terry l. ridder ><>
Cheers, ___________________________________________________________________ * * Tim Streater Network Engineer * * * Francis House * 112 Hills Road Tel +44 1223 302992 * Cambridge CB2 1PQ Fax +44 1223 303005 D A N T E United Kingdom WWW http://www.dante.net ____________________________________________________________________
On Tue, 17 Feb 2004, Tim Streater wrote:
At 15:50 17/02/2004, Terry Ridder wrote:
On Tue, 17 Feb 2004, Wilfried Woeber wrote:
are there any software utilities available for converting from rpsl to 'arin' format?
Sorry, I don't have an answer, but rather a question:
why don"t you try to do it "the other way 'round", as RPSL is properly described in an RFC?
Wilfried.
arin's db contains the most records.
logically, it makes sense to convert the other rir dbs to arin format.
also converting from arin to rpsl would lose information which exists in arin's db.
Examples please, both syntax and semantics.
i will use my own data for example: arin format: rpsl format: OrgName: Blue Danube Software n/a [1] OrgID: BDS-6 n/a [2] Address: <munged> n/a [1] Address: <munged> n/a [1] City: <munged> n/a [1] StateProv: <munged> n/a [1] PostalCode: <munged> n/a [1] Country: US country: US NetRange: 204.238.34.0 - 204.238.34.255 inetnum: 204.238.34.0 - 204.238.34.255 CIDR: 204.238.34.0/24 n/a [3] NetName: BDS2 netname: BDS2 NetHandle: NET-204-238-34-0-1 n/a [2] Parent: NET-204-0-0-0-0 n/a [2] NetType: Direct Assignment status: NameServer: EDGAR.BLAUEDONAU.COM rev-srv: NameServer: STRAUSS.BLAUEDONAU.COM rev-srv: NameServer: NEPTUNE.NIBCOMP.COM rev-srv: Comment: remarks: RegDate: 1995-03-04 n/a [4] Updated: 2003-09-03 changed: [5] [1] - parts contained in rpsl descr: lines. not easily parsed. [2] - does not exist in rpsl [3] - easily calculated [4] - the first rpsl changed: line could be taken as the arin regdate: [5] - the last rpsl changed: line could be taken as the arin updated: whois -h whois.ripe.net -s ARIN 204.238.34.200 netname: BDS2 descr: Blue Danube Software country: US admin-c: ARIN1-RIPE tech-c: ARIN1-RIPE remarks: ***************************************************** remarks: * This IPv4 network is assigned by the ARIN. * remarks: * Please query WHOIS.ARIN.NET for more information. * remarks: ***************************************************** mnt-by: ARIN-MNT changed: hostmaster@arin.net 19950304 changed: ripe-dbm@ripe.net 20030904 source: ARIN for my research purposes, nethandle and parent are important. orgid, is a nice to have.
those helping with the research have a better understanding of arin format than rpsl.
-- terry l. ridder ><>
participants (2)
-
terry l. ridder -
Tim Streater