- routing-wg - mailman.ripe.net

Help Please - Reducing Routes
by Daniel Karrenberg 11 Mar '96

11 Mar '96

Dear colleagues, I would like you all to help me a little with the text of an e-mail message I am about to program into a new robot. This robot detects redundant BGP routes and brings them to the attention of the contact persons of the ASes concerned. This is the direct result of the discussion we had at the last RIPE meeting about the need for reducing the number of routes and the consensus that we should mount a community effort to do something about it. I would like you to read the example message below and give me sugestions for improvements. It would also be useful to receive a short note saying "I could understand it, no suggestions", so that I can see how many actually tried to grok it. Note that this is not picking in any way on AS1273. I picked them because this message was the first one I saw that has all the optional elements in it. I also know that the ECRC crew is good humoured in general ;-). I hope to have the robot running sometime next week; but it is no good if people do not understand what they need to do. So please help! Daniel From: Less Routes <less-routes(a)ripe.net> To: "Dave F. Morton" <dave(a)ECRC.DE>, "Todd Ferguson" <todd(a)ECRC.DE>, "Kurt Kayser" <kurt(a)ecrc.de>, "Kurt Kayser" <kurt(a)ecrc.de>, "Waltraud Erber" <wer(a)ecrc.de>, Subject: Routes AS1273 can help eleminate Dear AS1273 contact persons, as you may know the Internet routing system is quite strained at the moment. The major cause of this is the number of routes in the system. This has already caused some service providers to restrict the number of routes they propagate. The RIPE NCC has analysed BGP routing tables and found that a significant number of routes (as many as 22% of the total) are apparently redundant. Your autonomous system is either originating some of those redundant routes or one of your immediate neighbors is doing so. We have found redundant routes by looking separately at each set of routes which we observe coming to us though a unique set of BGP paths. We believe that no routing information will be lost by eliminating redundant routes in in each set independently. We have included all information about the redundant routes your AS is directly involved with and included it in the message below. For each unique set of BGP paths observed in the routing table you will see a number of lines like - Paths: <as-path> [/ <as-path> ...] This is the set of AS paths observed in BGP routing. - Drop: <prefix> covered by <less-specific-prefix> These prefixes can be dropped from global routing because they are covered by a less specific (shorter) prefix observed via the same set of paths. - Aggregate: <prefix> from <more-specific-prefix> & <more-specific-prefix> The more specific prefixes can be aggregated (combined) into a less specific one. This works recursively, i.e. aggregates of aggregates may appear. This serves to show you how the aggregation was derived by us. - Announce: <prefix> The announce lines show you all non-redundant routes for this set of paths including those that could not be improved. This is what should be announced ideally. - Prefixes: <n> <n> is the number of prefixes observed via the set of paths. - Dropable: <n> <n> is the number of prefixes that can be dropped because they are covered by less specific prefixes (see above). - Agg-able: <n> <n> is the number of prefixes that can be dropped because they can be aggregated into less specific prefixes (see above). - Gainable: <n> <n> is the total number of prefixes that can be dropped without loosing information or routing functionality. We have compiled the information in two different sets: routes originated by your AS and routes originated by your AS's immediate neighbor ASes. We only consider neighbor ASes that appear to be 'downstream' from you from our point of view. If your AS originates routes, please consider reducing the announcements as indicated by dropping and/or aggregating routes. If you have multiple connections to (some of) your neighbors and you cannot aggregate or drop the announcements yourself because your immediate neighbor(s) need separate routes to choose the proper connection, please ask your neighbor(s) to do the aggregation for you. If you have a legitimate reason for announcing prefixes that our model considers redundant, we are *very* interested to hear from you, so that we can improve our model. Of course we are also interested in any feedback from you about the usefulness of this information to you and your willingnewss to use it. If the routes are originated by your neighbors, please contact them and bring this to their attention. We will be collecting this information regularly and make it available at ftp://ftp.ripe.net/ripe/less-routes/ in file names of the form AS<num> where <num> is the AS number. We will also regularly publish reports on the progress of this effort. Please act now. reducing the number of prefixes in the Internet routing system is absolutely required to make routing more stable for everyone. This affects you! Thank you The RIPE NCC Routing Team # BGP routes from amsterdam.ripe.net # at Thu Feb 1 07:54:35 1996 UTC # Possible improvementss for routes you originate: Paths: 1755 1273 Incomplete / 1128 1673 1239 1800 1755 1273 Incomplete Drop: 194.24.193/24 covered by 194.24.192/19 Aggregate: 194.24/23 from 194.24/24 & 194.24.1/24 Aggregate: 194.45.208/21 from 194.45.208/22 & 194.45.212/22 Aggregate: 194.115.102/23 from 194.115.102/24 & 194.115.103/24 Aggregate: 194.139.100/23 from 194.139.100/24 & 194.139.101/24 Aggregate: 194.139.102/23 from 194.139.102/24 & 194.139.103/24 Aggregate: 194.139.100/22 from 194.139.100/23 & 194.139.102/23 Announce: 193.22.160/22 Announce: 193.26.103/24 Announce: 193.29.189/24 Announce: 193.30.202/24 Announce: 193.96.229/24 Announce: 193.97.129/24 Announce: 193.97.140/24 Announce: 193.101.21/24 Announce: 193.102.110/24 Announce: 193.141.37/24 Announce: 193.141.94/24 Announce: 194.24/23 Announce: 194.24.4/24 Announce: 194.24.192/19 Announce: 194.31.6/23 Announce: 194.31.193/24 Announce: 194.45.160/22 Announce: 194.45.173/24 Announce: 194.45.186/24 Announce: 194.45.208/21 Announce: 194.55.32/24 Announce: 194.77.146/23 Announce: 194.99.111/24 Announce: 194.115.101/24 Announce: 194.115.102/23 Announce: 194.127.245/24 Announce: 194.139.100/22 Prefixes: 34 Dropable: 1 Agg-able: 6 Gainable: 7 # Possible improvements for routes originated # by your immediate neighbors. Paths: 1755 1273 2861 IGP / 1128 1673 1239 1800 1755 1273 2861 IGP Aggregate: 194.138.16/23 from 194.138.16/24 & 194.138.17/24 Announce: 194.138.16/23 Prefixes: 2 Dropable: 0 Agg-able: 1 Gainable: 1 Paths: 1755 1273 5401 IGP / 1128 1673 1239 1800 1755 1273 5401 IGP Aggregate: 194.77.60/23 from 194.77.60/24 & 194.77.61/24 Aggregate: 194.77.182/23 from 194.77.182/24 & 194.77.183/24 Aggregate: 194.77.196/23 from 194.77.196/24 & 194.77.197/24 Announce: 193.16.1/24 Announce: 193.96.105/24 Announce: 193.96.240/24 Announce: 193.100.124/23 Announce: 193.101.23/24 Announce: 193.101.68/24 Announce: 193.101.120/23 Announce: 193.101.166/24 Announce: 193.102.58/24 Announce: 193.102.128/22 Announce: 193.103.149/24 Announce: 194.15.215/24 Announce: 194.55.171/24 Announce: 194.77.46/23 Announce: 194.77.48/22 Announce: 194.77.52/23 Announce: 194.77.60/23 Announce: 194.77.65/24 Announce: 194.77.88/24 Announce: 194.77.111/24 Announce: 194.77.156/23 Announce: 194.77.160/24 Announce: 194.77.164/23 Announce: 194.77.166/24 Announce: 194.77.168/24 Announce: 194.77.176/24 Announce: 194.77.180/24 Announce: 194.77.182/23 Announce: 194.77.189/24 Announce: 194.77.196/23 Announce: 194.115.31/24 Announce: 194.127.100/24 Prefixes: 35 Dropable: 0 Agg-able: 3 Gainable: 3 Paths: 1755 1273 5401 IGP / 1128 1804 1800 1755 1273 5401 IGP Aggregate: 194.77.66/23 from 194.77.66/24 & 194.77.67/24 Announce: 193.16.3/24 Announce: 193.98.8/22 Announce: 193.98.92/23 Announce: 193.98.225/24 Announce: 193.100.96/24 Announce: 193.100.167/24 Announce: 193.101.2/24 Announce: 193.101.45/24 Announce: 193.101.62/23 Announce: 193.102.21/24 Announce: 193.102.83/24 Announce: 193.102.94/24 Announce: 193.103.134/24 Announce: 193.103.226/24 Announce: 194.64.169/24 Announce: 194.76.211/24 Announce: 194.77.56/22 Announce: 194.77.66/23 Announce: 194.77.94/24 Announce: 194.77.105/24 Announce: 194.77.110/24 Announce: 194.77.113/24 Announce: 194.77.138/24 Announce: 194.77.215/24 Prefixes: 25 Dropable: 0 Agg-able: 1 Gainable: 1

