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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] RIPE WHOIS blocked
- Previous message (by thread): [anti-abuse-wg] RIPE WHOIS blocked
- Next message (by thread): [anti-abuse-wg] RIPE WHOIS blocked
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
Woeber at CC.UniVie.ac.at
Tue Nov 18 21:16:53 CET 2014
Ronald F. Guilmette wrote: > ... For example, what's the difference between three three: > > -rw-r--r-- 1 ftp ftp 28491 Nov 18 00:26 ripe.db.as-block.gz > -rw-r--r-- 1 ftp ftp 1610549 Nov 18 00:26 ripe.db.as-set.gz > -rw-r--r-- 1 ftp ftp 7248902 Nov 18 00:26 ripe.db.aut-num.gz My 1st "wild guess" would be: - aut-num: individual AS numbers - as-block: a contiguous set of AS numbers starting with AS-a through AS-b - as-set: a list/enumeration of AS numbers (for which the same routing policy should be applied). Some of that stuff has been devised in the framework of RPSL (IETF RFCs some 15 years ago), but the implementations these days is no longer fully in line with those doc.s and have never been complete - unfortunately. -W
- Previous message (by thread): [anti-abuse-wg] RIPE WHOIS blocked
- Next message (by thread): [anti-abuse-wg] RIPE WHOIS blocked
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]