- Test - lists.nanog.org

RADB cleanup - route objects with no origin AS entries
by Brian Renaud 09 Jun '95

09 Jun '95

Many of the entries in the RADB were translated from entries present in the NSFNET PRDB. Some of the PRDB entries contained no information about Origin AS (Home AS), which is required for the RIPE/RADB syntax. When possible, therefore, information about the Origin AS was added to these PRDB entries when they were converted to the RADB system. However, in some cases no information could be found about the AS "owner," and these entries were converted to RADB Route objects without the required 'origin:' attribute. As we discussed at the NANOG conference in May, these objects will be removed from the RADB. This will be done on Wednesday, June 14. A copy of the 2030 route objects which will be removed from the registry has been put into a 600K file at: ftp://ftp.ra.net/routing.arbiter/radb/problems/radb.noorigin A compressed copy is available at: ftp://ftp.ra.net/routing.arbiter/radb/problems/radb.noorigin.gz If you have any questions regarding this, please send them to DB-admin(a)ra.net -Brian

1 0

subscribe
by Abir Hnidi 09 Jun '95

09 Jun '95

subscribe ahnidi(a)ascend.com

1 0

subscribe
by zhouws＠ns.bta.net.cn 09 Jun '95

09 Jun '95

subscribe zhouws(a)ns.bta.net.cn

1 0

AS690 use of multiple routing registries
by Steve Heimlich 06 Jun '95

06 Jun '95

Folks, This note outlines changes to the ANS AS690 use of various registries which comprise the Internet Routing Registry (IRR). [RIPE gang, please forward to your mailing lists as appropriate]. Currently, the IRR consists of the following four well-known registries: the RADB, the CA*Net registry, the MCI registry, and the RIPE registry. AS690, to date, has relied exclusively on the RADB for generation of its configurations. As a result, those organizations which would naturally register in the MCI, CA*Net, or RIPE registries have been making redundant registrations in the RADB to ensure connectivity with ANS. This redundant registration has been inconvenient for many, and leads to multiple copies of route objects with inconsistent attributes. As of next week, ANS will begin to use route objects from the CA*Net, MCI, and RIPE routing registries. In order to do this, we will first create an ANS registry (containing customers of ANS) with "source: ANS" as its distinguishing attribute. Beginning with next Wednesday's AS690 config run (changed from Tuesday due to the U.S. Memorial Day holiday), we will prefer routes with AS690 advisories from these registries in the following order: ANS, CA*Net, MCI, and the RADB. Once we verify that this has succeeded, we will include the RIPE registry ahead of the RADB on next Friday's config run (i.e., ANS, CA*Net, MCI, RIPE, RADB). This method for config generation will eliminate the need for multiple registrations of singly-homed routes. Toward the end of June, we expect to have software running which will eliminate the use of AS690 advisories. This software generates an initial policy first by using registered advisories (a one-time operation). Currently, this results in a 16,000 line aut-num object for AS690. As this is somewhat unreasonable, we will be reducing the number of per-network exceptions in favor of one policy per home AS. As we approach the deployment of this capability, we will be working with peer providers on arranging mutually acceptable policies with AS690. Steve

2 2

nanog notes for May 1995 meeting status
by sob＠academ.com 04 Jun '95

04 Jun '95

All the notes I took are now on line and available. I have not plugged in the speakers slides yet. That is next. Let me know if you find I have omitted something important in my notes that was not caputured on the slides. Let me know if I have something wrong. Thanks -- Stan | Academ Consulting Services |internet: sob(a)academ.com Olan | For more info on academ, see this |uucp: bcm!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.

1 0

more on nanog notes
by sob＠academ.com 04 Jun '95

04 Jun '95

The notes on Bill's talk that he sent to the list are now html-ized on the notes page at http://www.academ.com/nanog/may1995/index.html -- Stan | Academ Consulting Services |internet: sob(a)academ.com Olan | For more info on academ, see this |uucp: bcm!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.

1 0

NANOG notes
by sob＠academ.com 02 Jun '95

02 Jun '95

The agenda page with all the mailto's is up at the URL: http://www.academ.com/nanog/may1995 More to come!

1 0

Re: AS690 use of multiple routing registries
by Vadim Antonov 27 May '95

27 May '95

How about just doing like all other ISPs do? I.e. do policy at as-path level w/o the benefit of RADB. You don't need any new software to do that, and can do that right tomorrow. As it is now the ANS's policy to use RADB data to filter incoming routing updates generates about 60% of our trouble tickets, which is particularly aggravated by the fact that in most cases the resolution is completely outside of our control (like in case of AS 1800). IMO RADB already created more troubles than it will ever help to fix. I see no particluar reason for Sprint to spend any resources on keeping ANS's exterior routing sane. So do not expect "advisory: AS690" from us. Of course, (as ICM _has_ AUP) we can always start demanding NACRs from ANS. Just to make people who make decisions there to wake up. --vadim To: nanog(a)merit.edu Subject: AS690 use of multiple routing registries Date: Fri, 26 May 1995 16:44:47 -0400 From: Steve Heimlich <heimlich(a)ans.net> Status: R Folks, This note outlines changes to the ANS AS690 use of various registries which comprise the Internet Routing Registry (IRR). [RIPE gang, please forward to your mailing lists as appropriate]. Currently, the IRR consists of the following four well-known registries: the RADB, the CA*Net registry, the MCI registry, and the RIPE registry. AS690, to date, has relied exclusively on the RADB for generation of its configurations. As a result, those organizations which would naturally register in the MCI, CA*Net, or RIPE registries have been making redundant registrations in the RADB to ensure connectivity with ANS. This redundant registration has been inconvenient for many, and leads to multiple copies of route objects with inconsistent attributes. As of next week, ANS will begin to use route objects from the CA*Net, MCI, and RIPE routing registries. In order to do this, we will first create an ANS registry (containing customers of ANS) with "source: ANS" as its distinguishing attribute. Beginning with next Wednesday's AS690 config run (changed from Tuesday due to the U.S. Memorial Day holiday), we will prefer routes with AS690 advisories from these registries in the following order: ANS, CA*Net, MCI, and the RADB. Once we verify that this has succeeded, we will include the RIPE registry ahead of the RADB on next Friday's config run (i.e., ANS, CA*Net, MCI, RIPE, RADB). This method for config generation will eliminate the need for multiple registrations of singly-homed routes. Toward the end of June, we expect to have software running which will eliminate the use of AS690 advisories. This software generates an initial policy first by using registered advisories (a one-time operation). Currently, this results in a 16,000 line aut-num object for AS690. As this is somewhat unreasonable, we will be reducing the number of per-network exceptions in favor of one policy per home AS. As we approach the deployment of this capability, we will be working with peer providers on arranging mutually acceptable policies with AS690. Steve