3 3

RIPE Action 21.9: Fwd: E-J B: Draft doc m.cast router in routing reg.
by Wilfried Woeber, UniVie/ACOnet 25 Jan '96

25 Jan '96

FYI, this is the original proposal as circulated by Erik-Jan Bos. -Wilfried. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Subject: Draft document multicast router in routing registry From: Erik-Jan Bos <erik-jan.bos(a)surfnet.nl> Date: Sun, 07 May 1995 11:49:46 +0200 Mbone-EU, please find below a first version of a document describing a multicast router in a routing registry. I would like to have your comments and we can discuss it at the next Mbone WG meeting. I realize some of you might not have a chance to read it before the meeting. Well... here it is, I'll try to bring copies to the meeting. See you in Rome. --- Start of document A Multicast Router in the Routing Registry Erik-Jan Bos Document ID: ripe-nnn May, 1995 **** DRAFT ** WORK IN PROGRESS ** DRAFT **** ABSTRACT This document describes an addition to ripe-122 (Specifying an "Internet Router" in the Routing Registry) in which it is possible to define a multicast capable Internet routing within a routing registry. 1. Introduction With the growing of the Mbone worldwide, managing the Mbone becomes a complex task. The multicast-bone is starting to suffer from problems that used to be present in the unicast-bone several years ago, such as routing coordination. Today, registries are available for administering policies and routes and routers [1]. Tools are availble [2,3] for checking and analyzing the real world against what is registered. The Mbone could and should benefit from these technologies coming from the unicast world. The features of the specification described in this document will be usable e.g. in the RIPE Data Base, after review by the RIPE Data Base WG. After implementation tools could be developed for mapping and analyzing the Mbone. Furthermore, administrative details (such as contact person) are easily administered by well known procedures and easily retrievable. 2. Multicast routers versus unicast routers An "Internet Router" or a "gateway" in the current version of IP (IPv4) can be defined as follows [4]: "Gateways in the Internet form a cooperative, interconnected structure. Datagrams pass from gateway to gateway until they reach a gateway that can deliver the datagram directly." This definition can be applied to both unicast and multicast routers. Since both a unicast and multicast router are fulfilling the "Internet Router" function for different natures of traffic, there is no need for a special routing registry data base object. Moreover, both functions could be present in the same box. 3. Multicast router specification Since an Internet Router can perform both types of routing, this fact should be registerable in the routing registry. Each router is uniquely defined by by its object name, also known as the fully qualified domain name. Below is an example of a internet router object, specifying a multicast router: inet-rtr: broodjeham.surfnet.nl localas: AS1103 ifaddr: 192.87.106.102 255.255.255.0 ifaddr: 192.87.4.99 255.255.255.0 mpeer: 192.87.108.13 16 1 admin-c: Erik-Jan Bos tech-c: Henk Steenman notify: netmaster(a)surfnet.nl remarks: SURFnet Multicast router changed: Erik-Jan.Bos(a)surfnet.nl 950505 source: RIPE Several pieces of important information are present in this object. First of all there is the FQDN of the router, acting as object name. The Home Autonomous System Number is shown, which for a multicast router is merely for identification purposes only. Furthermore, the ifaddr:-lines show that this router has two interfaces, in two different networks. Finally, the DVMRP peers are shown with IP address, treshold and metric. All other attributes are common to other objects already defined for a routing registry [1]. For exact syntax definition see next chapter. 4. Multicast router Syntax Definition The multicast capable router object is defined here. Each of the possible attributes are shown, on a single line. The second column defined whether the attribute must be present [mandatory] of could be present [optional]. The third column defines whether exactly one line is allowed [single] or that more than one line of the same attribute is allowed [multiple]. In case an attribute has more lines than one, the name of the attribute must be repeated on each line. inet-rtr: [mandatory] [single] localas: [mandatory] [single] ifaddr: [mandatory] [multiple] mpeer: [mandatory] [multiple] admin-c: [mandatory] [multiple] tech-c: [mandatory] [multiple] notify: [optional] [multiple] remarks: [optional] [multiple] changed: [mandatory] [multiple] source: [mandatory] [single] Each attribute has the following syntax: inet-rtr: The fully qualified domain name of the router. localas: The Autonomous System to which the router belongs. ifaddr: An interface IPv4 address of the router. mpeer: A multicast peering of the router. Format: <mpeer address> <mpeer treshold> <mpeer metric> Example: mpeer: 192.87.108.13 16 1 Status: mandatory, multiple instances allowed. admin-c: Full name or uniquely assigned NIC-handle of a contact person for administrative matters. tech-c: Full name or uniquely assigned NIC-handle of a contact person for technical matters. notify: An e-mail address to which notifications of changes to this object should be send. remarks: Remarks or comments, for clarification purposes only. changed: The e-mail address and date of a change. source: Source of the information. 5. Acknowledgements This specification, being an addition to ripe-122, leans on the specification done by the author of ripe-122. Credits go to Tony Bates. Furthermore, the RIPE Mbone WG has done reviewing of this document and they receive credits as well. 6. Security considerations Security is not considered in this document. 7. References [1] Bates, Tony, "Specifying an Internet Router in the Routing Registry", ripe-122, October 1994. On-line at URL: ftp://ftp.ripe.net/ripe/docs/ripe-122.txt [2] PRIDE Tools Release 1. On-line at URL: ftp://ftp.ripe.net/pride/tools/pride-tools-1.tar.Z [3] Merit Inc. RRDB Tools. On-line at URL: ftp://rrdb.merit.edu/pub/meritrr [4] Douglas Comer, "Internetworking with TCP/IP", Prentice-Hall, 1988. ISBN: 0-13-470188-7. --- End of document __ Erik-Jan. --------------------------------------------------------------------------------

