New RIPE database software release
Dear Colleagues, we are happy to announce the new release of RIPE database software. It is running now on our production system and is available for download from: ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-2.2.tar.gz. Release notes are in: ftp://ftp.ripe.net/ripe/dbase/software/RELEASE-NOTES-2.2 Most important new features are: - PGP authentication support - referral mechanism for domains - referential integrity checks - new syntax checks - bug fixes For more details please read the release notes. If you have any problems, questions, remarks, bug reports - please send mail to ripe-dbm@ripe.net. User documentation describing new release is being worked on and we hope to make it available soon. We would also like to inform you that we have migrated our database server to new hardware and OS platform - it is now running on Sun Enterprise E450 machine under Solaris 2.6 operating system. We hope you will experience performance improvements. Best regards, Roman Karpiuk RIPE NCC Database Group
Hi, It was recently brought to our attention that RIPE have started to break down some legacy Class B networks and assign individual subnets thereof: inetnum: 130.243.32.0 - 130.243.63.255 netname: SE-DU descr: Dalarna University country: SE admin-c: ANNO1-RIPE tech-c: ANNO1-RIPE status: ASSIGNED PA mnt-by: SUNET-MNT changed: fredrik@sunet.se 19981202 source: RIPE This raises routability problems because many backbone operators filter out BGP announcements of this range with prefix length longer than /16. See for example <http://www.sprintlink.net/filter.htm>. And because, there is no "higher order" inetnum for the 130.243.0.0 - 130.243.255.255 so this makes no one entitled (from RIPE perspective) to advertise the 130.243.0.0/16 to solve the routing issues. And because of the lack of "higher order" inetnum, organisations like Dalarna University come to believe that they have portable address space. Portable, may be, but not necessarily routable. This problem is even further comlicated by the fact that administration of this /16 network does not appear to have been delegated to RIPE: alpha 48: whois -h whois.arin.net 130.243.0.0 Royal Institute of Sweden (NETBLK-NORDU4) S-100 44 Stockholm SWEDEN Netname: NORDU4 Netblock: 130.242.0.0 - 130.243.0.0 Coordinator: Liman, Lars-Johan (LL846-ARIN) LIMAN@SUNET.SE +46 8 790 65 60 (FAX) +46 8 24 11 79 Domain System inverse mapping provided by: SUNIC.SUNET.SE 192.36.148.18 SERVER.NORDU.NET 193.10.252.19 Record last updated on 16-Oct-98. Database last updated on 11-Dec-98 16:11:39 EDT. Please investigate and clarify. __ Pierre Thibaudeau | e-mail: <prt@Teleglobe.CA> TELEGLOBE CANADA | e-page: <prt-p@Teleglobe.CA> 1000, rue de La Gauchetiere ouest | Montreal, QC H3B 4X5 | Tel: +1-514-868-7257 Canada | fax: +1-514-868-8446
Pierre Thibaudeau <prt@Teleglobe.CA> writes: Hi,
It was recently brought to our attention that RIPE have started to break down some legacy Class B networks and assign individual subnets thereof. ...
Pierre, neither RIPE nor the RIPE NCC is doing anythig like that. This is an operational matter of SUNET. There is no reason for discussing this on multiple unrelated mailing lists. I will move this thread to the <routing-wg@ripe.net> list and include the relevant administrators. Those interested in the thread can either subscribe to <routing-wg@ripe.net> or follow its archives at http://www.ripe.net/mail-archives/routing-wg/index.html. If you have any further questions, please do not hesitate to contact us. Kind regards Daniel Karrenberg RIPE NCC Manager
On Mon, 14 Dec 1998 12:27:09 -0500 (EST) Pierre Thibaudeau <prt@Teleglobe.CA> wrote: Pierre, This looks like SUNET's problem and not RIPE's. [check mnt-by]. Regards, Neil.
Hi,
It was recently brought to our attention that RIPE have started to break down some legacy Class B networks and assign individual subnets thereof:
inetnum: 130.243.32.0 - 130.243.63.255 netname: SE-DU descr: Dalarna University country: SE admin-c: ANNO1-RIPE tech-c: ANNO1-RIPE status: ASSIGNED PA mnt-by: SUNET-MNT changed: fredrik@sunet.se 19981202 source: RIPE
This raises routability problems because many backbone operators filter out BGP announcements of this range with prefix length longer than /16. See for example <http://www.sprintlink.net/filter.htm>.
And because, there is no "higher order" inetnum for the 130.243.0.0 - 130.243.255.255 so this makes no one entitled (from RIPE perspective) to advertise the 130.243.0.0/16 to solve the routing issues.
And because of the lack of "higher order" inetnum, organisations like Dalarna University come to believe that they have portable address space. Portable, may be, but not necessarily routable.
This problem is even further comlicated by the fact that administration of this /16 network does not appear to have been delegated to RIPE:
alpha 48: whois -h whois.arin.net 130.243.0.0 Royal Institute of Sweden (NETBLK-NORDU4) S-100 44 Stockholm SWEDEN
Netname: NORDU4 Netblock: 130.242.0.0 - 130.243.0.0
Coordinator: Liman, Lars-Johan (LL846-ARIN) LIMAN@SUNET.SE +46 8 790 65 60 (FAX) +46 8 24 11 79
Domain System inverse mapping provided by:
SUNIC.SUNET.SE 192.36.148.18 SERVER.NORDU.NET 193.10.252.19
Record last updated on 16-Oct-98. Database last updated on 11-Dec-98 16:11:39 EDT.
Please investigate and clarify. __
Pierre Thibaudeau | e-mail: <prt@Teleglobe.CA> TELEGLOBE CANADA | e-page: <prt-p@Teleglobe.CA> 1000, rue de La Gauchetiere ouest | Montreal, QC H3B 4X5 | Tel: +1-514-868-7257 Canada | fax: +1-514-868-8446
-- Neil J. McRae - Alive and Kicking. C O L T I N T E R N E T neil@COLT.NET NetBSD-1.3.2 released! ftp://ftp.uk.netbsd.org/pub/NetBSD Free the daemon in your <A HREF="http://www.NetBSD.ORG/">computer!</A>
It was recently brought to our attention that RIPE have started to break down some legacy Class B networks and assign individual subnets thereof: ... This raises routability problems because many backbone operators filter out BGP announcements of this range with prefix length longer than /16. See for example <http://www.sprintlink.net/filter.htm>.
for the record, verio also filters B on /16. we do so because that is what the registries told us were allocation boundaries. if registries intend to change these policies, it would be kind to warn and discuss. randy
participants (5)
-
Daniel Karrenberg -
Neil J. McRae -
Pierre Thibaudeau -
Randy Bush -
RIPE Database Administration