1 0

How to Delete Objects from the RADB
by Brian Renaud 26 May '95

26 May '95

A number of you have had problems when you tried to delete an object from the RADB. Here is a brief tutorial on the subject. If you have additional questions, please send a note to db-admin(a)ra.net. -Brian How to Delete Objects from the RADB Internet Service Providers (ISPs) and network operators will often need to delete Route objects, AS objects, or Maintainer objects from the RADB. You'll need to delete a Route object (and submit a new one), for example, if: --You are changing ISPs and need to change the origin AS (Home AS) for your route --You are no longer using a particular route prefix --You are moving to a larger aggregate and want to delete a more specific prefix If you want to change any of the following attributes, you'll first need to delete the object, and then re-submit the corrected one: Object Field ----- ----- Route route: origin: AS aut-num: Maintainer mntner: Follow these instructions to delete an object from the RADB: 1. Use the whois tool to get a copy of the object exactly as it currently exists in the registry. Put the object in a temporary file. For example: whois -h whois.ra.net 10.1.2.0/24 > temp 2. Edit the 'temp' file you've created. If the file contains more than one object, remove the extra objects so that only the object or objects you want to delete remain. 3. Do not change any lines in the object(s) you want to delete. Simply append a line such as the following to the objects: delete: user(a)your.net <reason for the deletion> To delete more than one object, append a 'delete:' line to each object and separate each object by a blank line. Your 'temp' file might then look like this: route: 10.1.2/24 descr: Example-NET origin: AS0 mnt-by: AS0-MNT changed: pern@Example-NET 950525 source: RADB delete: user(a)your.net prefix no longer used route: 10.1.3/24 descr: Example-NET origin: AS0 comm-list: COMM_NSFNET advisory: AS690 1:701(136) 2:701(134) 3:1800 mnt-by: AS0-MNT changed: pern@Example-NET 950525 source: RADB delete: user(a)your.net prefix no longer used 4. Submit the object to auto-dbm(a)ra.net. For example: mail auto-dbm(a)ra.net < temp If you have further questions about deleting RADB objects, send e-mail to db-admin(a)ra.net.

2 1

Re: How to Delete Objects from the RADB
by Selina Priestley 25 May '95

25 May '95

This is very nice. Thanks! I think it's important to note specifically that the changed: attribute cannot be altered either in order for a delete to be accepted, since this is counter-intuitive for some folks (uh, me ;-). Selina > > A number of you have had problems when you tried to delete an object > from the RADB. Here is a brief tutorial on the subject. If you > have additional questions, please send a note to db-admin(a)ra.net. > > -Brian > > > How to Delete Objects from the RADB > > Internet Service Providers (ISPs) and network operators will often need > to delete Route objects, AS objects, or Maintainer objects from the > RADB. You'll need to delete a Route object (and submit a new one), for > example, if: > > --You are changing ISPs and need to change the origin AS (Home AS) for > your route > --You are no longer using a particular route prefix > --You are moving to a larger aggregate and want to delete a more > specific prefix > > If you want to change any of the following attributes, you'll first need > to delete the object, and then re-submit the corrected one: > > Object Field > ----- ----- > Route route: > origin: > AS aut-num: > Maintainer mntner: > > Follow these instructions to delete an object from the RADB: > > 1. Use the whois tool to get a copy of the object exactly as it currently > exists in the registry. Put the object in a temporary file. For > example: > > whois -h whois.ra.net 10.1.2.0/24 > temp > > 2. Edit the 'temp' file you've created. If the file contains more than > one object, remove the extra objects so that only the object or > objects you want to delete remain. > > 3. Do not change any lines in the object(s) you want to delete. Simply > append a line such as the following to the objects: > > delete: user(a)your.net <reason for the deletion> > > To delete more than one object, append a 'delete:' line to each object > and separate each object by a blank line. Your 'temp' file might then > look like this: > > route: 10.1.2/24 > descr: Example-NET > origin: AS0 > mnt-by: AS0-MNT > changed: pern@Example-NET 950525 > source: RADB > delete: user(a)your.net prefix no longer used > > route: 10.1.3/24 > descr: Example-NET > origin: AS0 > comm-list: COMM_NSFNET > advisory: AS690 1:701(136) 2:701(134) 3:1800 > mnt-by: AS0-MNT > changed: pern@Example-NET 950525 > source: RADB > delete: user(a)your.net prefix no longer used > > 4. Submit the object to auto-dbm(a)ra.net. For example: > > mail auto-dbm(a)ra.net < temp > > If you have further questions about deleting RADB objects, send e-mail > to db-admin(a)ra.net. >

1 0