1 0

RIPE Action 21.9: proposal for an ext. of inet-rtr (Mbone R.)
by Wilfried Woeber, UniVie/ACOnet 25 Jan '96

25 Jan '96

There is a fairly old action on Eric-Jan and me to circulate a proposal on extending the definition for the RIPE Database router object inet-rtr: The original definition is documented in ripe-122. The background for the proposed extension is the discussion about documenting the routing of "overlay" networks, most prominently the Mbone. Quite a while ago Erik-Jan Bos circulated a proposal to extend inet-rtr: with an mpeer: attribute. This proposed mpeer: attribute is/was intended to specifically document Mbone DVMRP tunnels. [ I'm going to re-distribute this paper in a separate message for those of you who don't have a copy readily available ] Further discussion revealed that by rearranging and extending the definition of the *existing* peer: attribute there is a possibility to make the concept even more general and potentially covering IP over IP, STUN, whatever. At the same time we could avoid inventing just another attribute. The current use of the attribute is: peer: <Peer address> <Peer AS> <Routing Protocol> [localAS ASnumber] The generalisation would involve changing that definition to peer: <Peer address> <Peer protocol> <peer-proto-specific info> So for the good old BGP peering this might then look like: peer: 192.87.4.6 BGP4 AS2122 localAS AS2121 for an Mbone tunnel this might be peer: 192.87.4.6 DVMRP metric thresh and for an IP-over-IP even peer: 192.87.4.6 IP Unfortunately this approach would require a non-compatible change to the existing peer: attribute. How many tools would be affected? What's the expected effort to fix these tools? Your opinions and input wrt to the concept and the proposal to change the peer: definiton for BGP peerings is appreciated - before we spend too much effort on the details.... Regards Wilfried -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Vienna University : Tel: +43 1 4065822 355 Universitaetsstrasse 7 : Fax: +43 1 4065822 170 A-1010 Vienna, Austria, Europe : NIC: WW144 --------------------------------------------------------------------------

1 0

Re: Question on % of good routes and plea for an RA mail list was Re: Routing registry was Re: Sprint BGP filters in 207.x.x.x?
by Steven J. Richardson 05 Jan '96

05 Jan '96

>From list-admin(a)merit.edu Thu Jan 4 05:03:27 1996 >Message-Id: <9601040929.AA14593(a)ncc.ripe.net> >To: hwb(a)upeksa.sdsc.edu (Hans-Werner Braun) >Cc: nanog(a)merit.edu, RIPE Routing WG <routing-wg(a)ripe.net> >Subject: Question on % of good routes and plea for an RA mail list was Re: Routing registry was Re: Sprint BGP filters in 207.x.x.x? >In-Reply-To: Your message of Wed, 03 Jan 1996 15:21:50 PST. > <199601032321.PAA24966(a)upeksa.sdsc.edu> >References: <199601032321.PAA24966(a)upeksa.sdsc.edu> >From: Daniel Karrenberg <Daniel.Karrenberg(a)ripe.net> >Date: Thu, 04 Jan 1996 10:29:49 +0100 >Sender: Daniel.Karrenberg(a)ripe.net >The early NSFnet one was done to configure a single backbone. Remember >that EGP was the state-of-the-art. NSFNet provided last resort routing >and everyone was happy. More complex registries were not needed to keep >track of this even when "back doors" appeared. > >In Europe the situation was not like that at all. Despite great efforts >we were never blessed with a single pan-European backbone or even a >last-resort routing service. This is why RIPE developed a routing >registry that was capable of being useful in a general topology of >indepoendent ISPs. FYI: Lest anyone think that the PRDB was single-backbone-specific in _design_ or capability (it pretty much was in terms of data), let me note that, when Andy Adams and I rewrote the PRDB from a SPIRES DB to a RDBMS (with help from Tom Libert and Sue Hares), we explicitly designed in the ability to include data from other backbones. This was initially done to support both the T1 and T3 backbones, but it could easily have supported other backbones as well. >Daniel Steve Richardson/Merit

2 1

Question on % of good routes and plea for an RA mail list was Re: Routing registry was Re: Sprint BGP filters in 207.x.x.x?
by Daniel Karrenberg 04 Jan '96

04 Jan '96

> hwb(a)upeksa.sdsc.edu (Hans-Werner Braun) writes: > It even predates the T1/... NSFNET backbone. We already used something > like that for the 56kbps Fuzzball based NSFNET backbone. In a sense, > the RIPE db etc. are latecomers here. Susan is correct, the NSFNET > implemented and formalized the routing data base in evolutionary > stages. Indeed there is an evoloution of routing policy databases/registries. The early NSFnet one was done to configure a single backbone. Remember that EGP was the state-of-the-art. NSFNet provided last resort routing and everyone was happy. More complex registries were not needed to keep track of this even when "back doors" appeared. In Europe the situation was not like that at all. Despite great efforts we were never blessed with a single pan-European backbone or even a last-resort routing service. This is why RIPE developed a routing registry that was capable of being useful in a general topology of indepoendent ISPs. We weren't more clever or had more foresight, we simply had the need earlier. I think it has been a good decision by the RA team to use this technology and to contribute to its development rather than inventing something new right away. Given the resources I would hope for more output in the way of tools etc. but I see it coming now. > Often despite complaints from many sites that wanted free and > uncontrolled flow of routing information. This is a great misconception about routing registries which comes from the time of the single backbone model. The routing registry and the backbone were then operated by the same people and used to enforce The Routing Policy. The situation is different now. Each ISP sets and enforces their routing policy. The routing registry only supports them in this. Of course a good routing policy is to not propagate routes to address space which is not assigned and to generally filter announcements from customers. But there is no way to use the routing registry to force ISPs to do reasonable things. > I am not arguing about whether the RIPE and the RA DB should or should > not be merged, just that there is a history to the steps taken, and > reconciling into a homogenious DB (format) would have to be a concious > effort by the parties seeing mutual benefit. Not that it should not > happen otherwise, it just won't, given project priorities. I am pessimistic at all. All routing registies use the same schema or very very similar ones. They currently call come from the ripe-181 specifications which are based on input from the RA people. The RADB, RIPE RR, MCI RR and all the others really form a global Internet RR which is quite useful already and can be made more useful. Two things are needed now: 1) Improve active maintenance by the registrars. This will by itself lead to better alignment between registries and remove duplicate registrations. 2) Produce and *deploy* more useful tools. If this is done well, ISPs will use those registries more and register in them because it is useful and interest. Daniel

1 0

195/8
by Daniel Karrenberg 18 Dec '95

18 Dec '95

> Sean Doran <smd(a)chops.icp.net> writes: > > Peter and I would naturally love to see no subnets of > 195/8 at all, and see everyone using any of 195/8 and > talking to networks outside Europe be required to provide > transit to all of 195/8. I fully agree that that is a very desirable goal. However, given the transmission tariff situation and the marketing practises of US ISPs in Europe it is probably not realistic right now. > Failing that, I want to see an absolute maximum of > about 1000 prefixes in 195/8, period. The RIPE NCC allocates address space. We have no control over how ISPs will set their routing policy and design their exterior routing. Would you like to consider for a moment the allocation data for 19[34]/8? prefix #allocs #allocs length 193/8 194/8 PA 12 1 0 PA 13 2 1 PA 14 6 1 PA 15 25 7 PA 16 55 60 PA 17 2 10 PA 18 4 25 PA 19 2 93 PI 16 50 52 ---- ---- Total 147 249 ==== ==== Notes: 1) The table only shows the prefixes currently allocated. 2) The RIPE NCC does allocate in such a way that future allocations can often be aggregated with present allocations. This means that a number of allocations will 'ripple upwards' in the table. It is important to note that we do not make any guarantees about that to our customers but still try to do the right thing. 3) Little can be said at present about the possibility of aggregation in PI space. 4) The allocation information is available in the RIPE database. However due to some procedural problems not all of it is up-to-date at present. We will have this corrected early next year. As you can see the total number of allocations is not that high. The provider aggregateable addresses could be routed in less than 200 routes for each block. Now consider the actual number of routes vs the address space covered for the 'C-Space' /16 block hosts routes hosts addres- / sed route 192.0.0.0 4733440 6471 731 193.0.0.0 8934656 2001 4465 194.0.0.0 6462208 1622 3984 195.0.0.0 1024 4 256 196.0.0.0 708864 356 1991 197.0.0.0 256 1 256 198.0.0.0 7400960 3668 2017 199.0.0.0 7735552 3270 2365 200.0.0.0 4625152 589 7852 201.0.0.0 256 1 256 202.0.0.0 3855680 1362 2830 203.0.0.0 5662720 690 8206 204.0.0.0 10388224 3517 2953 205.0.0.0 5851648 1775 3296 206.0.0.0 10236928 1573 6507 207.0.0.0 32768 3 10922 208.0.0.0 1024 4 256 C Space 76631360 26907 2848 You will note that Europe's performance is far better than that of anyone else if you consider the time of allocation. *Personal Soapbox The RIPE NCC allocation policy has resulted in significant aggregation well before anyone else's! I consider it quite arrogant of Sean Doran (and Peter) to tell us how we should set our policies. *End Personal Soapbox For next year we are planning to continuously compare allocations with observed routes in various ways. The goal of this is advise IRs and ISPs about possible improvements in allocation/assignment and routing. We consider this the appropriate strategy to improve route aggregation. > If you will guarantee that here and on paper, then as > Dennis Ferguson and Geert-Jan de Groot have pointed out in > various ways, there should be no trouble whatsoever with > listening to /19s or even /24s in 195/8. I can easily guarantee you on paper that we will make every effort not to make more than 1000 allocations from 195/8 and that we will supply you (as everyone else) with the data on valid allocation including whether they are PA or PI. Hint: This makes it easy to verify which /19s ot of 195/8 you need to accept. > If you can't do that and mean it and enforce it, then > the only option I see is to impose a bitwise filter which > sets a hard ceiling of the number of prefixes we will hear > in 195/8. It should be clear that the RIPE NCC cannot enforce routing policies of any ISP. In order to be totally clear I add that we also do not desire to ever do this because it is a "Bad Thing" (tm). However unless there is consensus that indiscriminate prefix length filters are a "Good Thing" (tm) and the majority of providers use them, we cannot waste of address space by raising our minimum allocation size. > Daniel> SprintLink will be well advised to take > Daniel> this into account when defining their routing > Daniel> policy. > > We did. Maybe someting went wrong in the definition process then because your policy will likely prevent connectivity to some parts of 195/8. Of course I assume that one of your goals is the largest possible connectivity. Maybe I am wrong, certainly I am curious. > Right now there is nothing allocated under 195/8 right > now, and so anything you allocate under 195/8 which isn't > aggregated into a 18-bit-or-shorter prefix simply will > never work from day one. You should probably consider > making this clear to everyone you allocate your /19s to, > if you plan to keep allocating nonaggregatable /19s. It will not work *with/over Sprintlink*. We already advise everyone that - we publish our allocation policy in the appropriate fora so that ISPs can take note of it - we have no control over the routing policies of service providers. I am sure that you can achieve the desired result by setting your filter in 195/8 to /19. Should the number of routes accepted by this filter grow beyond acceptable limits we will certainly work with you as with everyone else to improve the situation. If you intend to keep the filter at /18, I invite you to get out the word yourself. A good start would be to present it at the upcoming RIPE meeting in January. Curiously your's Daniel

1 0

RE: Routing wars pending?
by Hank Nussbacher 16 Nov '95

16 Nov '95

On Wed, 15 Nov 1995 11:00:04 MET you said: > With regard to the rest of your message - here is what we do, both as a > Service Provider Registry and a as backbone provider which has to deal > with routing: > > We strictly refuse requests to assign address space for further > sub-assignement. Adresses are *directly* assigned to the eventual user. > If a service provider wants to act as a Local-IR, then the proper way > of doing it is to get in touch with the RIPE-NCC and establish a > registry of it's own. Is that the general consensus in other countries? > > Just to make sure that everybody understands the rules, we explicitely > point out that the assignement is only valid for the purpose of > connecting (directly or through an intermediate step) to our backbone. > We explicitely reserve the right to reclaim the address space if these > conditions are not (or no longer) met. I know that RLR are slightly > different, of course. We have had problems with this also. > > With regard to routing, the answer is both collaboration by all > service providers (which is working rather well, I think) *and* > filtering based on the route objects in the RIPE database (which > appears to gain popularity). If somebody tries to play games, and most > of the backbones would have filters, then there is a good chance that > the hickup is confined to a small part of the Internet - which > eventually makes the "highjacked" addresses more or less useless. Yes Europe is very organized - but what do you do about the USA? > > And the multiple database issue should be sorted out anyway, because > the problem of inconsistency *is* there, even without malicious intent > on any side. > > Wilfried. > -------------------------------------------------------------------------- > Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at > Computer Center - ACOnet : > Vienna University : Tel: +43 1 4065822 355 > Universitaetsstrasse 7 : Fax: +43 1 4065822 170 > A-1010 Vienna, Austria, Europe : NIC: WW144 > -------------------------------------------------------------------------- Hank

2 1

RE: Routing wars pending?
by Wilfried Woeber, UniVie/ACOnet 15 Nov '95

15 Nov '95

Hi Hank! I don't know to what extent you have been following the discussions recently within RIPE wrt Registries of Last Resort... My first answer to the story below would be "stop the Registry of Last Resort business asap". Just to avoid making the mess even bigger... >ILAN acts as registry of last resort in Israel. It owns and assigns >IP addresses in the 192.114-118.0.0 address range. These 5 blocks >are owned by ILAN (AS378). Over the years, many IP addresses have >been assigned - in the past to individual companies and more lately >CIDR blocks to local ISPs. ILAN takes a $50 one time fee to register >the IP address for the requestor. Just a matter of terminology, I'm worried by your mixing of the LRL function and phrases like "owns and assigns" in the same sentence with "owned by ILAN (AS378)". If you were really sending these signals to your peers then there is a good chance of mis-understandings. With regard to the rest of your message - here is what we do, both as a Service Provider Registry and a as backbone provider which has to deal with routing: We strictly refuse requests to assign address space for further sub-assignement. Adresses are *directly* assigned to the eventual user. If a service provider wants to act as a Local-IR, then the proper way of doing it is to get in touch with the RIPE-NCC and establish a registry of it's own. Just to make sure that everybody understands the rules, we explicitely point out that the assignement is only valid for the purpose of connecting (directly or through an intermediate step) to our backbone. We explicitely reserve the right to reclaim the address space if these conditions are not (or no longer) met. I know that RLR are slightly different, of course. With regard to routing, the answer is both collaboration by all service providers (which is working rather well, I think) *and* filtering based on the route objects in the RIPE database (which appears to gain popularity). If somebody tries to play games, and most of the backbones would have filters, then there is a good chance that the hickup is confined to a small part of the Internet - which eventually makes the "highjacked" addresses more or less useless. And the multiple database issue should be sorted out anyway, because the problem of inconsistency *is* there, even without malicious intent on any side. Wilfried. -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Vienna University : Tel: +43 1 4065822 355 Universitaetsstrasse 7 : Fax: +43 1 4065822 170 A-1010 Vienna, Austria, Europe : NIC: WW144 --------------------------------------------------------------------------

1 0

New Document available: ripe-131
by RIPE NCC Document Annoucement Service 23 Oct '95

23 Oct '95

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-131 Title: The Advisory Attribute Author: David Kessens, RIPE NCC Date: 23 October 1995 Format: Obsoletes: ripe-130 Obsoleted by: Updates: ripe-181 Updated by: Old: Short content description ------------------------- Adds 'advisory' attributes to 'aut-num' objects. Use with care. FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/" followed by the command "get filename". The relevant filenames for this document are: ripe-131.txt for the ASCII version ripe-131.ps for the PostScript version Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server(a)ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the RIPE document by FTP or mail server. SEND ripe/docs/ripe-131.txt

1 0

New RA Tools Announcement
by Brian Renaud 18 Oct '95

18 Oct '95

Here is some additional location information for a number of the tools I discussed at the last meeting. -Brian ------- Forwarded Message Date: Wed, 18 Oct 1995 13:34:21 -0400 From: labovit(a)merit.edu To: nanog(a)merit.edu Subject: New RA Tools Announcement New Routing Arbiter Tools Announce ---------------------------------- The Routing Arbiter welcomes comments, bug-reports and suggestions for new tools. Please direct email to ra-team(a)ra.net. Please feel free to redistribute this announcement. A web version of this page lives at http://www.ra.net/~ra/tools ------------------------ Online Tools and Reports ------------------------ IRRWeb This graphical interface into the Internet Routing Registry makes it possible to use the Web to query the IRR and update RADB AS objects, Route objects, and Maintainer objects. Users can enter any value that can be submitted through a whois query, such as an AS number, network IP address, or maintainer. IRRWeb then displays the corresponding AS objects, Route objects, or Maintainer objects from the various registries in the IRR. Authorized maintainers can edit the objects directly; IRRWeb performs a cursory pre-check and mails the revised object to auto-dbm(a)ra.net. The user then receives e-mail from auto-dbm confirming and displaying the revised object, or explaining why the object was rejected. See http://www.ra.net/cgi-bin/ra/query-radb.pl Source code is available at ftp://ftp.ra.net/routing.arbiter/tools/irrweb.tar.gz Daily NAP Route Flap Reports</A> This new tool set generates daily reports of route flaps (link failures at regular and short intervals) throughout the Internet. Modeled after the reports originally produced by Curtis Villamizar of ANS, the new reports are generated using tools packaged with Merit's Multi-Threaded Routing Toolkit. The data is obtained from peering sessions with Route Servers at the interconnection points. The reports note the last state of the route (up or down), the length of time that a route existed (or did not exist) for that prefix, and the number of times a route for the prefix transitioned from down to up, up to down, or was replaced by a new route with changed attribute information. AS-path-specific information is also provided for every path announced for the prefix. See http://www.ra.net/~ra/tools/flap.html Route History Server The Route History Server provides a mechanism for tracking the announce/withdraw history of a given prefix for the last 24 hours. The History Server peers with the route servers at each NAP and records all BGP updates in History Server/Route Server peering session. See http://www.ra.net/cgi-bin/ra/rshist.pl ----------------------- Tools Available for FTP ----------------------- RSd The Route Server daemon (RSd) is an enhanced version of the GateD routing software that provides multiples views of routing information. The software provides a mechanism for network service provides to off-load the computational complexity of routing policy calculations from their routers. RSd supports configuration and transparent passing of BGP MEDs. The software also supports BGP route flap dampening. Available at ftp://ftp.ra.net/routing.arbiter/tools/rsd.tar.gz Peval A policy evaluator that inputs a RIPE-181 policy expression, performs essential background calculations such as symbolic evaluations and expansions, and outputs another RIPE-181 policy expression that is used by other tools, such as RTConfig. Available as part of the RAToolSet at ftp://ftp.ra.net/routing.arbiter/tools/RAToolSet RTConfig A router configuration tool that can be used by providers to generate router configs directly from the RADB or other IRR registries. Currently in production use for the RA Route Servers, ANSNET, and CA*net, RTConfig is a front-end tool that uses peval and radbserver transparently to users. Available as part of the RAToolSet at ftp://ftp.ra.net/routing.arbiter/tools/RAToolSet rrc2r/rrmerge This Cisco-to-RIPE-181 conversion package makes it possible for users to convert Cisco router configuration files to RIPE-181 objects that can be submitted to the Internet Routing Registry (IRR). The Cisco access-list can be converted into an explicit set of nets embedded in an AS object or represented as a community. The RADBserver is queried for any missing or previously registered information. Available at ftp://ftp.ra.net/routing.arbiter/tools/RAToolSet/rrc2r-0.2.tar.gz CiscoBGP IRR users have long recognized the need for tools that check the IRR against routes actually propagated in the Internet. CiscoBGP obtains and analyzes routing information from production Ciscos, and compares the data with routes in the IRR. The software also flags prefixes that are reserved by RFC 1597, Address Allocation for Private Internets. Available as part of the MRT software distribution at http://www.merit.edu/~mrt BGPCheck BGPCheck obtains and analyzes routing information from BGP4 peering sessions, and compares the data with routes in the IRR. The software also flags prefixes that are reserved by RFC 1597, <em>Address Allocation for Private Internets</em>. Available as part of the MRT software distribution at http://www.merit.edu/~mrt PRtraceroute The 'prtraceroute' tool is a powerful form of traceroute that displays the Autonomous Systems that a packet traverses. PRtraceroute was developed by the Pride project. A version of prtraceroute that queries the RADB is available at ftp://ftp.ra.net/routing.arbiter/pride/prtraceroute-2.0beta2.shar.gz ------------------ Tool Announcements ------------------ PGP-Based Radb Authentication Follow these steps to take advantage of the new RADB support for PGP-based digital signatures: 1. Register your public key with the Routing Arbiter Service. 2. Modify your Maintainer object to reflect your use of digital signatures. 3. Use PGP to sign your RADB transactions. For detailed instructions, see: http://www.ra.net/routing.arbiter/RA/RADB.tools.docs/pgp.html -- Craig Labovitz labovit(a)merit.edu Merit Network, Inc. 4251 Plymouth Road, Suite C. (313) 764-0252 (office) Ann Arbor, MI 48105 (313) 747-3745 (fax) ------- End of Forwarded Message

1 0