From maldwyn at ripe.net Mon Feb 1 13:02:22 1999 From: maldwyn at ripe.net (Maldwyn Morris) Date: Mon, 01 Feb 1999 13:02:22 +0100 Subject: ANN: Web141, the RIPE 141 syntax checking web page Message-ID: <199902011202.NAA14364@x40.ripe.net> Hi, As announced at the Local IR Working Group at the 32nd RIPE Meeting on 27/1/1999, the RIPE NCC European IP Address Space Request Syntax Checking web page, Web 141, is now functioning. The URL is: http://www.ripe.net/cgi-bin/web141/web141.pl.cgi Please note that it is only for formatting and syntax checking requests - you must send the request in an email to hostmaster at ripe.net for any action to be taken with it. You can fill in your RIPE 141 format address request in the boxes provided and merely convert the request to correctly formatted plain text suitable for pasting into an email, or you can also have the autohm program check the syntax of your request. This is the same program that checks RIPE 141 requests sent to hostmaster at ripe.net, so if you pass these checks you can be sure you will not fail the syntax checks there. However please note that other checks are performed before you are given what you are requesting, and your request may still fail these checks. The simple source of the web page generator and plain text converter ( using Perl5 and CGI.pm ) will be made available in two weeks, and autohm, the syntax checking tool also written in Perl 5, will be made available in four weeks. Please let the lir-wg list know if you have any comments on the web page or the checks that are done. Cheers, Maldwyn Morris Software Manager RIPE NCC From yiannos at ucy.ac.cy Tue Feb 2 15:35:23 1999 From: yiannos at ucy.ac.cy (Yiannos Pitas) Date: Tue, 02 Feb 1999 08:35:23 -0600 Subject: ANN: Web141, the RIPE 141 syntax checking web page References: <199902011202.NAA14364@x40.ripe.net> Message-ID: <36B70D2B.4A4ADEC0@ucy.ac.cy> Looking at the web page, it seems that every time we want to fill in a new request the #[CURRENT ADDRESS SPACE USAGE TEMPLATE]# must be filled in as well one by one, a time consuming task especially for those LIRs who manage a large address space. Is this what it is or Am I missing something here? Regards, Yiannos Pitas, University of Cyprus Maldwyn Morris wrote: > Hi, > > As announced at the Local IR Working Group at the 32nd RIPE Meeting on > 27/1/1999, the RIPE NCC European IP Address Space Request Syntax > Checking web page, Web 141, is now functioning. > > The URL is: > > http://www.ripe.net/cgi-bin/web141/web141.pl.cgi > > Please note that it is only for formatting and syntax checking > requests - you must send the request in an email to > hostmaster at ripe.net for any action to be taken with it. > > You can fill in your RIPE 141 format address request in the boxes > provided and merely convert the request to correctly formatted plain > text suitable for pasting into an email, or you can also have the > autohm program check the syntax of your request. This is the same > program that checks RIPE 141 requests sent to hostmaster at ripe.net, so > if you pass these checks you can be sure you will not fail the syntax > checks there. However please note that other checks are performed > before you are given what you are requesting, and your request may > still fail these checks. > > The simple source of the web page generator and plain text converter > ( using Perl5 and CGI.pm ) will be made available in two weeks, and > autohm, the syntax checking tool also written in Perl 5, will be made > available in four weeks. > > Please let the lir-wg list know if you have any comments on the web > page or the checks that are done. > > Cheers, > > Maldwyn Morris > Software Manager > RIPE NCC -- ----------------------------------------------------------------------------- Yiannos Pitas, | Computer Center, | Tel: 357-2-756186 University Of Cyprus, | Fax: 357-2-756082 Kallipoleos 75, | email: yiannos at ucy.ac.cy Nicosia, | http://www.ucy.ac.cy/ CYPRUS. | ---------------------------------------------------------------------------- From guyd at uk.uu.net Tue Feb 2 11:06:48 1999 From: guyd at uk.uu.net (Guy Davies) Date: Tue, 2 Feb 1999 10:06:48 +0000 (BST) Subject: Proposal to raise the maximum allocation to a single LIR Message-ID: Hi All, Following on from my comments at the LIR wg, I'd like to describe the issues we have and some possible solutions for these problems for the longer term. Our primary problem is that we wish to have administrative boundaries within our network separating the Backbone, LL Customers and Dial pools. It is usual to aggregate routing announcements at these administrative boundaries which is essential for the network's scalability and stability. Unfortunately, the current policy decided by the LIR working group states that the maximum amount of total free address space held by any single LIR is a /16. This can be really problematic due to the differing rates at which addresses for customers, backbone addressing and dial space are used up. It is possible to have a serious shortage of addresses for one aspect of your network while there is quite a lot of space remaining for the other areas. The restriction of a /16 means that it may not be possible to acquire more addresses for the area which has the need. It has also been generally noted that the RIPE NCC have not taken internal aggregation of routes into account when making allocations. While it may have been OK to ignore this aspect of network address allocation in the past, this is no longer the case and the decision must now be based also on realistic internal aggregation model. Below are some possible solutions to this problem. 1) Increase the maximum free space available for all LIRs to a shorter prefix. This has the disadvantage that it is contrary to RIPE's aim of conservation of address space. It sets a general precedent that any large or rapidly growing LIR can cite when requesting larger allocations. However, the advantage is that it doesn't make any specific differentiation between those LIRs who make use of the larger allocations and is, therefore, easier for the RIPE NCC to administer. 2) Devise some scheme to differentiate the maximum simultaneous available addresses for large registries from that for the small and medium registries. This has the disadvantage that it adds to the administrative load on the RIPE NCC. It is more difficult to manage exceptions. However, it means that the scope of the availability of more addresses is limited which more closely matches RIPE's aims of conservation of address space. 3) Make a specific exception for those organisations who can show evidence of a need for more than a /16 of address space simultaneously available. This adds even more administrative load on the RIPE NCC because it is based on single exceptions each of which could have a different agreement with the RIPE NCC. However, it matches more closely still the aims of conservation. 4) Setup a registry for each function which needs to be separately administered. This adds more administrative load (and cost) to the LIR and to RIPE NCC because there are more independent registries. The primary benefit is that this solution doesn't require any new policies to be made (unless it's contrary to policy for a single entity to have multiple registries for administrative convenience ;-) I'd like this to be the catalyst for some discussion of this subject on the lir-wg list. If anyone has similar concerns or issues, I'd be particularly keen to hear that. Regards, Guy --- Guy Davies UUNET, an MCI WorldCom company European Network Specialist 332 Science Park, Cambridge, CB4 4BZ, UK e: Guy.Davies at uk.uu.net t: +44 (0)1223 250457 f: +44 (0)1223 250412 From rpa at aurora.uk.insnet.net Tue Feb 2 12:13:01 1999 From: rpa at aurora.uk.insnet.net (Richard Almeida) Date: Tue, 2 Feb 1999 11:13:01 +0000 () Subject: Proposal to raise the maximum allocation to a single LIR In-Reply-To: from "Guy Davies" at Feb 2, 99 10:06:48 am Message-ID: <199902021113.LAA15924@aurora.uk.insnet.net> Hi We have lots of registries, as we've needed different CIDR blocks to put in different ASNs (most others seem to just break PA space if they want to do this) We own AS5378 - original INS backbone AS6660 - INS USA network AS6765 - Wisper network (recently aquired) AS6889 - Wisper USA network (recently aquired) What we have as a result is 3 RIPE registries, and 1 ARIN one. AS6889 doesnt originate anything, but uses space announced in AS6765 - which of course causes problems for them - we will either get another ARIN registry or migrate 6889 out totally. The 3rd RIPE one is for a subsidiary, that we know will one day talk BGP and thus needed to keep address space seperate from AS5378 - the growth rate of that business is substantially different to AS5378's address growth requirements So, summary, theres a case where multipe CIDR blocks are needed where one registry has multiple ASNs for routing policy reasons - aswell as the cases that Guy has described. So much of a case that we're willing to pay for 3 medium registries and 1 ARIN one ... Regards Richard From jhma at EU.net Tue Feb 2 21:41:22 1999 From: jhma at EU.net (James Aldridge) Date: Tue, 02 Feb 1999 21:41:22 +0100 Subject: Proposal to raise the maximum allocation to a single LIR In-Reply-To: Your message of "Tue, 02 Feb 1999 11:13:01 GMT." <199902021113.LAA15924@aurora.uk.insnet.net> Message-ID: <199902022041.VAA24211@aegir.EU.net> Richard Almeida wrote: > We have lots of registries, as we've needed different CIDR blocks to > put in different ASNs (most others seem to just break PA space if they > want to do this) > > We own > AS5378 - original INS backbone > AS6660 - INS USA network > AS6765 - Wisper network (recently aquired) > AS6889 - Wisper USA network (recently aquired) > > What we have as a result is 3 RIPE registries, and 1 ARIN one. AS6889 > doesnt originate anything, but uses space announced in AS6765 - which of > course causes problems for them - we will either get another ARIN registry > or migrate 6889 out totally. > > The 3rd RIPE one is for a subsidiary, that we know will one day talk BGP > and thus needed to keep address space seperate from AS5378 - the growth > rate of that business is substantially different to AS5378's address growth > requirements > > So, summary, theres a case where multipe CIDR blocks are needed where one > registry has multiple ASNs for routing policy reasons - aswell as the > cases that Guy has described. So much of a case that we're willing to > pay for 3 medium registries and 1 ARIN one ... Similarly, EUnet Communications Services pays the RIPE NCC for 6 large registries (as an "n=6" supernational registry) and (as n >= 5) we get a maximum allocation of 9 /16's which we distribute between EUnet's various national operations (In Austria, Belgium, Bulgaria, Switzerland, Egypt, Spain, Finland, France, Ireland, Lithuania, Luxembourg, Latvia, Malta, Norway, Poland, Portugal, Romania, Sweden, Slovenia, Slovakia, Syria and Tunisia. Other national EUnet's maintain their own small, medium or large registries) subject to normal RIPE rules. Richard, I don't understand the necessity of opening registries with both ARIN and the RIPE NCC. What advantage does this give you (unless, perhaps, you're trying to get more than your fair share of IP addresses... ;-) ? James ----- ___ - James Aldridge, Senior Network Engineer, ---- / / / ___ ____ _/_ -- EUnet Communications Services BV --- /--- / / / / /___/ / --- Singel 540, 1017 AZ Amsterdam, NL -- /___ /___/ / / /___ /_ ---- Tel: +31 20 530 5327; Fax: +31 20 622 4657 - ----- 24hr emergency number: +31 20 421 0865 From neil at COLT.NET Tue Feb 2 12:37:13 1999 From: neil at COLT.NET (Neil J. McRae) Date: Tue, 02 Feb 1999 11:37:13 +0000 Subject: Proposal to raise the maximum allocation to a single LIR In-Reply-To: Your message of "Tue, 02 Feb 1999 10:06:48 GMT." Message-ID: <199902021137.LAA15732@NetBSD.noc.COLT.NET> On Tue, 2 Feb 1999 10:06:48 +0000 (BST) Guy Davies wrote: > Our primary problem is that we wish to have administrative boundaries > within our network separating the Backbone, LL Customers and Dial pools. > It is usual to aggregate routing announcements at these administrative > boundaries which is essential for the network's scalability and stability. > Unfortunately, the current policy decided by the LIR working group states > that the maximum amount of total free address space held by any single LIR > is a /16. This can be really problematic due to the differing rates at > which addresses for customers, backbone addressing and dial space are used > up. It is possible to have a serious shortage of addresses for one aspect > of your network while there is quite a lot of space remaining for the > other areas. The restriction of a /16 means that it may not be possible > to acquire more addresses for the area which has the need. This is an interesting problem that I've ran into also. > 3) Make a specific exception for those organisations who can show evidence > of a need for more than a /16 of address space simultaneously available. > > This adds even more administrative load on the RIPE NCC because it is > based on single exceptions each of which could have a different agreement > with the RIPE NCC. However, it matches more closely still the aims of > conservation. Unfortunately, large organisations have in the past used amount of network address space as a criteria for network interconnection, even though one IP address can generate more traffic than some /16 [even /8s] in the routeing table currently. > > 4) Setup a registry for each function which needs to be separately > administered. > > This adds more administrative load (and cost) to the LIR and to RIPE NCC > because there are more independent registries. The primary benefit is > that this solution doesn't require any new policies to be made (unless > it's contrary to policy for a single entity to have multiple registries > for administrative convenience ;-) > This is something like what we have done at COLT. We have a registry for our backbone and we have registries for our local operating companies, we aren't as big as UUNET but this works for us, and I imagine you might even be talking about more LIR's for say, AS1849 as the backbone rather than AS702 as the backbone which I assume already have seperate LIRs. Under the current policies, I can't see any other way of achieving this other than setting up new LIRs. I can see the day where a registry for network areas might make sense, and to take your point about more admin load [cost is acceptable compared to margins and revenues when you are at this stage, and they can be justified in any business plan or budget], this really is only at the start of the process, its a few emails and documents to arrange to be signed and some internal documentation and training. In some ways creating a new LIR demostrates one part or another of all the suggestions you made. Some are good some are bad. Regards, Neil. -- Neil J. McRae - Alive and Kicking. C O L T I N T E R N E T neil at COLT.NET NetBSD-1.3.3 released! ftp://ftp.uk.netbsd.org/pub/NetBSD Free the daemon in your computer! From czmok at ipf.net Tue Feb 2 12:54:49 1999 From: czmok at ipf.net (Jan Czmok) Date: Tue, 2 Feb 1999 12:54:49 +0100 Subject: Proposal to raise the maximum allocation to a single LIR In-Reply-To: <199902021113.LAA15924@aurora.uk.insnet.net>; from Richard Almeida on Tue, Feb 02, 1999 at 11:13:01AM +0000 References: <199902021113.LAA15924@aurora.uk.insnet.net> Message-ID: <19990202125449.A15157@darwin.ipf.de> > Hi > > We have lots of registries, as we've needed different CIDR blocks to > put in different ASNs (most others seem to just break PA space if they > want to do this) > > We own > AS5378 - original INS backbone > AS6660 - INS USA network > AS6765 - Wisper network (recently aquired) > AS6889 - Wisper USA network (recently aquired) > > What we have as a result is 3 RIPE registries, and 1 ARIN one. AS6889 > doesnt originate anything, but uses space announced in AS6765 - which of > course causes problems for them - we will either get another ARIN registry > or migrate 6889 out totally. Hi Richard! We run into the same scenario: We own AS5409 - primary AS IPF.NET AS8543 - IPF.NET Spain AS8578 - IPF.NET UK Currently we use AS5409 for our borders. But the question arises, who will be responsible if we got customers in other countries (e.g. USA). Shall we assign then RIPE allocated address space (as we currently do for Spain and UK) or request ARIN Space with a different AS for USA ? Also, as we run under de.ipf, which is not sufficient, as our company grows, shall we switch to eu.ipf or use for each country a different lir ? The Ripe Documents didn't cover this scenario AFAIK... Greetings Jan Senior Network Engineer IPF.NET -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 240 bytes Desc: not available URL: From rpa at aurora.uk.insnet.net Wed Feb 3 09:11:35 1999 From: rpa at aurora.uk.insnet.net (Richard Almeida) Date: Wed, 3 Feb 1999 08:11:35 +0000 () Subject: Proposal to raise the maximum allocation to a single LIR In-Reply-To: <199902022041.VAA24211@aegir.EU.net> from "James Aldridge" at Feb 2, 99 09:41:22 pm Message-ID: <199902030811.IAA17903@aurora.uk.insnet.net> > Richard, I don't understand the necessity of opening registries with both > ARIN and the RIPE NCC. What advantage does this give you (unless, perhaps, > you're trying to get more than your fair share of IP addresses... ;-) ? It was actually a pre-arin USA address block for connecting our US customers in a different ASN (207.181.0.0/19) - we decided using a US "block" for US customers was nicer for some reason Cheers Richard From neil at COLT.NET Wed Feb 3 11:00:41 1999 From: neil at COLT.NET (Neil J. McRae) Date: Wed, 03 Feb 1999 10:00:41 +0000 Subject: Proposal to raise the maximum allocation to a single LIR In-Reply-To: Your message of "Tue, 02 Feb 1999 12:54:49 +0100." <19990202125449.A15157@darwin.ipf.de> Message-ID: <199902031000.KAA20015@NetBSD.noc.COLT.NET> On Tue, 2 Feb 1999 12:54:49 +0100 Jan Czmok wrote: > Hi Richard! > > We run into the same scenario: > > We own > AS5409 - primary AS IPF.NET > AS8543 - IPF.NET Spain > AS8578 - IPF.NET UK You only need a different AS if your managment of that part of the network is under different control policies. You can announce what ever you like to anyone without having to get different AS numbers. > > Currently we use AS5409 for our borders. But the question arises, who wil= > l be responsible if > we got customers in other countries (e.g. USA). Shall we assign then RIPE= > allocated address space > (as we currently do for Spain and UK) or request ARIN Space with a differ= > ent AS for USA ? > =20 > Also, as we run under de.ipf, which is not sufficient, as our company gro= > ws, shall we switch to eu.ipf > or use for each country a different lir ? > > The Ripe Documents didn't cover this scenario AFAIK... > I think a different block for each country makes sense, you don't _have_ to put this into a different AS. [fx: the next big shortage, as numbers!] -- Neil J. McRae - Alive and Kicking. C O L T I N T E R N E T neil at COLT.NET NetBSD-1.3.3 released! ftp://ftp.uk.netbsd.org/pub/NetBSD Free the daemon in your computer! From tkor at hol.gr Tue Feb 9 13:05:35 1999 From: tkor at hol.gr (Themistoklis Kordogiannis) Date: Tue, 9 Feb 1999 14:05:35 +0200 Subject: Web141, the RIPE 141 syntax checking web page In-Reply-To: <199902011202.NAA14364@x40.ripe.net> Message-ID: <000201be5424$803c64b0$0614000a@chaos.noc.hol.gr> Just two comments on the new form. After i filled all the entries and created the text output i've noticed on the #[PERSON TEMPLATE]# i get an empty phone: even though i've completed all the filelds. I understand that this page is just for checks, and that it uses the same checks with the robot, but is it possible on the person template to put a button so that if the person has a template, we just put the nic handle, press the button and all the rest of the fields are filled automatigically. Cheers Themis > -----Original Message----- > From: owner-lir-wg at ripe.net [mailto:owner-lir-wg at ripe.net]On Behalf Of > Maldwyn Morris > Sent: Monday, February 01, 1999 2:02 PM > To: lir-wg at ripe.net > Cc: local-ir at ripe.net > Subject: ANN: Web141, the RIPE 141 syntax checking web page > > > > Hi, > > As announced at the Local IR Working Group at the 32nd RIPE Meeting on > 27/1/1999, the RIPE NCC European IP Address Space Request Syntax > Checking web page, Web 141, is now functioning. > > The URL is: > > http://www.ripe.net/cgi-bin/web141/web141.pl.cgi > > Please note that it is only for formatting and syntax checking > requests - you must send the request in an email to > hostmaster at ripe.net for any action to be taken with it. > > You can fill in your RIPE 141 format address request in the boxes > provided and merely convert the request to correctly formatted plain > text suitable for pasting into an email, or you can also have the > autohm program check the syntax of your request. This is the same > program that checks RIPE 141 requests sent to hostmaster at ripe.net, so > if you pass these checks you can be sure you will not fail the syntax > checks there. However please note that other checks are performed > before you are given what you are requesting, and your request may > still fail these checks. > > The simple source of the web page generator and plain text converter > ( using Perl5 and CGI.pm ) will be made available in two weeks, and > autohm, the syntax checking tool also written in Perl 5, will be made > available in four weeks. > > Please let the lir-wg list know if you have any comments on the web > page or the checks that are done. > > Cheers, > > Maldwyn Morris > Software Manager > RIPE NCC > > From paula at ripe.net Wed Feb 10 14:38:52 1999 From: paula at ripe.net (Paula Caslav) Date: Wed, 10 Feb 1999 14:38:52 +0100 Subject: static verification methods Message-ID: <199902101338.OAA13152@x30.ripe.net> Hello all, At the Local IR working group at RIPE 32, the issue was raised about changing the policy for applying verification methods to cable connections. Here is our proposal on how to change this policy. First some background: A few years ago, the IANA asked the Regional Registries to keep an eye on "very small assignments to individuals". This means cases like static dial-up where a registry has to use one IP address per dial-up customer. Since these kinds of assignments could potentially use up a lot of address space, it was decided to strongly discourage using static addresses for this and that that we should monitor these assignments more closely. To do this, any Local Registry that assigns a lot of addresses for this purpose (more than 1024 addresses), was requested that they would have to enter each of these customers in the database individually (as is the case with all assignments to end-users). Later when some Local Registries had a problem with entering all their dial-up customers in the database for confidentiality problems, it was decided to add an alternative method that they could instead send us a weekly report showing the customers they added that week. This is so that the Regional Registries could still keep track of these kinds of assignments. In the last few years, more and more technologies have come along that fall under this procedure. Aside from static dial-up, other services such as web hosting (when not using http 1.1), cable connections, ADSL connections, some ISDN connections, etc.. often need to assign one IP address per customer. In many of these cases, using one IP address per customer is necessary because the host is usually permanently connected to the Internet. The issue was raised that applying these verification methods to technologies that are permanently connected to the Internet and need one IP address per customer, is too cumbersome and adds a lot of extra administrative overhead for the provider. We also realise that there are inconsistencies between the Regional Registries in dealing with these technologies. For these reasons, we would like to change the policy and make a distinction between technologies that are usually connected to the Internet permanently and those that are connected only temporarily. Here is the proposal for the new policy, please give us your comments by the end of next week. Permanently online: This includes technologies such as cable, ADSL, and various server (web, ftp, etc..) connections that are usually permanently connected to the Internet. It can also include analogue or digital (ISDN) dial-up connections if they are used for a service that needs to be permanently online and for services like dial-out on demand. For most of these connections, you need to assign one IP address per connection, even if using DHCP (which we recommend because it makes renumbering easier). We propose to change the policy and to not apply the verification methods to these types of connections. For these technologies, we still need to keep track of the amounts of addresses being assigned, however we would do this whenever the customer requests a new assignment for this purpose. Since these services are permanently connected to the Internet, we will probe these addresses to verify whether the assigned addresses really are in use. It must therefore be made clear to the RIPE NCC exactly which block of IP addresses is used for this purpose. We would expect to see that a high percentage are reachable. We might at this point request additional information to show that they have really used the addresses that were assigned for this purpose in the past- this could be in the form of a list of all URLs assigned, their DNS records, config files, etc.. something to show that the IP addresses are all in use. Virtual web hosting is the only one that has an alternative available (http 1.1) that would allow assigning one IP address for several hosts. Since we want to encourage that people use http 1.1, we propose to continue applying the special verification methods to virtual web hosting that doesn't use http 1.1. Temporarily online: This includes technologies that only need to be connected to the Internet temporarily, such as most telephone dial-up connections. We recommend the use of DHCP and assigning IP addresses based on the number of modem ports. We will therefore continue to apply the special verification methods to any organisation that assigns IP addresses based on the number of customers instead. From paula at ripe.net Wed Feb 10 14:41:17 1999 From: paula at ripe.net (Paula Caslav) Date: Wed, 10 Feb 1999 14:41:17 +0100 Subject: lowering maximum assignment window Message-ID: <199902101341.OAA13183@x30.ripe.net> Hi all, As we discussed in our audit report at the Local IR working group at the RIPE 32 meeting, we would like to propose a change in the maximum assignment window that a Registry can have. Currently an assignment window for a Registry can be anything between a 0 and a /19. The /19 assignment window, is a historical legacy. These Registries were for the most part free to assign up to 8192 addresses to a customer without coming to the RIPE NCC for approval. Since some of them are still operating as Local Registries, and they still have a /19 assignment window, this means that we have very little contact with them and we have seen in doing audits on these Registries that many of them are out of date with the procedures for assigning IP addresses, and using the database. We also notice that most of them do not really use this large assignment window fully- meaning that most of their assignments are smaller. The router technology has changed much in the last few years, which means that assignments to customers in general are much smaller. Given the fact that most Registries rarely make such large assignments, and the fact that having such a large assignment window makes it easy for them to lose touch with the RIPE NCC policies, we would like to propose having a lower maximum assignment window. We think a /21 maximum assignment window would be more reasonable. Actually for most Registries, a /24 or /23 assignment window is enough, since they rarely make larger assignments than that. However, for the Registries that make more large customer assignments, having up to a /21 assignment window would allow them room to make most of these larger assignment without coming to us for approval. Please think about this proposal and give us any comments by the end of next week. Kind regards, Paula Caslav Registration Services Manager RIPE NCC From stephenb at uk.uu.net Wed Feb 10 15:06:35 1999 From: stephenb at uk.uu.net (Stephen Burley) Date: Wed, 10 Feb 1999 14:06:35 -0000 (GMT) Subject: lowering maximum assignment window In-Reply-To: <199902101341.OAA13183@x30.ripe.net> Message-ID: Can I make a suggestion: We leave the maximum as a /19 and for a period of time lower the registries assignment window to a reasonable level i.e. a /22 or /23 which will give each registry the time to prove their procedures and expose them to RIPE policies again. This could be done on a rotational basis so each registry could prove to RIPE that they have good working practice. Once RIPE was happy with the registry they would raise the assignment window to the original size. This could be done on a 2 year basis. So within a 2 year period RIPE would be happy that any given registry is applying RIPE policy and DB correctly. Of course this would not need to be done to registries who RIPE are already in regular contact with. I propose this as i do not like adding more load on RIPE as we already have to wait 3 days for a response, costing time and money, something a customer will not accept, which is what lowering the assignment windows for everyone would create. My thoughts, any others? On 10-Feb-99 Paula Caslav wrote: > > Hi all, > > As we discussed in our audit report at the Local IR working group at > the RIPE 32 meeting, we would like to propose a change in the maximum > assignment window that a Registry can have. Currently an assignment > window for a Registry can be anything between a 0 and a /19. The /19 > assignment window, is a historical legacy. > > These Registries were for the most part free to assign up to 8192 > addresses to a customer without coming to the RIPE NCC for > approval. Since some of them are still operating as Local Registries, > and they still have a /19 assignment window, this means that we have > very little contact with them and we have seen in doing audits on > these Registries that many of them are out of date with the procedures > for assigning IP addresses, and using the database. We also notice > that most of them do not really use this large assignment window > fully- meaning that most of their assignments are smaller. The router > technology has changed much in the last few years, which means that > assignments to customers in general are much smaller. > > Given the fact that most Registries rarely make such large > assignments, and the fact that having such a large assignment window > makes it easy for them to lose touch with the RIPE NCC policies, we > would like to propose having a lower maximum assignment window. We > think a /21 maximum assignment window would be more > reasonable. > > Actually for most Registries, a /24 or /23 assignment window is > enough, since they rarely make larger assignments than that. However, > for the Registries that make more large customer assignments, having > up to a /21 assignment window would allow them room to make most of > these larger assignment without coming to us for approval. > > Please think about this proposal and give us any comments by the end of > next week. > > Kind regards, > > Paula Caslav > Registration Services Manager > RIPE NCC > > ---------------------------------- Stephen Burley Senior Hostmaster for UUNET Date: 10-Feb-99 Time: 13:45:02 http://www.uk.uu.net ---------------------------------- An MCI WorldCom Company From stephenb at uk.uu.net Wed Feb 10 15:33:10 1999 From: stephenb at uk.uu.net (Stephen Burley) Date: Wed, 10 Feb 1999 14:33:10 -0000 (GMT) Subject: lowering maximum assignment window In-Reply-To: <199902101414.OAA12875@NetBSD.noc.COLT.NET> Message-ID: > I'd disagree. Surely you ask your customers to justify anything more than a > /24's work of network address space? If you don't already do this you > are probably in breach of the RIPE guidelines, For +every+ customer we > have we fill out a RIPE form irrelevant of assignment window. I think this > should be mandatory, its easy to encapsulate the RIPE form in a > requirement survey for your new customers and have the Order Handling > System generate a vanilla RIPE form for your records or to send out for > approval from the RIPE NCC. I think a /19 as an assignment window is > way too high and I'd agree with what Paula has said in her email. > I am sorry, I think you misread my email. All assignments no matter how small should get a 141 form filled in and kept with customer records, but not sent to RIPE, unless its greater than a /19 or your assignment window. > If you aren't asking your customers what they need such large > assignments for then how do you know there is no waste of address > space? There was no mention in my email of not filling in 141 info for assignments or even gathering the information. All i said was to reduce a registries windows for a short time, so the info you already gather gets sent to ripe then when the window is raised once RIPE is happy we go back to not sending the request to RIPE but keep all the relavent data on file. We do large assignments so i do not agree that a /19 is too large, for most ISP's (small to medium) it is. > > Regards, > Neil. > -- > Neil J. McRae - Alive and Kicking. C O L T I N T E R N E T > neil at COLT.NET NetBSD-1.3.3 released! ftp://ftp.uk.netbsd.org/pub/NetBSD > Free the daemon in your computer! > > ---------------------------------- Stephen Burley Senior Hostmaster for UUNET Date: 10-Feb-99 Time: 14:16:05 http://www.uk.uu.net ---------------------------------- An MCI WorldCom Company From stephenb at uk.uu.net Wed Feb 10 15:42:22 1999 From: stephenb at uk.uu.net (Stephen Burley) Date: Wed, 10 Feb 1999 14:42:22 -0000 (GMT) Subject: lowering maximum assignment window In-Reply-To: <199902101435.OAA13013@NetBSD.noc.COLT.NET> Message-ID: On 10-Feb-99 Neil J. McRae wrote: > On Wed, 10 Feb 1999 14:33:10 -0000 (GMT) > Stephen Burley wrote: > > > I am sorry, I think you misread my email. All assignments no matter how > > small > > should get a 141 form filled in and kept with customer records, but not > > sent > to > > RIPE, unless its greater than a /19 or your assignment window. > > > > So you think that even though you have collected this information that > a turn around for a large block of 3 days is too long? I think its > acceptable > and that most customers who need this sort of space would understand that > it takes a little bit longer to organise. No again that is not what i said. If our assignment window is lowered it would have the effect of delaying insallations as we are committed to decreasing the order to installation time no matter how large or small the connection. I do not have a problem if it was a temp situation you could plan for. > > Regards, > Neil. > -- > Neil J. McRae - Alive and Kicking. C O L T I N T E R N E T > neil at COLT.NET NetBSD-1.3.3 released! ftp://ftp.uk.netbsd.org/pub/NetBSD > Free the daemon in your computer! > > ---------------------------------- Stephen Burley Senior Hostmaster for UUNET Date: 10-Feb-99 Time: 14:36:39 http://www.uk.uu.net ---------------------------------- An MCI WorldCom Company From neil at COLT.NET Wed Feb 10 15:14:56 1999 From: neil at COLT.NET (Neil J. McRae) Date: Wed, 10 Feb 1999 14:14:56 +0000 Subject: lowering maximum assignment window In-Reply-To: Your message of "Wed, 10 Feb 1999 14:06:35 GMT." Message-ID: <199902101414.OAA12875@NetBSD.noc.COLT.NET> On Wed, 10 Feb 1999 14:06:35 -0000 (GMT) Stephen Burley wrote: > Can I make a suggestion: > > We leave the maximum as a /19 and for a period of time lower the registries > assignment window to a reasonable level i.e. a /22 or /23 which will give eac h > registry the time to prove their procedures and expose them to RIPE policies > again. This could be done on a rotational basis so each registry could prove to > RIPE that they have good working practice. Once RIPE was happy with the > registry they would raise the assignment window to the original size. This > could be done on a 2 year basis. So within a 2 year period RIPE would be happ y > that any given registry is applying RIPE policy and DB correctly. Of course > this would not need to be done to registries who RIPE are already in regular > contact with. > > > I propose this as i do not like adding more load on RIPE as we already have > to wait 3 days for a response, costing time and money, something a customer w ill > not accept, which is what lowering the assignment windows for everyone would > create. > > My thoughts, any others? > I'd disagree. Surely you ask your customers to justify anything more than a /24's work of network address space? If you don't already do this you are probably in breach of the RIPE guidelines, For +every+ customer we have we fill out a RIPE form irrelevant of assignment window. I think this should be mandatory, its easy to encapsulate the RIPE form in a requirement survey for your new customers and have the Order Handling System generate a vanilla RIPE form for your records or to send out for approval from the RIPE NCC. I think a /19 as an assignment window is way too high and I'd agree with what Paula has said in her email. If you aren't asking your customers what they need such large assignments for then how do you know there is no waste of address space? Regards, Neil. -- Neil J. McRae - Alive and Kicking. C O L T I N T E R N E T neil at COLT.NET NetBSD-1.3.3 released! ftp://ftp.uk.netbsd.org/pub/NetBSD Free the daemon in your computer! From neil at COLT.NET Wed Feb 10 15:35:58 1999 From: neil at COLT.NET (Neil J. McRae) Date: Wed, 10 Feb 1999 14:35:58 +0000 Subject: lowering maximum assignment window In-Reply-To: Your message of "Wed, 10 Feb 1999 14:33:10 GMT." Message-ID: <199902101435.OAA13013@NetBSD.noc.COLT.NET> On Wed, 10 Feb 1999 14:33:10 -0000 (GMT) Stephen Burley wrote: > I am sorry, I think you misread my email. All assignments no matter how small > should get a 141 form filled in and kept with customer records, but not sent to > RIPE, unless its greater than a /19 or your assignment window. > So you think that even though you have collected this information that a turn around for a large block of 3 days is too long? I think its acceptable and that most customers who need this sort of space would understand that it takes a little bit longer to organise. Regards, Neil. -- Neil J. McRae - Alive and Kicking. C O L T I N T E R N E T neil at COLT.NET NetBSD-1.3.3 released! ftp://ftp.uk.netbsd.org/pub/NetBSD Free the daemon in your computer! From neil at COLT.NET Wed Feb 10 15:44:37 1999 From: neil at COLT.NET (Neil J. McRae) Date: Wed, 10 Feb 1999 14:44:37 +0000 Subject: lowering maximum assignment window In-Reply-To: Your message of "Wed, 10 Feb 1999 14:42:22 GMT." Message-ID: <199902101444.OAA13088@NetBSD.noc.COLT.NET> On Wed, 10 Feb 1999 14:42:22 -0000 (GMT) Stephen Burley wrote: > No again that is not what i said. If our assignment window is lowered it woul d > have the effect of delaying insallations as we are committed to decreasing th e > order to installation time no matter how large or small the connection. I do > not have a problem if it was a temp situation you could plan for. Why couldn't you plan for a permanent situation? Whats the difference? Its sound like that you just don't want the hassle of having to email the RIPE, in that case then thats just too bad. Regards, neil. -- Neil J. McRae - Alive and Kicking. C O L T I N T E R N E T neil at COLT.NET NetBSD-1.3.3 released! ftp://ftp.uk.netbsd.org/pub/NetBSD Free the daemon in your computer! From haug at seicom.net Wed Feb 10 17:00:43 1999 From: haug at seicom.net (Winfried Haug) Date: Wed, 10 Feb 1999 17:00:43 +0100 (CET) Subject: lowering maximum assignment window In-Reply-To: from Stephen Burley at "Feb 10, 99 02:33:10 pm" Message-ID: <199902101600.RAA21859@hq.seicom.net> Hello, we completly agree with the Mail from Neil > should get a 141 form filled in and kept with customer records, but not sent to > RIPE, unless its greater than a /19 or your assignment window. > > > If you aren't asking your customers what they need such large > > assignments for then how do you know there is no waste of address > > space? > > There was no mention in my email of not filling in 141 info for assignments or > even gathering the information. All i said was to reduce a registries windows > for a short time, so the info you already gather gets sent to ripe then when > the window is raised once RIPE is happy we go back to not sending the request > to RIPE but keep all the relavent data on file. We do large assignments so i do > not agree that a /19 is too large, for most ISP's (small to medium) it is. > well UUnet seems to have a /19 AW, so they had no need to contact the RIPE NCC for approval. If they would have done it, they would know, that this doesnt take very long time. Stephen, how many assignment > /21 do you have ? If you take a RIPE-141 for your own records, why not sending it to RIPE NCC ? The delay would be just 3-4 days, if you have a *good* RIPE-141 template... I dont think, the RIPE NCC Hostmasters are a team of idiots, they will check every request in a fair way so if your request is according to the current policy.. You have a big advantage over those ISPs, who only have a /23 or /22 AW and you are using this advantage against competing ISPs. If we have a customer with a need for a /21 we must send a template to RIPE NCC and wait 3-4 days, you can proceed without delay. Some very old IRs have some Class-B networks, which have never been assigned to them and they are still used, if you have a look in the global routing table, e.g for dialup-customers etc...(these networks are only allocated, but not assigned!) We think a /21 is enough and most *big* customers today are using a firewall, thus needing not more than a /23.... and for internal use, you are free to take adress space from 10.0.0.0 - 10.255.255.255 that is more than you ever need :-) -- Winfried Haug * Geschaeftsfuehrer * eMail: wh at seicom.net Laiblinsplatz 12 * 72793 Pfullingen * tel. +49 7121 9770 0 Hauptstaetterstr. 66 * 70178 Stuttgart * fax. +49 7121 9770 19 ------->> seicom.NET - making information available <<------- Internet access, network&security consulting and firewalls 34 Mbit USA (Teleglobe) * 100 Mbit DE-CIX * 34 Mbit WIN From phk at critter.freebsd.dk Wed Feb 10 20:46:21 1999 From: phk at critter.freebsd.dk (Poul-Henning Kamp) Date: Wed, 10 Feb 1999 20:46:21 +0100 Subject: lowering maximum assignment window In-Reply-To: Your message of "Wed, 10 Feb 1999 14:06:35 GMT." Message-ID: <23395.918675981@critter.freebsd.dk> Stephen, Just for reference, I ran over 12-14h worth of trafic data (cisco NetFlow), starting at jan27 midnight, looking for source IP numbers which have a RIPE record of status "ALLOCATED" but not one of "ASSIGNED". Apart from some special case legacy records in the RIPE database there clearly shouldn't be more than a few transient records while reality and database is trying to catch up with each other. Well, "ain't necessarily so" as they sang. Since I found problems with 898 inetnum objects in total about , I take the liberty of including the abbreviated output from my analysis in this email, the majority of people on this list has a entry or two to examine in more detail. These data are of course skewed by the location in the network where the data has been recorded (AS6785/Denmark), our close neighbors will be "oversampled" compared to distant LIRs in different cultures and language areas (since we don't have any major porn-servers on our site). Once you start to examine the output, some classes emerge: 1. "We don't care about/understand the RIPE-DB as long as we can allocate IP numbers to our customers" 2. "Typo/Braino", s/ASSIGNED/ALLOCATED/ for instance. 3. Test IP numbers. 4. Legacy registrations. 5. Transient phenomena. Classes 3, 4 & 5 doesn't really need anything done about them for now. Class 2 should just be pointed out and we can expect it to be fixed ASAP, if it isn't: transfer it to category #1. Class 1 on the other hand, at least in my opinion, are prime candidates for slamming the assignment window shut, auditing every single assignments done by that LIR and resetting the slow-start criteria until they have their act put together. Poul-Henning PS: I have offered Paula to email this report to her automatically every day if she wants it, if people want it, I can also stick it on a web-server for anyone who wants it. PPS: A lot of the Class 2 entries can be found by going through the database looking for entries having: "*st: ALLOCATED ..." but lacking "*mb: RIPE-NCC-HM-MNT" ----------------------------------------------------------------------- *na: RU-RELCOM-194-135 194.135.153.226 TOTAL 1 for *na: RU-RELCOM-194-135 *na: GR-FORTHNET-193-92 193.92.123.18 193.92.123.225 193.92.123.253 TOTAL 3 for *na: GR-FORTHNET-193-92 *na: IS-ISNET-194-144 194.144.241.225 TOTAL 1 for *na: IS-ISNET-194-144 *na: EU-ZZ-193-194 193.194.63.82 193.194.63.83 193.194.95.105 193.194.95.185 TOTAL 4 for *na: EU-ZZ-193-194 *na: SE-SUNET-193-10 193.10.7.205 193.10.12.25 193.10.36.7 193.10.38.123 193.10.38.139 193.10.40.128 193.10.48.2 193.10.48.5 193.10.53.49 193.10.53.69 193.10.53.186 193.10.62.6 193.10.80.42 193.10.81.33 193.10.102.199 193.10.105.24 193.10.105.89 193.10.105.226 193.10.107.3 ... TOTAL 74 for *na: SE-SUNET-193-10 *na: FR-RENATER-193-48-193-52 193.51.54.2 193.51.54.59 193.51.54.65 TOTAL 3 for *na: FR-RENATER-193-48-193-52 *na: FR-RENATER-193-54-193-55 193.54.149.10 193.54.149.18 TOTAL 2 for *na: FR-RENATER-193-54-193-55 *na: UK-JANET-193-60-193-63 193.61.255.3 193.62.23.13 193.62.111.1 193.62.135.51 193.63.235.1 TOTAL 5 for *na: UK-JANET-193-60-193-63 *na: CZ-CESNET-194-212-16 194.212.137.1 TOTAL 1 for *na: CZ-CESNET-194-212-16 *na: EU-EUNET-193-77 193.77.152.253 TOTAL 1 for *na: EU-EUNET-193-77 *na: NL-NLNET-193-78-193-79 193.79.207.6 193.79.207.7 193.79.207.8 TOTAL 3 for *na: NL-NLNET-193-78-193-79 *na: AT-EUNET-193-80 193.80.106.55 TOTAL 1 for *na: AT-EUNET-193-80 *na: AT-EUNET-193-81 193.81.83.2 193.81.83.3 TOTAL 2 for *na: AT-EUNET-193-81 *na: FR-EUNET-193-104-193-107 193.104.109.9 193.105.95.2 193.105.95.31 193.106.183.50 193.106.197.2 193.106.229.3 193.107.5.2 193.107.191.72 TOTAL 8 for *na: FR-EUNET-193-104-193-107 *na: RU-RELCOM-193-124-125 193.124.171.67 193.125.193.178 193.125.193.180 193.125.193.226 TOTAL 4 for *na: RU-RELCOM-193-124-125 *na: NO-UNINETT-193-156-193-157 193.156.55.186 193.156.55.200 193.156.55.201 TOTAL 3 for *na: NO-UNINETT-193-156-193-157 *na: UK-ISTEL-193-169 193.169.153.29 193.169.153.68 193.169.153.81 TOTAL 3 for *na: UK-ISTEL-193-169 *na: AT-ACONET-193-170-193-171 193.170.161.222 TOTAL 1 for *na: AT-ACONET-193-170-193-171 *na: DE-DFN-193-174-193-175 193.174.73.75 193.174.73.80 193.175.127.239 193.175.191.132 TOTAL 4 for *na: DE-DFN-193-174-193-175 *na: JO-NIC-193-188-64-95 193.188.84.99 TOTAL 1 for *na: JO-NIC-193-188-64-95 *na: EU-ZZ-193-0-255 193.189.172.2 193.189.182.31 193.189.182.68 193.189.182.77 193.189.182.156 193.189.183.102 193.189.186.33 193.189.191.29 193.189.191.106 193.189.231.194 193.189.250.194 TOTAL 11 for *na: EU-ZZ-193-0-255 *na: EU-IBM-194-196-16 194.196.53.194 194.196.53.210 194.196.119.33 TOTAL 3 for *na: EU-IBM-194-196-16 *na: FR-TELECOM-248-253 193.252.126.150 193.252.127.165 193.252.130.165 193.252.131.155 193.252.131.201 193.252.134.38 193.252.135.250 193.252.136.30 193.252.136.141 193.252.138.55 193.252.139.68 193.252.139.240 193.252.139.252 193.252.141.5 193.252.141.109 193.252.141.125 193.252.141.248 193.252.143.243 193.252.144.48 ... TOTAL 123 for *na: FR-TELECOM-248-253 *na: LT-OMNITEL-960119 194.176.42.34 TOTAL 1 for *na: LT-OMNITEL-960119 *na: IE-IOL-960123 194.125.107.2 TOTAL 1 for *na: IE-IOL-960123 *na: AT-APA-960125 194.232.198.1 194.232.199.193 194.232.209.38 194.232.209.172 194.232.209.205 TOTAL 5 for *na: AT-APA-960125 *na: SE-SUNET-960201 194.47.0.30 194.47.1.11 194.47.16.32 194.47.17.165 194.47.25.8 194.47.27.190 194.47.29.146 194.47.38.61 194.47.47.12 194.47.49.5 194.47.50.19 194.47.55.18 194.47.55.213 194.47.65.11 194.47.81.215 194.47.89.77 194.47.99.36 194.47.99.100 194.47.103.119 ... TOTAL 22 for *na: SE-SUNET-960201 *na: UK-ZZ-193-35-193-39 193.35.223.99 TOTAL 1 for *na: UK-ZZ-193-35-193-39 *na: SE-UMDAC-960209 194.165.229.246 194.165.248.34 TOTAL 2 for *na: SE-UMDAC-960209 *na: IT-UNISOURCE-960215 194.244.1.2 194.244.1.22 TOTAL 2 for *na: IT-UNISOURCE-960215 *na: FR-IWAY-960215 194.98.7.131 194.98.30.130 194.98.51.9 194.98.51.200 194.98.151.241 194.98.199.10 194.98.202.25 194.98.239.200 194.98.239.203 TOTAL 9 for *na: FR-IWAY-960215 *na: UK-JANET-960220 194.81.63.2 194.81.127.12 194.81.127.201 194.83.29.2 194.83.181.128 194.83.181.235 TOTAL 6 for *na: UK-JANET-960220 *na: DE-EUNET-960220 194.174.31.225 194.174.31.226 TOTAL 2 for *na: DE-EUNET-960220 *na: DE-ZZ-960229 194.246.72.7 TOTAL 1 for *na: DE-ZZ-960229 *na: FR-GROLIER-960305 194.117.212.2 TOTAL 1 for *na: FR-GROLIER-960305 *na: IT-INET-960311 194.185.126.40 194.185.253.3 194.185.253.33 TOTAL 3 for *na: IT-INET-960311 *na: DCB-GLOSTRUP 194.192.80.73 194.192.80.92 TOTAL 2 for *na: DCB-GLOSTRUP *na: FR-RENATER-960312 194.254.19.131 194.254.38.66 194.254.38.173 194.254.38.190 194.254.103.55 194.254.109.106 194.254.109.248 194.254.138.99 194.254.173.113 194.254.212.30 194.254.212.102 TOTAL 11 for *na: FR-RENATER-960312 *na: CZ-BOHEMIA-960321 193.165.214.81 TOTAL 1 for *na: CZ-BOHEMIA-960321 *na: EU-ZZ-194-38 194.38.168.242 TOTAL 1 for *na: EU-ZZ-194-38 *na: AT-SPARDAT-960401 194.118.1.9 194.118.1.128 194.118.1.130 194.118.1.170 194.118.1.241 194.118.1.244 194.118.11.2 194.118.17.78 194.118.26.68 194.118.26.74 194.118.26.84 194.118.26.222 194.118.27.113 194.118.28.226 194.118.29.70 194.118.33.1 TOTAL 16 for *na: AT-SPARDAT-960401 *na: ICL-DK 193.89.94.41 193.89.94.61 193.89.94.190 TOTAL 3 for *na: ICL-DK *na: FR-RENATER-940525 194.57.91.200 194.57.91.201 194.57.102.5 194.57.186.3 194.57.186.98 194.57.198.11 194.57.216.30 194.57.216.107 194.57.216.112 TOTAL 9 for *na: FR-RENATER-940525 *na: ES-ENCOMIX-960415 194.143.209.1 194.143.212.75 TOTAL 2 for *na: ES-ENCOMIX-960415 *na: UK-JANET-940418 194.66.183.18 TOTAL 1 for *na: UK-JANET-940418 *na: DK-AZLAN-960423 195.24.2.44 195.24.2.55 195.24.2.60 195.24.2.194 195.24.2.197 195.24.2.198 195.24.2.200 195.24.2.202 195.24.2.203 195.24.2.209 195.24.2.212 195.24.3.10 195.24.3.11 195.24.3.73 195.24.3.76 195.24.3.86 195.24.3.89 195.24.3.91 195.24.3.95 ... TOTAL 90 for *na: DK-AZLAN-960423 *na: HU-DATANET-960426 195.56.17.226 195.56.26.229 195.56.32.125 195.56.48.34 195.56.48.41 195.56.65.90 195.56.65.100 195.56.82.100 195.56.251.75 195.56.251.117 195.56.251.179 195.56.251.200 TOTAL 12 for *na: HU-DATANET-960426 *na: EU-ZZ-960501 193.43.8.1 TOTAL 1 for *na: EU-ZZ-960501 *na: ATOMICSW 194.192.102.5 194.192.102.7 194.192.102.8 194.192.102.38 194.192.102.65 194.192.102.128 194.192.102.130 194.192.102.169 194.192.102.191 194.192.102.194 TOTAL 10 for *na: ATOMICSW *na: PL-TELBANK-960503 195.136.64.177 195.136.78.2 195.136.78.51 195.136.250.200 195.136.250.201 TOTAL 5 for *na: PL-TELBANK-960503 *na: HR-CARNET-960508 193.198.128.82 TOTAL 1 for *na: HR-CARNET-960508 *na: DE-DFN-940920 194.94.79.60 194.94.79.80 194.94.83.60 194.94.127.221 194.95.179.193 194.95.179.196 194.95.179.197 194.95.223.39 TOTAL 8 for *na: DE-DFN-940920 *na: DE-SPACE-960515 195.30.253.4 TOTAL 1 for *na: DE-SPACE-960515 *na: UK-EDEX-960522 193.193.59.13 TOTAL 1 for *na: UK-EDEX-960522 *na: FR-ASI-960510 195.248.24.2 TOTAL 1 for *na: FR-ASI-960510 *na: IE-TELECOM-951109 194.106.137.130 TOTAL 1 for *na: IE-TELECOM-951109 *na: UK-MERCURY-960530 195.44.192.33 195.44.192.246 195.44.193.27 195.44.194.76 195.44.195.69 195.44.195.101 195.44.196.138 195.44.196.178 195.44.196.238 TOTAL 9 for *na: UK-MERCURY-960530 *na: DE-XLINK-94122 194.121.133.1 194.121.225.181 TOTAL 2 for *na: DE-XLINK-94122 *na: UK-ORANGENET-960610 193.218.162.189 TOTAL 1 for *na: UK-ORANGENET-960610 *na: UK-POL-960612 195.92.67.11 195.92.67.13 195.92.67.14 195.92.67.15 195.92.67.16 195.92.68.14 195.92.68.71 195.92.68.72 195.92.68.75 195.92.68.79 195.92.68.108 195.92.68.123 195.92.68.133 195.92.68.139 195.92.68.141 195.92.68.147 195.92.68.165 195.92.68.167 195.92.68.177 ... TOTAL 82 for *na: UK-POL-960612 *na: HU-ELENDER-951108 194.143.246.250 194.143.248.3 TOTAL 2 for *na: HU-ELENDER-951108 *na: FR-RENATER-950531 194.167.80.13 194.167.139.182 194.167.168.51 194.167.250.2 194.167.250.4 194.167.255.154 TOTAL 6 for *na: FR-RENATER-950531 *na: ES-TTD-951020 194.179.64.1 194.179.64.4 194.179.64.11 TOTAL 3 for *na: ES-TTD-951020 *na: UK-PSINET-960624 195.152.83.15 195.152.83.16 195.152.83.18 195.152.83.49 195.152.83.51 195.152.83.56 195.152.154.6 195.152.231.36 195.152.231.39 195.152.231.44 195.152.231.45 195.152.231.47 TOTAL 12 for *na: UK-PSINET-960624 *na: FR-RENATER-951206 194.214.172.161 194.214.172.165 194.214.218.100 194.214.218.110 194.214.237.51 194.214.237.58 194.214.237.74 TOTAL 7 for *na: FR-RENATER-951206 *na: RU-RELCOM-951221 194.220.214.2 TOTAL 1 for *na: RU-RELCOM-951221 *na: ES-TTD-951221 194.224.49.2 194.224.52.4 194.224.52.6 194.224.52.40 194.224.53.3 194.224.53.58 194.224.53.135 194.224.55.25 194.224.55.46 194.224.77.8 194.224.106.36 194.224.126.183 TOTAL 12 for *na: ES-TTD-951221 *na: UK-TECHNOCOM-960626 195.172.34.117 195.172.240.55 TOTAL 2 for *na: UK-TECHNOCOM-960626 *na: UK-ZETNET-960628 194.247.32.17 TOTAL 1 for *na: UK-ZETNET-960628 *na: DE-NETCOLOGNE-960716 194.8.218.141 194.8.218.228 TOTAL 2 for *na: DE-NETCOLOGNE-960716 *na: FR-RENATER-960718 195.220.63.93 TOTAL 1 for *na: FR-RENATER-960718 *na: RO-RNC-960722 193.230.207.226 TOTAL 1 for *na: RO-RNC-960722 *na: UK-BUSINESSNET-960723 194.88.95.9 TOTAL 1 for *na: UK-BUSINESSNET-960723 *na: RU-PTTNET-960801 195.34.16.58 195.34.16.120 195.34.16.123 195.34.17.13 195.34.17.18 195.34.27.39 TOTAL 6 for *na: RU-PTTNET-960801 *na: NL-WIREHUB-960814 195.86.56.10 195.86.56.88 195.86.56.100 195.86.56.104 195.86.56.106 195.86.56.107 195.86.56.110 195.86.56.130 195.86.56.134 195.86.123.45 195.86.123.142 195.86.123.155 195.86.123.186 TOTAL 13 for *na: NL-WIREHUB-960814 *na: SK-PUBNET-960819 195.98.23.4 TOTAL 1 for *na: SK-PUBNET-960819 *na: UK-U-NET-960819 195.102.32.28 195.102.33.45 195.102.33.54 195.102.33.194 195.102.33.207 195.102.34.10 195.102.34.17 195.102.34.18 195.102.34.37 195.102.34.49 195.102.191.81 TOTAL 11 for *na: UK-U-NET-960819 *na: SI-ARNES-960301 194.249.3.69 194.249.3.83 194.249.3.99 194.249.3.147 194.249.4.211 194.249.5.8 194.249.5.96 194.249.6.201 194.249.9.22 TOTAL 9 for *na: SI-ARNES-960301 *na: SK-NAPRI-960827 195.146.16.2 195.146.16.3 TOTAL 2 for *na: SK-NAPRI-960827 *na: FR-ISDNET-960827 195.154.0.131 195.154.91.34 195.154.96.2 195.154.97.1 195.154.97.2 195.154.97.5 195.154.97.66 195.154.97.121 195.154.100.1 195.154.100.147 195.154.100.163 195.154.129.227 195.154.129.228 195.154.132.130 195.154.132.132 195.154.132.133 195.154.132.134 195.154.132.135 195.154.132.137 ... TOTAL 25 for *na: FR-ISDNET-960827 *na: AT-PLUS-960912 194.112.200.194 TOTAL 1 for *na: AT-PLUS-960912 *na: RU-PETERLINK-960919 195.242.9.12 TOTAL 1 for *na: RU-PETERLINK-960919 *na: IT-ARCHWAY-961008 195.96.140.10 195.96.140.49 195.96.140.100 195.96.140.104 TOTAL 4 for *na: IT-ARCHWAY-961008 *na: IT-THEBRAIN-961010 195.216.136.130 195.216.136.151 TOTAL 2 for *na: IT-THEBRAIN-961010 *na: SK-NET-961016 195.12.135.66 TOTAL 1 for *na: SK-NET-961016 *na: FR-RENATER-961021 195.221.234.122 TOTAL 1 for *na: FR-RENATER-961021 *na: BG-NAT-961022 194.12.228.65 194.12.228.151 194.12.229.44 TOTAL 3 for *na: BG-NAT-961022 *na: MK-MPT-961024 195.26.129.66 TOTAL 1 for *na: MK-MPT-961024 *na: DE-INX-961101 195.21.6.18 195.21.169.2 195.21.207.53 195.21.207.102 TOTAL 4 for *na: DE-INX-961101 *na: PT-IPGLOBAL-961101 195.23.2.4 195.23.3.10 195.23.69.65 195.23.69.67 195.23.69.69 195.23.72.10 195.23.72.36 195.23.86.13 195.23.86.23 195.23.96.132 195.23.96.251 195.23.98.83 195.23.120.16 TOTAL 13 for *na: PT-IPGLOBAL-961101 *na: LV-NEONET-961107 195.62.139.195 195.62.139.205 TOTAL 2 for *na: LV-NEONET-961107 *na: CH-VIRTUAL-961107 195.66.138.17 TOTAL 1 for *na: CH-VIRTUAL-961107 *na: DE-MEDIAWAYS-960423 193.189.231.194 193.189.250.194 TOTAL 2 for *na: DE-MEDIAWAYS-960423 *na: IT-UNINET-961119 195.94.135.202 195.94.144.190 TOTAL 2 for *na: IT-UNINET-961119 *na: CZ-TERMINAL-961202 195.70.157.29 TOTAL 1 for *na: CZ-TERMINAL-961202 *na: IT-IUNET-961209 195.45.3.146 195.45.37.42 195.45.60.193 TOTAL 3 for *na: IT-IUNET-961209 *na: CH-NOVANET-961209 195.162.130.21 TOTAL 1 for *na: CH-NOVANET-961209 *na: CZ-PVTNET-961210 195.47.116.5 195.47.116.26 195.47.116.34 TOTAL 3 for *na: CZ-PVTNET-961210 *na: ES-TTD--960610-OESTE 195.76.178.35 195.76.235.6 195.76.235.32 195.76.251.210 TOTAL 4 for *na: ES-TTD--960610-OESTE *na: ES-TTD-961219-SUR 195.53.5.2 195.53.27.64 195.53.58.2 195.53.60.2 195.53.67.165 195.53.79.2 195.53.80.2 195.53.81.104 195.53.81.158 195.53.98.168 195.53.99.3 195.53.99.114 195.53.99.136 195.53.99.202 195.53.201.242 195.53.201.247 TOTAL 16 for *na: ES-TTD-961219-SUR *na: ES-TTD-961219-NORTE 195.55.3.2 195.55.3.60 195.55.5.5 195.55.5.31 195.55.8.5 195.55.8.51 195.55.170.15 195.55.198.1 195.55.198.14 TOTAL 9 for *na: ES-TTD-961219-NORTE *na: ES-TTD-961219-LEVANTE 195.57.11.242 195.57.62.243 195.57.188.2 195.57.188.3 195.57.188.74 195.57.190.5 195.57.208.34 195.57.208.35 195.57.221.34 195.57.221.51 195.57.246.131 TOTAL 11 for *na: ES-TTD-961219-LEVANTE *na: CH-SWISSONLINE-970123 195.24.73.187 195.24.82.215 195.24.87.104 195.24.91.129 TOTAL 4 for *na: CH-SWISSONLINE-970123 *na: DE-MEDIAWAYS-970127 195.71.128.14 195.71.142.181 TOTAL 2 for *na: DE-MEDIAWAYS-970127 *na: RU-MSU-940712 194.67.161.1 TOTAL 1 for *na: RU-MSU-940712 *na: RU-ZENON-970131 195.2.84.75 TOTAL 1 for *na: RU-ZENON-970131 *na: EU-ZZ-193-193-0-63 193.194.63.82 193.194.63.83 TOTAL 2 for *na: EU-ZZ-193-193-0-63 *na: EU-ZZ-960306 193.218.205.10 193.218.205.42 193.218.210.46 193.218.210.188 193.218.216.10 TOTAL 5 for *na: EU-ZZ-960306 *na: UK-BUSINESSNET-970212 195.50.65.18 195.50.65.19 195.50.65.22 195.50.65.23 195.50.94.16 195.50.101.198 195.50.104.192 195.50.104.211 195.50.104.233 195.50.104.250 195.50.105.18 195.50.105.107 195.50.105.188 195.50.105.189 195.50.106.94 195.50.106.124 195.50.107.124 195.50.107.178 195.50.107.218 TOTAL 19 for *na: UK-BUSINESSNET-970212 *na: FR-SIRIS-951227 194.183.202.253 TOTAL 1 for *na: FR-SIRIS-951227 *na: FI-EUNET-950112 193.64.151.161 193.64.151.162 193.64.151.164 193.64.151.209 193.64.151.228 193.64.151.229 193.64.151.230 193.65.248.170 193.65.248.178 TOTAL 9 for *na: FI-EUNET-950112 *na: UK-NETKONECT-960307 194.164.173.76 TOTAL 1 for *na: UK-NETKONECT-960307 *na: UK-ICLNET-951207 194.176.200.49 TOTAL 1 for *na: UK-ICLNET-951207 *na: SE-XPRESSONLINE-970225 195.162.69.13 195.162.69.14 195.162.69.73 195.162.69.96 195.162.69.98 TOTAL 5 for *na: SE-XPRESSONLINE-970225 *na: UK-PSINET-970227 195.153.32.130 195.153.64.65 195.153.222.65 TOTAL 3 for *na: UK-PSINET-970227 *na: IUNET-DYNA-1 195.45.3.146 TOTAL 1 for *na: IUNET-DYNA-1 *na: BE-UNISOURCE-970303 195.95.4.2 195.95.4.11 195.95.19.18 TOTAL 3 for *na: BE-UNISOURCE-970303 *na: EE-ESTPAK-951219 194.126.117.18 TOTAL 1 for *na: EE-ESTPAK-951219 *na: NL-IXE-970312 195.81.13.1 195.81.23.10 TOTAL 2 for *na: NL-IXE-970312 *na: ES-SARENET-960122 194.30.73.217 194.30.88.137 TOTAL 2 for *na: ES-SARENET-960122 *na: FI-CLINET-961004 194.100.19.130 194.100.45.250 TOTAL 2 for *na: FI-CLINET-961004 *na: DK-SEKTORNET-970320 195.181.6.140 195.181.6.153 195.181.44.4 195.181.220.130 TOTAL 4 for *na: DK-SEKTORNET-970320 *na: IE-INDIGO-951211 194.125.207.97 194.125.207.134 194.125.207.154 TOTAL 3 for *na: IE-INDIGO-951211 *na: UA-GU-970404 195.123.8.10 195.123.17.1 195.123.18.1 195.123.18.97 195.123.40.130 195.123.40.132 195.123.254.205 TOTAL 7 for *na: UA-GU-970404 *na: SI-TELEKOM-960419 193.189.172.2 193.189.182.31 193.189.182.68 193.189.182.77 193.189.182.156 193.189.183.102 193.189.186.33 193.189.191.29 193.189.191.106 TOTAL 9 for *na: SI-TELEKOM-960419 *na: AT-NEWMEDIA-970411 195.12.192.7 195.12.192.98 195.12.192.99 195.12.192.100 195.12.193.31 195.12.193.209 TOTAL 6 for *na: AT-NEWMEDIA-970411 *na: EE-ESTNET-970416 195.50.193.66 195.50.193.163 TOTAL 2 for *na: EE-ESTNET-970416 *na: UA-TM-970417 195.66.205.1 195.66.205.5 TOTAL 2 for *na: UA-TM-970417 *na: AT-ATNET-951212 194.152.163.17 TOTAL 1 for *na: AT-ATNET-951212 *na: EU-ATT-970402 195.121.1.34 195.121.1.66 195.121.6.37 195.121.6.51 195.121.6.57 195.121.6.59 195.121.6.61 195.121.6.98 195.121.6.99 195.121.6.100 195.121.6.143 195.121.6.144 195.121.6.163 195.121.6.196 195.121.8.2 195.121.9.89 195.121.9.115 195.121.18.16 195.121.18.109 ... TOTAL 91 for *na: EU-ATT-970402 *na: FR-SKY-960103 194.6.151.205 TOTAL 1 for *na: FR-SKY-960103 *na: IL-NETVISION-970428 62.0.128.40 62.0.128.86 62.0.128.107 62.0.128.138 62.0.145.135 62.0.145.139 62.0.145.232 62.0.146.8 62.0.146.10 62.0.146.89 62.0.149.78 62.0.149.100 62.0.152.1 62.0.153.19 62.0.153.39 62.0.153.194 62.0.154.12 62.0.154.211 62.0.154.235 ... TOTAL 30 for *na: IL-NETVISION-970428 *na: SPARDAT-NET-3 194.118.1.9 194.118.1.128 194.118.1.130 194.118.1.170 194.118.1.241 194.118.1.244 TOTAL 6 for *na: SPARDAT-NET-3 *na: SPARDAT-NET-10 194.118.26.68 194.118.26.74 194.118.26.84 194.118.26.222 TOTAL 4 for *na: SPARDAT-NET-10 *na: FI-KOLUMBUS-960904 193.229.72.76 193.229.80.98 193.229.99.10 193.229.129.183 193.229.159.3 193.229.159.4 193.229.163.54 193.229.164.163 193.229.165.38 193.229.204.246 193.229.226.156 TOTAL 11 for *na: FI-KOLUMBUS-960904 *na: FR-OLEANE-950711 194.2.128.1 194.2.128.2 194.2.128.4 194.2.128.6 194.2.128.16 194.2.128.27 194.2.128.247 194.2.128.248 TOTAL 8 for *na: FR-OLEANE-950711 *na: EE-UNINET-970506 194.204.43.159 TOTAL 1 for *na: EE-UNINET-970506 *na: UK-POL-970506 62.136.65.189 62.136.66.52 62.136.67.39 62.136.67.48 62.136.67.216 62.136.69.148 62.136.69.189 62.136.70.76 62.136.73.122 62.136.74.24 62.136.74.167 62.136.74.170 62.136.74.193 62.136.76.25 62.136.76.220 62.136.76.252 62.136.77.21 62.136.77.180 62.136.77.184 ... TOTAL 49 for *na: UK-POL-970506 *na: FUTURNET 195.53.98.168 195.53.99.3 195.53.99.114 195.53.99.136 195.53.99.202 TOTAL 5 for *na: FUTURNET *na: BSANTANDER 195.53.80.2 195.53.81.104 195.53.81.158 TOTAL 3 for *na: BSANTANDER *na: MSC 195.53.79.2 TOTAL 1 for *na: MSC *na: NACOM 195.53.67.165 TOTAL 1 for *na: NACOM *na: HPR2 195.53.60.2 TOTAL 1 for *na: HPR2 *na: ALHSYS 195.53.58.2 TOTAL 1 for *na: ALHSYS *na: RGC 195.53.27.64 TOTAL 1 for *na: RGC *na: PICMATIC 195.53.5.2 TOTAL 1 for *na: PICMATIC *na: PONFPARK 195.55.8.5 195.55.8.51 TOTAL 2 for *na: PONFPARK *na: IPONET 195.55.5.5 195.55.5.31 TOTAL 2 for *na: IPONET *na: GRAMA 195.55.3.2 195.55.3.60 TOTAL 2 for *na: GRAMA *na: DIPBADAJOZ 195.57.11.242 TOTAL 1 for *na: DIPBADAJOZ *na: CH-UNISOURCE-970526 193.5.175.194 TOTAL 1 for *na: CH-UNISOURCE-970526 *na: FR-NETSAT-970526 195.10.61.3 195.10.62.5 195.10.62.8 195.10.62.10 195.10.62.12 195.10.62.14 195.10.62.15 195.10.62.18 195.10.62.19 195.10.62.21 TOTAL 10 for *na: FR-NETSAT-970526 *na: DE-MEDIAWAYS-970527 62.52.135.107 62.52.135.119 62.52.152.34 62.52.154.157 62.52.155.89 62.52.159.217 62.52.179.13 62.52.179.82 62.52.179.92 62.52.179.115 62.52.249.52 62.52.249.116 TOTAL 12 for *na: DE-MEDIAWAYS-970527 *na: CH-UNISOURCE-970528 193.135.153.196 193.135.163.5 193.135.163.186 193.135.253.210 TOTAL 4 for *na: CH-UNISOURCE-970528 *na: CH-UNISOURCE-970528 193.247.71.67 TOTAL 1 for *na: CH-UNISOURCE-970528 *na: DK-ZZ-193-162-163 193.162.16.5 193.162.16.34 193.162.16.35 193.162.17.225 193.162.38.9 193.162.145.64 193.162.145.130 193.162.145.158 193.162.145.229 193.162.145.252 193.162.146.9 193.162.146.35 193.162.146.43 193.162.155.2 193.162.155.118 193.162.155.134 193.162.155.138 193.162.155.166 193.162.155.238 ... TOTAL 39 for *na: DK-ZZ-193-162-163 *na: SK-ZZ-194-1-128-255 194.1.128.2 194.1.128.5 194.1.128.10 194.1.128.14 194.1.128.27 194.1.128.40 194.1.133.42 TOTAL 7 for *na: SK-ZZ-194-1-128-255 *na: RU-RINET-970530 195.54.215.163 TOTAL 1 for *na: RU-RINET-970530 *na: SE-SUNET-970602 193.180.21.2 193.180.21.10 193.180.23.4 193.180.23.167 193.180.23.230 193.180.23.236 193.180.34.38 193.180.36.77 193.180.36.155 193.180.36.170 193.180.36.177 193.180.45.72 193.180.58.7 193.180.58.22 193.180.58.254 193.180.65.151 193.180.82.165 193.180.84.106 193.180.104.9 ... TOTAL 75 for *na: SE-SUNET-970602 *na: SE-SUNET-970602 193.234.191.242 193.234.191.244 193.234.247.10 193.235.16.226 193.235.17.3 193.235.17.33 193.235.21.40 193.235.48.53 193.235.76.171 193.235.87.109 193.235.88.87 193.235.89.1 193.235.89.27 193.235.89.122 193.235.95.250 193.235.118.30 193.235.118.37 193.235.223.10 193.235.229.100 TOTAL 19 for *na: SE-SUNET-970602 *na: SE-SUNET-970602 194.14.81.162 194.14.81.174 194.14.81.175 194.14.81.181 194.14.81.182 194.14.98.17 194.14.189.252 194.14.189.254 194.14.204.80 194.14.204.107 194.14.204.112 TOTAL 11 for *na: SE-SUNET-970602 *na: SE-SUNET-970602 194.68.13.18 194.68.13.19 TOTAL 2 for *na: SE-SUNET-970602 *na: SE-SUNET-970602 194.71.15.242 194.71.106.1 194.71.214.2 194.71.247.47 TOTAL 4 for *na: SE-SUNET-970602 *na: SE-SUNET-970602 194.103.185.80 194.103.191.1 194.103.205.14 194.103.205.20 194.103.205.100 TOTAL 5 for *na: SE-SUNET-970602 *na: SE-SUNET-970602 194.132.131.19 194.132.135.97 TOTAL 2 for *na: SE-SUNET-970602 *na: NO-POWERTECH-970603 195.159.94.50 195.159.99.10 TOTAL 2 for *na: NO-POWERTECH-970603 *na: NO-TELIANET-970603 195.18.205.50 195.18.205.51 195.18.205.52 195.18.205.53 TOTAL 4 for *na: NO-TELIANET-970603 *na: EE-MATK 194.126.117.18 TOTAL 1 for *na: EE-MATK *na: SE-ENGELHOLM-970612 195.216.32.194 195.216.34.1 195.216.34.8 195.216.45.20 195.216.45.122 TOTAL 5 for *na: SE-ENGELHOLM-970612 *na: TR-RAKSNET-960513 195.244.34.99 195.244.37.1 TOTAL 2 for *na: TR-RAKSNET-960513 *na: DK-KOMMUNEDATA-970626 195.50.58.3 TOTAL 1 for *na: DK-KOMMUNEDATA-970626 *na: AT-TELEKOM-970627 195.3.120.97 195.3.126.124 195.3.126.125 195.3.127.220 TOTAL 4 for *na: AT-TELEKOM-970627 *na: HU-INTERWARE-970704 195.70.54.241 TOTAL 1 for *na: HU-INTERWARE-970704 *na: UK-COMPULINK-951004 194.153.0.18 194.153.0.51 194.153.0.82 194.153.0.117 194.153.0.125 194.153.0.126 194.153.1.10 194.153.25.45 194.153.26.24 194.153.26.33 194.153.26.61 194.153.26.68 194.153.26.175 194.153.26.204 194.153.28.70 194.153.31.26 TOTAL 16 for *na: UK-COMPULINK-951004 *na: SE-SWIPNET-970130 193.12.6.130 193.12.6.144 193.12.6.146 193.12.198.82 193.12.198.98 193.12.205.1 193.12.209.1 193.12.209.37 193.12.243.4 193.12.243.40 193.12.243.59 193.12.243.62 193.12.243.75 193.12.243.104 193.12.243.150 193.12.255.26 193.12.255.253 193.13.14.38 193.13.15.2 ... TOTAL 243 for *na: SE-SWIPNET-970130 *na: NO-EAB-970716 195.134.43.2 195.134.44.10 195.134.44.132 TOTAL 3 for *na: NO-EAB-970716 *na: DE-KNIPP-970721 195.138.34.161 TOTAL 1 for *na: DE-KNIPP-970721 *na: DE-COSMIK-970728 195.182.40.1 195.182.40.218 TOTAL 2 for *na: DE-COSMIK-970728 *na: TR-ZZ-960827 195.142.1.3 195.142.1.5 195.142.148.200 195.142.234.169 TOTAL 4 for *na: TR-ZZ-960827 *na: EU-ZZ-194-93 194.93.79.84 194.93.79.91 194.93.128.1 194.93.128.2 194.93.128.3 194.93.128.28 194.93.133.1 194.93.134.3 194.93.134.119 194.93.154.49 TOTAL 10 for *na: EU-ZZ-194-93 *na: TR-ZZ-950223 194.27.5.46 TOTAL 1 for *na: TR-ZZ-950223 *na: DK-TJANTIK-970805 195.184.100.130 195.184.101.100 195.184.103.254 TOTAL 3 for *na: DK-TJANTIK-970805 *na: PL-NASK-970805 195.187.243.10 195.187.244.6 195.187.245.51 TOTAL 3 for *na: PL-NASK-970805 *na: DK-EUROCONNECT-970813 195.184.42.162 195.184.43.196 195.184.44.227 195.184.44.228 TOTAL 4 for *na: DK-EUROCONNECT-970813 *na: IT-FLASHNET-970814 195.191.1.73 195.191.1.91 195.191.2.13 195.191.2.185 195.191.4.85 195.191.80.59 195.191.105.150 195.191.105.226 TOTAL 8 for *na: IT-FLASHNET-970814 *na: FR-PRESSIMAGE-970826 194.150.34.223 TOTAL 1 for *na: FR-PRESSIMAGE-970826 *na: DE-KAMP-970827 195.62.99.200 195.62.120.231 TOTAL 2 for *na: DE-KAMP-970827 *na: FR-SATELNET-970520 195.28.196.66 TOTAL 1 for *na: FR-SATELNET-970520 *na: DE-NETCOLOGNE-970911 195.14.233.180 TOTAL 1 for *na: DE-NETCOLOGNE-970911 *na: FR-OLEANE-961101 195.25.216.129 195.25.238.136 TOTAL 2 for *na: FR-OLEANE-961101 *na: DE-IPF-970924 195.211.29.85 195.211.35.214 195.211.36.15 195.211.46.232 195.211.48.1 195.211.64.68 195.211.86.235 195.211.88.65 195.211.123.106 195.211.133.31 195.211.151.202 195.211.201.41 195.211.204.211 195.211.208.236 195.211.211.20 195.211.211.37 195.211.212.247 TOTAL 17 for *na: DE-IPF-970924 *na: EU-INFONET-970925 195.213.119.7 TOTAL 1 for *na: EU-INFONET-970925 *na: CZ-CZNET-971003 194.228.21.131 194.228.21.151 194.228.41.67 194.228.42.10 194.228.54.19 194.228.139.12 194.228.147.131 TOTAL 7 for *na: CZ-CZNET-971003 *na: DE-POP-971014 195.222.215.39 TOTAL 1 for *na: DE-POP-971014 *na: DE-INET-971014 195.34.161.30 TOTAL 1 for *na: DE-INET-971014 *na: ECRC-FFM2-NET 195.27.83.78 TOTAL 1 for *na: ECRC-FFM2-NET *na: DE-ECRC-961107 195.27.83.78 195.27.221.2 195.27.221.3 195.27.221.8 195.27.241.3 TOTAL 5 for *na: DE-ECRC-961107 *na: CH-MC-971031 195.130.185.43 TOTAL 1 for *na: CH-MC-971031 *na: SE-BAHNHOF-971105 195.178.163.100 195.178.163.102 TOTAL 2 for *na: SE-BAHNHOF-971105 *na: UK-DIAMOND-971110 195.182.182.2 TOTAL 1 for *na: UK-DIAMOND-971110 *na: UK-GLOBAL-971112 195.147.27.179 195.147.129.224 195.147.130.195 195.147.132.3 195.147.134.7 195.147.134.41 195.147.134.65 195.147.135.136 195.147.135.222 195.147.136.150 195.147.136.204 195.147.136.236 195.147.139.68 195.147.139.183 195.147.140.23 195.147.140.77 195.147.140.180 195.147.141.1 195.147.142.218 ... TOTAL 51 for *na: UK-GLOBAL-971112 *na: FR-CEGETEL-970326 195.115.64.201 TOTAL 1 for *na: FR-CEGETEL-970326 *na: DK-EUROCONNECT-971126 195.97.129.226 195.97.129.234 195.97.140.58 195.97.145.102 195.97.150.238 195.97.183.202 195.97.183.204 TOTAL 7 for *na: DK-EUROCONNECT-971126 *na: IT-ATSLINK-971128 195.62.230.106 TOTAL 1 for *na: IT-ATSLINK-971128 *na: ES-TTD-971208-SUR 195.235.56.237 195.235.80.163 195.235.114.46 195.235.115.70 195.235.115.143 195.235.115.243 195.235.116.144 195.235.116.152 195.235.117.4 195.235.117.21 195.235.118.55 195.235.118.113 195.235.118.242 195.235.119.88 195.235.119.160 195.235.121.68 195.235.121.76 195.235.121.80 195.235.122.104 ... TOTAL 23 for *na: ES-TTD-971208-SUR *na: FR-GLCONSULTANTS-971210 195.110.230.3 195.110.230.13 TOTAL 2 for *na: FR-GLCONSULTANTS-971210 *na: RU-SOVAM-971210 195.239.46.178 195.239.67.65 195.239.68.203 195.239.70.67 195.239.70.70 195.239.85.24 195.239.88.65 195.239.134.13 195.239.208.3 195.239.208.100 195.239.214.80 TOTAL 11 for *na: RU-SOVAM-971210 *na: GTO-OM-BLK01 206.49.110.246 TOTAL 1 for *na: GTO-OM-BLK01 *na: GTO-OM-BLK01 206.49.109.5 206.49.109.10 206.49.109.154 TOTAL 3 for *na: GTO-OM-BLK01 *na: GTO-OM-BLK01 206.49.101.5 206.49.101.6 206.49.101.40 206.49.101.129 TOTAL 4 for *na: GTO-OM-BLK01 *na: GTO-OM-BLK01 206.49.102.108 TOTAL 1 for *na: GTO-OM-BLK01 *na: PLANETENDK 195.215.34.105 TOTAL 1 for *na: PLANETENDK *na: MILLERFREEMANDK 195.215.34.82 TOTAL 1 for *na: MILLERFREEMANDK *na: BKIDK 195.215.34.194 TOTAL 1 for *na: BKIDK *na: A2Z-NETDK 195.215.36.2 195.215.36.3 195.215.36.4 195.215.36.5 195.215.36.18 195.215.36.19 195.215.36.20 195.215.36.36 195.215.36.40 TOTAL 9 for *na: A2Z-NETDK *na: HH-INDUSTRIDK 195.215.36.98 TOTAL 1 for *na: HH-INDUSTRIDK *na: FSRDK 195.215.36.230 TOTAL 1 for *na: FSRDK *na: NOVOPANDK 195.215.37.148 TOTAL 1 for *na: NOVOPANDK *na: BONDOSVANEDK 195.215.38.130 195.215.38.131 TOTAL 2 for *na: BONDOSVANEDK *na: FR-NORMANDNET-980114 195.7.97.109 195.7.98.16 195.7.102.1 TOTAL 3 for *na: FR-NORMANDNET-980114 *na: BE-INET-194-7 194.7.170.162 194.7.182.210 TOTAL 2 for *na: BE-INET-194-7 *na: LACTOSANDK 195.215.29.187 TOTAL 1 for *na: LACTOSANDK *na: UK-CINERGY-980120 195.28.167.170 TOTAL 1 for *na: UK-CINERGY-980120 *na: B-DATADK 195.215.52.130 TOTAL 1 for *na: B-DATADK *na: AVNDK 195.215.53.2 TOTAL 1 for *na: AVNDK *na: FR-IMAGINET-960610 195.68.29.214 195.68.29.217 195.68.35.153 195.68.36.20 TOTAL 4 for *na: FR-IMAGINET-960610 *na: EU-IBM-139-92-16 139.92.4.24 139.92.4.52 139.92.4.156 139.92.4.196 139.92.4.224 139.92.8.169 139.92.20.142 139.92.30.35 139.92.30.251 139.92.34.81 139.92.34.235 139.92.49.247 139.92.57.70 139.92.64.151 139.92.66.135 139.92.68.26 139.92.68.38 139.92.68.40 139.92.68.48 ... TOTAL 58 for *na: EU-IBM-139-92-16 *na: RU-MAXNET-980123 195.112.97.17 195.112.97.68 TOTAL 2 for *na: RU-MAXNET-980123 *na: LV-TELEKOM-980126 195.13.147.140 TOTAL 1 for *na: LV-TELEKOM-980126 *na: HU-INTERNET-980122 193.68.35.142 TOTAL 1 for *na: HU-INTERNET-980122 *na: NO-DAXNET-950315 193.216.27.130 TOTAL 1 for *na: NO-DAXNET-950315 *na: SE-UTFORS-970825 195.58.99.94 195.58.99.116 195.58.99.117 TOTAL 3 for *na: SE-UTFORS-970825 *na: DE-OPENNET-980127 195.202.112.21 TOTAL 1 for *na: DE-OPENNET-980127 *na: DAN-DOORSDK 195.215.54.130 195.215.54.145 TOTAL 2 for *na: DAN-DOORSDK *na: DE-BERGSKE 195.215.54.194 195.215.54.195 TOTAL 2 for *na: DE-BERGSKE *na: BONGBJOERNBAKDK 195.215.55.251 TOTAL 1 for *na: BONGBJOERNBAKDK *na: COMPAQDK 195.215.56.44 TOTAL 1 for *na: COMPAQDK *na: QUARKDK 195.215.56.66 TOTAL 1 for *na: QUARKDK *na: BR-MARINECOM 195.215.55.145 TOTAL 1 for *na: BR-MARINECOM *na: MA-ONPT-970523 194.204.224.75 TOTAL 1 for *na: MA-ONPT-970523 *na: VLKBRNO-CZ 194.212.137.1 TOTAL 1 for *na: VLKBRNO-CZ *na: STALDINDUSTRI 194.192.87.4 TOTAL 1 for *na: STALDINDUSTRI *na: PSEDK 195.215.56.90 TOTAL 1 for *na: PSEDK *na: POINT4-NET 194.205.28.15 TOTAL 1 for *na: POINT4-NET *na: SPROUTMATADOR 194.192.206.214 TOTAL 1 for *na: SPROUTMATADOR *na: FDC 195.215.58.67 TOTAL 1 for *na: FDC *na: SCANTICON-KOLDINGDK 195.215.57.194 TOTAL 1 for *na: SCANTICON-KOLDINGDK *na: MEDIBASE 195.215.58.34 TOTAL 1 for *na: MEDIBASE *na: INFASE 195.57.246.131 TOTAL 1 for *na: INFASE *na: NOLADK 195.215.58.212 TOTAL 1 for *na: NOLADK *na: HS-TARMDK 195.215.59.130 TOTAL 1 for *na: HS-TARMDK *na: FSPDK 195.215.59.35 TOTAL 1 for *na: FSPDK *na: FRIFERIEDK 195.215.59.2 TOTAL 1 for *na: FRIFERIEDK *na: MARITIMADK 195.215.60.2 195.215.60.66 TOTAL 2 for *na: MARITIMADK *na: OPTION-INTERNATIONAL-NV-NET 194.7.170.162 TOTAL 1 for *na: OPTION-INTERNATIONAL-NV-NET *na: SCANBECHCOM 195.215.59.98 TOTAL 1 for *na: SCANBECHCOM *na: RU-COMSTAR-980226 212.248.0.3 TOTAL 1 for *na: RU-COMSTAR-980226 *na: FR-INTERNEXT-951127 194.79.133.72 TOTAL 1 for *na: FR-INTERNEXT-951127 *na: FR-INTERNEXT-970523 195.5.196.47 TOTAL 1 for *na: FR-INTERNEXT-970523 *na: BOGPADK 195.215.61.18 195.215.61.19 TOTAL 2 for *na: BOGPADK *na: TITGEMEYERDK 193.89.47.2 TOTAL 1 for *na: TITGEMEYERDK *na: BG-SPNET-980310 212.50.2.193 212.50.25.8 TOTAL 2 for *na: BG-SPNET-980310 *na: DK-WEB-DENMARK-970218 195.78.67.177 195.78.67.189 195.78.67.213 195.78.67.229 195.78.67.249 195.78.67.250 195.78.74.74 195.78.74.89 195.78.74.116 195.78.74.120 195.78.74.122 195.78.75.88 195.78.75.89 195.78.75.90 195.78.75.245 195.78.76.37 195.78.76.41 195.78.76.42 195.78.76.49 ... TOTAL 47 for *na: DK-WEB-DENMARK-970218 *na: SE-LEISSNER-980312 212.3.5.124 212.3.6.130 TOTAL 2 for *na: SE-LEISSNER-980312 *na: SASAIRLINEDK 194.192.22.2 194.192.22.9 194.192.22.11 194.192.23.1 TOTAL 4 for *na: SASAIRLINEDK *na: DELTATC 194.192.70.10 TOTAL 1 for *na: DELTATC *na: BLANET 194.192.98.129 TOTAL 1 for *na: BLANET *na: GJNET 194.192.94.2 TOTAL 1 for *na: GJNET *na: ROYGRE 193.163.210.20 193.163.210.58 TOTAL 2 for *na: ROYGRE *na: ESBJERG-KOMMUNE 193.163.58.20 193.163.58.23 193.163.58.30 TOTAL 3 for *na: ESBJERG-KOMMUNE *na: AT-CYBERTRON-980316 212.236.3.195 212.236.3.200 TOTAL 2 for *na: AT-CYBERTRON-980316 *na: ABI-GROUPDK 193.88.73.18 TOTAL 1 for *na: ABI-GROUPDK *na: TR-SUPERONLINE-980318 195.33.204.6 195.33.204.70 195.33.205.182 195.33.205.186 195.33.205.195 195.33.206.46 195.33.206.178 195.33.218.108 195.33.219.124 195.33.219.188 195.33.220.38 195.33.221.95 195.33.222.164 TOTAL 13 for *na: TR-SUPERONLINE-980318 *na: IT-IUNET-930901 193.70.1.2 193.70.1.4 193.70.6.3 193.70.16.1 193.70.16.19 193.70.26.72 193.70.27.6 193.70.31.2 193.70.31.45 193.70.31.101 193.70.41.6 193.70.50.231 193.70.60.3 193.70.88.2 193.70.96.18 193.70.96.81 193.70.96.130 193.70.121.186 193.70.162.66 ... TOTAL 25 for *na: IT-IUNET-930901 *na: IT-IUNET-940426 193.76.81.227 193.76.126.2 193.76.126.138 193.76.127.2 193.76.127.5 193.76.127.8 193.76.127.10 193.76.148.71 193.76.217.6 193.76.217.7 193.76.224.2 193.76.224.93 193.76.248.2 TOTAL 13 for *na: IT-IUNET-940426 *na: TR-COMNET-980319 212.15.30.4 212.15.30.72 TOTAL 2 for *na: TR-COMNET-980319 *na: FR-CYBERCABLE-980319 212.198.0.66 212.198.0.67 212.198.1.66 212.198.6.59 212.198.15.65 212.198.18.209 212.198.21.77 212.198.30.93 212.198.33.49 212.198.34.17 212.198.35.10 212.198.38.88 212.198.45.111 212.198.45.180 212.198.48.118 212.198.68.17 212.198.104.88 212.198.104.175 212.198.107.153 ... TOTAL 31 for *na: FR-CYBERCABLE-980319 *na: EU-ATT-961118 195.33.64.3 195.33.64.148 195.33.64.149 TOTAL 3 for *na: EU-ATT-961118 *na: DE-GINKO-980324 212.202.67.93 212.202.67.96 212.202.69.49 TOTAL 3 for *na: DE-GINKO-980324 *na: TR-HURRIYET-980327 212.31.1.1 TOTAL 1 for *na: TR-HURRIYET-980327 *na: NET-PT-EUNET-BB 193.126.4.65 193.126.4.67 193.126.8.65 TOTAL 3 for *na: NET-PT-EUNET-BB *na: NET-PT-MINEDU 193.126.18.189 TOTAL 1 for *na: NET-PT-MINEDU *na: NET-PT-PARLAMENTO 193.126.90.1 TOTAL 1 for *na: NET-PT-PARLAMENTO *na: ATOMICSW 194.192.211.222 TOTAL 1 for *na: ATOMICSW *na: SE-DATAPHONE-980331 212.37.6.225 TOTAL 1 for *na: SE-DATAPHONE-980331 *na: TSAI 195.53.201.242 195.53.201.247 TOTAL 2 for *na: TSAI *na: DK-TELIANET-960206 194.19.134.14 194.19.134.15 194.19.134.17 194.19.134.18 194.19.134.19 194.19.134.22 194.19.134.23 194.19.134.29 194.19.179.17 194.19.179.34 194.19.179.35 194.19.179.36 TOTAL 12 for *na: DK-TELIANET-960206 *na: LV-TELIANET-960206 194.19.240.46 TOTAL 1 for *na: LV-TELIANET-960206 *na: DK-TELIANET-960319 194.255.32.66 194.255.32.73 194.255.32.89 194.255.32.90 194.255.32.174 TOTAL 5 for *na: DK-TELIANET-960319 *na: LT-TELIANET-971007 195.12.164.250 TOTAL 1 for *na: LT-TELIANET-971007 *na: SE-TELIANET-970121 195.67.156.39 195.67.156.52 195.67.156.132 195.67.156.241 195.67.157.23 195.67.157.101 195.67.157.164 195.67.157.241 195.67.157.243 195.67.188.67 195.67.188.150 195.67.188.183 195.67.188.209 195.67.188.235 195.67.188.241 195.67.188.243 195.67.189.11 195.67.189.34 195.67.189.74 ... TOTAL 109 for *na: SE-TELIANET-970121 *na: SE-TELIANET-970521 62.20.78.242 62.20.78.253 62.20.79.4 62.20.79.5 62.20.128.15 62.20.132.55 62.20.132.84 62.20.132.85 62.20.132.90 62.20.132.127 62.20.132.134 62.20.132.153 62.20.132.175 62.20.132.180 62.20.132.241 62.20.132.243 62.20.133.61 62.20.133.86 62.20.133.120 ... TOTAL 253 for *na: SE-TELIANET-970521 *na: SE-UMDAC-960209 212.32.129.225 212.32.130.10 212.32.130.23 212.32.153.61 TOTAL 4 for *na: SE-UMDAC-960209 *na: EDEKADK 194.192.17.226 TOTAL 1 for *na: EDEKADK *na: PLASTMODK 194.192.17.245 TOTAL 1 for *na: PLASTMODK *na: SKAMOLDK 194.192.17.234 TOTAL 1 for *na: SKAMOLDK *na: HECODK 194.192.64.130 TOTAL 1 for *na: HECODK *na: TV2BH 194.192.64.162 TOTAL 1 for *na: TV2BH *na: ADVOC 193.89.95.194 TOTAL 1 for *na: ADVOC *na: GNNETCOMDK 193.89.95.210 TOTAL 1 for *na: GNNETCOMDK *na: DE-REGIO-980409 212.218.64.3 TOTAL 1 for *na: DE-REGIO-980409 *na: CH-AGRI-980422 212.28.159.194 TOTAL 1 for *na: CH-AGRI-980422 *na: UK-COLT-980422 212.36.142.211 212.36.142.214 212.36.142.215 212.36.142.222 212.36.142.223 212.36.142.225 TOTAL 6 for *na: UK-COLT-980422 *na: SCAN-SPEAKDK 193.89.103.3 TOTAL 1 for *na: SCAN-SPEAKDK *na: BELLEVUE 193.89.103.35 TOTAL 1 for *na: BELLEVUE *na: TSAI 194.224.52.4 194.224.52.6 194.224.52.40 194.224.53.3 194.224.53.58 194.224.53.135 TOTAL 6 for *na: TSAI *na: TSAI 194.224.55.25 194.224.55.46 TOTAL 2 for *na: TSAI *na: EU-ZZ-193 193.5.175.194 193.10.7.205 193.10.12.25 193.10.36.7 193.10.38.123 193.10.38.139 193.10.40.128 193.10.48.2 193.10.48.5 193.10.53.49 193.10.53.69 193.10.53.186 193.10.62.6 193.10.80.42 193.10.81.33 193.10.102.199 193.10.105.24 193.10.105.89 193.10.105.226 ... TOTAL 967 for *na: EU-ZZ-193 *na: PL-NASK-960626 195.164.232.29 TOTAL 1 for *na: PL-NASK-960626 *na: PL-NASK-960520 193.59.87.130 TOTAL 1 for *na: PL-NASK-960520 *na: PL-NASK-194-181 194.181.34.160 194.181.245.194 TOTAL 2 for *na: PL-NASK-194-181 *na: NKT-PCDK 193.89.103.18 TOTAL 1 for *na: NKT-PCDK *na: MATRAC-FR 194.117.212.2 TOTAL 1 for *na: MATRAC-FR *na: LINDER-PRIVAT 195.215.63.50 TOTAL 1 for *na: LINDER-PRIVAT *na: DE-DIRECPC-980312 195.238.40.170 195.238.43.60 195.238.44.213 TOTAL 3 for *na: DE-DIRECPC-980312 *na: SASIBDK 193.89.126.2 TOTAL 1 for *na: SASIBDK *na: IQMEDIADK 195.215.63.62 TOTAL 1 for *na: IQMEDIADK *na: PL-POZMAN-980508 150.254.173.3 150.254.173.107 150.254.180.2 TOTAL 3 for *na: PL-POZMAN-980508 *na: RU-MTU-980511 212.30.179.1 212.30.179.4 TOTAL 2 for *na: RU-MTU-980511 *na: UK-NTLI-970819 194.168.81.251 194.168.160.5 TOTAL 2 for *na: UK-NTLI-970819 *na: UK-NTLI-980511 212.250.26.114 212.250.143.21 TOTAL 2 for *na: UK-NTLI-980511 *na: LILLEBAELTDK 194.192.221.24 TOTAL 1 for *na: LILLEBAELTDK *na: POL-WEBVIR2 194.152.77.229 TOTAL 1 for *na: POL-WEBVIR2 *na: LINDCADDK 194.192.96.2 TOTAL 1 for *na: LINDCADDK *na: DE-ECOMP-980518 212.3.157.100 TOTAL 1 for *na: DE-ECOMP-980518 *na: ELFORDK 195.215.64.26 TOTAL 1 for *na: ELFORDK *na: ROSENDAHL-AS 195.215.64.115 TOTAL 1 for *na: ROSENDAHL-AS *na: CHASHUDEDK 195.215.64.146 TOTAL 1 for *na: CHASHUDEDK *na: FLEXADK 194.192.249.2 194.192.249.15 TOTAL 2 for *na: FLEXADK *na: SECDATACOM 193.89.97.2 193.89.97.35 TOTAL 2 for *na: SECDATACOM *na: SECDATACOM 193.89.97.2 TOTAL 1 for *na: SECDATACOM *na: BFEDK 193.89.97.35 TOTAL 1 for *na: BFEDK *na: TURDK 194.192.117.60 194.192.117.64 TOTAL 2 for *na: TURDK *na: ONLINE-TRANSLATIONDK 193.89.97.66 TOTAL 1 for *na: ONLINE-TRANSLATIONDK *na: DANAEGDK 195.215.64.146 TOTAL 1 for *na: DANAEGDK *na: SE-TRANSPAC-950303 194.52.127.65 194.52.190.12 194.52.237.242 TOTAL 3 for *na: SE-TRANSPAC-950303 *na: SE-TRANSPAC-961022 195.17.40.1 195.17.40.2 195.17.40.3 195.17.41.130 195.17.41.139 195.17.53.100 195.17.59.20 195.17.59.25 195.17.59.200 195.17.61.3 195.17.61.11 195.17.61.206 195.17.66.6 195.17.70.86 195.17.70.118 195.17.70.212 195.17.72.11 195.17.73.5 195.17.73.46 ... TOTAL 27 for *na: SE-TRANSPAC-961022 *na: DE-NDH-971119 195.227.32.180 195.227.32.190 195.227.37.24 195.227.38.116 TOTAL 4 for *na: DE-NDH-971119 *na: NL-DEMON-980428 212.238.66.22 212.238.74.23 212.238.81.157 TOTAL 3 for *na: NL-DEMON-980428 *na: JALUCOM 193.89.124.2 TOTAL 1 for *na: JALUCOM *na: GKN-WHEELSDK 193.89.97.98 TOTAL 1 for *na: GKN-WHEELSDK *na: REALGRUPPENDK 195.215.64.226 TOTAL 1 for *na: REALGRUPPENDK *na: LIFDK 194.192.117.178 TOTAL 1 for *na: LIFDK *na: GETNET-MAGELLANO-NET 193.70.88.2 TOTAL 1 for *na: GETNET-MAGELLANO-NET *na: RAI-NET2 193.70.224.42 193.70.224.104 TOTAL 2 for *na: RAI-NET2 *na: PRIMODK 193.89.97.194 TOTAL 1 for *na: PRIMODK *na: UTS-NET 193.70.227.18 TOTAL 1 for *na: UTS-NET *na: DE-IPF-960429 195.88.14.6 195.88.89.6 TOTAL 2 for *na: DE-IPF-960429 *na: PIRELLI-NET-2 193.70.248.32 TOTAL 1 for *na: PIRELLI-NET-2 *na: IUNET-NET-1 193.70.255.38 TOTAL 1 for *na: IUNET-NET-1 *na: INFOSYS-NET 193.76.126.2 193.76.126.138 TOTAL 2 for *na: INFOSYS-NET *na: RAI-NET 193.76.127.2 193.76.127.5 193.76.127.8 193.76.127.10 TOTAL 4 for *na: RAI-NET *na: TLSOFT-C-BLOCK 193.76.148.71 TOTAL 1 for *na: TLSOFT-C-BLOCK *na: CSINFO-NET-C 193.76.217.6 193.76.217.7 TOTAL 2 for *na: CSINFO-NET-C *na: ZUCCHETTI-NET 193.76.224.2 193.76.224.93 TOTAL 2 for *na: ZUCCHETTI-NET *na: MANIFESTO-NET 193.76.248.2 TOTAL 1 for *na: MANIFESTO-NET *na: INFONET 194.19.240.46 TOTAL 1 for *na: INFONET *na: EU-GLOBALONE-OTHER-970109 194.133.38.148 194.133.48.10 194.133.50.10 194.133.58.101 194.133.58.103 194.133.58.104 194.133.58.105 194.133.58.131 194.133.130.12 194.133.250.5 194.133.250.214 TOTAL 11 for *na: EU-GLOBALONE-OTHER-970109 *na: BORDINGPURUPDK 195.215.65.106 TOTAL 1 for *na: BORDINGPURUPDK *na: SEKDDFDK 193.89.124.194 TOTAL 1 for *na: SEKDDFDK *na: WINTERTHURDK 195.215.65.194 TOTAL 1 for *na: WINTERTHURDK *na: ZIMMERDK 193.89.126.129 193.89.126.130 TOTAL 2 for *na: ZIMMERDK *na: HUENNEBECKDK 193.89.127.2 TOTAL 1 for *na: HUENNEBECKDK *na: SI-TELEKOM-980622 212.30.64.7 212.30.64.19 212.30.64.220 212.30.94.14 212.30.94.73 212.30.94.107 212.30.94.138 212.30.94.215 212.30.94.230 212.30.94.236 TOTAL 10 for *na: SI-TELEKOM-980622 *na: MEDICONDK 195.215.67.2 TOTAL 1 for *na: MEDICONDK *na: COTASDK 195.215.67.130 TOTAL 1 for *na: COTASDK *na: DANICASUPPLYDK 195.215.66.66 TOTAL 1 for *na: DANICASUPPLYDK *na: GEA-PHARM 195.215.68.2 195.215.68.5 TOTAL 2 for *na: GEA-PHARM *na: SKORINGEN 195.215.66.18 TOTAL 1 for *na: SKORINGEN *na: AMUSANDMOSENDK 193.89.127.130 193.89.127.169 TOTAL 2 for *na: AMUSANDMOSENDK *na: CINEMASCHOOLDK 193.89.126.214 TOTAL 1 for *na: CINEMASCHOOLDK *na: OKREPRODK 193.89.126.214 TOTAL 1 for *na: OKREPRODK *na: RU-COMTAT-980622 212.22.77.151 TOTAL 1 for *na: RU-COMTAT-980622 *na: TTDK 193.89.126.113 193.89.126.114 193.89.126.115 193.89.126.117 TOTAL 4 for *na: TTDK *na: NYBORGPLASTDK 193.89.135.130 TOTAL 1 for *na: NYBORGPLASTDK *na: EG-DATAINFORM-NET 195.215.69.18 TOTAL 1 for *na: EG-DATAINFORM-NET *na: F-ENGELCOM 195.215.70.3 TOTAL 1 for *na: F-ENGELCOM *na: DE-KOMTEL-980519 212.7.131.3 212.7.131.33 212.7.131.39 212.7.144.10 TOTAL 4 for *na: DE-KOMTEL-980519 *na: FRP-MASKINFABRIKDK 195.215.69.83 TOTAL 1 for *na: FRP-MASKINFABRIKDK *na: FOCON 193.89.135.98 TOTAL 1 for *na: FOCON *na: ZPTC-BLK04 209.88.92.1 TOTAL 1 for *na: ZPTC-BLK04 *na: ZPTC-BLK02 196.2.64.1 TOTAL 1 for *na: ZPTC-BLK02 *na: STUDIOSDK 193.89.135.114 TOTAL 1 for *na: STUDIOSDK *na: IWAYD1-3 194.128.98.225 TOTAL 1 for *na: IWAYD1-3 *na: LARSEACOM 193.89.186.2 TOTAL 1 for *na: LARSEACOM *na: TWIMEDIA-NET0 194.130.240.52 194.130.240.57 194.130.240.117 194.130.240.118 194.130.240.123 194.130.240.126 194.130.240.149 TOTAL 7 for *na: TWIMEDIA-NET0 *na: ORIFARMDK 193.89.186.194 TOTAL 1 for *na: ORIFARMDK *na: STENHOJDK 195.215.59.82 TOTAL 1 for *na: STENHOJDK *na: EUCVDK 194.192.212.2 194.192.212.3 194.192.212.18 194.192.212.19 194.192.212.25 TOTAL 5 for *na: EUCVDK *na: DANFYSIKDK 194.192.219.66 TOTAL 1 for *na: DANFYSIKDK *na: GRAFIKHUSETDK 193.89.186.226 TOTAL 1 for *na: GRAFIKHUSETDK *na: DE-BBTT-980716 212.21.76.1 TOTAL 1 for *na: DE-BBTT-980716 *na: GOTTSOFTWAREDK 193.89.161.2 193.89.161.6 193.89.161.7 193.89.161.25 193.89.161.28 193.89.161.29 TOTAL 6 for *na: GOTTSOFTWAREDK *na: SE-UUNET-970731 195.242.38.180 195.242.42.195 TOTAL 2 for *na: SE-UUNET-970731 *na: DELTAELEKTRONIKDK 195.215.64.242 TOTAL 1 for *na: DELTAELEKTRONIKDK *na: SYNKRONDK 193.89.187.2 193.89.187.3 193.89.187.14 193.89.187.28 193.89.187.130 193.89.187.134 193.89.187.136 193.89.187.140 193.89.187.142 193.89.187.143 193.89.187.160 193.89.187.176 193.89.187.205 193.89.187.249 193.89.187.254 TOTAL 15 for *na: SYNKRONDK *na: EU-ZZ-194 194.1.128.2 194.1.128.5 194.1.128.10 194.1.128.14 194.1.128.27 194.1.128.40 194.1.133.42 194.2.128.1 194.2.128.2 194.2.128.4 194.2.128.6 194.2.128.16 194.2.128.27 194.2.128.247 194.2.128.248 194.6.151.205 194.7.170.162 194.7.182.210 194.8.218.141 ... TOTAL 1050 for *na: EU-ZZ-194 *na: EU-ZZ-195 195.0.49.130 195.2.84.75 195.2.130.209 195.2.153.2 195.3.120.97 195.3.126.124 195.3.126.125 195.3.127.220 195.4.44.68 195.4.114.21 195.4.150.50 195.4.170.35 195.4.170.45 195.4.170.56 195.4.188.229 195.4.189.22 195.4.192.5 195.4.192.35 195.4.214.2 ... TOTAL 5078 for *na: EU-ZZ-195 *na: EU-ZZ-212 212.3.5.124 212.3.6.130 212.3.157.100 212.5.77.34 212.7.131.3 212.7.131.33 212.7.131.39 212.7.144.10 212.10.13.250 212.10.15.98 212.12.2.44 212.15.30.4 212.15.30.72 212.21.76.1 212.22.77.151 212.27.196.167 212.28.159.194 212.30.64.7 212.30.64.19 ... TOTAL 292 for *na: EU-ZZ-212 *na: EU-ZZ-62 62.0.128.40 62.0.128.86 62.0.128.107 62.0.128.138 62.0.145.135 62.0.145.139 62.0.145.232 62.0.146.8 62.0.146.10 62.0.146.89 62.0.149.78 62.0.149.100 62.0.152.1 62.0.153.19 62.0.153.39 62.0.153.194 62.0.154.12 62.0.154.211 62.0.154.235 ... TOTAL 369 for *na: EU-ZZ-62 *na: TR-FIDAN-980729 212.45.68.112 TOTAL 1 for *na: TR-FIDAN-980729 *na: UK-CONSTELLATION-980729 212.47.71.4 212.47.74.11 TOTAL 2 for *na: UK-CONSTELLATION-980729 *na: SCANTICONCOMWELL-REBILDDK 193.89.161.130 TOTAL 1 for *na: SCANTICONCOMWELL-REBILDDK *na: IONET-PSINET 38.193.29.47 38.193.29.55 38.193.48.78 38.193.48.85 38.193.48.172 38.193.49.93 38.193.49.134 38.193.49.140 38.193.50.40 38.193.50.156 38.193.51.1 38.193.51.110 38.193.51.129 38.193.52.109 38.193.52.147 38.193.52.178 38.193.53.111 38.193.54.35 38.193.54.57 ... TOTAL 46 for *na: IONET-PSINET *na: INDUSTRIELLENVEREINIGUNG-NET 194.118.28.226 TOTAL 1 for *na: INDUSTRIELLENVEREINIGUNG-NET *na: DTDGLUD-MARSTRANDDK 193.88.143.98 TOTAL 1 for *na: DTDGLUD-MARSTRANDDK *na: AE-EMIRNET-951122 194.170.163.87 194.170.164.13 194.170.168.3 194.170.168.15 194.170.168.28 194.170.168.68 194.170.168.81 194.170.168.94 TOTAL 8 for *na: AE-EMIRNET-951122 *na: NET-27-1 194.118.27.113 TOTAL 1 for *na: NET-27-1 *na: PTT-MUSEUMDK 193.89.63.2 TOTAL 1 for *na: PTT-MUSEUMDK *na: ALFIXCOM 195.215.73.66 TOTAL 1 for *na: ALFIXCOM *na: AMUCENTER 193.89.63.145 TOTAL 1 for *na: AMUCENTER *na: BIE-BERNTSEN-ASDK 193.89.63.66 193.89.63.67 TOTAL 2 for *na: BIE-BERNTSEN-ASDK *na: DANMARKS-AELDREBOLIGSELSKABDK 193.89.62.2 193.89.62.4 TOTAL 2 for *na: DANMARKS-AELDREBOLIGSELSKABDK *na: ZPTC-BLK02 196.2.64.1 TOTAL 1 for *na: ZPTC-BLK02 *na: EU-IBM-970507 62.200.88.141 TOTAL 1 for *na: EU-IBM-970507 *na: BRITEUK2-NET2 148.181.1.40 TOTAL 1 for *na: BRITEUK2-NET2 *na: TSCHUDI-EITZENDK 195.215.69.34 TOTAL 1 for *na: TSCHUDI-EITZENDK *na: CZ-EUNET-193-86 193.85.24.1 193.85.215.209 TOTAL 2 for *na: CZ-EUNET-193-86 *na: FI-HTC-961129 194.241.193.103 TOTAL 1 for *na: FI-HTC-961129 *na: DEVI-DK 195.24.10.150 TOTAL 1 for *na: DEVI-DK *na: KOMMUNEKREDIT-DK 195.24.10.138 TOTAL 1 for *na: KOMMUNEKREDIT-DK *na: INNOVISION-DK 195.24.10.113 195.24.10.120 195.24.10.121 TOTAL 3 for *na: INNOVISION-DK *na: FAERCHPLASTDK 195.215.74.130 TOTAL 1 for *na: FAERCHPLASTDK *na: NETXPERTDK 193.89.60.2 193.89.60.23 TOTAL 2 for *na: NETXPERTDK *na: INTERLUX 194.176.42.34 TOTAL 1 for *na: INTERLUX *na: GR-HELLASNET-980821 212.54.220.208 TOTAL 1 for *na: GR-HELLASNET-980821 *na: CASA-DE 194.140.53.2 TOTAL 1 for *na: CASA-DE *na: DE-MAZ-970704 195.179.11.129 195.179.50.126 195.179.62.60 195.179.76.20 195.179.80.10 195.179.87.85 195.179.246.2 195.179.246.26 195.179.251.2 195.179.251.3 TOTAL 10 for *na: DE-MAZ-970704 *na: KILROYTRAVELSCOM 193.89.62.234 193.89.62.235 TOTAL 2 for *na: KILROYTRAVELSCOM *na: THORANDERSEN 193.89.60.194 TOTAL 1 for *na: THORANDERSEN *na: FR-AAC 194.206.113.1 TOTAL 1 for *na: FR-AAC *na: JAN-IMPORTDK 193.89.103.26 TOTAL 1 for *na: JAN-IMPORTDK *na: SVANEKAER 195.215.71.17 195.215.71.18 TOTAL 2 for *na: SVANEKAER *na: CZ-VOL-980831 212.27.196.167 TOTAL 1 for *na: CZ-VOL-980831 *na: ODDERAVISDK 195.215.76.144 TOTAL 1 for *na: ODDERAVISDK *na: UK-SAQNET-961021 195.2.130.209 195.2.153.2 TOTAL 2 for *na: UK-SAQNET-961021 *na: SE-TELIANET-960201 194.236.32.36 194.236.32.61 194.236.82.23 194.236.105.103 194.237.125.22 TOTAL 5 for *na: SE-TELIANET-960201 *na: SE-TELIANET-960206 194.23.231.66 TOTAL 1 for *na: SE-TELIANET-960206 *na: HOWDENDK 193.89.136.1 TOTAL 1 for *na: HOWDENDK *na: FI-FUNET-960624 195.148.56.127 195.148.56.147 TOTAL 2 for *na: FI-FUNET-960624 *na: FI-FUNET-950315 193.166.225.182 193.167.87.93 TOTAL 2 for *na: FI-FUNET-950315 *na: DE-ROKA-960514 62.104.16.176 62.104.19.150 62.104.24.38 62.104.24.115 62.104.29.88 62.104.31.72 62.104.38.1 62.104.39.1 62.104.41.131 62.104.42.35 62.104.42.40 62.104.43.1 62.104.43.2 62.104.54.1 62.104.64.10 62.104.64.11 62.104.64.32 62.104.64.33 TOTAL 18 for *na: DE-ROKA-960514 *na: DE-ROKA-970303 194.97.65.175 194.97.69.231 TOTAL 2 for *na: DE-ROKA-970303 *na: DE-ROKA-960514 195.4.44.68 195.4.114.21 195.4.150.50 195.4.170.35 195.4.170.45 195.4.170.56 195.4.188.229 195.4.189.22 195.4.192.5 195.4.192.35 195.4.214.2 195.4.215.2 195.4.215.254 TOTAL 13 for *na: DE-ROKA-960514 *na: UK-EASYNET-960801 195.40.65.29 195.40.65.55 195.40.65.113 195.40.65.231 195.40.66.74 TOTAL 5 for *na: UK-EASYNET-960801 *na: NAF-AS 195.215.77.2 TOTAL 1 for *na: NAF-AS *na: CWOSISDK 193.89.29.66 TOTAL 1 for *na: CWOSISDK *na: SUNET-GBG-REGION-WEST 193.10.160.20 193.10.163.20 193.10.166.34 193.10.170.21 193.10.170.74 193.10.171.115 193.10.171.140 193.10.176.21 193.10.176.23 193.10.176.25 193.10.185.3 193.10.186.2 193.10.186.142 193.10.192.40 193.10.194.29 193.10.198.66 193.10.200.8 193.10.202.40 193.10.208.10 ... TOTAL 33 for *na: SUNET-GBG-REGION-WEST *na: SUNET-GBG-REGION-WEST 193.10.240.5 193.10.240.131 193.10.240.166 193.10.240.191 193.10.244.100 TOTAL 5 for *na: SUNET-GBG-REGION-WEST *na: SUNET-GBG-REGION-WEST 193.10.163.20 TOTAL 1 for *na: SUNET-GBG-REGION-WEST *na: GIGTFORENINGEN-AARHUSDK 193.89.29.131 193.89.29.132 193.89.29.133 193.89.29.134 193.89.29.135 193.89.29.136 193.89.29.137 TOTAL 7 for *na: GIGTFORENINGEN-AARHUSDK *na: ELBODAN 193.89.29.168 TOTAL 1 for *na: ELBODAN *na: SE-TELIANET-930901 194.16.15.18 194.16.15.19 194.16.203.148 194.16.211.62 194.17.155.17 194.17.195.198 194.17.195.253 194.17.197.211 194.17.211.228 194.18.167.2 194.18.199.1 194.18.243.233 TOTAL 12 for *na: SE-TELIANET-930901 *na: SE-TELIANET-930901 193.45.95.248 193.45.215.45 TOTAL 2 for *na: SE-TELIANET-930901 *na: UNITMESSERDK 193.89.60.178 TOTAL 1 for *na: UNITMESSERDK *na: ESFDK 195.215.128.66 TOTAL 1 for *na: ESFDK *na: IT-INTERBUSINESS-980401 212.210.31.246 TOTAL 1 for *na: IT-INTERBUSINESS-980401 *na: IT-INTERBUSINESS-970312 195.103.83.200 TOTAL 1 for *na: IT-INTERBUSINESS-970312 *na: BELWUE 129.143.2.1 129.143.2.4 129.143.75.11 129.143.96.137 TOTAL 4 for *na: BELWUE *na: DK-IMAGE-SCANDINAVIA 194.234.182.2 194.234.182.3 194.234.182.5 194.234.182.6 194.234.182.7 194.234.182.9 194.234.182.10 194.234.182.11 194.234.182.13 194.234.182.16 194.234.182.20 194.234.182.23 194.234.182.28 194.234.182.29 194.234.182.32 194.234.182.33 194.234.182.35 194.234.182.36 194.234.182.37 ... TOTAL 156 for *na: DK-IMAGE-SCANDINAVIA *na: BASCONDK 195.215.128.130 TOTAL 1 for *na: BASCONDK *na: FERRANTI-COMPUTER-SYSTEMS-NV-NET 194.7.182.210 TOTAL 1 for *na: FERRANTI-COMPUTER-SYSTEMS-NV-NET *na: SUNET-GBG-REGION-WEST 193.10.160.20 193.10.163.20 193.10.166.34 193.10.170.21 193.10.170.74 193.10.171.115 193.10.171.140 193.10.176.21 193.10.176.23 193.10.176.25 193.10.185.3 193.10.186.2 193.10.186.142 193.10.192.40 193.10.194.29 193.10.198.66 193.10.200.8 193.10.202.40 193.10.208.10 ... TOTAL 38 for *na: SUNET-GBG-REGION-WEST *na: BRT-VHSDR-NET 171.28.22.20 171.29.105.221 TOTAL 2 for *na: BRT-VHSDR-NET *na: EG-IE-951129 194.79.109.18 194.79.109.27 194.79.119.56 TOTAL 3 for *na: EG-IE-951129 *na: IT-NETTUNO-940726 193.207.158.100 TOTAL 1 for *na: IT-NETTUNO-940726 *na: UK-NETHEAD-960314 194.247.234.24 194.247.234.39 TOTAL 2 for *na: UK-NETHEAD-960314 *na: UA-ZZ-940217 194.44.212.194 TOTAL 1 for *na: UA-ZZ-940217 *na: DE-XLINK-940228 194.45.197.100 TOTAL 1 for *na: DE-XLINK-940228 *na: BE-INTERPAC-960213 194.78.15.195 194.78.21.76 194.78.27.1 194.78.27.10 194.78.33.48 194.78.36.5 194.78.41.100 194.78.42.1 194.78.42.2 194.78.45.194 194.78.45.208 194.78.47.3 194.78.47.12 194.78.47.66 194.78.47.78 194.78.47.85 194.78.48.13 194.78.50.1 194.78.50.249 ... TOTAL 39 for *na: BE-INTERPAC-960213 *na: IR-DCC-970722 195.146.46.2 TOTAL 1 for *na: IR-DCC-970722 *na: IT-TIN-980225 212.216.2.44 212.216.3.125 212.216.3.152 212.216.4.161 212.216.4.232 212.216.5.144 212.216.6.91 212.216.6.184 212.216.6.195 212.216.7.56 212.216.7.135 212.216.8.215 212.216.11.53 212.216.13.217 212.216.14.73 212.216.14.133 212.216.15.17 212.216.20.213 212.216.20.235 ... TOTAL 147 for *na: IT-TIN-980225 *na: RU-TULATELECOM-980220 212.12.2.44 TOTAL 1 for *na: RU-TULATELECOM-980220 *na: SE-OLL 194.103.185.80 TOTAL 1 for *na: SE-OLL *na: CH-CYBERLINK-980918 212.55.207.10 212.55.207.15 TOTAL 2 for *na: CH-CYBERLINK-980918 *na: UK-VBCNET-960404 194.207.148.170 194.207.149.126 194.207.190.65 TOTAL 3 for *na: UK-VBCNET-960404 *na: AT-VIANET-960612 194.96.97.5 194.96.209.97 TOTAL 2 for *na: AT-VIANET-960612 *na: BIMCO 195.24.4.34 195.24.4.37 TOTAL 2 for *na: BIMCO *na: STATOTECH 195.24.4.13 TOTAL 1 for *na: STATOTECH *na: INETPARTNER-DK 195.24.3.10 195.24.3.11 195.24.3.73 195.24.3.76 195.24.3.86 195.24.3.89 195.24.3.91 195.24.3.95 195.24.3.100 195.24.3.105 195.24.3.106 195.24.3.111 195.24.3.112 195.24.3.114 195.24.3.125 195.24.3.130 195.24.3.131 195.24.3.134 195.24.3.135 ... TOTAL 45 for *na: INETPARTNER-DK *na: OM-GTO-OMAN-980924 212.72.7.25 TOTAL 1 for *na: OM-GTO-OMAN-980924 *na: MUNTERSDK 195.215.131.195 TOTAL 1 for *na: MUNTERSDK *na: DIABETESFORENINGENDK 195.215.131.227 TOTAL 1 for *na: DIABETESFORENINGENDK *na: UK-NETLINK-960725 194.88.153.163 194.88.155.142 194.88.157.175 TOTAL 3 for *na: UK-NETLINK-960725 *na: DE-IVM-971022 62.204.1.1 62.204.1.2 TOTAL 2 for *na: DE-IVM-971022 *na: DE-IVM-971021 195.78.161.1 TOTAL 1 for *na: DE-IVM-971021 *na: DE-IVM-971231 195.247.224.195 195.247.235.131 TOTAL 2 for *na: DE-IVM-971231 *na: WINDFELDDK 195.215.132.70 TOTAL 1 for *na: WINDFELDDK *na: PETERSRESTHALDK 195.215.130.146 TOTAL 1 for *na: PETERSRESTHALDK *na: NAPRI-SK 194.1.128.2 194.1.128.5 194.1.128.10 194.1.128.14 194.1.128.27 194.1.128.40 194.1.133.42 TOTAL 7 for *na: NAPRI-SK *na: DE-CYBERNET-970513 195.143.13.2 195.143.13.102 195.143.49.29 195.143.51.135 195.143.108.2 195.143.109.2 195.143.109.66 195.143.109.117 195.143.114.89 195.143.116.34 195.143.118.1 195.143.118.5 195.143.118.6 195.143.118.12 195.143.128.5 195.143.162.68 195.143.162.93 TOTAL 17 for *na: DE-CYBERNET-970513 *na: SE-SKNET-970205 195.22.67.2 195.22.69.2 195.22.69.3 195.22.69.4 195.22.69.7 195.22.70.10 195.22.70.17 195.22.70.181 TOTAL 8 for *na: SE-SKNET-970205 *na: GRAINTECCOM 195.215.132.194 TOTAL 1 for *na: GRAINTECCOM *na: JACODANDK 195.215.132.202 TOTAL 1 for *na: JACODANDK *na: CKUDK 195.215.129.132 TOTAL 1 for *na: CKUDK *na: TKDK 195.215.133.66 TOTAL 1 for *na: TKDK *na: PHOTOTEAMDK 195.215.133.82 TOTAL 1 for *na: PHOTOTEAMDK *na: GTO-OM-BLK02 212.72.7.25 TOTAL 1 for *na: GTO-OM-BLK02 *na: DIRECTOFFICEDK 195.215.133.114 TOTAL 1 for *na: DIRECTOFFICEDK *na: TVMIDTVESTDK 195.215.134.2 TOTAL 1 for *na: TVMIDTVESTDK *na: UK-WEBFACTORY-960826 195.134.11.226 TOTAL 1 for *na: UK-WEBFACTORY-960826 *na: DK-PROVENTUM-970410 195.216.193.34 195.216.193.36 195.216.193.37 195.216.193.38 195.216.193.43 195.216.193.49 195.216.193.61 195.216.193.166 195.216.193.180 195.216.208.34 195.216.208.99 195.216.208.101 195.216.215.11 195.216.215.12 195.216.215.19 195.216.215.24 195.216.215.25 195.216.215.32 195.216.215.100 ... TOTAL 20 for *na: DK-PROVENTUM-970410 *na: FH-AALEN 141.18.1.12 141.18.15.59 TOTAL 2 for *na: FH-AALEN *na: IT-WIND-981015 212.245.248.178 TOTAL 1 for *na: IT-WIND-981015 *na: RIDK 195.215.134.214 TOTAL 1 for *na: RIDK *na: RU-ROSNIIROS-194-85 194.85.103.33 194.85.173.117 194.85.173.199 194.85.255.154 TOTAL 4 for *na: RU-ROSNIIROS-194-85 *na: RU-ROSNIIROS-960103 194.226.125.67 194.226.135.100 194.226.198.34 194.226.198.36 TOTAL 4 for *na: RU-ROSNIIROS-960103 *na: RU-ROSNIIROS-960719 195.208.252.2 TOTAL 1 for *na: RU-ROSNIIROS-960719 *na: RUWELDK 195.215.135.34 TOTAL 1 for *na: RUWELDK *na: MSASDK 195.215.135.130 195.215.135.133 TOTAL 2 for *na: MSASDK *na: DIGITAL-FOREST-NET2 208.208.207.3 208.208.207.27 208.208.207.65 208.208.207.254 TOTAL 4 for *na: DIGITAL-FOREST-NET2 *na: SE-PI-970311 195.7.82.196 TOTAL 1 for *na: SE-PI-970311 *na: IBC-NET 145.253.66.1 145.253.72.153 145.253.74.51 145.253.76.3 145.253.76.30 145.253.76.31 145.253.76.65 145.253.76.161 145.253.82.38 145.253.94.173 145.253.95.53 145.253.95.164 145.253.112.31 145.253.113.31 TOTAL 14 for *na: IBC-NET *na: ARCOR-IP 145.253.2.9 145.253.2.35 145.253.2.36 145.253.2.75 145.253.66.1 145.253.72.153 145.253.74.51 145.253.76.3 145.253.76.30 145.253.76.31 145.253.76.65 145.253.76.161 145.253.82.38 145.253.94.173 145.253.95.53 145.253.95.164 145.253.112.31 145.253.113.31 TOTAL 18 for *na: ARCOR-IP *na: CH-SUNRISE-970513 195.141.11.126 195.141.56.5 195.141.76.164 195.141.180.227 195.141.237.22 195.141.237.245 195.141.237.251 195.141.244.211 TOTAL 8 for *na: CH-SUNRISE-970513 *na: SCANTOPSDK 195.215.136.98 TOTAL 1 for *na: SCANTOPSDK *na: DEBELDK 195.215.136.131 TOTAL 1 for *na: DEBELDK *na: GR-FORTHNET-951220 194.219.168.164 194.219.171.30 194.219.171.68 TOTAL 3 for *na: GR-FORTHNET-951220 *na: NL-EURONET-961118 194.134.23.228 194.134.33.34 194.134.49.33 194.134.49.70 194.134.73.25 194.134.73.31 194.134.73.94 194.134.76.33 194.134.109.1 194.134.109.6 194.134.109.9 194.134.109.27 194.134.109.29 194.134.111.106 194.134.123.245 194.134.124.29 194.134.124.150 194.134.124.205 TOTAL 18 for *na: NL-EURONET-961118 *na: EU-EUNET-950315 193.73.103.80 193.73.103.82 193.73.103.121 TOTAL 3 for *na: EU-EUNET-950315 *na: EU-EUNET-930901 193.120.133.201 193.120.134.130 TOTAL 2 for *na: EU-EUNET-930901 *na: EU-EUNET-950526 193.121.83.66 TOTAL 1 for *na: EU-EUNET-950526 *na: EU-EUNET-960514 193.127.68.3 193.127.226.188 TOTAL 2 for *na: EU-EUNET-960514 *na: EU-EUNET-950811 194.191.254.254 TOTAL 1 for *na: EU-EUNET-950811 *na: EU-EUNET-970509 195.139.27.215 TOTAL 1 for *na: EU-EUNET-970509 *na: EU-EUNET-970509 195.207.23.48 195.207.28.2 TOTAL 2 for *na: EU-EUNET-970509 *na: EU-EUNET-980414 212.226.249.1 TOTAL 1 for *na: EU-EUNET-980414 *na: FORTH 139.91.1.1 139.91.1.17 139.91.191.3 139.91.191.203 TOTAL 4 for *na: FORTH *na: MANBW-DK 195.24.2.55 195.24.2.60 TOTAL 2 for *na: MANBW-DK *na: UK-DIALNET-980223 212.44.5.10 TOTAL 1 for *na: UK-DIALNET-980223 *na: ES-CESATEL-951122 194.140.67.10 194.140.71.186 194.140.80.4 TOTAL 3 for *na: ES-CESATEL-951122 *na: STAERKDK 195.215.136.194 TOTAL 1 for *na: STAERKDK *na: CNET 139.100.0.30 139.100.0.155 TOTAL 2 for *na: CNET *na: PL-TPSA-981028 212.160.3.85 212.160.15.48 212.160.15.168 212.160.15.187 212.160.16.8 212.160.26.55 212.160.26.74 212.160.26.120 212.160.28.252 212.160.44.126 212.160.48.150 212.160.48.208 212.160.62.52 212.160.62.61 TOTAL 14 for *na: PL-TPSA-981028 *na: SK-NETLAB-960927 195.168.0.2 195.168.1.2 195.168.1.4 195.168.1.20 195.168.1.24 195.168.13.34 195.168.13.35 195.168.47.34 195.168.177.33 TOTAL 9 for *na: SK-NETLAB-960927 *na: TRICON-DK 195.24.15.71 TOTAL 1 for *na: TRICON-DK *na: SK-PUBNET-981102 212.81.12.11 212.81.12.12 TOTAL 2 for *na: SK-PUBNET-981102 *na: RU-OMSK-970725 195.162.37.130 TOTAL 1 for *na: RU-OMSK-970725 *na: BG-BIT-970819 195.34.104.30 195.34.107.10 195.34.115.249 TOTAL 3 for *na: BG-BIT-970819 *na: ADVMB 195.215.138.50 TOTAL 1 for *na: ADVMB *na: PMB-DPFDK 195.215.138.83 TOTAL 1 for *na: PMB-DPFDK *na: UK-DEMON-981104 212.229.26.29 212.229.72.44 212.229.74.96 212.229.80.182 212.229.87.31 TOTAL 5 for *na: UK-DEMON-981104 *na: DE-ZZ-940420 194.55.63.2 TOTAL 1 for *na: DE-ZZ-940420 *na: DE-ZZ-950424 194.156.201.6 194.156.201.33 194.156.201.194 TOTAL 3 for *na: DE-ZZ-950424 *na: SE-BYGGDOK 193.10.7.205 TOTAL 1 for *na: SE-BYGGDOK *na: SE-KB 193.10.12.25 TOTAL 1 for *na: SE-KB *na: SE-NRM 193.10.36.7 TOTAL 1 for *na: SE-NRM *na: SE-KTH-HANINGE 193.10.38.123 193.10.38.139 TOTAL 2 for *na: SE-KTH-HANINGE *na: SE-CBNA 193.10.40.128 TOTAL 1 for *na: SE-CBNA *na: SE-HHS 193.10.48.2 193.10.48.5 TOTAL 2 for *na: SE-HHS *na: SE-HGOT 193.10.53.49 193.10.53.69 193.10.53.186 TOTAL 3 for *na: SE-HGOT *na: SE-MHS 193.10.62.6 TOTAL 1 for *na: SE-MHS *na: SUNET-34M 193.10.80.42 TOTAL 1 for *na: SUNET-34M *na: LUTH-34M 193.10.81.33 TOTAL 1 for *na: LUTH-34M *na: SE-SLUUME 193.10.102.199 TOTAL 1 for *na: SE-SLUUME *na: SE-MITTHS 193.10.105.24 193.10.105.89 193.10.105.226 193.10.107.3 193.10.108.69 193.10.108.139 193.10.112.99 193.10.119.68 193.10.119.226 TOTAL 9 for *na: SE-MITTHS *na: SE-MITTHS2 193.10.250.42 193.10.250.156 193.10.250.192 193.10.251.75 TOTAL 4 for *na: SE-MITTHS2 *na: HHNET 194.47.0.30 194.47.1.11 194.47.16.32 194.47.17.165 TOTAL 4 for *na: HHNET *na: HKRNET 194.47.25.8 194.47.27.190 194.47.29.146 194.47.38.61 194.47.47.12 TOTAL 5 for *na: HKRNET *na: ALNET 194.47.49.5 194.47.50.19 194.47.55.18 194.47.55.213 TOTAL 4 for *na: ALNET *na: VAXJO-NET 194.47.65.11 194.47.81.215 194.47.89.77 194.47.99.36 194.47.99.100 194.47.103.119 194.47.103.188 194.47.106.85 194.47.107.110 TOTAL 9 for *na: VAXJO-NET *na: NL-NLNET-970903 195.193.225.9 195.193.225.79 TOTAL 2 for *na: NL-NLNET-970903 *na: NL-NLNET-960122 194.229.115.34 194.229.190.5 194.229.213.59 TOTAL 3 for *na: NL-NLNET-960122 *na: JBMEDIADK 195.215.138.130 TOTAL 1 for *na: JBMEDIADK *na: MOLHU 171.31.0.1 TOTAL 1 for *na: MOLHU *na: FI-SONERA-193-208-193-211 193.208.135.186 TOTAL 1 for *na: FI-SONERA-193-208-193-211 *na: FI-SONERA-940902 194.89.25.34 194.89.179.18 TOTAL 2 for *na: FI-SONERA-940902 *na: FI-SONERA-951207 194.215.205.32 TOTAL 1 for *na: FI-SONERA-951207 *na: FI-SONERA-960306 194.251.255.57 194.251.255.231 194.251.255.232 194.251.255.233 194.251.255.234 TOTAL 5 for *na: FI-SONERA-960306 *na: RU-WEBPLUS-970414 195.131.23.250 195.131.53.61 TOTAL 2 for *na: RU-WEBPLUS-970414 *na: STATO-DK 195.24.14.101 TOTAL 1 for *na: STATO-DK *na: UK-DEMON-961002 195.11.242.207 195.11.242.250 195.11.243.18 195.11.243.21 TOTAL 4 for *na: UK-DEMON-961002 *na: UK-DEMON-980220 212.240.154.129 212.240.154.130 212.240.194.226 212.240.234.157 212.240.235.17 212.240.237.41 TOTAL 6 for *na: UK-DEMON-980220 *na: UK-DEMON-970724 193.237.3.146 193.237.17.8 193.237.50.62 193.237.65.172 193.237.93.177 193.237.97.210 193.237.132.136 193.237.137.84 193.237.149.241 193.237.154.85 193.237.168.51 193.237.174.39 193.237.174.200 193.237.213.213 193.237.228.150 193.237.239.104 193.237.250.55 TOTAL 17 for *na: UK-DEMON-970724 *na: UK-DEMON-970729 193.238.128.81 193.238.132.187 193.238.136.14 193.238.147.190 193.238.155.232 193.238.159.62 193.238.162.107 193.238.173.52 193.238.181.172 193.238.190.135 193.238.193.22 193.238.199.48 193.238.200.178 193.238.203.139 193.238.206.58 193.238.210.160 193.238.213.3 193.238.215.178 193.238.219.11 ... TOTAL 37 for *na: UK-DEMON-970729 *na: SE-UTFORS-981109 212.105.59.2 212.105.59.7 212.105.59.21 212.105.59.120 212.105.60.72 212.105.60.178 212.105.62.15 TOTAL 7 for *na: SE-UTFORS-981109 *na: UK-BT-961016 194.75.84.1 194.75.145.242 TOTAL 2 for *na: UK-BT-961016 *na: UK-BT-961016 195.99.65.212 195.99.66.211 TOTAL 2 for *na: UK-BT-961016 *na: RU-TCNET-970306 195.230.83.2 195.230.83.10 TOTAL 2 for *na: RU-TCNET-970306 *na: INTEROUTEDK 195.215.139.2 TOTAL 1 for *na: INTEROUTEDK *na: FR-OLEANE-970501 62.161.250.65 62.161.250.67 TOTAL 2 for *na: FR-OLEANE-970501 *na: COMPNEWS 144.178.159.75 144.178.159.77 TOTAL 2 for *na: COMPNEWS *na: FR-TRANSPAC-980416 212.234.33.66 212.234.56.3 212.234.106.77 TOTAL 3 for *na: FR-TRANSPAC-980416 *na: UK-CABLEINET-960227 194.117.129.2 194.117.129.214 194.117.129.235 194.117.131.92 194.117.143.2 TOTAL 5 for *na: UK-CABLEINET-960227 *na: UK-CABLEINET-960703 195.188.98.1 195.188.98.2 195.188.107.6 195.188.107.40 195.188.107.42 195.188.107.45 195.188.134.2 195.188.134.24 195.188.134.111 195.188.151.148 195.188.160.2 195.188.160.7 195.188.160.117 195.188.160.156 195.188.161.203 195.188.168.7 195.188.171.2 195.188.171.13 195.188.171.15 ... TOTAL 27 for *na: UK-CABLEINET-960703 *na: CH-PLUSNET-960123 194.230.4.36 TOTAL 1 for *na: CH-PLUSNET-960123 *na: DK-STOFANET-980226 212.10.13.250 212.10.15.98 TOTAL 2 for *na: DK-STOFANET-980226 *na: UK-POL-960119 194.152.77.229 TOTAL 1 for *na: UK-POL-960119 *na: UK-XARA-960916 195.224.85.1 195.224.85.201 195.224.85.202 195.224.85.204 195.224.107.12 195.224.107.17 195.224.107.24 195.224.107.25 195.224.107.50 195.224.107.57 195.224.107.150 195.224.107.248 195.224.117.26 195.224.160.10 195.224.160.11 195.224.160.253 195.224.188.1 195.224.188.13 195.224.189.1 ... TOTAL 25 for *na: UK-XARA-960916 *na: RU-RELLINE-960225 195.146.72.146 195.146.79.150 TOTAL 2 for *na: RU-RELLINE-960225 *na: RU-MCNTT-980119 195.28.39.81 TOTAL 1 for *na: RU-MCNTT-980119 *na: SE-SVIKKOM 194.68.13.18 194.68.13.19 TOTAL 2 for *na: SE-SVIKKOM *na: UK-INS-194-205-16 194.205.28.15 194.205.70.14 TOTAL 2 for *na: UK-INS-194-205-16 *na: DE-MBT-970808 195.189.0.34 195.189.0.39 195.189.1.39 TOTAL 3 for *na: DE-MBT-970808 *na: UK-DEMON-951221 194.222.1.211 194.222.6.8 194.222.26.223 194.222.44.212 194.222.52.131 194.222.56.100 194.222.57.188 194.222.62.30 194.222.62.209 194.222.65.237 194.222.68.241 194.222.89.17 194.222.90.167 194.222.94.179 194.222.101.123 194.222.113.146 194.222.124.124 194.222.125.39 194.222.160.92 ... TOTAL 28 for *na: UK-DEMON-951221 *na: DE-SGH-980407 193.218.205.10 193.218.205.42 193.218.210.46 193.218.210.188 193.218.216.10 TOTAL 5 for *na: DE-SGH-980407 *na: NL-UNISOURCE-951004 193.172.127.93 TOTAL 1 for *na: NL-UNISOURCE-951004 *na: NL-UNISOURCE-950410 194.151.126.99 194.151.126.166 194.151.224.7 194.151.231.130 194.151.231.194 194.151.234.18 TOTAL 6 for *na: NL-UNISOURCE-950410 *na: FR-TRANSPAC-970307 195.101.197.117 195.101.197.216 195.101.233.253 TOTAL 3 for *na: FR-TRANSPAC-970307 *na: FR-TRANSPAC-960304 194.250.180.54 TOTAL 1 for *na: FR-TRANSPAC-960304 *na: FR-TRANSPAC-194-206 194.206.113.1 194.206.217.49 194.206.218.35 194.206.218.40 TOTAL 4 for *na: FR-TRANSPAC-194-206 *na: FR-TRANSPAC-951019 194.51.238.1 194.51.238.2 TOTAL 2 for *na: FR-TRANSPAC-951019 *na: RU-GLASNET-961224 195.218.159.130 TOTAL 1 for *na: RU-GLASNET-961224 *na: SE-TELENORDIA-980908 195.163.66.82 195.163.66.84 TOTAL 2 for *na: SE-TELENORDIA-980908 *na: SE-TELENORDIA-960612 195.100.172.2 195.100.176.194 195.100.208.76 TOTAL 3 for *na: SE-TELENORDIA-960612 *na: DE-ZZ-930921 194.15.149.71 TOTAL 1 for *na: DE-ZZ-930921 *na: DE-GTN-960124 194.231.199.2 TOTAL 1 for *na: DE-GTN-960124 *na: BANGOR 147.143.2.1 147.143.200.22 TOTAL 2 for *na: BANGOR *na: EU-GLOBALONE-NORTH-970327 195.119.76.11 195.119.76.20 195.119.102.102 195.119.102.178 195.119.102.207 195.119.156.34 195.119.156.35 195.119.160.38 195.119.160.230 195.119.180.14 195.119.184.2 195.119.184.42 195.119.184.130 195.119.190.2 195.119.196.2 195.119.209.117 TOTAL 16 for *na: EU-GLOBALONE-NORTH-970327 *na: EU-GLOBALONE-NORTH-961222 194.234.0.40 194.234.0.60 194.234.0.66 194.234.0.130 194.234.0.165 194.234.0.210 194.234.1.98 194.234.1.130 194.234.1.162 194.234.1.163 194.234.1.164 194.234.1.177 194.234.1.181 194.234.1.187 194.234.2.67 194.234.2.98 194.234.2.162 194.234.3.98 194.234.3.130 ... TOTAL 456 for *na: EU-GLOBALONE-NORTH-961222 *na: DSM-NET 163.175.153.2 TOTAL 1 for *na: DSM-NET *na: CH-INNET-960807 195.70.1.100 TOTAL 1 for *na: CH-INNET-960807 *na: IT-CLIO-961016 195.60.129.43 195.60.139.14 TOTAL 2 for *na: IT-CLIO-961016 *na: UK-IMMINUS-960603 193.193.121.68 TOTAL 1 for *na: UK-IMMINUS-960603 *na: UK-MAILBOX-970903 195.82.101.170 TOTAL 1 for *na: UK-MAILBOX-970903 *na: ISICOM-NET1 194.98.30.130 TOTAL 1 for *na: ISICOM-NET1 *na: BODILSENDK 195.215.139.158 TOTAL 1 for *na: BODILSENDK *na: CH-DECKPOINT-960708 194.38.168.242 TOTAL 1 for *na: CH-DECKPOINT-960708 *na: FR-COM-LESULIS 194.167.80.13 TOTAL 1 for *na: FR-COM-LESULIS *na: IMI-C-NET 193.70.60.3 TOTAL 1 for *na: IMI-C-NET *na: MAGIA-C-NET 193.70.50.231 TOTAL 1 for *na: MAGIA-C-NET *na: BASICPROPERTIES-C-NET 193.70.41.6 TOTAL 1 for *na: BASICPROPERTIES-C-NET *na: TAU-C-NET 193.70.31.2 193.70.31.45 193.70.31.101 TOTAL 3 for *na: TAU-C-NET *na: ITALWAY-C-NET 193.70.27.6 TOTAL 1 for *na: ITALWAY-C-NET *na: LOGIKOS-C-NET 193.70.26.72 TOTAL 1 for *na: LOGIKOS-C-NET *na: COSMOS-C-NET 193.70.6.3 TOTAL 1 for *na: COSMOS-C-NET *na: NETPOINT-S-NET 193.70.121.186 TOTAL 1 for *na: NETPOINT-S-NET *na: ICM-C-NET 193.70.96.18 193.70.96.81 193.70.96.130 TOTAL 3 for *na: ICM-C-NET *na: SIS-NET 193.70.16.1 193.70.16.19 TOTAL 2 for *na: SIS-NET *na: CONMET-C-NET 193.70.1.2 193.70.1.4 TOTAL 2 for *na: CONMET-C-NET *na: FR-ACADEMIE-GRENOBLE 195.221.234.122 TOTAL 1 for *na: FR-ACADEMIE-GRENOBLE *na: FR-ACADEMIE-GRENOBLE 193.54.149.10 193.54.149.18 TOTAL 2 for *na: FR-ACADEMIE-GRENOBLE *na: BH-BATELCO-960415 193.188.107.84 193.188.111.63 193.188.113.113 193.188.113.205 193.188.113.243 TOTAL 5 for *na: BH-BATELCO-960415 *na: BG-BASNET-980211 195.96.230.220 TOTAL 1 for *na: BG-BASNET-980211 *na: IL-EURONET-RG-981126 212.68.133.84 212.68.134.69 212.68.153.213 212.68.156.71 212.68.158.49 TOTAL 5 for *na: IL-EURONET-RG-981126 *na: AP-HOP-PARIS 164.2.255.241 TOTAL 1 for *na: AP-HOP-PARIS *na: FR-IWAY-981127 212.208.41.134 212.208.41.135 212.208.41.136 212.208.54.250 TOTAL 4 for *na: FR-IWAY-981127 *na: FR-IEMN-NET 193.51.54.2 193.51.54.59 193.51.54.65 TOTAL 3 for *na: FR-IEMN-NET *na: FR-IWAY-980206 212.208.41.134 212.208.41.135 212.208.41.136 212.208.54.250 TOTAL 4 for *na: FR-IWAY-980206 *na: BG-ITD-981130 212.116.133.130 TOTAL 1 for *na: BG-ITD-981130 *na: RU-MACOMNET-970312 195.128.73.200 195.128.81.13 TOTAL 2 for *na: RU-MACOMNET-970312 *na: RU-ROSTELECOM-970605 195.161.8.6 195.161.8.70 195.161.8.178 TOTAL 3 for *na: RU-ROSTELECOM-970605 *na: DE-CSL-GMBH-960222 194.245.33.226 194.245.40.2 194.245.40.40 TOTAL 3 for *na: DE-CSL-GMBH-960222 *na: HOLVRIEKADK 195.215.141.2 TOTAL 1 for *na: HOLVRIEKADK *na: BERLINGSKE-DK 195.24.2.194 195.24.2.197 195.24.2.198 195.24.2.200 195.24.2.202 195.24.2.203 195.24.2.209 195.24.2.212 TOTAL 8 for *na: BERLINGSKE-DK *na: VOLADK 195.215.140.179 TOTAL 1 for *na: VOLADK *na: AE-EMIRNET-971125 195.229.228.19 195.229.230.184 195.229.231.16 TOTAL 3 for *na: AE-EMIRNET-971125 *na: UUNET-DK 195.24.26.76 195.24.26.77 TOTAL 2 for *na: UUNET-DK *na: RUNTIMEDK 195.215.142.34 TOTAL 1 for *na: RUNTIMEDK *na: GDCDK 195.215.142.194 TOTAL 1 for *na: GDCDK *na: TDI 195.215.15.254 TOTAL 1 for *na: TDI *na: TDI 195.215.15.250 TOTAL 1 for *na: TDI *na: TDI 195.215.15.18 TOTAL 1 for *na: TDI *na: KIJAKADK 195.215.143.65 TOTAL 1 for *na: KIJAKADK *na: DKNET-44 193.88.44.10 193.88.44.21 193.88.44.22 193.88.44.23 193.88.44.29 193.88.44.35 193.88.44.36 193.88.44.42 193.88.44.43 193.88.44.45 193.88.44.47 193.88.44.48 193.88.44.60 193.88.44.152 193.88.44.155 193.88.44.194 TOTAL 16 for *na: DKNET-44 *na: SUNET 193.88.184.18 193.88.184.64 193.88.184.71 193.88.184.243 TOTAL 4 for *na: SUNET *na: BOSCHTELECOM 193.88.175.66 TOTAL 1 for *na: BOSCHTELECOM *na: RU-DEMOS-970415 195.133.0.8 195.133.8.85 195.133.61.61 TOTAL 3 for *na: RU-DEMOS-970415 *na: RU-DEMOS-940901 194.87.5.3 194.87.5.54 194.87.5.55 194.87.11.112 194.87.158.2 194.87.200.22 194.87.200.48 194.87.200.50 TOTAL 8 for *na: RU-DEMOS-940901 *na: COLORPRINT-DKDK 195.215.143.194 TOTAL 1 for *na: COLORPRINT-DKDK *na: SOTOFTEDK 195.215.144.22 TOTAL 1 for *na: SOTOFTEDK *na: DK-HOSTMASTER 195.215.15.2 195.215.15.4 TOTAL 2 for *na: DK-HOSTMASTER *na: DK-TELEDANMARK-950420 193.88.44.10 193.88.44.21 193.88.44.22 193.88.44.23 193.88.44.29 193.88.44.35 193.88.44.36 193.88.44.42 193.88.44.43 193.88.44.45 193.88.44.47 193.88.44.48 193.88.44.60 193.88.44.152 193.88.44.155 193.88.44.194 193.88.65.46 193.88.65.66 193.88.65.70 ... TOTAL 149 for *na: DK-TELEDANMARK-950420 *na: DK-TELEDANMARK-950920 194.182.129.11 194.182.129.12 194.182.129.37 194.182.129.50 194.182.129.53 194.182.129.67 194.182.129.76 194.182.144.66 194.182.150.154 194.182.150.171 TOTAL 10 for *na: DK-TELEDANMARK-950920 *na: DK-TELEDANMARK-950920 194.182.233.147 TOTAL 1 for *na: DK-TELEDANMARK-950920 *na: DK-TELEDANMARK-950829 194.192.16.2 194.192.17.226 194.192.17.234 194.192.17.245 194.192.20.82 194.192.20.86 194.192.22.2 194.192.22.9 194.192.22.11 194.192.23.1 194.192.64.130 194.192.64.162 194.192.70.10 194.192.80.73 194.192.80.92 194.192.87.4 194.192.94.2 194.192.96.2 194.192.98.129 ... TOTAL 45 for *na: DK-TELEDANMARK-950829 *na: DK-TELEDANMARK-960502 194.239.77.137 194.239.77.138 194.239.77.218 194.239.144.201 194.239.144.205 194.239.144.212 194.239.144.217 194.239.144.221 194.239.144.234 194.239.144.236 194.239.144.239 194.239.144.241 194.239.162.140 194.239.162.144 194.239.162.148 194.239.162.150 194.239.162.151 194.239.162.156 194.239.162.170 ... TOTAL 26 for *na: DK-TELEDANMARK-960502 *na: DK-TELEDANMARK-961204 195.41.117.130 195.41.117.133 195.41.138.66 195.41.138.71 195.41.138.72 195.41.142.138 195.41.217.2 195.41.217.8 TOTAL 8 for *na: DK-TELEDANMARK-961204 *na: DK-TELEDANMARK-971007 195.215.2.6 195.215.3.131 195.215.15.2 195.215.15.4 195.215.15.18 195.215.15.250 195.215.15.254 195.215.29.187 195.215.34.82 195.215.34.105 195.215.34.194 195.215.36.2 195.215.36.3 195.215.36.4 195.215.36.5 195.215.36.18 195.215.36.19 195.215.36.20 195.215.36.36 ... TOTAL 124 for *na: DK-TELEDANMARK-971007 *na: DK-TELEDANMARK-980107 195.249.16.2 195.249.16.194 195.249.32.18 195.249.33.7 195.249.33.8 195.249.33.9 195.249.33.10 195.249.33.11 195.249.33.12 195.249.33.13 195.249.33.16 195.249.33.21 195.249.33.22 195.249.33.25 195.249.33.27 195.249.33.28 195.249.33.30 195.249.33.34 195.249.33.35 ... TOTAL 3773 for *na: DK-TELEDANMARK-980107 *na: UMUNET 130.239.8.8 130.239.8.10 130.239.8.204 130.239.8.214 130.239.16.3 130.239.18.140 130.239.18.145 130.239.22.8 130.239.26.105 130.239.26.167 130.239.28.4 130.239.28.5 130.239.38.55 130.239.40.19 130.239.43.182 130.239.96.21 130.239.117.80 130.239.122.157 130.239.122.219 ... TOTAL 28 for *na: UMUNET *na: RU-MACOMNET-980710 212.5.77.34 TOTAL 1 for *na: RU-MACOMNET-980710 *na: PREFORM-DK 195.24.31.139 195.24.31.151 195.24.31.160 195.24.31.170 195.24.31.209 TOTAL 5 for *na: PREFORM-DK *na: PL-NASK-148-81 148.81.4.6 148.81.4.210 148.81.15.66 148.81.16.51 148.81.17.34 148.81.18.28 148.81.33.11 148.81.34.120 148.81.52.11 148.81.64.68 148.81.68.98 148.81.77.63 148.81.80.1 148.81.83.51 148.81.93.18 148.81.126.6 148.81.127.3 148.81.145.16 148.81.145.165 ... TOTAL 26 for *na: PL-NASK-148-81 *na: UK-PIPEX-19951207 194.216.51.2 TOTAL 1 for *na: UK-PIPEX-19951207 *na: UK-PIPEX-950921 194.200.207.10 194.200.207.139 194.200.207.151 194.200.207.155 194.200.207.174 194.200.207.200 194.200.207.232 194.202.125.96 194.202.125.152 194.202.125.195 TOTAL 10 for *na: UK-PIPEX-950921 *na: UK-PIPEX-193-128-133 193.128.12.2 193.131.13.151 193.131.65.10 193.133.22.53 193.133.96.130 193.133.111.45 193.133.111.50 TOTAL 7 for *na: UK-PIPEX-193-128-133 *na: UK-PIPEX-194-128-131 194.128.98.225 194.130.42.1 194.130.159.16 194.130.159.173 194.130.159.185 194.130.159.230 194.130.240.52 194.130.240.57 194.130.240.117 194.130.240.118 194.130.240.123 194.130.240.126 194.130.240.149 TOTAL 13 for *na: UK-PIPEX-194-128-131 *na: PIPEX-NET 158.43.4.26 158.43.4.42 158.43.17.138 158.43.17.182 158.43.34.162 158.43.52.2 158.43.55.38 158.43.56.6 158.43.56.102 158.43.56.106 158.43.69.78 158.43.74.246 158.43.109.2 158.43.128.8 158.43.128.11 158.43.128.25 158.43.128.26 158.43.128.38 158.43.128.41 ... TOTAL 78 for *na: PIPEX-NET *na: ASEDK 195.215.144.91 TOTAL 1 for *na: ASEDK *na: MONDIALDK 195.215.144.162 195.215.144.174 TOTAL 2 for *na: MONDIALDK *na: SPAENCOMDK 195.215.144.226 TOTAL 1 for *na: SPAENCOMDK *na: BA-BIHNET-970730 195.222.38.147 195.222.38.238 195.222.46.61 TOTAL 3 for *na: BA-BIHNET-970730 *na: DKNET-PIP-AALB 193.89.17.129 193.89.17.133 193.89.17.134 193.89.17.136 193.89.17.140 193.89.17.143 193.89.17.149 193.89.17.153 193.89.17.154 193.89.17.155 193.89.17.157 193.89.17.158 TOTAL 12 for *na: DKNET-PIP-AALB *na: DKNET-PIP-AARH 193.89.17.8 193.89.17.9 193.89.17.19 193.89.17.29 193.89.17.32 193.89.17.37 193.89.17.38 193.89.17.40 193.89.17.45 193.89.17.50 193.89.17.51 193.89.17.53 193.89.17.54 193.89.17.55 193.89.17.56 193.89.17.59 193.89.17.61 TOTAL 17 for *na: DKNET-PIP-AARH *na: NATIONALBANKENDK 195.215.143.254 TOTAL 1 for *na: NATIONALBANKENDK *na: ITID 194.192.20.82 194.192.20.86 TOTAL 2 for *na: ITID *na: AVSUNIRAS 193.89.40.13 193.89.40.40 TOTAL 2 for *na: AVSUNIRAS *na: DANTRANSPORT 193.162.16.5 193.162.16.34 193.162.16.35 193.162.17.225 TOTAL 4 for *na: DANTRANSPORT *na: INGNET 193.88.80.10 193.88.80.129 193.88.80.253 193.88.82.2 193.88.82.26 TOTAL 5 for *na: INGNET *na: RSA-DK 195.24.8.234 TOTAL 1 for *na: RSA-DK *na: DE-NACAMAR-970106 195.63.225.1 TOTAL 1 for *na: DE-NACAMAR-970106 *na: DE-NACAMAR-970805 195.185.146.52 TOTAL 1 for *na: DE-NACAMAR-970805 *na: DE-NACAMAR-970502 62.144.99.3 TOTAL 1 for *na: DE-NACAMAR-970502 *na: VIRTUALWWW-3 194.202.125.96 194.202.125.152 194.202.125.195 TOTAL 3 for *na: VIRTUALWWW-3 *na: VIRTUALWWW 194.200.207.10 194.200.207.139 194.200.207.151 194.200.207.155 194.200.207.174 194.200.207.200 194.200.207.232 TOTAL 7 for *na: VIRTUALWWW *na: GR-HOL-970303 195.97.24.2 TOTAL 1 for *na: GR-HOL-970303 *na: SOFTCOM-DK 195.24.31.66 195.24.31.67 TOTAL 2 for *na: SOFTCOM-DK *na: BKMED-DK 195.24.15.252 TOTAL 1 for *na: BKMED-DK *na: ES-MEDUSA-960710 194.140.53.2 TOTAL 1 for *na: ES-MEDUSA-960710 *na: RU-DSI-970728 195.206.50.1 TOTAL 1 for *na: RU-DSI-970728 *na: BILWINCOOM 195.215.145.146 TOTAL 1 for *na: BILWINCOOM *na: SILICONDK 195.215.145.193 195.215.145.194 195.215.145.219 TOTAL 3 for *na: SILICONDK *na: TRIPTRAPDK 195.215.146.129 195.215.146.130 TOTAL 2 for *na: TRIPTRAPDK *na: NV-POPS 62.0.128.40 62.0.128.86 62.0.128.107 62.0.128.138 62.0.145.135 62.0.145.139 62.0.145.232 62.0.146.8 62.0.146.10 62.0.146.89 62.0.149.78 62.0.149.100 62.0.152.1 62.0.153.19 62.0.153.39 62.0.153.194 62.0.154.12 62.0.154.211 62.0.154.235 ... TOTAL 30 for *na: NV-POPS *na: POLSL-NET 157.158.1.3 157.158.1.4 157.158.16.167 157.158.67.1 157.158.67.102 157.158.208.62 TOTAL 6 for *na: POLSL-NET *na: DZ-ARN-970407 193.194.95.105 193.194.95.185 TOTAL 2 for *na: DZ-ARN-970407 *na: DEN-SALVATIONARMY-ORG 195.215.146.211 TOTAL 1 for *na: DEN-SALVATIONARMY-ORG *na: CZ-CZECHNET-960130 194.213.235.175 TOTAL 1 for *na: CZ-CZECHNET-960130 *na: SE-PHARMA 193.180.21.2 193.180.21.10 TOTAL 2 for *na: SE-PHARMA *na: SE-SIGNUM 193.180.23.4 193.180.23.167 193.180.23.230 193.180.23.236 TOTAL 4 for *na: SE-SIGNUM *na: SE-EXPRESSEN 193.180.34.38 193.180.36.77 193.180.36.155 193.180.36.170 193.180.36.177 193.180.45.72 TOTAL 6 for *na: SE-EXPRESSEN *na: SE-GOTTHARD 193.180.58.7 193.180.58.22 193.180.58.254 TOTAL 3 for *na: SE-GOTTHARD *na: J-SAINSBURY 193.133.96.130 TOTAL 1 for *na: J-SAINSBURY *na: UK-MISTRAL-971114 195.184.226.162 TOTAL 1 for *na: UK-MISTRAL-971114 *na: TELIANET 62.20.128.15 62.20.132.55 62.20.132.84 62.20.132.85 62.20.132.90 62.20.132.127 62.20.132.134 62.20.132.153 62.20.132.175 62.20.132.180 62.20.132.241 62.20.132.243 62.20.133.61 62.20.133.86 62.20.133.120 62.20.133.125 62.20.133.148 62.20.133.180 62.20.133.198 ... TOTAL 248 for *na: TELIANET *na: TELIANET 195.67.156.39 195.67.156.52 195.67.156.132 195.67.156.241 195.67.157.23 195.67.157.101 195.67.157.164 195.67.157.241 195.67.157.243 TOTAL 9 for *na: TELIANET *na: TELIANET 195.67.188.67 195.67.188.150 195.67.188.183 195.67.188.209 195.67.188.235 195.67.188.241 195.67.188.243 195.67.189.11 195.67.189.34 195.67.189.74 195.67.189.85 195.67.189.144 195.67.189.241 195.67.190.123 195.67.190.127 195.67.190.151 195.67.190.209 195.67.190.241 195.67.190.242 ... TOTAL 100 for *na: TELIANET *na: DE-CALLISTO-970110 151.189.12.2 151.189.12.7 151.189.12.208 151.189.13.25 151.189.16.1 151.189.16.174 151.189.24.2 151.189.38.12 151.189.95.66 TOTAL 9 for *na: DE-CALLISTO-970110 *na: FFEI-NET 194.130.42.1 TOTAL 1 for *na: FFEI-NET *na: FR-EASYNET-970224 195.114.64.109 195.114.64.129 195.114.64.193 195.114.64.198 195.114.64.218 195.114.64.230 195.114.64.231 195.114.64.232 195.114.64.238 195.114.64.240 195.114.68.208 195.114.88.158 TOTAL 12 for *na: FR-EASYNET-970224 *na: SE-GBGGYM 193.180.65.151 193.180.82.165 193.180.84.106 TOTAL 3 for *na: SE-GBGGYM *na: SE-HBENERGY 193.180.104.9 193.180.104.10 193.180.104.12 193.180.104.23 193.180.104.252 193.180.104.254 TOTAL 6 for *na: SE-HBENERGY *na: SE-HBENERGY 193.180.106.148 193.180.108.172 193.180.108.188 TOTAL 3 for *na: SE-HBENERGY *na: SE-HBENERGY 193.180.113.89 193.180.113.91 TOTAL 2 for *na: SE-HBENERGY *na: SE-AGA 193.180.184.1 TOTAL 1 for *na: SE-AGA *na: SE-STRODE 193.180.197.10 TOTAL 1 for *na: SE-STRODE *na: SE-KM 193.180.207.1 TOTAL 1 for *na: SE-KM *na: SE-GOTKOM 193.180.228.194 TOTAL 1 for *na: SE-GOTKOM *na: SE-TRANAS-2 193.180.229.7 193.180.229.8 TOTAL 2 for *na: SE-TRANAS-2 *na: SE-BOSTADEN-NET 193.180.246.34 193.180.246.149 TOTAL 2 for *na: SE-BOSTADEN-NET *na: SE-LMSOFA 193.180.251.38 193.180.251.39 TOTAL 2 for *na: SE-LMSOFA *na: SE-VV 193.181.57.1 TOTAL 1 for *na: SE-VV *na: SE-D-DATA 193.181.154.17 193.181.154.65 TOTAL 2 for *na: SE-D-DATA *na: NL-WAPI-19990111 195.121.1.34 195.121.1.66 195.121.6.37 195.121.6.51 195.121.6.57 195.121.6.59 195.121.6.61 195.121.6.98 195.121.6.99 195.121.6.100 195.121.6.143 195.121.6.144 195.121.6.163 195.121.6.196 195.121.8.2 195.121.9.89 195.121.9.115 195.121.18.16 195.121.18.109 ... TOTAL 91 for *na: NL-WAPI-19990111 *na: SE-BLTID 193.181.241.3 193.181.241.170 TOTAL 2 for *na: SE-BLTID *na: MATAV 145.236.188.45 145.236.196.37 145.236.208.91 145.236.208.248 145.236.209.115 145.236.212.9 145.236.224.231 145.236.224.244 145.236.224.248 145.236.224.249 145.236.224.250 145.236.226.87 145.236.237.12 145.236.240.204 145.236.241.98 TOTAL 15 for *na: MATAV *na: KG-ASIAINFO-971015 195.38.187.33 TOTAL 1 for *na: KG-ASIAINFO-971015 *na: DE-OK-990112 212.72.65.4 TOTAL 1 for *na: DE-OK-990112 *na: WROCPOLIP 156.17.2.116 156.17.2.177 156.17.5.2 156.17.5.3 156.17.8.1 156.17.10.162 156.17.10.166 156.17.30.4 156.17.35.2 156.17.35.3 156.17.35.8 156.17.35.27 156.17.55.101 156.17.71.34 156.17.71.47 156.17.108.1 156.17.108.26 156.17.204.14 156.17.209.162 ... TOTAL 22 for *na: WROCPOLIP *na: PT-RCCN-193-136-137 193.136.0.1 193.136.185.191 193.137.7.1 193.137.56.17 193.137.56.21 193.137.68.17 193.137.127.65 193.137.127.129 193.137.239.226 TOTAL 9 for *na: PT-RCCN-193-136-137 *na: SE-COMPUTERLAND-NET1 193.14.2.5 TOTAL 1 for *na: SE-COMPUTERLAND-NET1 *na: SE-OW 193.12.198.82 193.12.198.98 TOTAL 2 for *na: SE-OW *na: SE-TERACOM-NET1 193.12.205.1 TOTAL 1 for *na: SE-TERACOM-NET1 *na: SE-NETTIME-NET1 193.12.209.1 193.12.209.37 TOTAL 2 for *na: SE-NETTIME-NET1 *na: SE-EVERY-NET1 193.12.243.4 193.12.243.40 193.12.243.59 193.12.243.62 193.12.243.75 193.12.243.104 193.12.243.150 TOTAL 7 for *na: SE-EVERY-NET1 *na: SE-DALSLAND-NET1 193.12.255.26 193.12.255.253 TOTAL 2 for *na: SE-DALSLAND-NET1 *na: SE-RADIOD-NET1 193.13.14.38 TOTAL 1 for *na: SE-RADIOD-NET1 *na: IT-INTERBUSINESS-950606 151.99.133.1 151.99.133.129 151.99.197.10 151.99.197.15 151.99.238.35 151.99.238.44 151.99.247.2 151.99.247.7 151.99.250.2 151.99.250.6 151.99.250.31 151.99.250.32 TOTAL 12 for *na: IT-INTERBUSINESS-950606 *na: SE-LKOMMUN-NET 193.13.15.2 193.13.15.3 193.13.15.7 193.13.15.31 193.13.15.71 TOTAL 5 for *na: SE-LKOMMUN-NET *na: SE-POLHEM-NET1 193.13.20.253 TOTAL 1 for *na: SE-POLHEM-NET1 *na: SE-HALDEX 193.13.23.220 TOTAL 1 for *na: SE-HALDEX *na: SE-ATVDA-NET1 193.13.28.1 TOTAL 1 for *na: SE-ATVDA-NET1 *na: SE-MATTEUS-NET1 193.13.53.30 193.13.53.42 TOTAL 2 for *na: SE-MATTEUS-NET1 *na: SE-BT-NET 193.13.114.18 193.13.114.31 TOTAL 2 for *na: SE-BT-NET *na: SE-FLT-NET 193.13.115.80 TOTAL 1 for *na: SE-FLT-NET *na: SE-KRISTIANSTAD-NET1 193.13.129.16 193.13.129.41 193.13.129.53 193.13.129.66 193.13.129.116 193.13.129.120 193.13.129.143 193.13.129.183 193.13.129.203 193.13.129.250 TOTAL 10 for *na: SE-KRISTIANSTAD-NET1 *na: SE-TIDTALJE-NET 193.13.135.1 TOTAL 1 for *na: SE-TIDTALJE-NET *na: SE-FALUKURIR-NET1 193.13.136.253 TOTAL 1 for *na: SE-FALUKURIR-NET1 *na: SE-LAGERCRANTZ-EL-NET1 193.13.140.4 193.13.140.14 193.13.141.3 193.13.141.10 193.13.141.13 TOTAL 5 for *na: SE-LAGERCRANTZ-EL-NET1 *na: SE-VARBERGENERGI-NET1 193.13.151.2 193.13.151.45 193.13.151.130 193.13.151.144 193.13.151.184 TOTAL 5 for *na: SE-VARBERGENERGI-NET1 *na: SE-AGEMA-NET1 193.13.175.130 TOTAL 1 for *na: SE-AGEMA-NET1 *na: SE-DATARUTIN-NET3 193.13.176.1 TOTAL 1 for *na: SE-DATARUTIN-NET3 *na: SE-AXIS-NET1 193.13.178.2 193.13.178.7 193.13.178.10 TOTAL 3 for *na: SE-AXIS-NET1 *na: SE-BIZIT-NET1 193.13.179.10 193.13.179.106 193.13.179.114 193.13.179.155 193.13.179.161 TOTAL 5 for *na: SE-BIZIT-NET1 *na: SE-FREDRIKA-NET1 193.13.222.15 193.13.222.53 193.13.222.58 TOTAL 3 for *na: SE-FREDRIKA-NET1 *na: SE-ITT1-NET1 193.13.224.252 TOTAL 1 for *na: SE-ITT1-NET1 *na: SE-DATAOFFICE-NET1 193.13.229.11 TOTAL 1 for *na: SE-DATAOFFICE-NET1 *na: SE-BULLERDATA-NET1 193.13.231.1 193.13.231.2 193.13.231.21 193.13.231.152 193.13.231.182 193.13.231.196 193.13.231.207 TOTAL 7 for *na: SE-BULLERDATA-NET1 *na: SE-IDG-NET1 193.13.235.50 193.13.235.51 193.13.235.52 193.13.235.91 193.13.235.98 193.13.235.99 193.13.235.129 193.13.235.140 193.13.235.194 193.13.235.196 TOTAL 10 for *na: SE-IDG-NET1 *na: SE-MEMORY-NET 193.13.247.17 193.13.247.75 193.13.247.114 TOTAL 3 for *na: SE-MEMORY-NET *na: SE-MEDO-NET1 193.13.252.60 TOTAL 1 for *na: SE-MEDO-NET1 *na: SE-MM-NET 193.13.144.1 193.13.144.2 193.13.144.16 193.13.144.46 193.13.144.61 TOTAL 5 for *na: SE-MM-NET *na: SE-CARNEGIE-NET1 193.13.182.10 193.13.182.11 193.13.182.20 TOTAL 3 for *na: SE-CARNEGIE-NET1 *na: SE-TYCHOBRAHE-NET1 193.14.3.3 TOTAL 1 for *na: SE-TYCHOBRAHE-NET1 *na: SE-ARVIKA-NET1 193.14.10.129 TOTAL 1 for *na: SE-ARVIKA-NET1 *na: SE-GRAFCE-NET1 193.14.12.88 TOTAL 1 for *na: SE-GRAFCE-NET1 *na: SE-IM-NET1 193.14.22.222 TOTAL 1 for *na: SE-IM-NET1 *na: SE-HYPER-NET1 193.14.26.1 193.14.26.209 193.14.26.229 TOTAL 3 for *na: SE-HYPER-NET1 *na: SE-PAGINA-NET1 193.14.45.16 TOTAL 1 for *na: SE-PAGINA-NET1 *na: SE-ALE-NET1 193.14.51.70 TOTAL 1 for *na: SE-ALE-NET1 *na: SE-EKSJO-NET1 193.14.53.10 193.14.53.21 TOTAL 2 for *na: SE-EKSJO-NET1 *na: SE-SP-NET1 193.14.55.39 193.14.55.64 193.14.55.123 193.14.55.223 193.14.55.230 193.14.55.252 TOTAL 6 for *na: SE-SP-NET1 *na: SE-FOLKUNIVERSITETET-NET1 193.14.60.3 193.14.60.253 TOTAL 2 for *na: SE-FOLKUNIVERSITETET-NET1 *na: SE-STHLMMASSAN-NET1 193.14.63.130 TOTAL 1 for *na: SE-STHLMMASSAN-NET1 *na: SE-RALTON-NET1 193.14.66.10 193.14.66.230 TOTAL 2 for *na: SE-RALTON-NET1 *na: SE-MAGAZINE-NET1 193.14.67.1 193.14.67.83 TOTAL 2 for *na: SE-MAGAZINE-NET1 *na: SE-LIBER 193.14.71.219 193.14.71.221 193.14.71.253 TOTAL 3 for *na: SE-LIBER *na: SE-TYCHOBRAHE-NET2 193.14.75.101 TOTAL 1 for *na: SE-TYCHOBRAHE-NET2 *na: SE-USIS-NET1 193.14.78.1 TOTAL 1 for *na: SE-USIS-NET1 *na: SE-INFOM-NET1 193.14.81.1 193.14.81.11 TOTAL 2 for *na: SE-INFOM-NET1 *na: SE-QD1-NET1 193.14.86.220 TOTAL 1 for *na: SE-QD1-NET1 *na: SE-MALMOSTAD-NET1 193.14.94.100 193.14.94.109 193.14.94.188 193.14.94.215 193.14.94.253 TOTAL 5 for *na: SE-MALMOSTAD-NET1 *na: SE-FILBORNASKOLAN-NET1 193.14.103.101 193.14.103.252 TOTAL 2 for *na: SE-FILBORNASKOLAN-NET1 *na: SE-IKONMEDIA-NET1 193.14.104.1 193.14.104.2 193.14.104.70 TOTAL 3 for *na: SE-IKONMEDIA-NET1 *na: SSC-NET1 193.14.109.53 TOTAL 1 for *na: SSC-NET1 *na: SE-PROGRAMB-NET1 193.14.113.1 193.14.113.9 TOTAL 2 for *na: SE-PROGRAMB-NET1 *na: SE-NECTAR-NET1 193.14.116.1 TOTAL 1 for *na: SE-NECTAR-NET1 *na: SE-METRO-NET1 193.14.118.100 193.14.118.104 TOTAL 2 for *na: SE-METRO-NET1 *na: SE-SOFIASK-NET1 193.14.120.149 TOTAL 1 for *na: SE-SOFIASK-NET1 *na: SE-ADELFORSSK-NET1 193.14.125.2 TOTAL 1 for *na: SE-ADELFORSSK-NET1 *na: SE-BORGHOLM-NET1 193.14.135.89 TOTAL 1 for *na: SE-BORGHOLM-NET1 *na: SE-ACOM-NET1 193.14.144.200 TOTAL 1 for *na: SE-ACOM-NET1 *na: SE-BAHNHOF-NET1 193.14.145.193 193.14.145.227 193.14.145.229 TOTAL 3 for *na: SE-BAHNHOF-NET1 *na: SE-INGRAM-NET1 193.14.147.220 TOTAL 1 for *na: SE-INGRAM-NET1 *na: SE-VARBERGENERGI-NET2 193.14.149.2 193.14.149.116 TOTAL 2 for *na: SE-VARBERGENERGI-NET2 *na: SE-NIKOLAISKOLAN-NET1 193.14.153.161 TOTAL 1 for *na: SE-NIKOLAISKOLAN-NET1 *na: SE-SPPI-NET1 193.14.160.50 TOTAL 1 for *na: SE-SPPI-NET1 *na: SE-SYSTEMBOLAGETI-NET1 193.14.160.67 193.14.160.74 TOTAL 2 for *na: SE-SYSTEMBOLAGETI-NET1 *na: SE-LIMT-NET1 193.14.160.130 TOTAL 1 for *na: SE-LIMT-NET1 *na: SE-ELLOS-NET1 193.14.160.202 193.14.160.203 TOTAL 2 for *na: SE-ELLOS-NET1 *na: SE-YSTAD-NET1 193.14.161.97 TOTAL 1 for *na: SE-YSTAD-NET1 *na: LRF-NET2 193.14.162.66 TOTAL 1 for *na: LRF-NET2 *na: SE-SIDA-NET1 193.14.162.82 193.14.162.83 TOTAL 2 for *na: SE-SIDA-NET1 *na: SE-SORMAN-NET1 193.14.162.98 TOTAL 1 for *na: SE-SORMAN-NET1 *na: SE-TRANSCOM-NET1 193.14.163.134 193.14.163.140 TOTAL 2 for *na: SE-TRANSCOM-NET1 *na: SPARBANKEN-FINN-NET1 193.14.163.216 TOTAL 1 for *na: SPARBANKEN-FINN-NET1 *na: SE-HADAB-NET1 193.14.165.6 193.14.165.8 TOTAL 2 for *na: SE-HADAB-NET1 *na: SE-DDNG-NET1 193.14.165.132 TOTAL 1 for *na: SE-DDNG-NET1 *na: SE-UBI-NET1 193.14.168.2 TOTAL 1 for *na: SE-UBI-NET1 *na: SE-INFOWAY-NET1 193.14.170.78 193.14.170.79 TOTAL 2 for *na: SE-INFOWAY-NET1 *na: EU-EUNET-960405 195.0.49.130 TOTAL 1 for *na: EU-EUNET-960405 *na: SE-MICROTRONICA-NET 193.14.172.130 TOTAL 1 for *na: SE-MICROTRONICA-NET *na: SE-EUROFLORIST-NET1 193.14.173.130 TOTAL 1 for *na: SE-EUROFLORIST-NET1 *na: SE-BUSINESS-NET1 193.14.173.218 193.14.173.219 193.14.173.222 TOTAL 3 for *na: SE-BUSINESS-NET1 *na: EU-EUNET-960726 193.95.194.113 193.95.206.133 TOTAL 2 for *na: EU-EUNET-960726 *na: SE-SCANDI-NET2 193.14.174.9 TOTAL 1 for *na: SE-SCANDI-NET2 *na: SE-HOGANAS-NET1 193.14.174.242 TOTAL 1 for *na: SE-HOGANAS-NET1 *na: SE-AVISA-NET1 193.14.175.12 TOTAL 1 for *na: SE-AVISA-NET1 *na: SE-ATLASCOPCO-NET1 193.14.199.253 TOTAL 1 for *na: SE-ATLASCOPCO-NET1 *na: SE-EUROPEDU-NET1 193.14.200.1 193.14.200.2 193.14.200.3 193.14.200.7 193.14.200.8 193.14.200.12 193.14.200.13 193.14.200.17 193.14.200.60 193.14.200.99 TOTAL 10 for *na: SE-EUROPEDU-NET1 *na: SE-CROSSNET-NET1 193.14.201.5 193.14.201.10 193.14.201.12 193.14.201.14 193.14.201.21 TOTAL 5 for *na: SE-CROSSNET-NET1 *na: SE-MEDANETWORK-NET1 193.14.204.1 193.14.204.62 193.14.204.140 TOTAL 3 for *na: SE-MEDANETWORK-NET1 *na: SE-IBS-NET1 193.14.205.5 193.14.205.7 193.14.205.14 TOTAL 3 for *na: SE-IBS-NET1 *na: SE-ECOLINE-NET1 193.14.227.62 TOTAL 1 for *na: SE-ECOLINE-NET1 *na: SE-INSTFORSK-NET1 193.14.239.140 TOTAL 1 for *na: SE-INSTFORSK-NET1 *na: SE-ASOGYMN-NET 193.14.244.126 TOTAL 1 for *na: SE-ASOGYMN-NET *na: SE-OFFICINEN 193.13.29.235 TOTAL 1 for *na: SE-OFFICINEN *na: SE-HALLPOST1-NET 193.13.112.66 TOTAL 1 for *na: SE-HALLPOST1-NET *na: SE-HALLPOST2-NET 193.13.121.10 TOTAL 1 for *na: SE-HALLPOST2-NET *na: SE-AFTON 193.13.160.144 193.13.160.180 193.13.160.200 193.13.161.2 TOTAL 4 for *na: SE-AFTON *na: SE-BONNIER-NET1 193.14.43.90 TOTAL 1 for *na: SE-BONNIER-NET1 *na: SE-TV3-NET1 193.14.64.1 193.14.64.14 193.14.64.20 193.14.64.100 TOTAL 4 for *na: SE-TV3-NET1 *na: SE-GBP-NET1 193.14.195.40 193.14.195.50 TOTAL 2 for *na: SE-GBP-NET1 *na: SE-FIBD 193.14.210.200 TOTAL 1 for *na: SE-FIBD *na: SE-LUND 193.14.211.2 193.14.211.3 193.14.212.9 193.14.212.71 193.14.212.109 193.14.212.111 193.14.212.135 193.14.212.165 193.14.212.212 193.14.213.101 TOTAL 10 for *na: SE-LUND *na: SE-DATAPLUS-NET1 193.14.88.250 TOTAL 1 for *na: SE-DATAPLUS-NET1 *na: SE-KOMVUXKUNGALV-NET2 193.13.217.14 TOTAL 1 for *na: SE-KOMVUXKUNGALV-NET2 *na: SE-CEDERROTH1-NET1 193.14.100.10 TOTAL 1 for *na: SE-CEDERROTH1-NET1 *na: CZ-NETFORCE-960110 194.213.206.48 TOTAL 1 for *na: CZ-NETFORCE-960110 *na: CON-INKDK 195.215.149.146 TOTAL 1 for *na: CON-INKDK *na: UA-ALKAR-971007 195.248.166.36 TOTAL 1 for *na: UA-ALKAR-971007 *na: RANDHS 193.89.57.9 193.89.57.29 193.89.57.47 193.89.57.82 193.89.57.104 193.89.57.115 193.89.57.122 TOTAL 7 for *na: RANDHS *na: INSERT 193.95.194.113 TOTAL 1 for *na: INSERT *na: SE-SONERA-960723 195.84.56.22 195.84.122.131 195.84.122.132 195.84.134.226 TOTAL 4 for *na: SE-SONERA-960723 *na: HAHADK 195.215.151.242 TOTAL 1 for *na: HAHADK *na: OXFORD-UNIV 163.1.2.1 163.1.2.9 163.1.7.48 163.1.16.100 163.1.21.102 163.1.29.191 163.1.67.206 163.1.80.29 163.1.136.80 163.1.137.3 163.1.138.66 163.1.138.183 163.1.144.109 163.1.146.5 163.1.162.79 163.1.164.157 163.1.219.1 163.1.219.77 163.1.244.140 ... TOTAL 21 for *na: OXFORD-UNIV *na: DE-EUNET-193-96-193-103 193.103.207.35 193.103.207.36 TOTAL 2 for *na: DE-EUNET-193-96-193-103 *na: SE-MSC 193.182.113.10 TOTAL 1 for *na: SE-MSC *na: SE-ABRA 193.182.122.10 TOTAL 1 for *na: SE-ABRA *na: SE-ADBDOK 193.182.146.102 TOTAL 1 for *na: SE-ADBDOK *na: SE-STORTORP 193.182.150.1 TOTAL 1 for *na: SE-STORTORP *na: SE-TECATOR 193.182.166.2 TOTAL 1 for *na: SE-TECATOR *na: SE-HELDAG 193.182.171.150 193.182.172.114 TOTAL 2 for *na: SE-HELDAG *na: SE-SYDSVENSK2 193.182.191.113 193.182.191.114 TOTAL 2 for *na: SE-SYDSVENSK2 *na: SE-REKTOR 193.182.241.234 TOTAL 1 for *na: SE-REKTOR *na: SE-IMS 193.183.19.65 193.183.19.100 TOTAL 2 for *na: SE-IMS *na: SE-PROGAMENIUS 193.183.49.8 TOTAL 1 for *na: SE-PROGAMENIUS *na: SE-TIPS 193.183.60.1 TOTAL 1 for *na: SE-TIPS *na: SE-LUXNET 193.183.68.17 TOTAL 1 for *na: SE-LUXNET *na: UA-LUCKYNET-980414 62.244.59.134 TOTAL 1 for *na: UA-LUCKYNET-980414 *na: UK-ASPEN-960722 194.93.128.1 194.93.128.2 194.93.128.3 194.93.128.28 194.93.133.1 194.93.134.3 194.93.134.119 194.93.154.49 TOTAL 8 for *na: UK-ASPEN-960722 *na: SE-JONKOM 193.183.204.3 193.183.205.2 193.183.212.211 193.183.212.230 193.183.213.2 193.183.213.254 193.183.214.2 193.183.214.4 193.183.215.4 193.183.216.2 193.183.216.5 193.183.217.2 193.183.218.157 TOTAL 13 for *na: SE-JONKOM *na: SE-TT 193.183.175.252 TOTAL 1 for *na: SE-TT *na: SE-STHBIB 193.183.252.153 TOTAL 1 for *na: SE-STHBIB *na: SE-HUDDINGE 193.183.253.2 TOTAL 1 for *na: SE-HUDDINGE *na: SE-NB 193.234.191.242 193.234.191.244 TOTAL 2 for *na: SE-NB *na: SE-CAPMEL 193.234.247.10 TOTAL 1 for *na: SE-CAPMEL *na: UNISOURCE-BB 194.151.224.7 194.151.231.130 194.151.231.194 194.151.234.18 TOTAL 4 for *na: UNISOURCE-BB *na: EU-EUNET-19960315 193.68.143.254 193.68.172.1 193.68.203.74 TOTAL 3 for *na: EU-EUNET-19960315 *na: EU-EUNET-19950315 193.126.4.65 193.126.4.67 193.126.8.65 193.126.16.230 193.126.18.189 193.126.90.1 TOTAL 6 for *na: EU-EUNET-19950315 *na: EU-EUNET-19940215 193.95.100.6 TOTAL 1 for *na: EU-EUNET-19940215 *na: FR-FTH 193.252.251.253 TOTAL 1 for *na: FR-FTH *na: SE-SKOPRI 193.235.16.226 TOTAL 1 for *na: SE-SKOPRI *na: SE-THORSMAN-2 193.235.17.3 193.235.17.33 TOTAL 2 for *na: SE-THORSMAN-2 *na: SE-TIPS-2 193.235.21.40 TOTAL 1 for *na: SE-TIPS-2 *na: SE-SDS 193.235.48.53 TOTAL 1 for *na: SE-SDS *na: SE-ADA 193.235.76.171 TOTAL 1 for *na: SE-ADA *na: SE-NORRKOM 193.235.87.109 193.235.88.87 193.235.89.1 193.235.89.27 193.235.89.122 193.235.95.250 TOTAL 6 for *na: SE-NORRKOM *na: SE-PRESSB2 193.235.118.30 193.235.118.37 TOTAL 2 for *na: SE-PRESSB2 *na: SE-DIGEST 193.235.223.10 TOTAL 1 for *na: SE-DIGEST *na: SE-PHARMDATA 193.235.229.100 TOTAL 1 for *na: SE-PHARMDATA *na: FR-WANADOO 193.252.126.150 193.252.127.165 193.252.130.165 193.252.131.155 193.252.131.201 193.252.134.38 193.252.135.250 193.252.136.30 193.252.136.141 193.252.138.55 193.252.139.68 193.252.139.240 193.252.139.252 193.252.141.5 193.252.141.109 193.252.141.125 193.252.141.248 193.252.143.243 193.252.144.48 ... TOTAL 115 for *na: FR-WANADOO *na: FR-WANADOO 194.51.238.1 194.51.238.2 TOTAL 2 for *na: FR-WANADOO *na: IPPNET 130.183.1.21 130.183.70.10 130.183.72.185 TOTAL 3 for *na: IPPNET *na: SE-SMART 194.14.81.162 194.14.81.174 194.14.81.175 194.14.81.181 194.14.81.182 TOTAL 5 for *na: SE-SMART *na: SE-PRIVGIRO 194.14.98.17 TOTAL 1 for *na: SE-PRIVGIRO *na: CH-PETREL-961017 195.15.82.115 195.15.83.231 195.15.196.11 195.15.196.41 195.15.196.51 TOTAL 5 for *na: CH-PETREL-961017 ----------------------------------------------------------------------- -- Poul-Henning Kamp FreeBSD coreteam member phk at FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! From neil at COLT.NET Thu Feb 11 11:01:05 1999 From: neil at COLT.NET (Neil J. McRae) Date: Thu, 11 Feb 1999 10:01:05 +0000 Subject: lowering maximum assignment window In-Reply-To: Your message of "Wed, 10 Feb 1999 20:46:21 +0100." <23395.918675981@critter.freebsd.dk> Message-ID: <199902111001.KAA17677@NetBSD.noc.COLT.NET> On Wed, 10 Feb 1999 20:46:21 +0100 Poul-Henning Kamp wrote: Excellent email! Poul: > COLT-980422 > 212.36.142.211 > 212.36.142.214 > 212.36.142.215 > 212.36.142.222 > 212.36.142.223 > 212.36.142.225 > TOTAL 6 for *na: UK-COLT-980422 Oops, not sure what happened here but its being resoloved now. Typical that our most busy customer isn't registered sigh :-) -- Neil J. McRae - Alive and Kicking. C O L T I N T E R N E T neil at COLT.NET NetBSD-1.3.3 released! ftp://ftp.uk.netbsd.org/pub/NetBSD Free the daemon in your computer! From paula at ripe.net Thu Feb 11 11:37:33 1999 From: paula at ripe.net (Paula Caslav) Date: Thu, 11 Feb 1999 11:37:33 +0100 Subject: lowering maximum assignment window In-Reply-To: Your message of Wed, 10 Feb 1999 20:46:21 +0100. <23395.918675981@critter.freebsd.dk> References: <23395.918675981@critter.freebsd.dk> Message-ID: <199902111037.LAA15359@x30.ripe.net> Hello all, It's good to see so much discussion on this topic. This is an excellent tool and I have already started discussion with Poul-Henning on how we can put it to some use. On Stephen Burley's proposal to lower the assignment windows of the /19 registries temporarily and raise it again after they've shown that they understand the procedures. I think that's a good way of approaching it, however, I would hesitate to raise the assignment window back to a full /19. I think it would be better to raise it to an amount that matches the size of the requests that we've seen from the registry. For example if we temporarily lower the assignment window to a /23 and we suddenly get a few very good requests that are around the size of a /22, wouldn't it be better to raise the assignment window to a /22 since that seems to match the Registry's needs better? If I look at the assignments made by Registries that have /19 assignment windows, most of them rarely make assignments larger than a /21. I suppose that if there is a registry that often makes /20 or /19 assignments, after they send several of these assignments to us, and we see that they understand the policies fully and are using addresses efficiently, we could consider giving them a /20 or /19 assignment window after all. However, I don't expect this to happen in most cases since most Registries just don't make this size of assignments frequently. Kind regards, Paula Caslav RIPE NCC Poul-Henning Kamp writes: * * Stephen, * * Just for reference, I ran over 12-14h worth of trafic data (cisco * NetFlow), starting at jan27 midnight, looking for source IP numbers * which have a RIPE record of status "ALLOCATED" but not one of * "ASSIGNED". * * Apart from some special case legacy records in the RIPE database * there clearly shouldn't be more than a few transient records while * reality and database is trying to catch up with each other. * * Well, "ain't necessarily so" as they sang. * * Since I found problems with 898 inetnum objects in total about , * I take the liberty of including the abbreviated output from my * analysis in this email, the majority of people on this list has * a entry or two to examine in more detail. * * These data are of course skewed by the location in the network * where the data has been recorded (AS6785/Denmark), our close * neighbors will be "oversampled" compared to distant LIRs in different * cultures and language areas (since we don't have any major porn-servers * on our site). * * Once you start to examine the output, some classes emerge: * * 1. "We don't care about/understand the RIPE-DB as long as we can * allocate IP numbers to our customers" * * 2. "Typo/Braino", s/ASSIGNED/ALLOCATED/ for instance. * * 3. Test IP numbers. * * 4. Legacy registrations. * * 5. Transient phenomena. * * Classes 3, 4 & 5 doesn't really need anything done about them for * now. * * Class 2 should just be pointed out and we can expect it to be * fixed ASAP, if it isn't: transfer it to category #1. * * Class 1 on the other hand, at least in my opinion, are prime * candidates for slamming the assignment window shut, auditing every * single assignments done by that LIR and resetting the slow-start * criteria until they have their act put together. * * Poul-Henning * * * PS: I have offered Paula to email this report to her automatically * every day if she wants it, if people want it, I can also stick it * on a web-server for anyone who wants it. * * PPS: A lot of the Class 2 entries can be found by going through * the database looking for entries having: * "*st: ALLOCATED ..." * but lacking * "*mb: RIPE-NCC-HM-MNT" * * --------------------------------------------------------------------- -- * *na: RU-RELCOM-194-135 * 194.135.153.226 * TOTAL 1 for *na: RU-RELCOM-194-135 * * *na: GR-FORTHNET-193-92 * 193.92.123.18 * 193.92.123.225 * 193.92.123.253 * TOTAL 3 for *na: GR-FORTHNET-193-92 * * *na: IS-ISNET-194-144 * 194.144.241.225 * TOTAL 1 for *na: IS-ISNET-194-144 * * *na: EU-ZZ-193-194 * 193.194.63.82 * 193.194.63.83 * 193.194.95.105 * 193.194.95.185 * TOTAL 4 for *na: EU-ZZ-193-194 * * *na: SE-SUNET-193-10 * 193.10.7.205 * 193.10.12.25 * 193.10.36.7 * 193.10.38.123 * 193.10.38.139 * 193.10.40.128 * 193.10.48.2 * 193.10.48.5 * 193.10.53.49 * 193.10.53.69 * 193.10.53.186 * 193.10.62.6 * 193.10.80.42 * 193.10.81.33 * 193.10.102.199 * 193.10.105.24 * 193.10.105.89 * 193.10.105.226 * 193.10.107.3 * ... * TOTAL 74 for *na: SE-SUNET-193-10 * * *na: FR-RENATER-193-48-193-52 * 193.51.54.2 * 193.51.54.59 * 193.51.54.65 * TOTAL 3 for *na: FR-RENATER-193-48-193-52 * * *na: FR-RENATER-193-54-193-55 * 193.54.149.10 * 193.54.149.18 * TOTAL 2 for *na: FR-RENATER-193-54-193-55 * * *na: UK-JANET-193-60-193-63 * 193.61.255.3 * 193.62.23.13 * 193.62.111.1 * 193.62.135.51 * 193.63.235.1 * TOTAL 5 for *na: UK-JANET-193-60-193-63 * * *na: CZ-CESNET-194-212-16 * 194.212.137.1 * TOTAL 1 for *na: CZ-CESNET-194-212-16 * * *na: EU-EUNET-193-77 * 193.77.152.253 * TOTAL 1 for *na: EU-EUNET-193-77 * * *na: NL-NLNET-193-78-193-79 * 193.79.207.6 * 193.79.207.7 * 193.79.207.8 * TOTAL 3 for *na: NL-NLNET-193-78-193-79 * * *na: AT-EUNET-193-80 * 193.80.106.55 * TOTAL 1 for *na: AT-EUNET-193-80 * * *na: AT-EUNET-193-81 * 193.81.83.2 * 193.81.83.3 * TOTAL 2 for *na: AT-EUNET-193-81 * * *na: FR-EUNET-193-104-193-107 * 193.104.109.9 * 193.105.95.2 * 193.105.95.31 * 193.106.183.50 * 193.106.197.2 * 193.106.229.3 * 193.107.5.2 * 193.107.191.72 TOTAL 8 for *na: FR-EUNET-193-104-193-107 * * *na: RU-RELCOM-193-124-125 * 193.124.171.67 * 193.125.193.178 * 193.125.193.180 * 193.125.193.226 * TOTAL 4 for *na: RU-RELCOM-193-124-125 * * *na: NO-UNINETT-193-156-193-157 * 193.156.55.186 * 193.156.55.200 * 193.156.55.201 * TOTAL 3 for *na: NO-UNINETT-193-156-193-157 * * *na: UK-ISTEL-193-169 * 193.169.153.29 * 193.169.153.68 * 193.169.153.81 * TOTAL 3 for *na: UK-ISTEL-193-169 * * *na: AT-ACONET-193-170-193-171 * 193.170.161.222 * TOTAL 1 for *na: AT-ACONET-193-170-193-171 * * *na: DE-DFN-193-174-193-175 * 193.174.73.75 * 193.174.73.80 * 193.175.127.239 * 193.175.191.132 * TOTAL 4 for *na: DE-DFN-193-174-193-175 * * *na: JO-NIC-193-188-64-95 * 193.188.84.99 * TOTAL 1 for *na: JO-NIC-193-188-64-95 * * *na: EU-ZZ-193-0-255 * 193.189.172.2 * 193.189.182.31 * 193.189.182.68 * 193.189.182.77 * 193.189.182.156 * 193.189.183.102 * 193.189.186.33 * 193.189.191.29 * 193.189.191.106 * 193.189.231.194 * 193.189.250.194 * TOTAL 11 for *na: EU-ZZ-193-0-255 * * *na: EU-IBM-194-196-16 * 194.196.53.194 * 194.196.53.210 * 194.196.119.33 * TOTAL 3 for *na: EU-IBM-194-196-16 * * *na: FR-TELECOM-248-253 * 193.252.126.150 * 193.252.127.165 * 193.252.130.165 * 193.252.131.155 * 193.252.131.201 * 193.252.134.38 * 193.252.135.250 * 193.252.136.30 * 193.252.136.141 * 193.252.138.55 * 193.252.139.68 * 193.252.139.240 * 193.252.139.252 * 193.252.141.5 * 193.252.141.109 * 193.252.141.125 * 193.252.141.248 * 193.252.143.243 * 193.252.144.48 * ... * TOTAL 123 for *na: FR-TELECOM-248-253 * * *na: LT-OMNITEL-960119 * 194.176.42.34 * TOTAL 1 for *na: LT-OMNITEL-960119 * * *na: IE-IOL-960123 * 194.125.107.2 * TOTAL 1 for *na: IE-IOL-960123 * * *na: AT-APA-960125 * 194.232.198.1 * 194.232.199.193 * 194.232.209.38 * 194.232.209.172 * 194.232.209.205 * TOTAL 5 for *na: AT-APA-960125 * * *na: SE-SUNET-960201 * 194.47.0.30 * 194.47.1.11 * 194.47.16.32 * 194.47.17.165 * 194.47.25.8 * 194.47.27.190 * 194.47.29.146 * 194.47.38.61 * 194.47.47.12 * 194.47.49.5 * 194.47.50.19 * 194.47.55.18 * 194.47.55.213 * 194.47.65.11 * 194.47.81.215 * 194.47.89.77 * 194.47.99.36 * 194.47.99.100 * 194.47.103.119 * ... * TOTAL 22 for *na: SE-SUNET-960201 * * *na: UK-ZZ-193-35-193-39 * 193.35.223.99 * TOTAL 1 for *na: UK-ZZ-193-35-193-39 * * *na: SE-UMDAC-960209 * 194.165.229.246 * 194.165.248.34 * TOTAL 2 for *na: SE-UMDAC-960209 * * *na: IT-UNISOURCE-960215 * 194.244.1.2 * 194.244.1.22 * TOTAL 2 for *na: IT-UNISOURCE-960215 * * *na: FR-IWAY-960215 * 194.98.7.131 * 194.98.30.130 * 194.98.51.9 * 194.98.51.200 * 194.98.151.241 * 194.98.199.10 * 194.98.202.25 * 194.98.239.200 * 194.98.239.203 * TOTAL 9 for *na: FR-IWAY-960215 * * *na: UK-JANET-960220 * 194.81.63.2 * 194.81.127.12 * 194.81.127.201 * 194.83.29.2 * 194.83.181.128 * 194.83.181.235 * TOTAL 6 for *na: UK-JANET-960220 * * *na: DE-EUNET-960220 * 194.174.31.225 * 194.174.31.226 * TOTAL 2 for *na: DE-EUNET-960220 * * *na: DE-ZZ-960229 * 194.246.72.7 * TOTAL 1 for *na: DE-ZZ-960229 * * *na: FR-GROLIER-960305 * 194.117.212.2 * TOTAL 1 for *na: FR-GROLIER-960305 * * *na: IT-INET-960311 * 194.185.126.40 * 194.185.253.3 * 194.185.253.33 * TOTAL 3 for *na: IT-INET-960311 * * *na: DCB-GLOSTRUP * 194.192.80.73 * 194.192.80.92 * TOTAL 2 for *na: DCB-GLOSTRUP * * *na: FR-RENATER-960312 * 194.254.19.131 * 194.254.38.66 * 194.254.38.173 * 194.254.38.190 * 194.254.103.55 * 194.254.109.106 * 194.254.109.248 * 194.254.138.99 * 194.254.173.113 * 194.254.212.30 * 194.254.212.102 * TOTAL 11 for *na: FR-RENATER-960312 * * *na: CZ-BOHEMIA-960321 * 193.165.214.81 * TOTAL 1 for *na: CZ-BOHEMIA-960321 * * *na: EU-ZZ-194-38 * 194.38.168.242 * TOTAL 1 for *na: EU-ZZ-194-38 * * *na: AT-SPARDAT-960401 * 194.118.1.9 * 194.118.1.128 * 194.118.1.130 * 194.118.1.170 * 194.118.1.241 * 194.118.1.244 * 194.118.11.2 * 194.118.17.78 * 194.118.26.68 * 194.118.26.74 * 194.118.26.84 * 194.118.26.222 * 194.118.27.113 * 194.118.28.226 * 194.118.29.70 * 194.118.33.1 * TOTAL 16 for *na: AT-SPARDAT-960401 * * *na: ICL-DK * 193.89.94.41 * 193.89.94.61 * 193.89.94.190 * TOTAL 3 for *na: ICL-DK * * *na: FR-RENATER-940525 * 194.57.91.200 * 194.57.91.201 * 194.57.102.5 * 194.57.186.3 * 194.57.186.98 * 194.57.198.11 * 194.57.216.30 * 194.57.216.107 * 194.57.216.112 * TOTAL 9 for *na: FR-RENATER-940525 * * *na: ES-ENCOMIX-960415 * 194.143.209.1 * 194.143.212.75 * TOTAL 2 for *na: ES-ENCOMIX-960415 * * *na: UK-JANET-940418 * 194.66.183.18 * TOTAL 1 for *na: UK-JANET-940418 * * *na: DK-AZLAN-960423 * 195.24.2.44 * 195.24.2.55 * 195.24.2.60 * 195.24.2.194 * 195.24.2.197 * 195.24.2.198 * 195.24.2.200 * 195.24.2.202 * 195.24.2.203 * 195.24.2.209 * 195.24.2.212 * 195.24.3.10 * 195.24.3.11 * 195.24.3.73 * 195.24.3.76 * 195.24.3.86 * 195.24.3.89 * 195.24.3.91 * 195.24.3.95 * ... * TOTAL 90 for *na: DK-AZLAN-960423 * * *na: HU-DATANET-960426 * 195.56.17.226 * 195.56.26.229 * 195.56.32.125 * 195.56.48.34 * 195.56.48.41 * 195.56.65.90 * 195.56.65.100 * 195.56.82.100 * 195.56.251.75 * 195.56.251.117 * 195.56.251.179 * 195.56.251.200 * TOTAL 12 for *na: HU-DATANET-960426 * * *na: EU-ZZ-960501 * 193.43.8.1 * TOTAL 1 for *na: EU-ZZ-960501 * * *na: ATOMICSW * 194.192.102.5 * 194.192.102.7 * 194.192.102.8 * 194.192.102.38 * 194.192.102.65 * 194.192.102.128 * 194.192.102.130 * 194.192.102.169 * 194.192.102.191 * 194.192.102.194 * TOTAL 10 for *na: ATOMICSW * * *na: PL-TELBANK-960503 * 195.136.64.177 * 195.136.78.2 * 195.136.78.51 * 195.136.250.200 * 195.136.250.201 * TOTAL 5 for *na: PL-TELBANK-960503 * * *na: HR-CARNET-960508 * 193.198.128.82 * TOTAL 1 for *na: HR-CARNET-960508 * * *na: DE-DFN-940920 * 194.94.79.60 * 194.94.79.80 * 194.94.83.60 * 194.94.127.221 * 194.95.179.193 * 194.95.179.196 * 194.95.179.197 * 194.95.223.39 * TOTAL 8 for *na: DE-DFN-940920 * * *na: DE-SPACE-960515 * 195.30.253.4 * TOTAL 1 for *na: DE-SPACE-960515 * * *na: UK-EDEX-960522 * 193.193.59.13 * TOTAL 1 for *na: UK-EDEX-960522 * * *na: FR-ASI-960510 * 195.248.24.2 * TOTAL 1 for *na: FR-ASI-960510 * * *na: IE-TELECOM-951109 * 194.106.137.130 * TOTAL 1 for *na: IE-TELECOM-951109 * * *na: UK-MERCURY-960530 * 195.44.192.33 * 195.44.192.246 * 195.44.193.27 * 195.44.194.76 * 195.44.195.69 * 195.44.195.101 * 195.44.196.138 * 195.44.196.178 * 195.44.196.238 * TOTAL 9 for *na: UK-MERCURY-960530 * * *na: DE-XLINK-94122 * 194.121.133.1 * 194.121.225.181 * TOTAL 2 for *na: DE-XLINK-94122 * * *na: UK-ORANGENET-960610 * 193.218.162.189 * TOTAL 1 for *na: UK-ORANGENET-960610 * * *na: UK-POL-960612 * 195.92.67.11 * 195.92.67.13 * 195.92.67.14 * 195.92.67.15 * 195.92.67.16 * 195.92.68.14 * 195.92.68.71 * 195.92.68.72 * 195.92.68.75 * 195.92.68.79 * 195.92.68.108 * 195.92.68.123 * 195.92.68.133 * 195.92.68.139 * 195.92.68.141 * 195.92.68.147 * 195.92.68.165 * 195.92.68.167 * 195.92.68.177 * ... * TOTAL 82 for *na: UK-POL-960612 * * *na: HU-ELENDER-951108 * 194.143.246.250 * 194.143.248.3 * TOTAL 2 for *na: HU-ELENDER-951108 * * *na: FR-RENATER-950531 * 194.167.80.13 * 194.167.139.182 * 194.167.168.51 * 194.167.250.2 * 194.167.250.4 * 194.167.255.154 * TOTAL 6 for *na: FR-RENATER-950531 * * *na: ES-TTD-951020 * 194.179.64.1 * 194.179.64.4 * 194.179.64.11 * TOTAL 3 for *na: ES-TTD-951020 * * *na: UK-PSINET-960624 * 195.152.83.15 * 195.152.83.16 * 195.152.83.18 * 195.152.83.49 * 195.152.83.51 * 195.152.83.56 * 195.152.154.6 * 195.152.231.36 * 195.152.231.39 * 195.152.231.44 * 195.152.231.45 * 195.152.231.47 * TOTAL 12 for *na: UK-PSINET-960624 * * *na: FR-RENATER-951206 * 194.214.172.161 * 194.214.172.165 * 194.214.218.100 * 194.214.218.110 * 194.214.237.51 * 194.214.237.58 * 194.214.237.74 * TOTAL 7 for *na: FR-RENATER-951206 * * *na: RU-RELCOM-951221 * 194.220.214.2 * TOTAL 1 for *na: RU-RELCOM-951221 * * *na: ES-TTD-951221 * 194.224.49.2 * 194.224.52.4 * 194.224.52.6 * 194.224.52.40 * 194.224.53.3 * 194.224.53.58 * 194.224.53.135 * 194.224.55.25 * 194.224.55.46 * 194.224.77.8 * 194.224.106.36 * 194.224.126.183 * TOTAL 12 for *na: ES-TTD-951221 * * *na: UK-TECHNOCOM-960626 * 195.172.34.117 * 195.172.240.55 * TOTAL 2 for *na: UK-TECHNOCOM-960626 * * *na: UK-ZETNET-960628 * 194.247.32.17 * TOTAL 1 for *na: UK-ZETNET-960628 * * *na: DE-NETCOLOGNE-960716 * 194.8.218.141 * 194.8.218.228 * TOTAL 2 for *na: DE-NETCOLOGNE-960716 * * *na: FR-RENATER-960718 * 195.220.63.93 * TOTAL 1 for *na: FR-RENATER-960718 * * *na: RO-RNC-960722 * 193.230.207.226 * TOTAL 1 for *na: RO-RNC-960722 * * *na: UK-BUSINESSNET-960723 * 194.88.95.9 * TOTAL 1 for *na: UK-BUSINESSNET-960723 * * *na: RU-PTTNET-960801 * 195.34.16.58 * 195.34.16.120 * 195.34.16.123 * 195.34.17.13 * 195.34.17.18 * 195.34.27.39 * TOTAL 6 for *na: RU-PTTNET-960801 * * *na: NL-WIREHUB-960814 * 195.86.56.10 * 195.86.56.88 * 195.86.56.100 * 195.86.56.104 * 195.86.56.106 * 195.86.56.107 * 195.86.56.110 * 195.86.56.130 * 195.86.56.134 * 195.86.123.45 * 195.86.123.142 * 195.86.123.155 * 195.86.123.186 * TOTAL 13 for *na: NL-WIREHUB-960814 * * *na: SK-PUBNET-960819 * 195.98.23.4 * TOTAL 1 for *na: SK-PUBNET-960819 * * *na: UK-U-NET-960819 * 195.102.32.28 * 195.102.33.45 * 195.102.33.54 * 195.102.33.194 * 195.102.33.207 195.102.34.10 * 195.102.34.17 * 195.102.34.18 * 195.102.34.37 * 195.102.34.49 * 195.102.191.81 * TOTAL 11 for *na: UK-U-NET-960819 * * *na: SI-ARNES-960301 * 194.249.3.69 * 194.249.3.83 * 194.249.3.99 * 194.249.3.147 * 194.249.4.211 * 194.249.5.8 * 194.249.5.96 * 194.249.6.201 * 194.249.9.22 * TOTAL 9 for *na: SI-ARNES-960301 * * *na: SK-NAPRI-960827 * 195.146.16.2 * 195.146.16.3 * TOTAL 2 for *na: SK-NAPRI-960827 * * *na: FR-ISDNET-960827 * 195.154.0.131 * 195.154.91.34 * 195.154.96.2 * 195.154.97.1 * 195.154.97.2 * 195.154.97.5 * 195.154.97.66 * 195.154.97.121 * 195.154.100.1 * 195.154.100.147 * 195.154.100.163 * 195.154.129.227 * 195.154.129.228 * 195.154.132.130 * 195.154.132.132 * 195.154.132.133 * 195.154.132.134 * 195.154.132.135 * 195.154.132.137 * ... * TOTAL 25 for *na: FR-ISDNET-960827 * * *na: AT-PLUS-960912 * 194.112.200.194 * TOTAL 1 for *na: AT-PLUS-960912 * * *na: RU-PETERLINK-960919 * 195.242.9.12 * TOTAL 1 for *na: RU-PETERLINK-960919 * * *na: IT-ARCHWAY-961008 * 195.96.140.10 * 195.96.140.49 * 195.96.140.100 * 195.96.140.104 * TOTAL 4 for *na: IT-ARCHWAY-961008 * * *na: IT-THEBRAIN-961010 * 195.216.136.130 * 195.216.136.151 * TOTAL 2 for *na: IT-THEBRAIN-961010 * * *na: SK-NET-961016 * 195.12.135.66 * TOTAL 1 for *na: SK-NET-961016 * * *na: FR-RENATER-961021 * 195.221.234.122 * TOTAL 1 for *na: FR-RENATER-961021 * * *na: BG-NAT-961022 * 194.12.228.65 * 194.12.228.151 * 194.12.229.44 * TOTAL 3 for *na: BG-NAT-961022 * * *na: MK-MPT-961024 * 195.26.129.66 * TOTAL 1 for *na: MK-MPT-961024 * * *na: DE-INX-961101 * 195.21.6.18 * 195.21.169.2 * 195.21.207.53 * 195.21.207.102 * TOTAL 4 for *na: DE-INX-961101 * * *na: PT-IPGLOBAL-961101 * 195.23.2.4 * 195.23.3.10 * 195.23.69.65 * 195.23.69.67 * 195.23.69.69 * 195.23.72.10 * 195.23.72.36 * 195.23.86.13 * 195.23.86.23 * 195.23.96.132 * 195.23.96.251 * 195.23.98.83 * 195.23.120.16 * TOTAL 13 for *na: PT-IPGLOBAL-961101 * * *na: LV-NEONET-961107 * 195.62.139.195 * 195.62.139.205 * TOTAL 2 for *na: LV-NEONET-961107 * * *na: CH-VIRTUAL-961107 * 195.66.138.17 * TOTAL 1 for *na: CH-VIRTUAL-961107 * * *na: DE-MEDIAWAYS-960423 * 193.189.231.194 * 193.189.250.194 * TOTAL 2 for *na: DE-MEDIAWAYS-960423 * * *na: IT-UNINET-961119 * 195.94.135.202 * 195.94.144.190 * TOTAL 2 for *na: IT-UNINET-961119 * * *na: CZ-TERMINAL-961202 * 195.70.157.29 * TOTAL 1 for *na: CZ-TERMINAL-961202 * * *na: IT-IUNET-961209 * 195.45.3.146 * 195.45.37.42 * 195.45.60.193 * TOTAL 3 for *na: IT-IUNET-961209 * * *na: CH-NOVANET-961209 * 195.162.130.21 * TOTAL 1 for *na: CH-NOVANET-961209 * * *na: CZ-PVTNET-961210 * 195.47.116.5 * 195.47.116.26 * 195.47.116.34 * TOTAL 3 for *na: CZ-PVTNET-961210 * * *na: ES-TTD--960610-OESTE * 195.76.178.35 * 195.76.235.6 * 195.76.235.32 * 195.76.251.210 * TOTAL 4 for *na: ES-TTD--960610-OESTE * * *na: ES-TTD-961219-SUR * 195.53.5.2 * 195.53.27.64 * 195.53.58.2 * 195.53.60.2 * 195.53.67.165 * 195.53.79.2 * 195.53.80.2 * 195.53.81.104 * 195.53.81.158 * 195.53.98.168 * 195.53.99.3 * 195.53.99.114 * 195.53.99.136 * 195.53.99.202 * 195.53.201.242 * 195.53.201.247 * TOTAL 16 for *na: ES-TTD-961219-SUR * * *na: ES-TTD-961219-NORTE * 195.55.3.2 * 195.55.3.60 * 195.55.5.5 * 195.55.5.31 * 195.55.8.5 * 195.55.8.51 * 195.55.170.15 * 195.55.198.1 * 195.55.198.14 * TOTAL 9 for *na: ES-TTD-961219-NORTE * * *na: ES-TTD-961219-LEVANTE * 195.57.11.242 * 195.57.62.243 * 195.57.188.2 * 195.57.188.3 * 195.57.188.74 * 195.57.190.5 * 195.57.208.34 * 195.57.208.35 * 195.57.221.34 * 195.57.221.51 * 195.57.246.131 * TOTAL 11 for *na: ES-TTD-961219-LEVANTE * * *na: CH-SWISSONLINE-970123 * 195.24.73.187 * 195.24.82.215 * 195.24.87.104 * 195.24.91.129 * TOTAL 4 for *na: CH-SWISSONLINE-970123 * * *na: DE-MEDIAWAYS-970127 * 195.71.128.14 * 195.71.142.181 * TOTAL 2 for *na: DE-MEDIAWAYS-970127 * * *na: RU-MSU-940712 * 194.67.161.1 * TOTAL 1 for *na: RU-MSU-940712 * * *na: RU-ZENON-970131 * 195.2.84.75 * TOTAL 1 for *na: RU-ZENON-970131 * * *na: EU-ZZ-193-193-0-63 * 193.194.63.82 * 193.194.63.83 * TOTAL 2 for *na: EU-ZZ-193-193-0-63 * * *na: EU-ZZ-960306 * 193.218.205.10 * 193.218.205.42 * 193.218.210.46 * 193.218.210.188 * 193.218.216.10 * TOTAL 5 for *na: EU-ZZ-960306 * * *na: UK-BUSINESSNET-970212 * 195.50.65.18 * 195.50.65.19 * 195.50.65.22 * 195.50.65.23 * 195.50.94.16 * 195.50.101.198 * 195.50.104.192 * 195.50.104.211 * 195.50.104.233 * 195.50.104.250 * 195.50.105.18 * 195.50.105.107 * 195.50.105.188 * 195.50.105.189 * 195.50.106.94 * 195.50.106.124 * 195.50.107.124 * 195.50.107.178 * 195.50.107.218 * TOTAL 19 for *na: UK-BUSINESSNET-970212 * * *na: FR-SIRIS-951227 * 194.183.202.253 * TOTAL 1 for *na: FR-SIRIS-951227 * * *na: FI-EUNET-950112 * 193.64.151.161 * 193.64.151.162 * 193.64.151.164 * 193.64.151.209 * 193.64.151.228 * 193.64.151.229 * 193.64.151.230 * 193.65.248.170 * 193.65.248.178 * TOTAL 9 for *na: FI-EUNET-950112 * * *na: UK-NETKONECT-960307 * 194.164.173.76 * TOTAL 1 for *na: UK-NETKONECT-960307 * * *na: UK-ICLNET-951207 * 194.176.200.49 * TOTAL 1 for *na: UK-ICLNET-951207 * * *na: SE-XPRESSONLINE-970225 * 195.162.69.13 * 195.162.69.14 * 195.162.69.73 * 195.162.69.96 * 195.162.69.98 * TOTAL 5 for *na: SE-XPRESSONLINE-970225 * * *na: UK-PSINET-970227 * 195.153.32.130 * 195.153.64.65 * 195.153.222.65 * TOTAL 3 for *na: UK-PSINET-970227 * * *na: IUNET-DYNA-1 * 195.45.3.146 * TOTAL 1 for *na: IUNET-DYNA-1 * * *na: BE-UNISOURCE-970303 * 195.95.4.2 * 195.95.4.11 * 195.95.19.18 * TOTAL 3 for *na: BE-UNISOURCE-970303 * * *na: EE-ESTPAK-951219 * 194.126.117.18 * TOTAL 1 for *na: EE-ESTPAK-951219 * * *na: NL-IXE-970312 * 195.81.13.1 * 195.81.23.10 * TOTAL 2 for *na: NL-IXE-970312 * * *na: ES-SARENET-960122 * 194.30.73.217 * 194.30.88.137 * TOTAL 2 for *na: ES-SARENET-960122 * * *na: FI-CLINET-961004 * 194.100.19.130 * 194.100.45.250 * TOTAL 2 for *na: FI-CLINET-961004 * * *na: DK-SEKTORNET-970320 * 195.181.6.140 * 195.181.6.153 * 195.181.44.4 * 195.181.220.130 * TOTAL 4 for *na: DK-SEKTORNET-970320 * * *na: IE-INDIGO-951211 * 194.125.207.97 * 194.125.207.134 * 194.125.207.154 * TOTAL 3 for *na: IE-INDIGO-951211 * * *na: UA-GU-970404 * 195.123.8.10 * 195.123.17.1 * 195.123.18.1 * 195.123.18.97 * 195.123.40.130 * 195.123.40.132 * 195.123.254.205 * TOTAL 7 for *na: UA-GU-970404 * * *na: SI-TELEKOM-960419 * 193.189.172.2 * 193.189.182.31 * 193.189.182.68 * 193.189.182.77 * 193.189.182.156 * 193.189.183.102 * 193.189.186.33 * 193.189.191.29 * 193.189.191.106 * TOTAL 9 for *na: SI-TELEKOM-960419 * * *na: AT-NEWMEDIA-970411 * 195.12.192.7 * 195.12.192.98 * 195.12.192.99 * 195.12.192.100 * 195.12.193.31 * 195.12.193.209 * TOTAL 6 for *na: AT-NEWMEDIA-970411 * * *na: EE-ESTNET-970416 * 195.50.193.66 * 195.50.193.163 * TOTAL 2 for *na: EE-ESTNET-970416 * * *na: UA-TM-970417 * 195.66.205.1 * 195.66.205.5 * TOTAL 2 for *na: UA-TM-970417 * * *na: AT-ATNET-951212 * 194.152.163.17 * TOTAL 1 for *na: AT-ATNET-951212 * * *na: EU-ATT-970402 * 195.121.1.34 * 195.121.1.66 * 195.121.6.37 * 195.121.6.51 * 195.121.6.57 * 195.121.6.59 * 195.121.6.61 * 195.121.6.98 * 195.121.6.99 * 195.121.6.100 * 195.121.6.143 * 195.121.6.144 * 195.121.6.163 * 195.121.6.196 * 195.121.8.2 * 195.121.9.89 * 195.121.9.115 * 195.121.18.16 * 195.121.18.109 * ... * TOTAL 91 for *na: EU-ATT-970402 * * *na: FR-SKY-960103 * 194.6.151.205 * TOTAL 1 for *na: FR-SKY-960103 * * *na: IL-NETVISION-970428 * 62.0.128.40 * 62.0.128.86 * 62.0.128.107 * 62.0.128.138 * 62.0.145.135 * 62.0.145.139 * 62.0.145.232 * 62.0.146.8 * 62.0.146.10 * 62.0.146.89 * 62.0.149.78 * 62.0.149.100 * 62.0.152.1 * 62.0.153.19 * 62.0.153.39 * 62.0.153.194 * 62.0.154.12 * 62.0.154.211 * 62.0.154.235 * ... * TOTAL 30 for *na: IL-NETVISION-970428 * * *na: SPARDAT-NET-3 * 194.118.1.9 * 194.118.1.128 * 194.118.1.130 * 194.118.1.170 * 194.118.1.241 * 194.118.1.244 * TOTAL 6 for *na: SPARDAT-NET-3 * * *na: SPARDAT-NET-10 * 194.118.26.68 * 194.118.26.74 * 194.118.26.84 * 194.118.26.222 * TOTAL 4 for *na: SPARDAT-NET-10 * * *na: FI-KOLUMBUS-960904 * 193.229.72.76 * 193.229.80.98 * 193.229.99.10 * 193.229.129.183 * 193.229.159.3 * 193.229.159.4 * 193.229.163.54 * 193.229.164.163 * 193.229.165.38 * 193.229.204.246 * 193.229.226.156 * TOTAL 11 for *na: FI-KOLUMBUS-960904 * * *na: FR-OLEANE-950711 * 194.2.128.1 * 194.2.128.2 * 194.2.128.4 * 194.2.128.6 * 194.2.128.16 * 194.2.128.27 * 194.2.128.247 * 194.2.128.248 * TOTAL 8 for *na: FR-OLEANE-950711 * * *na: EE-UNINET-970506 * 194.204.43.159 * TOTAL 1 for *na: EE-UNINET-970506 * * *na: UK-POL-970506 * 62.136.65.189 * 62.136.66.52 * 62.136.67.39 * 62.136.67.48 * 62.136.67.216 * 62.136.69.148 * 62.136.69.189 * 62.136.70.76 * 62.136.73.122 * 62.136.74.24 * 62.136.74.167 * 62.136.74.170 * 62.136.74.193 * 62.136.76.25 * 62.136.76.220 * 62.136.76.252 * 62.136.77.21 * 62.136.77.180 * 62.136.77.184 * ... * TOTAL 49 for *na: UK-POL-970506 * * *na: FUTURNET * 195.53.98.168 * 195.53.99.3 * 195.53.99.114 * 195.53.99.136 * 195.53.99.202 * TOTAL 5 for *na: FUTURNET * * *na: BSANTANDER * 195.53.80.2 * 195.53.81.104 * 195.53.81.158 * TOTAL 3 for *na: BSANTANDER * * *na: MSC * 195.53.79.2 * TOTAL 1 for *na: MSC * * *na: NACOM * 195.53.67.165 * TOTAL 1 for *na: NACOM * * *na: HPR2 * 195.53.60.2 * TOTAL 1 for *na: HPR2 * * *na: ALHSYS * 195.53.58.2 * TOTAL 1 for *na: ALHSYS * * *na: RGC * 195.53.27.64 * TOTAL 1 for *na: RGC * * *na: PICMATIC * 195.53.5.2 * TOTAL 1 for *na: PICMATIC * * *na: PONFPARK * 195.55.8.5 * 195.55.8.51 * TOTAL 2 for *na: PONFPARK * * *na: IPONET * 195.55.5.5 * 195.55.5.31 * TOTAL 2 for *na: IPONET * * *na: GRAMA * 195.55.3.2 * 195.55.3.60 * TOTAL 2 for *na: GRAMA * * *na: DIPBADAJOZ * 195.57.11.242 * TOTAL 1 for *na: DIPBADAJOZ * * *na: CH-UNISOURCE-970526 * 193.5.175.194 * TOTAL 1 for *na: CH-UNISOURCE-970526 * * *na: FR-NETSAT-970526 * 195.10.61.3 * 195.10.62.5 * 195.10.62.8 * 195.10.62.10 * 195.10.62.12 * 195.10.62.14 * 195.10.62.15 * 195.10.62.18 * 195.10.62.19 * 195.10.62.21 * TOTAL 10 for *na: FR-NETSAT-970526 * * *na: DE-MEDIAWAYS-970527 * 62.52.135.107 * 62.52.135.119 * 62.52.152.34 * 62.52.154.157 * 62.52.155.89 * 62.52.159.217 * 62.52.179.13 * 62.52.179.82 * 62.52.179.92 * 62.52.179.115 * 62.52.249.52 * 62.52.249.116 * TOTAL 12 for *na: DE-MEDIAWAYS-970527 * * *na: CH-UNISOURCE-970528 * 193.135.153.196 * 193.135.163.5 * 193.135.163.186 * 193.135.253.210 * TOTAL 4 for *na: CH-UNISOURCE-970528 * * *na: CH-UNISOURCE-970528 * 193.247.71.67 * TOTAL 1 for *na: CH-UNISOURCE-970528 * * *na: DK-ZZ-193-162-163 * 193.162.16.5 * 193.162.16.34 * 193.162.16.35 * 193.162.17.225 * 193.162.38.9 * 193.162.145.64 * 193.162.145.130 * 193.162.145.158 * 193.162.145.229 * 193.162.145.252 * 193.162.146.9 * 193.162.146.35 * 193.162.146.43 * 193.162.155.2 * 193.162.155.118 * 193.162.155.134 * 193.162.155.138 * 193.162.155.166 * 193.162.155.238 * ... * TOTAL 39 for *na: DK-ZZ-193-162-163 * * *na: SK-ZZ-194-1-128-255 * 194.1.128.2 * 194.1.128.5 * 194.1.128.10 * 194.1.128.14 * 194.1.128.27 * 194.1.128.40 * 194.1.133.42 * TOTAL 7 for *na: SK-ZZ-194-1-128-255 * * *na: RU-RINET-970530 * 195.54.215.163 * TOTAL 1 for *na: RU-RINET-970530 * * *na: SE-SUNET-970602 * 193.180.21.2 * 193.180.21.10 * 193.180.23.4 * 193.180.23.167 * 193.180.23.230 * 193.180.23.236 * 193.180.34.38 * 193.180.36.77 * 193.180.36.155 * 193.180.36.170 * 193.180.36.177 * 193.180.45.72 * 193.180.58.7 * 193.180.58.22 * 193.180.58.254 * 193.180.65.151 * 193.180.82.165 * 193.180.84.106 * 193.180.104.9 * ... * TOTAL 75 for *na: SE-SUNET-970602 * * *na: SE-SUNET-970602 * 193.234.191.242 * 193.234.191.244 * 193.234.247.10 * 193.235.16.226 * 193.235.17.3 * 193.235.17.33 * 193.235.21.40 * 193.235.48.53 * 193.235.76.171 * 193.235.87.109 * 193.235.88.87 * 193.235.89.1 * 193.235.89.27 * 193.235.89.122 * 193.235.95.250 * 193.235.118.30 * 193.235.118.37 * 193.235.223.10 * 193.235.229.100 * TOTAL 19 for *na: SE-SUNET-970602 * * *na: SE-SUNET-970602 * 194.14.81.162 * 194.14.81.174 * 194.14.81.175 * 194.14.81.181 * 194.14.81.182 * 194.14.98.17 * 194.14.189.252 * 194.14.189.254 * 194.14.204.80 * 194.14.204.107 * 194.14.204.112 * TOTAL 11 for *na: SE-SUNET-970602 * * *na: SE-SUNET-970602 * 194.68.13.18 * 194.68.13.19 * TOTAL 2 for *na: SE-SUNET-970602 * * *na: SE-SUNET-970602 * 194.71.15.242 * 194.71.106.1 * 194.71.214.2 * 194.71.247.47 * TOTAL 4 for *na: SE-SUNET-970602 * * *na: SE-SUNET-970602 * 194.103.185.80 * 194.103.191.1 * 194.103.205.14 * 194.103.205.20 * 194.103.205.100 * TOTAL 5 for *na: SE-SUNET-970602 * * *na: SE-SUNET-970602 * 194.132.131.19 * 194.132.135.97 * TOTAL 2 for *na: SE-SUNET-970602 * * *na: NO-POWERTECH-970603 * 195.159.94.50 * 195.159.99.10 * TOTAL 2 for *na: NO-POWERTECH-970603 * * *na: NO-TELIANET-970603 * 195.18.205.50 * 195.18.205.51 * 195.18.205.52 * 195.18.205.53 * TOTAL 4 for *na: NO-TELIANET-970603 * * *na: EE-MATK * 194.126.117.18 * TOTAL 1 for *na: EE-MATK * * *na: SE-ENGELHOLM-970612 * 195.216.32.194 * 195.216.34.1 * 195.216.34.8 * 195.216.45.20 * 195.216.45.122 * TOTAL 5 for *na: SE-ENGELHOLM-970612 * * *na: TR-RAKSNET-960513 * 195.244.34.99 * 195.244.37.1 * TOTAL 2 for *na: TR-RAKSNET-960513 * * *na: DK-KOMMUNEDATA-970626 * 195.50.58.3 * TOTAL 1 for *na: DK-KOMMUNEDATA-970626 * * *na: AT-TELEKOM-970627 * 195.3.120.97 * 195.3.126.124 * 195.3.126.125 * 195.3.127.220 * TOTAL 4 for *na: AT-TELEKOM-970627 * * *na: HU-INTERWARE-970704 * 195.70.54.241 * TOTAL 1 for *na: HU-INTERWARE-970704 * * *na: UK-COMPULINK-951004 * 194.153.0.18 * 194.153.0.51 * 194.153.0.82 * 194.153.0.117 * 194.153.0.125 * 194.153.0.126 * 194.153.1.10 * 194.153.25.45 * 194.153.26.24 * 194.153.26.33 * 194.153.26.61 * 194.153.26.68 * 194.153.26.175 * 194.153.26.204 * 194.153.28.70 * 194.153.31.26 * TOTAL 16 for *na: UK-COMPULINK-951004 * * *na: SE-SWIPNET-970130 * 193.12.6.130 * 193.12.6.144 * 193.12.6.146 * 193.12.198.82 * 193.12.198.98 * 193.12.205.1 * 193.12.209.1 * 193.12.209.37 * 193.12.243.4 * 193.12.243.40 * 193.12.243.59 * 193.12.243.62 * 193.12.243.75 * 193.12.243.104 * 193.12.243.150 * 193.12.255.26 * 193.12.255.253 * 193.13.14.38 * 193.13.15.2 * ... * TOTAL 243 for *na: SE-SWIPNET-970130 * * *na: NO-EAB-970716 * 195.134.43.2 * 195.134.44.10 * 195.134.44.132 * TOTAL 3 for *na: NO-EAB-970716 * * *na: DE-KNIPP-970721 * 195.138.34.161 * TOTAL 1 for *na: DE-KNIPP-970721 * * *na: DE-COSMIK-970728 * 195.182.40.1 * 195.182.40.218 * TOTAL 2 for *na: DE-COSMIK-970728 * * *na: TR-ZZ-960827 * 195.142.1.3 * 195.142.1.5 * 195.142.148.200 * 195.142.234.169 * TOTAL 4 for *na: TR-ZZ-960827 * * *na: EU-ZZ-194-93 * 194.93.79.84 * 194.93.79.91 * 194.93.128.1 * 194.93.128.2 * 194.93.128.3 * 194.93.128.28 * 194.93.133.1 * 194.93.134.3 * 194.93.134.119 * 194.93.154.49 * TOTAL 10 for *na: EU-ZZ-194-93 * * *na: TR-ZZ-950223 * 194.27.5.46 * TOTAL 1 for *na: TR-ZZ-950223 * * *na: DK-TJANTIK-970805 * 195.184.100.130 * 195.184.101.100 * 195.184.103.254 * TOTAL 3 for *na: DK-TJANTIK-970805 * * *na: PL-NASK-970805 * 195.187.243.10 * 195.187.244.6 * 195.187.245.51 * TOTAL 3 for *na: PL-NASK-970805 * * *na: DK-EUROCONNECT-970813 * 195.184.42.162 * 195.184.43.196 * 195.184.44.227 * 195.184.44.228 * TOTAL 4 for *na: DK-EUROCONNECT-970813 * * *na: IT-FLASHNET-970814 * 195.191.1.73 * 195.191.1.91 * 195.191.2.13 * 195.191.2.185 * 195.191.4.85 * 195.191.80.59 * 195.191.105.150 * 195.191.105.226 * TOTAL 8 for *na: IT-FLASHNET-970814 * * *na: FR-PRESSIMAGE-970826 * 194.150.34.223 * TOTAL 1 for *na: FR-PRESSIMAGE-970826 * * *na: DE-KAMP-970827 * 195.62.99.200 * 195.62.120.231 * TOTAL 2 for *na: DE-KAMP-970827 * * *na: FR-SATELNET-970520 * 195.28.196.66 * TOTAL 1 for *na: FR-SATELNET-970520 * * *na: DE-NETCOLOGNE-970911 * 195.14.233.180 * TOTAL 1 for *na: DE-NETCOLOGNE-970911 * * *na: FR-OLEANE-961101 * 195.25.216.129 * 195.25.238.136 * TOTAL 2 for *na: FR-OLEANE-961101 * * *na: DE-IPF-970924 * 195.211.29.85 * 195.211.35.214 * 195.211.36.15 * 195.211.46.232 * 195.211.48.1 * 195.211.64.68 * 195.211.86.235 * 195.211.88.65 * 195.211.123.106 * 195.211.133.31 * 195.211.151.202 * 195.211.201.41 * 195.211.204.211 * 195.211.208.236 * 195.211.211.20 * 195.211.211.37 * 195.211.212.247 * TOTAL 17 for *na: DE-IPF-970924 * * *na: EU-INFONET-970925 * 195.213.119.7 * TOTAL 1 for *na: EU-INFONET-970925 * * *na: CZ-CZNET-971003 * 194.228.21.131 * 194.228.21.151 * 194.228.41.67 * 194.228.42.10 * 194.228.54.19 * 194.228.139.12 * 194.228.147.131 * TOTAL 7 for *na: CZ-CZNET-971003 * * *na: DE-POP-971014 * 195.222.215.39 * TOTAL 1 for *na: DE-POP-971014 * * *na: DE-INET-971014 * 195.34.161.30 * TOTAL 1 for *na: DE-INET-971014 * * *na: ECRC-FFM2-NET * 195.27.83.78 * TOTAL 1 for *na: ECRC-FFM2-NET * * *na: DE-ECRC-961107 * 195.27.83.78 * 195.27.221.2 * 195.27.221.3 * 195.27.221.8 * 195.27.241.3 * TOTAL 5 for *na: DE-ECRC-961107 * * *na: CH-MC-971031 * 195.130.185.43 * TOTAL 1 for *na: CH-MC-971031 * * *na: SE-BAHNHOF-971105 * 195.178.163.100 * 195.178.163.102 * TOTAL 2 for *na: SE-BAHNHOF-971105 * * *na: UK-DIAMOND-971110 * 195.182.182.2 * TOTAL 1 for *na: UK-DIAMOND-971110 * * *na: UK-GLOBAL-971112 * 195.147.27.179 * 195.147.129.224 * 195.147.130.195 * 195.147.132.3 * 195.147.134.7 * 195.147.134.41 * 195.147.134.65 * 195.147.135.136 * 195.147.135.222 * 195.147.136.150 * 195.147.136.204 * 195.147.136.236 * 195.147.139.68 * 195.147.139.183 * 195.147.140.23 * 195.147.140.77 * 195.147.140.180 * 195.147.141.1 * 195.147.142.218 * ... * TOTAL 51 for *na: UK-GLOBAL-971112 * * *na: FR-CEGETEL-970326 * 195.115.64.201 * TOTAL 1 for *na: FR-CEGETEL-970326 * * *na: DK-EUROCONNECT-971126 * 195.97.129.226 * 195.97.129.234 * 195.97.140.58 * 195.97.145.102 * 195.97.150.238 * 195.97.183.202 * 195.97.183.204 * TOTAL 7 for *na: DK-EUROCONNECT-971126 * * *na: IT-ATSLINK-971128 * 195.62.230.106 * TOTAL 1 for *na: IT-ATSLINK-971128 * * *na: ES-TTD-971208-SUR * 195.235.56.237 * 195.235.80.163 * 195.235.114.46 * 195.235.115.70 * 195.235.115.143 * 195.235.115.243 * 195.235.116.144 * 195.235.116.152 * 195.235.117.4 * 195.235.117.21 * 195.235.118.55 * 195.235.118.113 * 195.235.118.242 * 195.235.119.88 * 195.235.119.160 * 195.235.121.68 * 195.235.121.76 * 195.235.121.80 * 195.235.122.104 * ... * TOTAL 23 for *na: ES-TTD-971208-SUR * * *na: FR-GLCONSULTANTS-971210 * 195.110.230.3 * 195.110.230.13 * TOTAL 2 for *na: FR-GLCONSULTANTS-971210 * * *na: RU-SOVAM-971210 * 195.239.46.178 * 195.239.67.65 * 195.239.68.203 * 195.239.70.67 * 195.239.70.70 * 195.239.85.24 * 195.239.88.65 * 195.239.134.13 * 195.239.208.3 * 195.239.208.100 * 195.239.214.80 * TOTAL 11 for *na: RU-SOVAM-971210 * * *na: GTO-OM-BLK01 * 206.49.110.246 * TOTAL 1 for *na: GTO-OM-BLK01 * * *na: GTO-OM-BLK01 * 206.49.109.5 * 206.49.109.10 * 206.49.109.154 * TOTAL 3 for *na: GTO-OM-BLK01 * * *na: GTO-OM-BLK01 * 206.49.101.5 * 206.49.101.6 * 206.49.101.40 * 206.49.101.129 * TOTAL 4 for *na: GTO-OM-BLK01 * * *na: GTO-OM-BLK01 * 206.49.102.108 * TOTAL 1 for *na: GTO-OM-BLK01 * * *na: PLANETENDK * 195.215.34.105 * TOTAL 1 for *na: PLANETENDK * * *na: MILLERFREEMANDK * 195.215.34.82 * TOTAL 1 for *na: MILLERFREEMANDK * * *na: BKIDK * 195.215.34.194 * TOTAL 1 for *na: BKIDK * * *na: A2Z-NETDK * 195.215.36.2 * 195.215.36.3 * 195.215.36.4 * 195.215.36.5 * 195.215.36.18 * 195.215.36.19 * 195.215.36.20 * 195.215.36.36 * 195.215.36.40 * TOTAL 9 for *na: A2Z-NETDK * * *na: HH-INDUSTRIDK * 195.215.36.98 * TOTAL 1 for *na: HH-INDUSTRIDK * * *na: FSRDK * 195.215.36.230 * TOTAL 1 for *na: FSRDK * * *na: NOVOPANDK * 195.215.37.148 * TOTAL 1 for *na: NOVOPANDK * * *na: BONDOSVANEDK * 195.215.38.130 * 195.215.38.131 * TOTAL 2 for *na: BONDOSVANEDK * * *na: FR-NORMANDNET-980114 * 195.7.97.109 * 195.7.98.16 * 195.7.102.1 * TOTAL 3 for *na: FR-NORMANDNET-980114 * * *na: BE-INET-194-7 * 194.7.170.162 * 194.7.182.210 * TOTAL 2 for *na: BE-INET-194-7 * * *na: LACTOSANDK * 195.215.29.187 * TOTAL 1 for *na: LACTOSANDK * * *na: UK-CINERGY-980120 * 195.28.167.170 * TOTAL 1 for *na: UK-CINERGY-980120 * * *na: B-DATADK * 195.215.52.130 * TOTAL 1 for *na: B-DATADK * * *na: AVNDK * 195.215.53.2 * TOTAL 1 for *na: AVNDK * * *na: FR-IMAGINET-960610 * 195.68.29.214 * 195.68.29.217 * 195.68.35.153 * 195.68.36.20 * TOTAL 4 for *na: FR-IMAGINET-960610 * * *na: EU-IBM-139-92-16 * 139.92.4.24 * 139.92.4.52 * 139.92.4.156 * 139.92.4.196 * 139.92.4.224 * 139.92.8.169 * 139.92.20.142 * 139.92.30.35 * 139.92.30.251 * 139.92.34.81 * 139.92.34.235 * 139.92.49.247 * 139.92.57.70 * 139.92.64.151 * 139.92.66.135 * 139.92.68.26 * 139.92.68.38 * 139.92.68.40 * 139.92.68.48 * ... * TOTAL 58 for *na: EU-IBM-139-92-16 * * *na: RU-MAXNET-980123 * 195.112.97.17 * 195.112.97.68 * TOTAL 2 for *na: RU-MAXNET-980123 * * *na: LV-TELEKOM-980126 * 195.13.147.140 * TOTAL 1 for *na: LV-TELEKOM-980126 * * *na: HU-INTERNET-980122 * 193.68.35.142 * TOTAL 1 for *na: HU-INTERNET-980122 * * *na: NO-DAXNET-950315 * 193.216.27.130 * TOTAL 1 for *na: NO-DAXNET-950315 * * *na: SE-UTFORS-970825 * 195.58.99.94 * 195.58.99.116 * 195.58.99.117 * TOTAL 3 for *na: SE-UTFORS-970825 * * *na: DE-OPENNET-980127 * 195.202.112.21 * TOTAL 1 for *na: DE-OPENNET-980127 * * *na: DAN-DOORSDK * 195.215.54.130 * 195.215.54.145 * TOTAL 2 for *na: DAN-DOORSDK * * *na: DE-BERGSKE * 195.215.54.194 * 195.215.54.195 * TOTAL 2 for *na: DE-BERGSKE * * *na: BONGBJOERNBAKDK * 195.215.55.251 * TOTAL 1 for *na: BONGBJOERNBAKDK * * *na: COMPAQDK * 195.215.56.44 * TOTAL 1 for *na: COMPAQDK * * *na: QUARKDK * 195.215.56.66 * TOTAL 1 for *na: QUARKDK * * *na: BR-MARINECOM * 195.215.55.145 * TOTAL 1 for *na: BR-MARINECOM * * *na: MA-ONPT-970523 * 194.204.224.75 * TOTAL 1 for *na: MA-ONPT-970523 * * *na: VLKBRNO-CZ * 194.212.137.1 * TOTAL 1 for *na: VLKBRNO-CZ * * *na: STALDINDUSTRI * 194.192.87.4 * TOTAL 1 for *na: STALDINDUSTRI * * *na: PSEDK * 195.215.56.90 * TOTAL 1 for *na: PSEDK * * *na: POINT4-NET * 194.205.28.15 * TOTAL 1 for *na: POINT4-NET * * *na: SPROUTMATADOR * 194.192.206.214 * TOTAL 1 for *na: SPROUTMATADOR * * *na: FDC * 195.215.58.67 * TOTAL 1 for *na: FDC * * *na: SCANTICON-KOLDINGDK * 195.215.57.194 * TOTAL 1 for *na: SCANTICON-KOLDINGDK * * *na: MEDIBASE * 195.215.58.34 * TOTAL 1 for *na: MEDIBASE * * *na: INFASE * 195.57.246.131 * TOTAL 1 for *na: INFASE * * *na: NOLADK * 195.215.58.212 * TOTAL 1 for *na: NOLADK * * *na: HS-TARMDK * 195.215.59.130 * TOTAL 1 for *na: HS-TARMDK * * *na: FSPDK * 195.215.59.35 * TOTAL 1 for *na: FSPDK * * *na: FRIFERIEDK * 195.215.59.2 * TOTAL 1 for *na: FRIFERIEDK * * *na: MARITIMADK * 195.215.60.2 * 195.215.60.66 * TOTAL 2 for *na: MARITIMADK * * *na: OPTION-INTERNATIONAL-NV-NET * 194.7.170.162 * TOTAL 1 for *na: OPTION-INTERNATIONAL-NV-NET * * *na: SCANBECHCOM * 195.215.59.98 * TOTAL 1 for *na: SCANBECHCOM * * *na: RU-COMSTAR-980226 * 212.248.0.3 * TOTAL 1 for *na: RU-COMSTAR-980226 * * *na: FR-INTERNEXT-951127 * 194.79.133.72 * TOTAL 1 for *na: FR-INTERNEXT-951127 * * *na: FR-INTERNEXT-970523 * 195.5.196.47 * TOTAL 1 for *na: FR-INTERNEXT-970523 * * *na: BOGPADK * 195.215.61.18 * 195.215.61.19 * TOTAL 2 for *na: BOGPADK * * *na: TITGEMEYERDK * 193.89.47.2 * TOTAL 1 for *na: TITGEMEYERDK * *na: BG-SPNET-980310 * 212.50.2.193 * 212.50.25.8 * TOTAL 2 for *na: BG-SPNET-980310 * * *na: DK-WEB-DENMARK-970218 * 195.78.67.177 * 195.78.67.189 * 195.78.67.213 * 195.78.67.229 * 195.78.67.249 * 195.78.67.250 * 195.78.74.74 * 195.78.74.89 * 195.78.74.116 * 195.78.74.120 * 195.78.74.122 * 195.78.75.88 * 195.78.75.89 * 195.78.75.90 * 195.78.75.245 * 195.78.76.37 * 195.78.76.41 * 195.78.76.42 * 195.78.76.49 * ... * TOTAL 47 for *na: DK-WEB-DENMARK-970218 * * *na: SE-LEISSNER-980312 * 212.3.5.124 * 212.3.6.130 * TOTAL 2 for *na: SE-LEISSNER-980312 * * *na: SASAIRLINEDK * 194.192.22.2 * 194.192.22.9 * 194.192.22.11 * 194.192.23.1 * TOTAL 4 for *na: SASAIRLINEDK * * *na: DELTATC * 194.192.70.10 * TOTAL 1 for *na: DELTATC * * *na: BLANET * 194.192.98.129 * TOTAL 1 for *na: BLANET * * *na: GJNET * 194.192.94.2 * TOTAL 1 for *na: GJNET * * *na: ROYGRE * 193.163.210.20 * 193.163.210.58 * TOTAL 2 for *na: ROYGRE * * *na: ESBJERG-KOMMUNE * 193.163.58.20 * 193.163.58.23 * 193.163.58.30 * TOTAL 3 for *na: ESBJERG-KOMMUNE * * *na: AT-CYBERTRON-980316 * 212.236.3.195 * 212.236.3.200 * TOTAL 2 for *na: AT-CYBERTRON-980316 * * *na: ABI-GROUPDK * 193.88.73.18 * TOTAL 1 for *na: ABI-GROUPDK * * *na: TR-SUPERONLINE-980318 * 195.33.204.6 * 195.33.204.70 * 195.33.205.182 * 195.33.205.186 * 195.33.205.195 * 195.33.206.46 * 195.33.206.178 * 195.33.218.108 * 195.33.219.124 * 195.33.219.188 * 195.33.220.38 * 195.33.221.95 * 195.33.222.164 * TOTAL 13 for *na: TR-SUPERONLINE-980318 * * *na: IT-IUNET-930901 * 193.70.1.2 * 193.70.1.4 * 193.70.6.3 * 193.70.16.1 * 193.70.16.19 * 193.70.26.72 * 193.70.27.6 * 193.70.31.2 * 193.70.31.45 * 193.70.31.101 * 193.70.41.6 * 193.70.50.231 * 193.70.60.3 * 193.70.88.2 * 193.70.96.18 * 193.70.96.81 193.70.96.130 * 193.70.121.186 * 193.70.162.66 * ... * TOTAL 25 for *na: IT-IUNET-930901 * * *na: IT-IUNET-940426 * 193.76.81.227 * 193.76.126.2 * 193.76.126.138 * 193.76.127.2 * 193.76.127.5 * 193.76.127.8 * 193.76.127.10 * 193.76.148.71 * 193.76.217.6 * 193.76.217.7 * 193.76.224.2 * 193.76.224.93 * 193.76.248.2 * TOTAL 13 for *na: IT-IUNET-940426 * * *na: TR-COMNET-980319 * 212.15.30.4 * 212.15.30.72 * TOTAL 2 for *na: TR-COMNET-980319 * * *na: FR-CYBERCABLE-980319 * 212.198.0.66 * 212.198.0.67 * 212.198.1.66 * 212.198.6.59 * 212.198.15.65 * 212.198.18.209 * 212.198.21.77 * 212.198.30.93 * 212.198.33.49 * 212.198.34.17 * 212.198.35.10 * 212.198.38.88 * 212.198.45.111 * 212.198.45.180 * 212.198.48.118 * 212.198.68.17 * 212.198.104.88 * 212.198.104.175 * 212.198.107.153 * ... * TOTAL 31 for *na: FR-CYBERCABLE-980319 * * *na: EU-ATT-961118 * 195.33.64.3 * 195.33.64.148 * 195.33.64.149 * TOTAL 3 for *na: EU-ATT-961118 * * *na: DE-GINKO-980324 * 212.202.67.93 * 212.202.67.96 * 212.202.69.49 * TOTAL 3 for *na: DE-GINKO-980324 * * *na: TR-HURRIYET-980327 * 212.31.1.1 * TOTAL 1 for *na: TR-HURRIYET-980327 * * *na: NET-PT-EUNET-BB * 193.126.4.65 * 193.126.4.67 * 193.126.8.65 * TOTAL 3 for *na: NET-PT-EUNET-BB * * *na: NET-PT-MINEDU * 193.126.18.189 * TOTAL 1 for *na: NET-PT-MINEDU * * *na: NET-PT-PARLAMENTO * 193.126.90.1 * TOTAL 1 for *na: NET-PT-PARLAMENTO * * *na: ATOMICSW * 194.192.211.222 * TOTAL 1 for *na: ATOMICSW * * *na: SE-DATAPHONE-980331 * 212.37.6.225 * TOTAL 1 for *na: SE-DATAPHONE-980331 * * *na: TSAI * 195.53.201.242 * 195.53.201.247 * TOTAL 2 for *na: TSAI * * *na: DK-TELIANET-960206 * 194.19.134.14 * 194.19.134.15 * 194.19.134.17 * 194.19.134.18 * 194.19.134.19 * 194.19.134.22 * 194.19.134.23 * 194.19.134.29 * 194.19.179.17 * 194.19.179.34 * 194.19.179.35 * 194.19.179.36 * TOTAL 12 for *na: DK-TELIANET-960206 * * *na: LV-TELIANET-960206 * 194.19.240.46 * TOTAL 1 for *na: LV-TELIANET-960206 * * *na: DK-TELIANET-960319 * 194.255.32.66 * 194.255.32.73 * 194.255.32.89 * 194.255.32.90 * 194.255.32.174 * TOTAL 5 for *na: DK-TELIANET-960319 * * *na: LT-TELIANET-971007 * 195.12.164.250 * TOTAL 1 for *na: LT-TELIANET-971007 * * *na: SE-TELIANET-970121 * 195.67.156.39 * 195.67.156.52 * 195.67.156.132 * 195.67.156.241 * 195.67.157.23 * 195.67.157.101 * 195.67.157.164 * 195.67.157.241 * 195.67.157.243 * 195.67.188.67 * 195.67.188.150 * 195.67.188.183 * 195.67.188.209 * 195.67.188.235 * 195.67.188.241 * 195.67.188.243 * 195.67.189.11 * 195.67.189.34 * 195.67.189.74 * ... * TOTAL 109 for *na: SE-TELIANET-970121 * * *na: SE-TELIANET-970521 * 62.20.78.242 * 62.20.78.253 * 62.20.79.4 * 62.20.79.5 * 62.20.128.15 * 62.20.132.55 * 62.20.132.84 * 62.20.132.85 * 62.20.132.90 * 62.20.132.127 * 62.20.132.134 * 62.20.132.153 * 62.20.132.175 * 62.20.132.180 * 62.20.132.241 * 62.20.132.243 * 62.20.133.61 * 62.20.133.86 * 62.20.133.120 * ... * TOTAL 253 for *na: SE-TELIANET-970521 * * *na: SE-UMDAC-960209 * 212.32.129.225 * 212.32.130.10 * 212.32.130.23 * 212.32.153.61 * TOTAL 4 for *na: SE-UMDAC-960209 * * *na: EDEKADK * 194.192.17.226 * TOTAL 1 for *na: EDEKADK * * *na: PLASTMODK * 194.192.17.245 * TOTAL 1 for *na: PLASTMODK * * *na: SKAMOLDK * 194.192.17.234 * TOTAL 1 for *na: SKAMOLDK * * *na: HECODK * 194.192.64.130 * TOTAL 1 for *na: HECODK * * *na: TV2BH * 194.192.64.162 * TOTAL 1 for *na: TV2BH * * *na: ADVOC * 193.89.95.194 * TOTAL 1 for *na: ADVOC * * *na: GNNETCOMDK * 193.89.95.210 * TOTAL 1 for *na: GNNETCOMDK * * *na: DE-REGIO-980409 * 212.218.64.3 * TOTAL 1 for *na: DE-REGIO-980409 * * *na: CH-AGRI-980422 * 212.28.159.194 * TOTAL 1 for *na: CH-AGRI-980422 * * *na: UK-COLT-980422 * 212.36.142.211 * 212.36.142.214 * 212.36.142.215 * 212.36.142.222 * 212.36.142.223 * 212.36.142.225 * TOTAL 6 for *na: UK-COLT-980422 * * *na: SCAN-SPEAKDK * 193.89.103.3 * TOTAL 1 for *na: SCAN-SPEAKDK * * *na: BELLEVUE * 193.89.103.35 * TOTAL 1 for *na: BELLEVUE * * *na: TSAI * 194.224.52.4 * 194.224.52.6 * 194.224.52.40 * 194.224.53.3 * 194.224.53.58 * 194.224.53.135 * TOTAL 6 for *na: TSAI * * *na: TSAI * 194.224.55.25 * 194.224.55.46 * TOTAL 2 for *na: TSAI * * *na: EU-ZZ-193 * 193.5.175.194 * 193.10.7.205 * 193.10.12.25 * 193.10.36.7 * 193.10.38.123 * 193.10.38.139 * 193.10.40.128 * 193.10.48.2 * 193.10.48.5 * 193.10.53.49 * 193.10.53.69 * 193.10.53.186 * 193.10.62.6 * 193.10.80.42 * 193.10.81.33 * 193.10.102.199 * 193.10.105.24 * 193.10.105.89 * 193.10.105.226 * ... * TOTAL 967 for *na: EU-ZZ-193 * * *na: PL-NASK-960626 * 195.164.232.29 * TOTAL 1 for *na: PL-NASK-960626 * * *na: PL-NASK-960520 * 193.59.87.130 * TOTAL 1 for *na: PL-NASK-960520 * * *na: PL-NASK-194-181 * 194.181.34.160 * 194.181.245.194 * TOTAL 2 for *na: PL-NASK-194-181 * * *na: NKT-PCDK * 193.89.103.18 * TOTAL 1 for *na: NKT-PCDK * * *na: MATRAC-FR * 194.117.212.2 * TOTAL 1 for *na: MATRAC-FR * * *na: LINDER-PRIVAT * 195.215.63.50 * TOTAL 1 for *na: LINDER-PRIVAT * * *na: DE-DIRECPC-980312 * 195.238.40.170 * 195.238.43.60 * 195.238.44.213 * TOTAL 3 for *na: DE-DIRECPC-980312 * * *na: SASIBDK * 193.89.126.2 * TOTAL 1 for *na: SASIBDK * * *na: IQMEDIADK * 195.215.63.62 * TOTAL 1 for *na: IQMEDIADK * * *na: PL-POZMAN-980508 * 150.254.173.3 * 150.254.173.107 * 150.254.180.2 * TOTAL 3 for *na: PL-POZMAN-980508 * * *na: RU-MTU-980511 * 212.30.179.1 * 212.30.179.4 * TOTAL 2 for *na: RU-MTU-980511 * * *na: UK-NTLI-970819 * 194.168.81.251 * 194.168.160.5 * TOTAL 2 for *na: UK-NTLI-970819 * * *na: UK-NTLI-980511 * 212.250.26.114 * 212.250.143.21 * TOTAL 2 for *na: UK-NTLI-980511 * * *na: LILLEBAELTDK * 194.192.221.24 * TOTAL 1 for *na: LILLEBAELTDK * * *na: POL-WEBVIR2 * 194.152.77.229 * TOTAL 1 for *na: POL-WEBVIR2 * * *na: LINDCADDK * 194.192.96.2 * TOTAL 1 for *na: LINDCADDK * * *na: DE-ECOMP-980518 * 212.3.157.100 * TOTAL 1 for *na: DE-ECOMP-980518 * * *na: ELFORDK * 195.215.64.26 * TOTAL 1 for *na: ELFORDK * * *na: ROSENDAHL-AS * 195.215.64.115 * TOTAL 1 for *na: ROSENDAHL-AS * * *na: CHASHUDEDK * 195.215.64.146 * TOTAL 1 for *na: CHASHUDEDK * * *na: FLEXADK * 194.192.249.2 * 194.192.249.15 * TOTAL 2 for *na: FLEXADK * * *na: SECDATACOM * 193.89.97.2 * 193.89.97.35 * TOTAL 2 for *na: SECDATACOM * * *na: SECDATACOM * 193.89.97.2 * TOTAL 1 for *na: SECDATACOM * * *na: BFEDK * 193.89.97.35 * TOTAL 1 for *na: BFEDK * * *na: TURDK * 194.192.117.60 * 194.192.117.64 * TOTAL 2 for *na: TURDK * * *na: ONLINE-TRANSLATIONDK * 193.89.97.66 * TOTAL 1 for *na: ONLINE-TRANSLATIONDK * * *na: DANAEGDK * 195.215.64.146 * TOTAL 1 for *na: DANAEGDK * * *na: SE-TRANSPAC-950303 * 194.52.127.65 * 194.52.190.12 * 194.52.237.242 * TOTAL 3 for *na: SE-TRANSPAC-950303 * * *na: SE-TRANSPAC-961022 * 195.17.40.1 * 195.17.40.2 * 195.17.40.3 * 195.17.41.130 * 195.17.41.139 * 195.17.53.100 * 195.17.59.20 * 195.17.59.25 * 195.17.59.200 * 195.17.61.3 * 195.17.61.11 * 195.17.61.206 * 195.17.66.6 * 195.17.70.86 * 195.17.70.118 * 195.17.70.212 * 195.17.72.11 * 195.17.73.5 * 195.17.73.46 * ... * TOTAL 27 for *na: SE-TRANSPAC-961022 * * *na: DE-NDH-971119 * 195.227.32.180 * 195.227.32.190 * 195.227.37.24 * 195.227.38.116 * TOTAL 4 for *na: DE-NDH-971119 * * *na: NL-DEMON-980428 * 212.238.66.22 * 212.238.74.23 * 212.238.81.157 * TOTAL 3 for *na: NL-DEMON-980428 * * *na: JALUCOM * 193.89.124.2 * TOTAL 1 for *na: JALUCOM * * *na: GKN-WHEELSDK * 193.89.97.98 * TOTAL 1 for *na: GKN-WHEELSDK * * *na: REALGRUPPENDK * 195.215.64.226 * TOTAL 1 for *na: REALGRUPPENDK * * *na: LIFDK * 194.192.117.178 * TOTAL 1 for *na: LIFDK * * *na: GETNET-MAGELLANO-NET * 193.70.88.2 * TOTAL 1 for *na: GETNET-MAGELLANO-NET * * *na: RAI-NET2 * 193.70.224.42 * 193.70.224.104 * TOTAL 2 for *na: RAI-NET2 * * *na: PRIMODK * 193.89.97.194 * TOTAL 1 for *na: PRIMODK * * *na: UTS-NET * 193.70.227.18 * TOTAL 1 for *na: UTS-NET * * *na: DE-IPF-960429 * 195.88.14.6 * 195.88.89.6 * TOTAL 2 for *na: DE-IPF-960429 * * *na: PIRELLI-NET-2 * 193.70.248.32 * TOTAL 1 for *na: PIRELLI-NET-2 * * *na: IUNET-NET-1 * 193.70.255.38 * TOTAL 1 for *na: IUNET-NET-1 * * *na: INFOSYS-NET * 193.76.126.2 * 193.76.126.138 * TOTAL 2 for *na: INFOSYS-NET * * *na: RAI-NET * 193.76.127.2 * 193.76.127.5 * 193.76.127.8 * 193.76.127.10 * TOTAL 4 for *na: RAI-NET * * *na: TLSOFT-C-BLOCK * 193.76.148.71 * TOTAL 1 for *na: TLSOFT-C-BLOCK * * *na: CSINFO-NET-C * 193.76.217.6 * 193.76.217.7 * TOTAL 2 for *na: CSINFO-NET-C * * *na: ZUCCHETTI-NET * 193.76.224.2 * 193.76.224.93 * TOTAL 2 for *na: ZUCCHETTI-NET * * *na: MANIFESTO-NET * 193.76.248.2 * TOTAL 1 for *na: MANIFESTO-NET * * *na: INFONET * 194.19.240.46 * TOTAL 1 for *na: INFONET * * *na: EU-GLOBALONE-OTHER-970109 * 194.133.38.148 * 194.133.48.10 * 194.133.50.10 * 194.133.58.101 * 194.133.58.103 * 194.133.58.104 * 194.133.58.105 * 194.133.58.131 * 194.133.130.12 * 194.133.250.5 * 194.133.250.214 * TOTAL 11 for *na: EU-GLOBALONE-OTHER-970109 * * *na: BORDINGPURUPDK * 195.215.65.106 * TOTAL 1 for *na: BORDINGPURUPDK * * *na: SEKDDFDK * 193.89.124.194 * TOTAL 1 for *na: SEKDDFDK * * *na: WINTERTHURDK * 195.215.65.194 * TOTAL 1 for *na: WINTERTHURDK * * *na: ZIMMERDK * 193.89.126.129 * 193.89.126.130 * TOTAL 2 for *na: ZIMMERDK * * *na: HUENNEBECKDK * 193.89.127.2 * TOTAL 1 for *na: HUENNEBECKDK * * *na: SI-TELEKOM-980622 * 212.30.64.7 * 212.30.64.19 * 212.30.64.220 * 212.30.94.14 * 212.30.94.73 * 212.30.94.107 * 212.30.94.138 * 212.30.94.215 * 212.30.94.230 * 212.30.94.236 * TOTAL 10 for *na: SI-TELEKOM-980622 * * *na: MEDICONDK * 195.215.67.2 * TOTAL 1 for *na: MEDICONDK * * *na: COTASDK * 195.215.67.130 * TOTAL 1 for *na: COTASDK * * *na: DANICASUPPLYDK * 195.215.66.66 * TOTAL 1 for *na: DANICASUPPLYDK * * *na: GEA-PHARM * 195.215.68.2 * 195.215.68.5 * TOTAL 2 for *na: GEA-PHARM * * *na: SKORINGEN * 195.215.66.18 * TOTAL 1 for *na: SKORINGEN * * *na: AMUSANDMOSENDK * 193.89.127.130 * 193.89.127.169 * TOTAL 2 for *na: AMUSANDMOSENDK * * *na: CINEMASCHOOLDK * 193.89.126.214 * TOTAL 1 for *na: CINEMASCHOOLDK * * *na: OKREPRODK * 193.89.126.214 * TOTAL 1 for *na: OKREPRODK * * *na: RU-COMTAT-980622 * 212.22.77.151 * TOTAL 1 for *na: RU-COMTAT-980622 * * *na: TTDK * 193.89.126.113 * 193.89.126.114 * 193.89.126.115 * 193.89.126.117 * TOTAL 4 for *na: TTDK * * *na: NYBORGPLASTDK * 193.89.135.130 * TOTAL 1 for *na: NYBORGPLASTDK * * *na: EG-DATAINFORM-NET * 195.215.69.18 * TOTAL 1 for *na: EG-DATAINFORM-NET * * *na: F-ENGELCOM * 195.215.70.3 * TOTAL 1 for *na: F-ENGELCOM * * *na: DE-KOMTEL-980519 * 212.7.131.3 * 212.7.131.33 * 212.7.131.39 * 212.7.144.10 * TOTAL 4 for *na: DE-KOMTEL-980519 * * *na: FRP-MASKINFABRIKDK * 195.215.69.83 * TOTAL 1 for *na: FRP-MASKINFABRIKDK * * *na: FOCON * 193.89.135.98 * TOTAL 1 for *na: FOCON * * *na: ZPTC-BLK04 * 209.88.92.1 * TOTAL 1 for *na: ZPTC-BLK04 * * *na: ZPTC-BLK02 * 196.2.64.1 * TOTAL 1 for *na: ZPTC-BLK02 * * *na: STUDIOSDK * 193.89.135.114 * TOTAL 1 for *na: STUDIOSDK * * *na: IWAYD1-3 * 194.128.98.225 * TOTAL 1 for *na: IWAYD1-3 * * *na: LARSEACOM * 193.89.186.2 * TOTAL 1 for *na: LARSEACOM * * *na: TWIMEDIA-NET0 * 194.130.240.52 * 194.130.240.57 * 194.130.240.117 * 194.130.240.118 * 194.130.240.123 * 194.130.240.126 * 194.130.240.149 * TOTAL 7 for *na: TWIMEDIA-NET0 * * *na: ORIFARMDK * 193.89.186.194 * TOTAL 1 for *na: ORIFARMDK * * *na: STENHOJDK * 195.215.59.82 * TOTAL 1 for *na: STENHOJDK * * *na: EUCVDK * 194.192.212.2 * 194.192.212.3 * 194.192.212.18 * 194.192.212.19 * 194.192.212.25 * TOTAL 5 for *na: EUCVDK * * *na: DANFYSIKDK * 194.192.219.66 * TOTAL 1 for *na: DANFYSIKDK * * *na: GRAFIKHUSETDK * 193.89.186.226 * TOTAL 1 for *na: GRAFIKHUSETDK * * *na: DE-BBTT-980716 * 212.21.76.1 * TOTAL 1 for *na: DE-BBTT-980716 * * *na: GOTTSOFTWAREDK * 193.89.161.2 * 193.89.161.6 * 193.89.161.7 * 193.89.161.25 * 193.89.161.28 * 193.89.161.29 * TOTAL 6 for *na: GOTTSOFTWAREDK * * *na: SE-UUNET-970731 * 195.242.38.180 * 195.242.42.195 * TOTAL 2 for *na: SE-UUNET-970731 * * *na: DELTAELEKTRONIKDK * 195.215.64.242 * TOTAL 1 for *na: DELTAELEKTRONIKDK * * *na: SYNKRONDK * 193.89.187.2 * 193.89.187.3 * 193.89.187.14 * 193.89.187.28 * 193.89.187.130 * 193.89.187.134 * 193.89.187.136 * 193.89.187.140 * 193.89.187.142 * 193.89.187.143 * 193.89.187.160 * 193.89.187.176 * 193.89.187.205 * 193.89.187.249 * 193.89.187.254 * TOTAL 15 for *na: SYNKRONDK * * *na: EU-ZZ-194 * 194.1.128.2 * 194.1.128.5 * 194.1.128.10 * 194.1.128.14 * 194.1.128.27 * 194.1.128.40 * 194.1.133.42 * 194.2.128.1 * 194.2.128.2 * 194.2.128.4 * 194.2.128.6 * 194.2.128.16 * 194.2.128.27 * 194.2.128.247 * 194.2.128.248 * 194.6.151.205 * 194.7.170.162 * 194.7.182.210 * 194.8.218.141 * ... * TOTAL 1050 for *na: EU-ZZ-194 * * *na: EU-ZZ-195 * 195.0.49.130 * 195.2.84.75 * 195.2.130.209 * 195.2.153.2 * 195.3.120.97 * 195.3.126.124 * 195.3.126.125 * 195.3.127.220 * 195.4.44.68 * 195.4.114.21 * 195.4.150.50 * 195.4.170.35 * 195.4.170.45 * 195.4.170.56 * 195.4.188.229 * 195.4.189.22 * 195.4.192.5 * 195.4.192.35 * 195.4.214.2 * ... * TOTAL 5078 for *na: EU-ZZ-195 * * *na: EU-ZZ-212 * 212.3.5.124 * 212.3.6.130 * 212.3.157.100 * 212.5.77.34 * 212.7.131.3 * 212.7.131.33 * 212.7.131.39 * 212.7.144.10 * 212.10.13.250 * 212.10.15.98 * 212.12.2.44 * 212.15.30.4 * 212.15.30.72 * 212.21.76.1 * 212.22.77.151 * 212.27.196.167 * 212.28.159.194 * 212.30.64.7 * 212.30.64.19 * ... * TOTAL 292 for *na: EU-ZZ-212 * * *na: EU-ZZ-62 * 62.0.128.40 * 62.0.128.86 * 62.0.128.107 * 62.0.128.138 * 62.0.145.135 * 62.0.145.139 * 62.0.145.232 * 62.0.146.8 * 62.0.146.10 * 62.0.146.89 * 62.0.149.78 * 62.0.149.100 * 62.0.152.1 * 62.0.153.19 * 62.0.153.39 * 62.0.153.194 * 62.0.154.12 * 62.0.154.211 * 62.0.154.235 * ... * TOTAL 369 for *na: EU-ZZ-62 * * *na: TR-FIDAN-980729 * 212.45.68.112 * TOTAL 1 for *na: TR-FIDAN-980729 * * *na: UK-CONSTELLATION-980729 * 212.47.71.4 * 212.47.74.11 * TOTAL 2 for *na: UK-CONSTELLATION-980729 * * *na: SCANTICONCOMWELL-REBILDDK * 193.89.161.130 * TOTAL 1 for *na: SCANTICONCOMWELL-REBILDDK * * *na: IONET-PSINET * 38.193.29.47 * 38.193.29.55 * 38.193.48.78 * 38.193.48.85 * 38.193.48.172 * 38.193.49.93 * 38.193.49.134 * 38.193.49.140 * 38.193.50.40 * 38.193.50.156 * 38.193.51.1 * 38.193.51.110 * 38.193.51.129 * 38.193.52.109 * 38.193.52.147 * 38.193.52.178 * 38.193.53.111 * 38.193.54.35 * 38.193.54.57 * ... * TOTAL 46 for *na: IONET-PSINET * * *na: INDUSTRIELLENVEREINIGUNG-NET * 194.118.28.226 * TOTAL 1 for *na: INDUSTRIELLENVEREINIGUNG-NET * * *na: DTDGLUD-MARSTRANDDK * 193.88.143.98 * TOTAL 1 for *na: DTDGLUD-MARSTRANDDK * * *na: AE-EMIRNET-951122 * 194.170.163.87 * 194.170.164.13 * 194.170.168.3 * 194.170.168.15 * 194.170.168.28 * 194.170.168.68 * 194.170.168.81 * 194.170.168.94 * TOTAL 8 for *na: AE-EMIRNET-951122 * * *na: NET-27-1 * 194.118.27.113 * TOTAL 1 for *na: NET-27-1 * * *na: PTT-MUSEUMDK * 193.89.63.2 * TOTAL 1 for *na: PTT-MUSEUMDK * * *na: ALFIXCOM * 195.215.73.66 * TOTAL 1 for *na: ALFIXCOM * * *na: AMUCENTER * 193.89.63.145 * TOTAL 1 for *na: AMUCENTER * * *na: BIE-BERNTSEN-ASDK * 193.89.63.66 * 193.89.63.67 * TOTAL 2 for *na: BIE-BERNTSEN-ASDK * * *na: DANMARKS-AELDREBOLIGSELSKABDK * 193.89.62.2 * 193.89.62.4 * TOTAL 2 for *na: DANMARKS-AELDREBOLIGSELSKABDK * * *na: ZPTC-BLK02 * 196.2.64.1 * TOTAL 1 for *na: ZPTC-BLK02 * * *na: EU-IBM-970507 * 62.200.88.141 * TOTAL 1 for *na: EU-IBM-970507 * * *na: BRITEUK2-NET2 * 148.181.1.40 * TOTAL 1 for *na: BRITEUK2-NET2 * * *na: TSCHUDI-EITZENDK * 195.215.69.34 * TOTAL 1 for *na: TSCHUDI-EITZENDK * * *na: CZ-EUNET-193-86 * 193.85.24.1 * 193.85.215.209 * TOTAL 2 for *na: CZ-EUNET-193-86 * * *na: FI-HTC-961129 * 194.241.193.103 * TOTAL 1 for *na: FI-HTC-961129 * * *na: DEVI-DK * 195.24.10.150 * TOTAL 1 for *na: DEVI-DK * * *na: KOMMUNEKREDIT-DK * 195.24.10.138 * TOTAL 1 for *na: KOMMUNEKREDIT-DK * * *na: INNOVISION-DK * 195.24.10.113 * 195.24.10.120 * 195.24.10.121 * TOTAL 3 for *na: INNOVISION-DK * * *na: FAERCHPLASTDK * 195.215.74.130 * TOTAL 1 for *na: FAERCHPLASTDK * * *na: NETXPERTDK * 193.89.60.2 * 193.89.60.23 * TOTAL 2 for *na: NETXPERTDK * * *na: INTERLUX * 194.176.42.34 * TOTAL 1 for *na: INTERLUX * * *na: GR-HELLASNET-980821 * 212.54.220.208 * TOTAL 1 for *na: GR-HELLASNET-980821 * * *na: CASA-DE * 194.140.53.2 * TOTAL 1 for *na: CASA-DE * * *na: DE-MAZ-970704 * 195.179.11.129 * 195.179.50.126 * 195.179.62.60 * 195.179.76.20 * 195.179.80.10 * 195.179.87.85 * 195.179.246.2 * 195.179.246.26 * 195.179.251.2 * 195.179.251.3 * TOTAL 10 for *na: DE-MAZ-970704 * * *na: KILROYTRAVELSCOM * 193.89.62.234 * 193.89.62.235 * TOTAL 2 for *na: KILROYTRAVELSCOM * * *na: THORANDERSEN * 193.89.60.194 * TOTAL 1 for *na: THORANDERSEN * * *na: FR-AAC * 194.206.113.1 * TOTAL 1 for *na: FR-AAC * * *na: JAN-IMPORTDK * 193.89.103.26 * TOTAL 1 for *na: JAN-IMPORTDK * * *na: SVANEKAER * 195.215.71.17 * 195.215.71.18 * TOTAL 2 for *na: SVANEKAER * * *na: CZ-VOL-980831 * 212.27.196.167 * TOTAL 1 for *na: CZ-VOL-980831 * * *na: ODDERAVISDK * 195.215.76.144 * TOTAL 1 for *na: ODDERAVISDK * * *na: UK-SAQNET-961021 * 195.2.130.209 * 195.2.153.2 * TOTAL 2 for *na: UK-SAQNET-961021 * * *na: SE-TELIANET-960201 * 194.236.32.36 * 194.236.32.61 * 194.236.82.23 * 194.236.105.103 * 194.237.125.22 * TOTAL 5 for *na: SE-TELIANET-960201 * * *na: SE-TELIANET-960206 * 194.23.231.66 * TOTAL 1 for *na: SE-TELIANET-960206 * * *na: HOWDENDK * 193.89.136.1 * TOTAL 1 for *na: HOWDENDK * * *na: FI-FUNET-960624 * 195.148.56.127 * 195.148.56.147 * TOTAL 2 for *na: FI-FUNET-960624 * * *na: FI-FUNET-950315 * 193.166.225.182 * 193.167.87.93 * TOTAL 2 for *na: FI-FUNET-950315 * * *na: DE-ROKA-960514 * 62.104.16.176 * 62.104.19.150 * 62.104.24.38 * 62.104.24.115 * 62.104.29.88 * 62.104.31.72 * 62.104.38.1 * 62.104.39.1 * 62.104.41.131 * 62.104.42.35 * 62.104.42.40 62.104.43.1 * 62.104.43.2 * 62.104.54.1 * 62.104.64.10 * 62.104.64.11 * 62.104.64.32 * 62.104.64.33 * TOTAL 18 for *na: DE-ROKA-960514 * * *na: DE-ROKA-970303 * 194.97.65.175 * 194.97.69.231 * TOTAL 2 for *na: DE-ROKA-970303 * * *na: DE-ROKA-960514 * 195.4.44.68 * 195.4.114.21 * 195.4.150.50 * 195.4.170.35 * 195.4.170.45 * 195.4.170.56 * 195.4.188.229 * 195.4.189.22 * 195.4.192.5 * 195.4.192.35 * 195.4.214.2 * 195.4.215.2 * 195.4.215.254 * TOTAL 13 for *na: DE-ROKA-960514 * * *na: UK-EASYNET-960801 * 195.40.65.29 * 195.40.65.55 * 195.40.65.113 * 195.40.65.231 * 195.40.66.74 * TOTAL 5 for *na: UK-EASYNET-960801 * * *na: NAF-AS * 195.215.77.2 * TOTAL 1 for *na: NAF-AS * * *na: CWOSISDK * 193.89.29.66 * TOTAL 1 for *na: CWOSISDK * * *na: SUNET-GBG-REGION-WEST * 193.10.160.20 * 193.10.163.20 * 193.10.166.34 * 193.10.170.21 * 193.10.170.74 * 193.10.171.115 * 193.10.171.140 * 193.10.176.21 * 193.10.176.23 * 193.10.176.25 * 193.10.185.3 * 193.10.186.2 * 193.10.186.142 * 193.10.192.40 * 193.10.194.29 * 193.10.198.66 * 193.10.200.8 * 193.10.202.40 * 193.10.208.10 * ... * TOTAL 33 for *na: SUNET-GBG-REGION-WEST * * *na: SUNET-GBG-REGION-WEST * 193.10.240.5 * 193.10.240.131 * 193.10.240.166 * 193.10.240.191 * 193.10.244.100 * TOTAL 5 for *na: SUNET-GBG-REGION-WEST * * *na: SUNET-GBG-REGION-WEST * 193.10.163.20 * TOTAL 1 for *na: SUNET-GBG-REGION-WEST * * *na: GIGTFORENINGEN-AARHUSDK * 193.89.29.131 * 193.89.29.132 * 193.89.29.133 * 193.89.29.134 * 193.89.29.135 * 193.89.29.136 * 193.89.29.137 * TOTAL 7 for *na: GIGTFORENINGEN-AARHUSDK * * *na: ELBODAN * 193.89.29.168 * TOTAL 1 for *na: ELBODAN * * *na: SE-TELIANET-930901 * 194.16.15.18 * 194.16.15.19 * 194.16.203.148 * 194.16.211.62 * 194.17.155.17 * 194.17.195.198 194.17.195.253 * 194.17.197.211 * 194.17.211.228 * 194.18.167.2 * 194.18.199.1 * 194.18.243.233 * TOTAL 12 for *na: SE-TELIANET-930901 * * *na: SE-TELIANET-930901 * 193.45.95.248 * 193.45.215.45 * TOTAL 2 for *na: SE-TELIANET-930901 * * *na: UNITMESSERDK * 193.89.60.178 * TOTAL 1 for *na: UNITMESSERDK * * *na: ESFDK * 195.215.128.66 * TOTAL 1 for *na: ESFDK * * *na: IT-INTERBUSINESS-980401 * 212.210.31.246 * TOTAL 1 for *na: IT-INTERBUSINESS-980401 * * *na: IT-INTERBUSINESS-970312 * 195.103.83.200 * TOTAL 1 for *na: IT-INTERBUSINESS-970312 * * *na: BELWUE * 129.143.2.1 * 129.143.2.4 * 129.143.75.11 * 129.143.96.137 * TOTAL 4 for *na: BELWUE * * *na: DK-IMAGE-SCANDINAVIA * 194.234.182.2 * 194.234.182.3 * 194.234.182.5 * 194.234.182.6 * 194.234.182.7 * 194.234.182.9 * 194.234.182.10 * 194.234.182.11 * 194.234.182.13 * 194.234.182.16 * 194.234.182.20 * 194.234.182.23 * 194.234.182.28 * 194.234.182.29 * 194.234.182.32 * 194.234.182.33 * 194.234.182.35 * 194.234.182.36 * 194.234.182.37 * ... * TOTAL 156 for *na: DK-IMAGE-SCANDINAVIA * * *na: BASCONDK * 195.215.128.130 * TOTAL 1 for *na: BASCONDK * * *na: FERRANTI-COMPUTER-SYSTEMS-NV-NET * 194.7.182.210 * TOTAL 1 for *na: FERRANTI-COMPUTER-SYSTEMS-NV-NET * * *na: SUNET-GBG-REGION-WEST * 193.10.160.20 * 193.10.163.20 * 193.10.166.34 * 193.10.170.21 * 193.10.170.74 * 193.10.171.115 * 193.10.171.140 * 193.10.176.21 * 193.10.176.23 * 193.10.176.25 * 193.10.185.3 * 193.10.186.2 * 193.10.186.142 * 193.10.192.40 * 193.10.194.29 * 193.10.198.66 * 193.10.200.8 * 193.10.202.40 * 193.10.208.10 * ... * TOTAL 38 for *na: SUNET-GBG-REGION-WEST * * *na: BRT-VHSDR-NET * 171.28.22.20 * 171.29.105.221 * TOTAL 2 for *na: BRT-VHSDR-NET * * *na: EG-IE-951129 * 194.79.109.18 * 194.79.109.27 * 194.79.119.56 * TOTAL 3 for *na: EG-IE-951129 * * *na: IT-NETTUNO-940726 * 193.207.158.100 * TOTAL 1 for *na: IT-NETTUNO-940726 * * *na: UK-NETHEAD-960314 * 194.247.234.24 * 194.247.234.39 * TOTAL 2 for *na: UK-NETHEAD-960314 * * *na: UA-ZZ-940217 * 194.44.212.194 * TOTAL 1 for *na: UA-ZZ-940217 * * *na: DE-XLINK-940228 * 194.45.197.100 * TOTAL 1 for *na: DE-XLINK-940228 * * *na: BE-INTERPAC-960213 * 194.78.15.195 * 194.78.21.76 * 194.78.27.1 * 194.78.27.10 * 194.78.33.48 * 194.78.36.5 * 194.78.41.100 * 194.78.42.1 * 194.78.42.2 * 194.78.45.194 * 194.78.45.208 * 194.78.47.3 * 194.78.47.12 * 194.78.47.66 * 194.78.47.78 * 194.78.47.85 * 194.78.48.13 * 194.78.50.1 * 194.78.50.249 * ... * TOTAL 39 for *na: BE-INTERPAC-960213 * * *na: IR-DCC-970722 * 195.146.46.2 * TOTAL 1 for *na: IR-DCC-970722 * * *na: IT-TIN-980225 * 212.216.2.44 * 212.216.3.125 * 212.216.3.152 * 212.216.4.161 * 212.216.4.232 * 212.216.5.144 * 212.216.6.91 * 212.216.6.184 * 212.216.6.195 * 212.216.7.56 * 212.216.7.135 * 212.216.8.215 * 212.216.11.53 * 212.216.13.217 * 212.216.14.73 * 212.216.14.133 * 212.216.15.17 * 212.216.20.213 * 212.216.20.235 * ... * TOTAL 147 for *na: IT-TIN-980225 * * *na: RU-TULATELECOM-980220 * 212.12.2.44 * TOTAL 1 for *na: RU-TULATELECOM-980220 * * *na: SE-OLL * 194.103.185.80 * TOTAL 1 for *na: SE-OLL * * *na: CH-CYBERLINK-980918 * 212.55.207.10 * 212.55.207.15 * TOTAL 2 for *na: CH-CYBERLINK-980918 * * *na: UK-VBCNET-960404 * 194.207.148.170 * 194.207.149.126 * 194.207.190.65 * TOTAL 3 for *na: UK-VBCNET-960404 * * *na: AT-VIANET-960612 * 194.96.97.5 * 194.96.209.97 * TOTAL 2 for *na: AT-VIANET-960612 * * *na: BIMCO * 195.24.4.34 * 195.24.4.37 * TOTAL 2 for *na: BIMCO * * *na: STATOTECH * 195.24.4.13 * TOTAL 1 for *na: STATOTECH * * *na: INETPARTNER-DK * 195.24.3.10 * 195.24.3.11 * 195.24.3.73 * 195.24.3.76 * 195.24.3.86 * 195.24.3.89 * 195.24.3.91 * 195.24.3.95 * 195.24.3.100 * 195.24.3.105 * 195.24.3.106 * 195.24.3.111 * 195.24.3.112 * 195.24.3.114 * 195.24.3.125 * 195.24.3.130 * 195.24.3.131 * 195.24.3.134 * 195.24.3.135 * ... * TOTAL 45 for *na: INETPARTNER-DK * * *na: OM-GTO-OMAN-980924 * 212.72.7.25 * TOTAL 1 for *na: OM-GTO-OMAN-980924 * * *na: MUNTERSDK * 195.215.131.195 * TOTAL 1 for *na: MUNTERSDK * * *na: DIABETESFORENINGENDK * 195.215.131.227 * TOTAL 1 for *na: DIABETESFORENINGENDK * * *na: UK-NETLINK-960725 * 194.88.153.163 * 194.88.155.142 * 194.88.157.175 * TOTAL 3 for *na: UK-NETLINK-960725 * * *na: DE-IVM-971022 * 62.204.1.1 * 62.204.1.2 * TOTAL 2 for *na: DE-IVM-971022 * * *na: DE-IVM-971021 * 195.78.161.1 * TOTAL 1 for *na: DE-IVM-971021 * * *na: DE-IVM-971231 * 195.247.224.195 * 195.247.235.131 * TOTAL 2 for *na: DE-IVM-971231 * * *na: WINDFELDDK * 195.215.132.70 * TOTAL 1 for *na: WINDFELDDK * * *na: PETERSRESTHALDK * 195.215.130.146 * TOTAL 1 for *na: PETERSRESTHALDK * * *na: NAPRI-SK * 194.1.128.2 * 194.1.128.5 * 194.1.128.10 * 194.1.128.14 * 194.1.128.27 * 194.1.128.40 * 194.1.133.42 * TOTAL 7 for *na: NAPRI-SK * * *na: DE-CYBERNET-970513 * 195.143.13.2 * 195.143.13.102 * 195.143.49.29 * 195.143.51.135 * 195.143.108.2 * 195.143.109.2 * 195.143.109.66 * 195.143.109.117 * 195.143.114.89 * 195.143.116.34 * 195.143.118.1 * 195.143.118.5 * 195.143.118.6 * 195.143.118.12 * 195.143.128.5 * 195.143.162.68 * 195.143.162.93 * TOTAL 17 for *na: DE-CYBERNET-970513 * * *na: SE-SKNET-970205 * 195.22.67.2 * 195.22.69.2 * 195.22.69.3 * 195.22.69.4 * 195.22.69.7 * 195.22.70.10 * 195.22.70.17 * 195.22.70.181 * TOTAL 8 for *na: SE-SKNET-970205 * * *na: GRAINTECCOM * 195.215.132.194 * TOTAL 1 for *na: GRAINTECCOM * * *na: JACODANDK * 195.215.132.202 * TOTAL 1 for *na: JACODANDK * * *na: CKUDK * 195.215.129.132 * TOTAL 1 for *na: CKUDK * * *na: TKDK * 195.215.133.66 * TOTAL 1 for *na: TKDK * * *na: PHOTOTEAMDK * 195.215.133.82 * TOTAL 1 for *na: PHOTOTEAMDK * * *na: GTO-OM-BLK02 * 212.72.7.25 * TOTAL 1 for *na: GTO-OM-BLK02 * * *na: DIRECTOFFICEDK * 195.215.133.114 * TOTAL 1 for *na: DIRECTOFFICEDK * * *na: TVMIDTVESTDK * 195.215.134.2 * TOTAL 1 for *na: TVMIDTVESTDK * * *na: UK-WEBFACTORY-960826 * 195.134.11.226 * TOTAL 1 for *na: UK-WEBFACTORY-960826 * * *na: DK-PROVENTUM-970410 * 195.216.193.34 * 195.216.193.36 * 195.216.193.37 * 195.216.193.38 * 195.216.193.43 * 195.216.193.49 * 195.216.193.61 * 195.216.193.166 * 195.216.193.180 * 195.216.208.34 * 195.216.208.99 * 195.216.208.101 * 195.216.215.11 * 195.216.215.12 * 195.216.215.19 * 195.216.215.24 * 195.216.215.25 * 195.216.215.32 * 195.216.215.100 * ... * TOTAL 20 for *na: DK-PROVENTUM-970410 * * *na: FH-AALEN * 141.18.1.12 * 141.18.15.59 * TOTAL 2 for *na: FH-AALEN * * *na: IT-WIND-981015 * 212.245.248.178 * TOTAL 1 for *na: IT-WIND-981015 * * *na: RIDK * 195.215.134.214 * TOTAL 1 for *na: RIDK * * *na: RU-ROSNIIROS-194-85 * 194.85.103.33 * 194.85.173.117 * 194.85.173.199 * 194.85.255.154 * TOTAL 4 for *na: RU-ROSNIIROS-194-85 * * *na: RU-ROSNIIROS-960103 * 194.226.125.67 * 194.226.135.100 * 194.226.198.34 * 194.226.198.36 * TOTAL 4 for *na: RU-ROSNIIROS-960103 * * *na: RU-ROSNIIROS-960719 * 195.208.252.2 * TOTAL 1 for *na: RU-ROSNIIROS-960719 * * *na: RUWELDK * 195.215.135.34 * TOTAL 1 for *na: RUWELDK * * *na: MSASDK * 195.215.135.130 * 195.215.135.133 * TOTAL 2 for *na: MSASDK * * *na: DIGITAL-FOREST-NET2 * 208.208.207.3 * 208.208.207.27 * 208.208.207.65 * 208.208.207.254 * TOTAL 4 for *na: DIGITAL-FOREST-NET2 * * *na: SE-PI-970311 * 195.7.82.196 * TOTAL 1 for *na: SE-PI-970311 * * *na: IBC-NET * 145.253.66.1 * 145.253.72.153 * 145.253.74.51 * 145.253.76.3 * 145.253.76.30 * 145.253.76.31 * 145.253.76.65 * 145.253.76.161 * 145.253.82.38 * 145.253.94.173 * 145.253.95.53 * 145.253.95.164 * 145.253.112.31 * 145.253.113.31 * TOTAL 14 for *na: IBC-NET * * *na: ARCOR-IP * 145.253.2.9 * 145.253.2.35 * 145.253.2.36 * 145.253.2.75 * 145.253.66.1 * 145.253.72.153 * 145.253.74.51 * 145.253.76.3 * 145.253.76.30 * 145.253.76.31 * 145.253.76.65 * 145.253.76.161 * 145.253.82.38 * 145.253.94.173 * 145.253.95.53 * 145.253.95.164 * 145.253.112.31 * 145.253.113.31 * TOTAL 18 for *na: ARCOR-IP * * *na: CH-SUNRISE-970513 * 195.141.11.126 * 195.141.56.5 * 195.141.76.164 * 195.141.180.227 * 195.141.237.22 * 195.141.237.245 * 195.141.237.251 * 195.141.244.211 * TOTAL 8 for *na: CH-SUNRISE-970513 * * *na: SCANTOPSDK * 195.215.136.98 * TOTAL 1 for *na: SCANTOPSDK * * *na: DEBELDK * 195.215.136.131 * TOTAL 1 for *na: DEBELDK * * *na: GR-FORTHNET-951220 * 194.219.168.164 * 194.219.171.30 * 194.219.171.68 * TOTAL 3 for *na: GR-FORTHNET-951220 * * *na: NL-EURONET-961118 * 194.134.23.228 * 194.134.33.34 * 194.134.49.33 * 194.134.49.70 * 194.134.73.25 * 194.134.73.31 * 194.134.73.94 * 194.134.76.33 * 194.134.109.1 * 194.134.109.6 * 194.134.109.9 * 194.134.109.27 * 194.134.109.29 * 194.134.111.106 * 194.134.123.245 * 194.134.124.29 * 194.134.124.150 * 194.134.124.205 * TOTAL 18 for *na: NL-EURONET-961118 * * *na: EU-EUNET-950315 * 193.73.103.80 * 193.73.103.82 * 193.73.103.121 * TOTAL 3 for *na: EU-EUNET-950315 * * *na: EU-EUNET-930901 * 193.120.133.201 * 193.120.134.130 * TOTAL 2 for *na: EU-EUNET-930901 * * *na: EU-EUNET-950526 * 193.121.83.66 * TOTAL 1 for *na: EU-EUNET-950526 * * *na: EU-EUNET-960514 * 193.127.68.3 * 193.127.226.188 * TOTAL 2 for *na: EU-EUNET-960514 * * *na: EU-EUNET-950811 * 194.191.254.254 * TOTAL 1 for *na: EU-EUNET-950811 * * *na: EU-EUNET-970509 * 195.139.27.215 * TOTAL 1 for *na: EU-EUNET-970509 * * *na: EU-EUNET-970509 * 195.207.23.48 * 195.207.28.2 * TOTAL 2 for *na: EU-EUNET-970509 * * *na: EU-EUNET-980414 * 212.226.249.1 * TOTAL 1 for *na: EU-EUNET-980414 * * *na: FORTH * 139.91.1.1 * 139.91.1.17 * 139.91.191.3 * 139.91.191.203 * TOTAL 4 for *na: FORTH * * *na: MANBW-DK * 195.24.2.55 * 195.24.2.60 * TOTAL 2 for *na: MANBW-DK * * *na: UK-DIALNET-980223 * 212.44.5.10 * TOTAL 1 for *na: UK-DIALNET-980223 * * *na: ES-CESATEL-951122 * 194.140.67.10 * 194.140.71.186 * 194.140.80.4 * TOTAL 3 for *na: ES-CESATEL-951122 * * *na: STAERKDK * 195.215.136.194 * TOTAL 1 for *na: STAERKDK * * *na: CNET * 139.100.0.30 * 139.100.0.155 * TOTAL 2 for *na: CNET * * *na: PL-TPSA-981028 * 212.160.3.85 * 212.160.15.48 * 212.160.15.168 * 212.160.15.187 * 212.160.16.8 * 212.160.26.55 * 212.160.26.74 * 212.160.26.120 * 212.160.28.252 * 212.160.44.126 * 212.160.48.150 * 212.160.48.208 * 212.160.62.52 * 212.160.62.61 * TOTAL 14 for *na: PL-TPSA-981028 * * *na: SK-NETLAB-960927 * 195.168.0.2 * 195.168.1.2 * 195.168.1.4 * 195.168.1.20 * 195.168.1.24 * 195.168.13.34 * 195.168.13.35 * 195.168.47.34 * 195.168.177.33 * TOTAL 9 for *na: SK-NETLAB-960927 * * *na: TRICON-DK * 195.24.15.71 * TOTAL 1 for *na: TRICON-DK * * *na: SK-PUBNET-981102 * 212.81.12.11 * 212.81.12.12 * TOTAL 2 for *na: SK-PUBNET-981102 * * *na: RU-OMSK-970725 * 195.162.37.130 * TOTAL 1 for *na: RU-OMSK-970725 * * *na: BG-BIT-970819 * 195.34.104.30 * 195.34.107.10 * 195.34.115.249 * TOTAL 3 for *na: BG-BIT-970819 * * *na: ADVMB * 195.215.138.50 * TOTAL 1 for *na: ADVMB * * *na: PMB-DPFDK * 195.215.138.83 * TOTAL 1 for *na: PMB-DPFDK * * *na: UK-DEMON-981104 * 212.229.26.29 * 212.229.72.44 * 212.229.74.96 * 212.229.80.182 * 212.229.87.31 * TOTAL 5 for *na: UK-DEMON-981104 * * *na: DE-ZZ-940420 * 194.55.63.2 * TOTAL 1 for *na: DE-ZZ-940420 * * *na: DE-ZZ-950424 * 194.156.201.6 * 194.156.201.33 * 194.156.201.194 * TOTAL 3 for *na: DE-ZZ-950424 * * *na: SE-BYGGDOK * 193.10.7.205 * TOTAL 1 for *na: SE-BYGGDOK * * *na: SE-KB * 193.10.12.25 * TOTAL 1 for *na: SE-KB * * *na: SE-NRM * 193.10.36.7 * TOTAL 1 for *na: SE-NRM * * *na: SE-KTH-HANINGE * 193.10.38.123 * 193.10.38.139 * TOTAL 2 for *na: SE-KTH-HANINGE * * *na: SE-CBNA * 193.10.40.128 * TOTAL 1 for *na: SE-CBNA * * *na: SE-HHS * 193.10.48.2 * 193.10.48.5 * TOTAL 2 for *na: SE-HHS * * *na: SE-HGOT * 193.10.53.49 * 193.10.53.69 * 193.10.53.186 * TOTAL 3 for *na: SE-HGOT * * *na: SE-MHS * 193.10.62.6 * TOTAL 1 for *na: SE-MHS * * *na: SUNET-34M * 193.10.80.42 * TOTAL 1 for *na: SUNET-34M * * *na: LUTH-34M * 193.10.81.33 * TOTAL 1 for *na: LUTH-34M * * *na: SE-SLUUME * 193.10.102.199 * TOTAL 1 for *na: SE-SLUUME * * *na: SE-MITTHS * 193.10.105.24 * 193.10.105.89 * 193.10.105.226 * 193.10.107.3 * 193.10.108.69 * 193.10.108.139 * 193.10.112.99 * 193.10.119.68 * 193.10.119.226 * TOTAL 9 for *na: SE-MITTHS * * *na: SE-MITTHS2 * 193.10.250.42 * 193.10.250.156 * 193.10.250.192 * 193.10.251.75 * TOTAL 4 for *na: SE-MITTHS2 * * *na: HHNET * 194.47.0.30 * 194.47.1.11 * 194.47.16.32 * 194.47.17.165 * TOTAL 4 for *na: HHNET * * *na: HKRNET * 194.47.25.8 * 194.47.27.190 * 194.47.29.146 * 194.47.38.61 * 194.47.47.12 * TOTAL 5 for *na: HKRNET * * *na: ALNET * 194.47.49.5 * 194.47.50.19 * 194.47.55.18 * 194.47.55.213 * TOTAL 4 for *na: ALNET * * *na: VAXJO-NET * 194.47.65.11 * 194.47.81.215 * 194.47.89.77 * 194.47.99.36 * 194.47.99.100 * 194.47.103.119 * 194.47.103.188 * 194.47.106.85 * 194.47.107.110 * TOTAL 9 for *na: VAXJO-NET * * *na: NL-NLNET-970903 * 195.193.225.9 * 195.193.225.79 * TOTAL 2 for *na: NL-NLNET-970903 * * *na: NL-NLNET-960122 * 194.229.115.34 * 194.229.190.5 * 194.229.213.59 * TOTAL 3 for *na: NL-NLNET-960122 * * *na: JBMEDIADK * 195.215.138.130 * TOTAL 1 for *na: JBMEDIADK * * *na: MOLHU * 171.31.0.1 * TOTAL 1 for *na: MOLHU * * *na: FI-SONERA-193-208-193-211 * 193.208.135.186 * TOTAL 1 for *na: FI-SONERA-193-208-193-211 * * *na: FI-SONERA-940902 * 194.89.25.34 * 194.89.179.18 * TOTAL 2 for *na: FI-SONERA-940902 * * *na: FI-SONERA-951207 * 194.215.205.32 * TOTAL 1 for *na: FI-SONERA-951207 * * *na: FI-SONERA-960306 * 194.251.255.57 * 194.251.255.231 * 194.251.255.232 * 194.251.255.233 * 194.251.255.234 * TOTAL 5 for *na: FI-SONERA-960306 * * *na: RU-WEBPLUS-970414 * 195.131.23.250 * 195.131.53.61 * TOTAL 2 for *na: RU-WEBPLUS-970414 * * *na: STATO-DK * 195.24.14.101 * TOTAL 1 for *na: STATO-DK * * *na: UK-DEMON-961002 * 195.11.242.207 * 195.11.242.250 * 195.11.243.18 * 195.11.243.21 * TOTAL 4 for *na: UK-DEMON-961002 * * *na: UK-DEMON-980220 * 212.240.154.129 * 212.240.154.130 * 212.240.194.226 * 212.240.234.157 * 212.240.235.17 * 212.240.237.41 * TOTAL 6 for *na: UK-DEMON-980220 * * *na: UK-DEMON-970724 * 193.237.3.146 * 193.237.17.8 * 193.237.50.62 * 193.237.65.172 * 193.237.93.177 * 193.237.97.210 * 193.237.132.136 * 193.237.137.84 * 193.237.149.241 * 193.237.154.85 * 193.237.168.51 * 193.237.174.39 * 193.237.174.200 * 193.237.213.213 * 193.237.228.150 * 193.237.239.104 * 193.237.250.55 * TOTAL 17 for *na: UK-DEMON-970724 * * *na: UK-DEMON-970729 * 193.238.128.81 * 193.238.132.187 * 193.238.136.14 * 193.238.147.190 * 193.238.155.232 * 193.238.159.62 * 193.238.162.107 * 193.238.173.52 * 193.238.181.172 * 193.238.190.135 * 193.238.193.22 * 193.238.199.48 * 193.238.200.178 * 193.238.203.139 * 193.238.206.58 * 193.238.210.160 * 193.238.213.3 * 193.238.215.178 * 193.238.219.11 * ... * TOTAL 37 for *na: UK-DEMON-970729 * * *na: SE-UTFORS-981109 * 212.105.59.2 * 212.105.59.7 * 212.105.59.21 * 212.105.59.120 * 212.105.60.72 * 212.105.60.178 * 212.105.62.15 * TOTAL 7 for *na: SE-UTFORS-981109 * * *na: UK-BT-961016 * 194.75.84.1 * 194.75.145.242 * TOTAL 2 for *na: UK-BT-961016 * * *na: UK-BT-961016 * 195.99.65.212 * 195.99.66.211 * TOTAL 2 for *na: UK-BT-961016 * * *na: RU-TCNET-970306 * 195.230.83.2 * 195.230.83.10 * TOTAL 2 for *na: RU-TCNET-970306 * * *na: INTEROUTEDK * 195.215.139.2 * TOTAL 1 for *na: INTEROUTEDK * * *na: FR-OLEANE-970501 * 62.161.250.65 * 62.161.250.67 * TOTAL 2 for *na: FR-OLEANE-970501 * * *na: COMPNEWS * 144.178.159.75 * 144.178.159.77 * TOTAL 2 for *na: COMPNEWS * * *na: FR-TRANSPAC-980416 * 212.234.33.66 * 212.234.56.3 * 212.234.106.77 * TOTAL 3 for *na: FR-TRANSPAC-980416 * * *na: UK-CABLEINET-960227 * 194.117.129.2 * 194.117.129.214 * 194.117.129.235 * 194.117.131.92 * 194.117.143.2 * TOTAL 5 for *na: UK-CABLEINET-960227 * * *na: UK-CABLEINET-960703 * 195.188.98.1 * 195.188.98.2 * 195.188.107.6 * 195.188.107.40 * 195.188.107.42 * 195.188.107.45 * 195.188.134.2 * 195.188.134.24 * 195.188.134.111 * 195.188.151.148 * 195.188.160.2 * 195.188.160.7 * 195.188.160.117 * 195.188.160.156 * 195.188.161.203 * 195.188.168.7 * 195.188.171.2 * 195.188.171.13 * 195.188.171.15 * ... * TOTAL 27 for *na: UK-CABLEINET-960703 * * *na: CH-PLUSNET-960123 * 194.230.4.36 * TOTAL 1 for *na: CH-PLUSNET-960123 * * *na: DK-STOFANET-980226 * 212.10.13.250 * 212.10.15.98 * TOTAL 2 for *na: DK-STOFANET-980226 * * *na: UK-POL-960119 * 194.152.77.229 * TOTAL 1 for *na: UK-POL-960119 * * *na: UK-XARA-960916 * 195.224.85.1 * 195.224.85.201 * 195.224.85.202 * 195.224.85.204 * 195.224.107.12 * 195.224.107.17 * 195.224.107.24 * 195.224.107.25 * 195.224.107.50 * 195.224.107.57 * 195.224.107.150 * 195.224.107.248 * 195.224.117.26 * 195.224.160.10 * 195.224.160.11 * 195.224.160.253 * 195.224.188.1 * 195.224.188.13 * 195.224.189.1 * ... * TOTAL 25 for *na: UK-XARA-960916 * * *na: RU-RELLINE-960225 * 195.146.72.146 * 195.146.79.150 * TOTAL 2 for *na: RU-RELLINE-960225 * * *na: RU-MCNTT-980119 * 195.28.39.81 * TOTAL 1 for *na: RU-MCNTT-980119 * * *na: SE-SVIKKOM * 194.68.13.18 * 194.68.13.19 * TOTAL 2 for *na: SE-SVIKKOM * * *na: UK-INS-194-205-16 * 194.205.28.15 * 194.205.70.14 * TOTAL 2 for *na: UK-INS-194-205-16 * * *na: DE-MBT-970808 * 195.189.0.34 * 195.189.0.39 * 195.189.1.39 * TOTAL 3 for *na: DE-MBT-970808 * * *na: UK-DEMON-951221 * 194.222.1.211 * 194.222.6.8 * 194.222.26.223 * 194.222.44.212 * 194.222.52.131 * 194.222.56.100 * 194.222.57.188 * 194.222.62.30 * 194.222.62.209 * 194.222.65.237 * 194.222.68.241 * 194.222.89.17 * 194.222.90.167 * 194.222.94.179 * 194.222.101.123 * 194.222.113.146 * 194.222.124.124 * 194.222.125.39 * 194.222.160.92 * ... * TOTAL 28 for *na: UK-DEMON-951221 * * *na: DE-SGH-980407 * 193.218.205.10 * 193.218.205.42 * 193.218.210.46 * 193.218.210.188 * 193.218.216.10 * TOTAL 5 for *na: DE-SGH-980407 * * *na: NL-UNISOURCE-951004 * 193.172.127.93 * TOTAL 1 for *na: NL-UNISOURCE-951004 * * *na: NL-UNISOURCE-950410 * 194.151.126.99 * 194.151.126.166 * 194.151.224.7 * 194.151.231.130 * 194.151.231.194 * 194.151.234.18 * TOTAL 6 for *na: NL-UNISOURCE-950410 * * *na: FR-TRANSPAC-970307 * 195.101.197.117 * 195.101.197.216 * 195.101.233.253 * TOTAL 3 for *na: FR-TRANSPAC-970307 * * *na: FR-TRANSPAC-960304 * 194.250.180.54 * TOTAL 1 for *na: FR-TRANSPAC-960304 * * *na: FR-TRANSPAC-194-206 * 194.206.113.1 * 194.206.217.49 * 194.206.218.35 * 194.206.218.40 * TOTAL 4 for *na: FR-TRANSPAC-194-206 * * *na: FR-TRANSPAC-951019 * 194.51.238.1 * 194.51.238.2 * TOTAL 2 for *na: FR-TRANSPAC-951019 * * *na: RU-GLASNET-961224 * 195.218.159.130 * TOTAL 1 for *na: RU-GLASNET-961224 * * *na: SE-TELENORDIA-980908 * 195.163.66.82 * 195.163.66.84 * TOTAL 2 for *na: SE-TELENORDIA-980908 * * *na: SE-TELENORDIA-960612 * 195.100.172.2 * 195.100.176.194 195.100.208.76 * TOTAL 3 for *na: SE-TELENORDIA-960612 * * *na: DE-ZZ-930921 * 194.15.149.71 * TOTAL 1 for *na: DE-ZZ-930921 * * *na: DE-GTN-960124 * 194.231.199.2 * TOTAL 1 for *na: DE-GTN-960124 * * *na: BANGOR * 147.143.2.1 * 147.143.200.22 * TOTAL 2 for *na: BANGOR * * *na: EU-GLOBALONE-NORTH-970327 * 195.119.76.11 * 195.119.76.20 * 195.119.102.102 * 195.119.102.178 * 195.119.102.207 * 195.119.156.34 * 195.119.156.35 * 195.119.160.38 * 195.119.160.230 * 195.119.180.14 * 195.119.184.2 * 195.119.184.42 * 195.119.184.130 * 195.119.190.2 * 195.119.196.2 * 195.119.209.117 * TOTAL 16 for *na: EU-GLOBALONE-NORTH-970327 * * *na: EU-GLOBALONE-NORTH-961222 * 194.234.0.40 * 194.234.0.60 * 194.234.0.66 * 194.234.0.130 * 194.234.0.165 * 194.234.0.210 * 194.234.1.98 * 194.234.1.130 * 194.234.1.162 * 194.234.1.163 * 194.234.1.164 * 194.234.1.177 * 194.234.1.181 * 194.234.1.187 * 194.234.2.67 * 194.234.2.98 * 194.234.2.162 * 194.234.3.98 * 194.234.3.130 * ... * TOTAL 456 for *na: EU-GLOBALONE-NORTH-961222 * * *na: DSM-NET * 163.175.153.2 * TOTAL 1 for *na: DSM-NET * * *na: CH-INNET-960807 * 195.70.1.100 * TOTAL 1 for *na: CH-INNET-960807 * * *na: IT-CLIO-961016 * 195.60.129.43 * 195.60.139.14 * TOTAL 2 for *na: IT-CLIO-961016 * * *na: UK-IMMINUS-960603 * 193.193.121.68 * TOTAL 1 for *na: UK-IMMINUS-960603 * * *na: UK-MAILBOX-970903 * 195.82.101.170 * TOTAL 1 for *na: UK-MAILBOX-970903 * * *na: ISICOM-NET1 * 194.98.30.130 * TOTAL 1 for *na: ISICOM-NET1 * * *na: BODILSENDK * 195.215.139.158 * TOTAL 1 for *na: BODILSENDK * * *na: CH-DECKPOINT-960708 * 194.38.168.242 * TOTAL 1 for *na: CH-DECKPOINT-960708 * * *na: FR-COM-LESULIS * 194.167.80.13 * TOTAL 1 for *na: FR-COM-LESULIS * * *na: IMI-C-NET * 193.70.60.3 * TOTAL 1 for *na: IMI-C-NET * * *na: MAGIA-C-NET * 193.70.50.231 * TOTAL 1 for *na: MAGIA-C-NET * * *na: BASICPROPERTIES-C-NET * 193.70.41.6 * TOTAL 1 for *na: BASICPROPERTIES-C-NET * * *na: TAU-C-NET * 193.70.31.2 * 193.70.31.45 * 193.70.31.101 * TOTAL 3 for *na: TAU-C-NET * * *na: ITALWAY-C-NET * 193.70.27.6 * TOTAL 1 for *na: ITALWAY-C-NET * * *na: LOGIKOS-C-NET * 193.70.26.72 * TOTAL 1 for *na: LOGIKOS-C-NET * * *na: COSMOS-C-NET * 193.70.6.3 * TOTAL 1 for *na: COSMOS-C-NET * * *na: NETPOINT-S-NET * 193.70.121.186 * TOTAL 1 for *na: NETPOINT-S-NET * * *na: ICM-C-NET * 193.70.96.18 * 193.70.96.81 * 193.70.96.130 * TOTAL 3 for *na: ICM-C-NET * * *na: SIS-NET * 193.70.16.1 * 193.70.16.19 * TOTAL 2 for *na: SIS-NET * * *na: CONMET-C-NET * 193.70.1.2 * 193.70.1.4 * TOTAL 2 for *na: CONMET-C-NET * * *na: FR-ACADEMIE-GRENOBLE * 195.221.234.122 * TOTAL 1 for *na: FR-ACADEMIE-GRENOBLE * * *na: FR-ACADEMIE-GRENOBLE * 193.54.149.10 * 193.54.149.18 * TOTAL 2 for *na: FR-ACADEMIE-GRENOBLE * * *na: BH-BATELCO-960415 * 193.188.107.84 * 193.188.111.63 * 193.188.113.113 * 193.188.113.205 * 193.188.113.243 TOTAL 5 for *na: BH-BATELCO-960415 * * *na: BG-BASNET-980211 * 195.96.230.220 * TOTAL 1 for *na: BG-BASNET-980211 * * *na: IL-EURONET-RG-981126 * 212.68.133.84 * 212.68.134.69 * 212.68.153.213 * 212.68.156.71 * 212.68.158.49 * TOTAL 5 for *na: IL-EURONET-RG-981126 * * *na: AP-HOP-PARIS * 164.2.255.241 * TOTAL 1 for *na: AP-HOP-PARIS * * *na: FR-IWAY-981127 * 212.208.41.134 * 212.208.41.135 * 212.208.41.136 * 212.208.54.250 * TOTAL 4 for *na: FR-IWAY-981127 * * *na: FR-IEMN-NET * 193.51.54.2 * 193.51.54.59 * 193.51.54.65 * TOTAL 3 for *na: FR-IEMN-NET * * *na: FR-IWAY-980206 * 212.208.41.134 * 212.208.41.135 * 212.208.41.136 * 212.208.54.250 * TOTAL 4 for *na: FR-IWAY-980206 * * *na: BG-ITD-981130 * 212.116.133.130 * TOTAL 1 for *na: BG-ITD-981130 * * *na: RU-MACOMNET-970312 * 195.128.73.200 * 195.128.81.13 * TOTAL 2 for *na: RU-MACOMNET-970312 * * *na: RU-ROSTELECOM-970605 * 195.161.8.6 * 195.161.8.70 * 195.161.8.178 * TOTAL 3 for *na: RU-ROSTELECOM-970605 * * *na: DE-CSL-GMBH-960222 * 194.245.33.226 * 194.245.40.2 * 194.245.40.40 * TOTAL 3 for *na: DE-CSL-GMBH-960222 * * *na: HOLVRIEKADK * 195.215.141.2 * TOTAL 1 for *na: HOLVRIEKADK * * *na: BERLINGSKE-DK * 195.24.2.194 * 195.24.2.197 * 195.24.2.198 * 195.24.2.200 * 195.24.2.202 * 195.24.2.203 * 195.24.2.209 * 195.24.2.212 * TOTAL 8 for *na: BERLINGSKE-DK * * *na: VOLADK * 195.215.140.179 * TOTAL 1 for *na: VOLADK * * *na: AE-EMIRNET-971125 * 195.229.228.19 * 195.229.230.184 * 195.229.231.16 * TOTAL 3 for *na: AE-EMIRNET-971125 * * *na: UUNET-DK * 195.24.26.76 * 195.24.26.77 * TOTAL 2 for *na: UUNET-DK * * *na: RUNTIMEDK * 195.215.142.34 * TOTAL 1 for *na: RUNTIMEDK * * *na: GDCDK * 195.215.142.194 * TOTAL 1 for *na: GDCDK * * *na: TDI * 195.215.15.254 * TOTAL 1 for *na: TDI * * *na: TDI * 195.215.15.250 * TOTAL 1 for *na: TDI * * *na: TDI * 195.215.15.18 * TOTAL 1 for *na: TDI * * *na: KIJAKADK * 195.215.143.65 * TOTAL 1 for *na: KIJAKADK * * *na: DKNET-44 * 193.88.44.10 * 193.88.44.21 * 193.88.44.22 * 193.88.44.23 * 193.88.44.29 * 193.88.44.35 * 193.88.44.36 * 193.88.44.42 * 193.88.44.43 * 193.88.44.45 * 193.88.44.47 * 193.88.44.48 * 193.88.44.60 * 193.88.44.152 * 193.88.44.155 * 193.88.44.194 * TOTAL 16 for *na: DKNET-44 * * *na: SUNET * 193.88.184.18 * 193.88.184.64 * 193.88.184.71 * 193.88.184.243 * TOTAL 4 for *na: SUNET * * *na: BOSCHTELECOM * 193.88.175.66 * TOTAL 1 for *na: BOSCHTELECOM * * *na: RU-DEMOS-970415 * 195.133.0.8 * 195.133.8.85 * 195.133.61.61 * TOTAL 3 for *na: RU-DEMOS-970415 * * *na: RU-DEMOS-940901 * 194.87.5.3 * 194.87.5.54 * 194.87.5.55 * 194.87.11.112 * 194.87.158.2 * 194.87.200.22 * 194.87.200.48 * 194.87.200.50 * TOTAL 8 for *na: RU-DEMOS-940901 * * *na: COLORPRINT-DKDK * 195.215.143.194 * TOTAL 1 for *na: COLORPRINT-DKDK * * *na: SOTOFTEDK * 195.215.144.22 * TOTAL 1 for *na: SOTOFTEDK * * *na: DK-HOSTMASTER * 195.215.15.2 * 195.215.15.4 * TOTAL 2 for *na: DK-HOSTMASTER * * *na: DK-TELEDANMARK-950420 * 193.88.44.10 * 193.88.44.21 * 193.88.44.22 * 193.88.44.23 * 193.88.44.29 * 193.88.44.35 * 193.88.44.36 * 193.88.44.42 * 193.88.44.43 * 193.88.44.45 * 193.88.44.47 * 193.88.44.48 * 193.88.44.60 * 193.88.44.152 * 193.88.44.155 * 193.88.44.194 * 193.88.65.46 * 193.88.65.66 * 193.88.65.70 * ... * TOTAL 149 for *na: DK-TELEDANMARK-950420 * * *na: DK-TELEDANMARK-950920 * 194.182.129.11 * 194.182.129.12 * 194.182.129.37 * 194.182.129.50 * 194.182.129.53 * 194.182.129.67 * 194.182.129.76 * 194.182.144.66 * 194.182.150.154 * 194.182.150.171 * TOTAL 10 for *na: DK-TELEDANMARK-950920 * * *na: DK-TELEDANMARK-950920 * 194.182.233.147 * TOTAL 1 for *na: DK-TELEDANMARK-950920 * * *na: DK-TELEDANMARK-950829 * 194.192.16.2 * 194.192.17.226 * 194.192.17.234 * 194.192.17.245 * 194.192.20.82 * 194.192.20.86 * 194.192.22.2 * 194.192.22.9 * 194.192.22.11 * 194.192.23.1 * 194.192.64.130 * 194.192.64.162 * 194.192.70.10 * 194.192.80.73 * 194.192.80.92 * 194.192.87.4 * 194.192.94.2 * 194.192.96.2 * 194.192.98.129 * ... * TOTAL 45 for *na: DK-TELEDANMARK-950829 * * *na: DK-TELEDANMARK-960502 * 194.239.77.137 * 194.239.77.138 * 194.239.77.218 * 194.239.144.201 * 194.239.144.205 * 194.239.144.212 * 194.239.144.217 * 194.239.144.221 * 194.239.144.234 * 194.239.144.236 * 194.239.144.239 * 194.239.144.241 * 194.239.162.140 * 194.239.162.144 * 194.239.162.148 * 194.239.162.150 * 194.239.162.151 * 194.239.162.156 * 194.239.162.170 * ... * TOTAL 26 for *na: DK-TELEDANMARK-960502 * * *na: DK-TELEDANMARK-961204 * 195.41.117.130 * 195.41.117.133 * 195.41.138.66 * 195.41.138.71 * 195.41.138.72 * 195.41.142.138 * 195.41.217.2 * 195.41.217.8 * TOTAL 8 for *na: DK-TELEDANMARK-961204 * * *na: DK-TELEDANMARK-971007 * 195.215.2.6 * 195.215.3.131 * 195.215.15.2 * 195.215.15.4 * 195.215.15.18 * 195.215.15.250 * 195.215.15.254 * 195.215.29.187 * 195.215.34.82 * 195.215.34.105 * 195.215.34.194 * 195.215.36.2 * 195.215.36.3 * 195.215.36.4 * 195.215.36.5 * 195.215.36.18 * 195.215.36.19 * 195.215.36.20 * 195.215.36.36 * ... * TOTAL 124 for *na: DK-TELEDANMARK-971007 * * *na: DK-TELEDANMARK-980107 * 195.249.16.2 * 195.249.16.194 * 195.249.32.18 * 195.249.33.7 * 195.249.33.8 * 195.249.33.9 * 195.249.33.10 * 195.249.33.11 * 195.249.33.12 * 195.249.33.13 * 195.249.33.16 * 195.249.33.21 * 195.249.33.22 * 195.249.33.25 * 195.249.33.27 * 195.249.33.28 * 195.249.33.30 * 195.249.33.34 * 195.249.33.35 * ... * TOTAL 3773 for *na: DK-TELEDANMARK-980107 * * *na: UMUNET * 130.239.8.8 * 130.239.8.10 * 130.239.8.204 * 130.239.8.214 * 130.239.16.3 * 130.239.18.140 * 130.239.18.145 * 130.239.22.8 * 130.239.26.105 * 130.239.26.167 * 130.239.28.4 * 130.239.28.5 * 130.239.38.55 * 130.239.40.19 * 130.239.43.182 * 130.239.96.21 * 130.239.117.80 * 130.239.122.157 * 130.239.122.219 * ... * TOTAL 28 for *na: UMUNET * * *na: RU-MACOMNET-980710 * 212.5.77.34 * TOTAL 1 for *na: RU-MACOMNET-980710 * * *na: PREFORM-DK * 195.24.31.139 * 195.24.31.151 * 195.24.31.160 * 195.24.31.170 * 195.24.31.209 * TOTAL 5 for *na: PREFORM-DK * * *na: PL-NASK-148-81 * 148.81.4.6 * 148.81.4.210 * 148.81.15.66 * 148.81.16.51 * 148.81.17.34 * 148.81.18.28 * 148.81.33.11 * 148.81.34.120 * 148.81.52.11 * 148.81.64.68 * 148.81.68.98 * 148.81.77.63 * 148.81.80.1 * 148.81.83.51 * 148.81.93.18 * 148.81.126.6 * 148.81.127.3 * 148.81.145.16 * 148.81.145.165 * ... * TOTAL 26 for *na: PL-NASK-148-81 * * *na: UK-PIPEX-19951207 * 194.216.51.2 * TOTAL 1 for *na: UK-PIPEX-19951207 * * *na: UK-PIPEX-950921 * 194.200.207.10 * 194.200.207.139 * 194.200.207.151 * 194.200.207.155 * 194.200.207.174 * 194.200.207.200 * 194.200.207.232 * 194.202.125.96 * 194.202.125.152 * 194.202.125.195 * TOTAL 10 for *na: UK-PIPEX-950921 * * *na: UK-PIPEX-193-128-133 * 193.128.12.2 * 193.131.13.151 * 193.131.65.10 * 193.133.22.53 * 193.133.96.130 * 193.133.111.45 * 193.133.111.50 * TOTAL 7 for *na: UK-PIPEX-193-128-133 * * *na: UK-PIPEX-194-128-131 * 194.128.98.225 * 194.130.42.1 * 194.130.159.16 * 194.130.159.173 * 194.130.159.185 * 194.130.159.230 * 194.130.240.52 * 194.130.240.57 * 194.130.240.117 * 194.130.240.118 * 194.130.240.123 * 194.130.240.126 * 194.130.240.149 * TOTAL 13 for *na: UK-PIPEX-194-128-131 * * *na: PIPEX-NET * 158.43.4.26 * 158.43.4.42 * 158.43.17.138 * 158.43.17.182 * 158.43.34.162 * 158.43.52.2 * 158.43.55.38 * 158.43.56.6 * 158.43.56.102 * 158.43.56.106 * 158.43.69.78 * 158.43.74.246 * 158.43.109.2 * 158.43.128.8 * 158.43.128.11 * 158.43.128.25 * 158.43.128.26 * 158.43.128.38 * 158.43.128.41 * ... * TOTAL 78 for *na: PIPEX-NET * * *na: ASEDK * 195.215.144.91 * TOTAL 1 for *na: ASEDK * * *na: MONDIALDK * 195.215.144.162 * 195.215.144.174 * TOTAL 2 for *na: MONDIALDK * * *na: SPAENCOMDK * 195.215.144.226 * TOTAL 1 for *na: SPAENCOMDK * * *na: BA-BIHNET-970730 * 195.222.38.147 * 195.222.38.238 * 195.222.46.61 * TOTAL 3 for *na: BA-BIHNET-970730 * * *na: DKNET-PIP-AALB * 193.89.17.129 * 193.89.17.133 * 193.89.17.134 * 193.89.17.136 * 193.89.17.140 * 193.89.17.143 * 193.89.17.149 * 193.89.17.153 * 193.89.17.154 * 193.89.17.155 * 193.89.17.157 * 193.89.17.158 * TOTAL 12 for *na: DKNET-PIP-AALB * * *na: DKNET-PIP-AARH * 193.89.17.8 * 193.89.17.9 * 193.89.17.19 * 193.89.17.29 * 193.89.17.32 * 193.89.17.37 * 193.89.17.38 * 193.89.17.40 * 193.89.17.45 * 193.89.17.50 * 193.89.17.51 * 193.89.17.53 * 193.89.17.54 * 193.89.17.55 * 193.89.17.56 * 193.89.17.59 * 193.89.17.61 * TOTAL 17 for *na: DKNET-PIP-AARH * * *na: NATIONALBANKENDK * 195.215.143.254 * TOTAL 1 for *na: NATIONALBANKENDK * * *na: ITID * 194.192.20.82 * 194.192.20.86 * TOTAL 2 for *na: ITID * * *na: AVSUNIRAS * 193.89.40.13 * 193.89.40.40 * TOTAL 2 for *na: AVSUNIRAS * * *na: DANTRANSPORT * 193.162.16.5 * 193.162.16.34 * 193.162.16.35 * 193.162.17.225 * TOTAL 4 for *na: DANTRANSPORT * * *na: INGNET * 193.88.80.10 * 193.88.80.129 * 193.88.80.253 * 193.88.82.2 * 193.88.82.26 * TOTAL 5 for *na: INGNET * * *na: RSA-DK * 195.24.8.234 * TOTAL 1 for *na: RSA-DK * * *na: DE-NACAMAR-970106 * 195.63.225.1 * TOTAL 1 for *na: DE-NACAMAR-970106 * * *na: DE-NACAMAR-970805 * 195.185.146.52 * TOTAL 1 for *na: DE-NACAMAR-970805 * * *na: DE-NACAMAR-970502 * 62.144.99.3 * TOTAL 1 for *na: DE-NACAMAR-970502 * * *na: VIRTUALWWW-3 * 194.202.125.96 * 194.202.125.152 * 194.202.125.195 * TOTAL 3 for *na: VIRTUALWWW-3 * * *na: VIRTUALWWW * 194.200.207.10 * 194.200.207.139 * 194.200.207.151 * 194.200.207.155 * 194.200.207.174 * 194.200.207.200 * 194.200.207.232 * TOTAL 7 for *na: VIRTUALWWW * * *na: GR-HOL-970303 * 195.97.24.2 * TOTAL 1 for *na: GR-HOL-970303 * * *na: SOFTCOM-DK * 195.24.31.66 * 195.24.31.67 * TOTAL 2 for *na: SOFTCOM-DK * * *na: BKMED-DK * 195.24.15.252 * TOTAL 1 for *na: BKMED-DK * * *na: ES-MEDUSA-960710 * 194.140.53.2 * TOTAL 1 for *na: ES-MEDUSA-960710 * * *na: RU-DSI-970728 * 195.206.50.1 * TOTAL 1 for *na: RU-DSI-970728 * * *na: BILWINCOOM * 195.215.145.146 * TOTAL 1 for *na: BILWINCOOM * * *na: SILICONDK * 195.215.145.193 * 195.215.145.194 * 195.215.145.219 * TOTAL 3 for *na: SILICONDK * * *na: TRIPTRAPDK * 195.215.146.129 * 195.215.146.130 * TOTAL 2 for *na: TRIPTRAPDK * * *na: NV-POPS * 62.0.128.40 * 62.0.128.86 * 62.0.128.107 * 62.0.128.138 * 62.0.145.135 * 62.0.145.139 * 62.0.145.232 * 62.0.146.8 * 62.0.146.10 * 62.0.146.89 * 62.0.149.78 * 62.0.149.100 * 62.0.152.1 * 62.0.153.19 * 62.0.153.39 * 62.0.153.194 * 62.0.154.12 * 62.0.154.211 * 62.0.154.235 * ... * TOTAL 30 for *na: NV-POPS * * *na: POLSL-NET * 157.158.1.3 * 157.158.1.4 * 157.158.16.167 * 157.158.67.1 * 157.158.67.102 * 157.158.208.62 * TOTAL 6 for *na: POLSL-NET * * *na: DZ-ARN-970407 * 193.194.95.105 * 193.194.95.185 * TOTAL 2 for *na: DZ-ARN-970407 * * *na: DEN-SALVATIONARMY-ORG * 195.215.146.211 * TOTAL 1 for *na: DEN-SALVATIONARMY-ORG * * *na: CZ-CZECHNET-960130 * 194.213.235.175 * TOTAL 1 for *na: CZ-CZECHNET-960130 * *na: SE-PHARMA * 193.180.21.2 * 193.180.21.10 * TOTAL 2 for *na: SE-PHARMA * * *na: SE-SIGNUM * 193.180.23.4 * 193.180.23.167 * 193.180.23.230 * 193.180.23.236 * TOTAL 4 for *na: SE-SIGNUM * * *na: SE-EXPRESSEN * 193.180.34.38 * 193.180.36.77 * 193.180.36.155 * 193.180.36.170 * 193.180.36.177 * 193.180.45.72 * TOTAL 6 for *na: SE-EXPRESSEN * * *na: SE-GOTTHARD * 193.180.58.7 * 193.180.58.22 * 193.180.58.254 * TOTAL 3 for *na: SE-GOTTHARD * * *na: J-SAINSBURY * 193.133.96.130 * TOTAL 1 for *na: J-SAINSBURY * * *na: UK-MISTRAL-971114 * 195.184.226.162 * TOTAL 1 for *na: UK-MISTRAL-971114 * * *na: TELIANET * 62.20.128.15 * 62.20.132.55 * 62.20.132.84 * 62.20.132.85 * 62.20.132.90 * 62.20.132.127 * 62.20.132.134 * 62.20.132.153 * 62.20.132.175 * 62.20.132.180 * 62.20.132.241 * 62.20.132.243 * 62.20.133.61 * 62.20.133.86 * 62.20.133.120 * 62.20.133.125 * 62.20.133.148 * 62.20.133.180 * 62.20.133.198 * ... * TOTAL 248 for *na: TELIANET * * *na: TELIANET * 195.67.156.39 * 195.67.156.52 * 195.67.156.132 * 195.67.156.241 * 195.67.157.23 * 195.67.157.101 * 195.67.157.164 * 195.67.157.241 * 195.67.157.243 * TOTAL 9 for *na: TELIANET * * *na: TELIANET * 195.67.188.67 * 195.67.188.150 * 195.67.188.183 * 195.67.188.209 * 195.67.188.235 * 195.67.188.241 * 195.67.188.243 * 195.67.189.11 * 195.67.189.34 * 195.67.189.74 * 195.67.189.85 * 195.67.189.144 * 195.67.189.241 * 195.67.190.123 * 195.67.190.127 * 195.67.190.151 * 195.67.190.209 * 195.67.190.241 * 195.67.190.242 * ... * TOTAL 100 for *na: TELIANET * * *na: DE-CALLISTO-970110 * 151.189.12.2 * 151.189.12.7 * 151.189.12.208 * 151.189.13.25 * 151.189.16.1 * 151.189.16.174 * 151.189.24.2 * 151.189.38.12 * 151.189.95.66 * TOTAL 9 for *na: DE-CALLISTO-970110 * * *na: FFEI-NET * 194.130.42.1 * TOTAL 1 for *na: FFEI-NET * * *na: FR-EASYNET-970224 * 195.114.64.109 * 195.114.64.129 * 195.114.64.193 * 195.114.64.198 * 195.114.64.218 * 195.114.64.230 * 195.114.64.231 * 195.114.64.232 * 195.114.64.238 * 195.114.64.240 * 195.114.68.208 * 195.114.88.158 * TOTAL 12 for *na: FR-EASYNET-970224 * * *na: SE-GBGGYM * 193.180.65.151 * 193.180.82.165 * 193.180.84.106 * TOTAL 3 for *na: SE-GBGGYM * * *na: SE-HBENERGY * 193.180.104.9 * 193.180.104.10 * 193.180.104.12 * 193.180.104.23 * 193.180.104.252 * 193.180.104.254 * TOTAL 6 for *na: SE-HBENERGY * * *na: SE-HBENERGY * 193.180.106.148 * 193.180.108.172 * 193.180.108.188 * TOTAL 3 for *na: SE-HBENERGY * * *na: SE-HBENERGY * 193.180.113.89 * 193.180.113.91 * TOTAL 2 for *na: SE-HBENERGY * * *na: SE-AGA * 193.180.184.1 * TOTAL 1 for *na: SE-AGA * * *na: SE-STRODE * 193.180.197.10 * TOTAL 1 for *na: SE-STRODE * * *na: SE-KM * 193.180.207.1 * TOTAL 1 for *na: SE-KM * * *na: SE-GOTKOM * 193.180.228.194 * TOTAL 1 for *na: SE-GOTKOM * * *na: SE-TRANAS-2 * 193.180.229.7 * 193.180.229.8 * TOTAL 2 for *na: SE-TRANAS-2 * * *na: SE-BOSTADEN-NET * 193.180.246.34 * 193.180.246.149 * TOTAL 2 for *na: SE-BOSTADEN-NET * * *na: SE-LMSOFA * 193.180.251.38 * 193.180.251.39 * TOTAL 2 for *na: SE-LMSOFA * * *na: SE-VV * 193.181.57.1 * TOTAL 1 for *na: SE-VV * * *na: SE-D-DATA * 193.181.154.17 * 193.181.154.65 * TOTAL 2 for *na: SE-D-DATA * * *na: NL-WAPI-19990111 * 195.121.1.34 * 195.121.1.66 * 195.121.6.37 * 195.121.6.51 * 195.121.6.57 * 195.121.6.59 * 195.121.6.61 * 195.121.6.98 * 195.121.6.99 * 195.121.6.100 * 195.121.6.143 * 195.121.6.144 * 195.121.6.163 * 195.121.6.196 * 195.121.8.2 * 195.121.9.89 * 195.121.9.115 * 195.121.18.16 * 195.121.18.109 * ... * TOTAL 91 for *na: NL-WAPI-19990111 * * *na: SE-BLTID * 193.181.241.3 * 193.181.241.170 * TOTAL 2 for *na: SE-BLTID * * *na: MATAV * 145.236.188.45 * 145.236.196.37 * 145.236.208.91 * 145.236.208.248 * 145.236.209.115 * 145.236.212.9 * 145.236.224.231 * 145.236.224.244 * 145.236.224.248 * 145.236.224.249 * 145.236.224.250 * 145.236.226.87 * 145.236.237.12 * 145.236.240.204 * 145.236.241.98 * TOTAL 15 for *na: MATAV * * *na: KG-ASIAINFO-971015 * 195.38.187.33 * TOTAL 1 for *na: KG-ASIAINFO-971015 * * *na: DE-OK-990112 * 212.72.65.4 * TOTAL 1 for *na: DE-OK-990112 * * *na: WROCPOLIP * 156.17.2.116 * 156.17.2.177 * 156.17.5.2 * 156.17.5.3 * 156.17.8.1 * 156.17.10.162 * 156.17.10.166 * 156.17.30.4 * 156.17.35.2 * 156.17.35.3 * 156.17.35.8 * 156.17.35.27 * 156.17.55.101 * 156.17.71.34 * 156.17.71.47 * 156.17.108.1 * 156.17.108.26 * 156.17.204.14 * 156.17.209.162 * ... * TOTAL 22 for *na: WROCPOLIP * * *na: PT-RCCN-193-136-137 * 193.136.0.1 * 193.136.185.191 * 193.137.7.1 * 193.137.56.17 * 193.137.56.21 * 193.137.68.17 * 193.137.127.65 * 193.137.127.129 * 193.137.239.226 * TOTAL 9 for *na: PT-RCCN-193-136-137 * * *na: SE-COMPUTERLAND-NET1 * 193.14.2.5 * TOTAL 1 for *na: SE-COMPUTERLAND-NET1 * * *na: SE-OW * 193.12.198.82 * 193.12.198.98 * TOTAL 2 for *na: SE-OW * * *na: SE-TERACOM-NET1 * 193.12.205.1 * TOTAL 1 for *na: SE-TERACOM-NET1 * * *na: SE-NETTIME-NET1 * 193.12.209.1 * 193.12.209.37 * TOTAL 2 for *na: SE-NETTIME-NET1 * * *na: SE-EVERY-NET1 * 193.12.243.4 * 193.12.243.40 * 193.12.243.59 * 193.12.243.62 * 193.12.243.75 * 193.12.243.104 * 193.12.243.150 * TOTAL 7 for *na: SE-EVERY-NET1 * * *na: SE-DALSLAND-NET1 * 193.12.255.26 * 193.12.255.253 * TOTAL 2 for *na: SE-DALSLAND-NET1 * * *na: SE-RADIOD-NET1 * 193.13.14.38 * TOTAL 1 for *na: SE-RADIOD-NET1 * * *na: IT-INTERBUSINESS-950606 * 151.99.133.1 * 151.99.133.129 * 151.99.197.10 * 151.99.197.15 * 151.99.238.35 * 151.99.238.44 * 151.99.247.2 * 151.99.247.7 * 151.99.250.2 * 151.99.250.6 * 151.99.250.31 * 151.99.250.32 * TOTAL 12 for *na: IT-INTERBUSINESS-950606 * * *na: SE-LKOMMUN-NET * 193.13.15.2 * 193.13.15.3 * 193.13.15.7 * 193.13.15.31 * 193.13.15.71 * TOTAL 5 for *na: SE-LKOMMUN-NET * * *na: SE-POLHEM-NET1 * 193.13.20.253 * TOTAL 1 for *na: SE-POLHEM-NET1 * * *na: SE-HALDEX * 193.13.23.220 * TOTAL 1 for *na: SE-HALDEX * * *na: SE-ATVDA-NET1 * 193.13.28.1 * TOTAL 1 for *na: SE-ATVDA-NET1 * * *na: SE-MATTEUS-NET1 * 193.13.53.30 * 193.13.53.42 * TOTAL 2 for *na: SE-MATTEUS-NET1 * * *na: SE-BT-NET * 193.13.114.18 * 193.13.114.31 * TOTAL 2 for *na: SE-BT-NET * * *na: SE-FLT-NET * 193.13.115.80 * TOTAL 1 for *na: SE-FLT-NET * * *na: SE-KRISTIANSTAD-NET1 * 193.13.129.16 * 193.13.129.41 * 193.13.129.53 * 193.13.129.66 * 193.13.129.116 * 193.13.129.120 * 193.13.129.143 * 193.13.129.183 * 193.13.129.203 * 193.13.129.250 * TOTAL 10 for *na: SE-KRISTIANSTAD-NET1 * * *na: SE-TIDTALJE-NET * 193.13.135.1 * TOTAL 1 for *na: SE-TIDTALJE-NET * * *na: SE-FALUKURIR-NET1 * 193.13.136.253 * TOTAL 1 for *na: SE-FALUKURIR-NET1 * * *na: SE-LAGERCRANTZ-EL-NET1 * 193.13.140.4 * 193.13.140.14 * 193.13.141.3 * 193.13.141.10 * 193.13.141.13 * TOTAL 5 for *na: SE-LAGERCRANTZ-EL-NET1 * * *na: SE-VARBERGENERGI-NET1 * 193.13.151.2 * 193.13.151.45 * 193.13.151.130 * 193.13.151.144 * 193.13.151.184 * TOTAL 5 for *na: SE-VARBERGENERGI-NET1 * * *na: SE-AGEMA-NET1 * 193.13.175.130 * TOTAL 1 for *na: SE-AGEMA-NET1 * * *na: SE-DATARUTIN-NET3 * 193.13.176.1 * TOTAL 1 for *na: SE-DATARUTIN-NET3 * * *na: SE-AXIS-NET1 * 193.13.178.2 * 193.13.178.7 * 193.13.178.10 * TOTAL 3 for *na: SE-AXIS-NET1 * * *na: SE-BIZIT-NET1 * 193.13.179.10 * 193.13.179.106 * 193.13.179.114 * 193.13.179.155 * 193.13.179.161 * TOTAL 5 for *na: SE-BIZIT-NET1 * * *na: SE-FREDRIKA-NET1 * 193.13.222.15 * 193.13.222.53 * 193.13.222.58 * TOTAL 3 for *na: SE-FREDRIKA-NET1 * * *na: SE-ITT1-NET1 * 193.13.224.252 * TOTAL 1 for *na: SE-ITT1-NET1 * * *na: SE-DATAOFFICE-NET1 * 193.13.229.11 * TOTAL 1 for *na: SE-DATAOFFICE-NET1 * * *na: SE-BULLERDATA-NET1 * 193.13.231.1 * 193.13.231.2 * 193.13.231.21 * 193.13.231.152 * 193.13.231.182 * 193.13.231.196 * 193.13.231.207 * TOTAL 7 for *na: SE-BULLERDATA-NET1 * * *na: SE-IDG-NET1 * 193.13.235.50 * 193.13.235.51 * 193.13.235.52 * 193.13.235.91 * 193.13.235.98 * 193.13.235.99 * 193.13.235.129 * 193.13.235.140 * 193.13.235.194 * 193.13.235.196 * TOTAL 10 for *na: SE-IDG-NET1 * * *na: SE-MEMORY-NET * 193.13.247.17 * 193.13.247.75 * 193.13.247.114 * TOTAL 3 for *na: SE-MEMORY-NET * * *na: SE-MEDO-NET1 * 193.13.252.60 * TOTAL 1 for *na: SE-MEDO-NET1 * * *na: SE-MM-NET * 193.13.144.1 * 193.13.144.2 * 193.13.144.16 * 193.13.144.46 * 193.13.144.61 * TOTAL 5 for *na: SE-MM-NET * * *na: SE-CARNEGIE-NET1 * 193.13.182.10 * 193.13.182.11 * 193.13.182.20 * TOTAL 3 for *na: SE-CARNEGIE-NET1 * * *na: SE-TYCHOBRAHE-NET1 * 193.14.3.3 * TOTAL 1 for *na: SE-TYCHOBRAHE-NET1 * * *na: SE-ARVIKA-NET1 * 193.14.10.129 * TOTAL 1 for *na: SE-ARVIKA-NET1 * * *na: SE-GRAFCE-NET1 * 193.14.12.88 * TOTAL 1 for *na: SE-GRAFCE-NET1 * * *na: SE-IM-NET1 * 193.14.22.222 * TOTAL 1 for *na: SE-IM-NET1 * * *na: SE-HYPER-NET1 * 193.14.26.1 * 193.14.26.209 * 193.14.26.229 * TOTAL 3 for *na: SE-HYPER-NET1 * * *na: SE-PAGINA-NET1 * 193.14.45.16 * TOTAL 1 for *na: SE-PAGINA-NET1 * * *na: SE-ALE-NET1 * 193.14.51.70 * TOTAL 1 for *na: SE-ALE-NET1 * * *na: SE-EKSJO-NET1 * 193.14.53.10 * 193.14.53.21 * TOTAL 2 for *na: SE-EKSJO-NET1 * * *na: SE-SP-NET1 * 193.14.55.39 * 193.14.55.64 * 193.14.55.123 * 193.14.55.223 * 193.14.55.230 * 193.14.55.252 * TOTAL 6 for *na: SE-SP-NET1 * * *na: SE-FOLKUNIVERSITETET-NET1 * 193.14.60.3 * 193.14.60.253 * TOTAL 2 for *na: SE-FOLKUNIVERSITETET-NET1 * * *na: SE-STHLMMASSAN-NET1 * 193.14.63.130 * TOTAL 1 for *na: SE-STHLMMASSAN-NET1 * * *na: SE-RALTON-NET1 * 193.14.66.10 * 193.14.66.230 * TOTAL 2 for *na: SE-RALTON-NET1 * * *na: SE-MAGAZINE-NET1 * 193.14.67.1 * 193.14.67.83 * TOTAL 2 for *na: SE-MAGAZINE-NET1 * * *na: SE-LIBER * 193.14.71.219 * 193.14.71.221 * 193.14.71.253 * TOTAL 3 for *na: SE-LIBER * * *na: SE-TYCHOBRAHE-NET2 * 193.14.75.101 * TOTAL 1 for *na: SE-TYCHOBRAHE-NET2 * * *na: SE-USIS-NET1 * 193.14.78.1 * TOTAL 1 for *na: SE-USIS-NET1 * * *na: SE-INFOM-NET1 * 193.14.81.1 * 193.14.81.11 * TOTAL 2 for *na: SE-INFOM-NET1 * * *na: SE-QD1-NET1 * 193.14.86.220 * TOTAL 1 for *na: SE-QD1-NET1 * * *na: SE-MALMOSTAD-NET1 * 193.14.94.100 * 193.14.94.109 * 193.14.94.188 * 193.14.94.215 * 193.14.94.253 * TOTAL 5 for *na: SE-MALMOSTAD-NET1 * * *na: SE-FILBORNASKOLAN-NET1 * 193.14.103.101 * 193.14.103.252 * TOTAL 2 for *na: SE-FILBORNASKOLAN-NET1 * * *na: SE-IKONMEDIA-NET1 * 193.14.104.1 * 193.14.104.2 * 193.14.104.70 * TOTAL 3 for *na: SE-IKONMEDIA-NET1 * * *na: SSC-NET1 * 193.14.109.53 * TOTAL 1 for *na: SSC-NET1 * * *na: SE-PROGRAMB-NET1 * 193.14.113.1 * 193.14.113.9 * TOTAL 2 for *na: SE-PROGRAMB-NET1 * * *na: SE-NECTAR-NET1 * 193.14.116.1 * TOTAL 1 for *na: SE-NECTAR-NET1 * * *na: SE-METRO-NET1 * 193.14.118.100 * 193.14.118.104 * TOTAL 2 for *na: SE-METRO-NET1 * * *na: SE-SOFIASK-NET1 * 193.14.120.149 * TOTAL 1 for *na: SE-SOFIASK-NET1 * * *na: SE-ADELFORSSK-NET1 * 193.14.125.2 * TOTAL 1 for *na: SE-ADELFORSSK-NET1 * * *na: SE-BORGHOLM-NET1 * 193.14.135.89 * TOTAL 1 for *na: SE-BORGHOLM-NET1 * * *na: SE-ACOM-NET1 * 193.14.144.200 * TOTAL 1 for *na: SE-ACOM-NET1 * * *na: SE-BAHNHOF-NET1 * 193.14.145.193 * 193.14.145.227 * 193.14.145.229 * TOTAL 3 for *na: SE-BAHNHOF-NET1 * * *na: SE-INGRAM-NET1 * 193.14.147.220 * TOTAL 1 for *na: SE-INGRAM-NET1 * * *na: SE-VARBERGENERGI-NET2 * 193.14.149.2 * 193.14.149.116 * TOTAL 2 for *na: SE-VARBERGENERGI-NET2 * * *na: SE-NIKOLAISKOLAN-NET1 * 193.14.153.161 * TOTAL 1 for *na: SE-NIKOLAISKOLAN-NET1 * * *na: SE-SPPI-NET1 * 193.14.160.50 * TOTAL 1 for *na: SE-SPPI-NET1 * * *na: SE-SYSTEMBOLAGETI-NET1 * 193.14.160.67 * 193.14.160.74 * TOTAL 2 for *na: SE-SYSTEMBOLAGETI-NET1 * * *na: SE-LIMT-NET1 * 193.14.160.130 * TOTAL 1 for *na: SE-LIMT-NET1 * * *na: SE-ELLOS-NET1 * 193.14.160.202 * 193.14.160.203 * TOTAL 2 for *na: SE-ELLOS-NET1 * * *na: SE-YSTAD-NET1 * 193.14.161.97 * TOTAL 1 for *na: SE-YSTAD-NET1 * * *na: LRF-NET2 * 193.14.162.66 * TOTAL 1 for *na: LRF-NET2 * * *na: SE-SIDA-NET1 * 193.14.162.82 * 193.14.162.83 * TOTAL 2 for *na: SE-SIDA-NET1 * * *na: SE-SORMAN-NET1 * 193.14.162.98 * TOTAL 1 for *na: SE-SORMAN-NET1 * * *na: SE-TRANSCOM-NET1 * 193.14.163.134 * 193.14.163.140 * TOTAL 2 for *na: SE-TRANSCOM-NET1 * * *na: SPARBANKEN-FINN-NET1 * 193.14.163.216 * TOTAL 1 for *na: SPARBANKEN-FINN-NET1 * * *na: SE-HADAB-NET1 * 193.14.165.6 * 193.14.165.8 * TOTAL 2 for *na: SE-HADAB-NET1 * * *na: SE-DDNG-NET1 * 193.14.165.132 * TOTAL 1 for *na: SE-DDNG-NET1 * * *na: SE-UBI-NET1 * 193.14.168.2 * TOTAL 1 for *na: SE-UBI-NET1 * * *na: SE-INFOWAY-NET1 * 193.14.170.78 * 193.14.170.79 * TOTAL 2 for *na: SE-INFOWAY-NET1 * * *na: EU-EUNET-960405 * 195.0.49.130 * TOTAL 1 for *na: EU-EUNET-960405 * * *na: SE-MICROTRONICA-NET * 193.14.172.130 * TOTAL 1 for *na: SE-MICROTRONICA-NET * * *na: SE-EUROFLORIST-NET1 * 193.14.173.130 * TOTAL 1 for *na: SE-EUROFLORIST-NET1 * * *na: SE-BUSINESS-NET1 * 193.14.173.218 * 193.14.173.219 * 193.14.173.222 * TOTAL 3 for *na: SE-BUSINESS-NET1 * * *na: EU-EUNET-960726 * 193.95.194.113 * 193.95.206.133 * TOTAL 2 for *na: EU-EUNET-960726 * * *na: SE-SCANDI-NET2 * 193.14.174.9 * TOTAL 1 for *na: SE-SCANDI-NET2 * * *na: SE-HOGANAS-NET1 * 193.14.174.242 * TOTAL 1 for *na: SE-HOGANAS-NET1 * * *na: SE-AVISA-NET1 * 193.14.175.12 * TOTAL 1 for *na: SE-AVISA-NET1 * * *na: SE-ATLASCOPCO-NET1 * 193.14.199.253 * TOTAL 1 for *na: SE-ATLASCOPCO-NET1 * * *na: SE-EUROPEDU-NET1 * 193.14.200.1 * 193.14.200.2 * 193.14.200.3 * 193.14.200.7 * 193.14.200.8 * 193.14.200.12 * 193.14.200.13 * 193.14.200.17 * 193.14.200.60 * 193.14.200.99 * TOTAL 10 for *na: SE-EUROPEDU-NET1 * * *na: SE-CROSSNET-NET1 * 193.14.201.5 * 193.14.201.10 * 193.14.201.12 * 193.14.201.14 * 193.14.201.21 * TOTAL 5 for *na: SE-CROSSNET-NET1 * * *na: SE-MEDANETWORK-NET1 * 193.14.204.1 * 193.14.204.62 * 193.14.204.140 * TOTAL 3 for *na: SE-MEDANETWORK-NET1 * * *na: SE-IBS-NET1 * 193.14.205.5 * 193.14.205.7 * 193.14.205.14 * TOTAL 3 for *na: SE-IBS-NET1 * * *na: SE-ECOLINE-NET1 * 193.14.227.62 * TOTAL 1 for *na: SE-ECOLINE-NET1 * * *na: SE-INSTFORSK-NET1 * 193.14.239.140 * TOTAL 1 for *na: SE-INSTFORSK-NET1 * * *na: SE-ASOGYMN-NET * 193.14.244.126 * TOTAL 1 for *na: SE-ASOGYMN-NET * * *na: SE-OFFICINEN * 193.13.29.235 * TOTAL 1 for *na: SE-OFFICINEN * * *na: SE-HALLPOST1-NET * 193.13.112.66 * TOTAL 1 for *na: SE-HALLPOST1-NET * * *na: SE-HALLPOST2-NET * 193.13.121.10 * TOTAL 1 for *na: SE-HALLPOST2-NET * * *na: SE-AFTON * 193.13.160.144 * 193.13.160.180 * 193.13.160.200 * 193.13.161.2 * TOTAL 4 for *na: SE-AFTON * * *na: SE-BONNIER-NET1 * 193.14.43.90 * TOTAL 1 for *na: SE-BONNIER-NET1 * * *na: SE-TV3-NET1 * 193.14.64.1 * 193.14.64.14 * 193.14.64.20 * 193.14.64.100 * TOTAL 4 for *na: SE-TV3-NET1 * * *na: SE-GBP-NET1 * 193.14.195.40 * 193.14.195.50 * TOTAL 2 for *na: SE-GBP-NET1 * * *na: SE-FIBD * 193.14.210.200 * TOTAL 1 for *na: SE-FIBD * * *na: SE-LUND * 193.14.211.2 * 193.14.211.3 * 193.14.212.9 * 193.14.212.71 * 193.14.212.109 * 193.14.212.111 * 193.14.212.135 * 193.14.212.165 * 193.14.212.212 * 193.14.213.101 * TOTAL 10 for *na: SE-LUND * * *na: SE-DATAPLUS-NET1 * 193.14.88.250 * TOTAL 1 for *na: SE-DATAPLUS-NET1 * * *na: SE-KOMVUXKUNGALV-NET2 * 193.13.217.14 * TOTAL 1 for *na: SE-KOMVUXKUNGALV-NET2 * * *na: SE-CEDERROTH1-NET1 * 193.14.100.10 * TOTAL 1 for *na: SE-CEDERROTH1-NET1 * * *na: CZ-NETFORCE-960110 * 194.213.206.48 * TOTAL 1 for *na: CZ-NETFORCE-960110 * * *na: CON-INKDK * 195.215.149.146 * TOTAL 1 for *na: CON-INKDK * * *na: UA-ALKAR-971007 * 195.248.166.36 * TOTAL 1 for *na: UA-ALKAR-971007 * * *na: RANDHS * 193.89.57.9 * 193.89.57.29 * 193.89.57.47 * 193.89.57.82 * 193.89.57.104 * 193.89.57.115 * 193.89.57.122 * TOTAL 7 for *na: RANDHS * * *na: INSERT * 193.95.194.113 * TOTAL 1 for *na: INSERT * * *na: SE-SONERA-960723 * 195.84.56.22 * 195.84.122.131 * 195.84.122.132 * 195.84.134.226 * TOTAL 4 for *na: SE-SONERA-960723 * * *na: HAHADK * 195.215.151.242 * TOTAL 1 for *na: HAHADK * * *na: OXFORD-UNIV * 163.1.2.1 * 163.1.2.9 * 163.1.7.48 * 163.1.16.100 * 163.1.21.102 * 163.1.29.191 * 163.1.67.206 * 163.1.80.29 * 163.1.136.80 * 163.1.137.3 * 163.1.138.66 * 163.1.138.183 * 163.1.144.109 * 163.1.146.5 * 163.1.162.79 * 163.1.164.157 * 163.1.219.1 * 163.1.219.77 * 163.1.244.140 * ... * TOTAL 21 for *na: OXFORD-UNIV * * *na: DE-EUNET-193-96-193-103 * 193.103.207.35 * 193.103.207.36 * TOTAL 2 for *na: DE-EUNET-193-96-193-103 * * *na: SE-MSC * 193.182.113.10 * TOTAL 1 for *na: SE-MSC * * *na: SE-ABRA * 193.182.122.10 * TOTAL 1 for *na: SE-ABRA * * *na: SE-ADBDOK * 193.182.146.102 * TOTAL 1 for *na: SE-ADBDOK * * *na: SE-STORTORP * 193.182.150.1 * TOTAL 1 for *na: SE-STORTORP * * *na: SE-TECATOR * 193.182.166.2 * TOTAL 1 for *na: SE-TECATOR * * *na: SE-HELDAG * 193.182.171.150 * 193.182.172.114 * TOTAL 2 for *na: SE-HELDAG * * *na: SE-SYDSVENSK2 * 193.182.191.113 * 193.182.191.114 * TOTAL 2 for *na: SE-SYDSVENSK2 * * *na: SE-REKTOR * 193.182.241.234 * TOTAL 1 for *na: SE-REKTOR * * *na: SE-IMS * 193.183.19.65 * 193.183.19.100 * TOTAL 2 for *na: SE-IMS * * *na: SE-PROGAMENIUS * 193.183.49.8 * TOTAL 1 for *na: SE-PROGAMENIUS * * *na: SE-TIPS * 193.183.60.1 * TOTAL 1 for *na: SE-TIPS * * *na: SE-LUXNET * 193.183.68.17 * TOTAL 1 for *na: SE-LUXNET * * *na: UA-LUCKYNET-980414 * 62.244.59.134 * TOTAL 1 for *na: UA-LUCKYNET-980414 * * *na: UK-ASPEN-960722 * 194.93.128.1 * 194.93.128.2 * 194.93.128.3 * 194.93.128.28 * 194.93.133.1 * 194.93.134.3 * 194.93.134.119 * 194.93.154.49 * TOTAL 8 for *na: UK-ASPEN-960722 * * *na: SE-JONKOM * 193.183.204.3 * 193.183.205.2 * 193.183.212.211 * 193.183.212.230 * 193.183.213.2 * 193.183.213.254 * 193.183.214.2 * 193.183.214.4 * 193.183.215.4 * 193.183.216.2 * 193.183.216.5 * 193.183.217.2 * 193.183.218.157 * TOTAL 13 for *na: SE-JONKOM * * *na: SE-TT * 193.183.175.252 * TOTAL 1 for *na: SE-TT * * *na: SE-STHBIB * 193.183.252.153 * TOTAL 1 for *na: SE-STHBIB * * *na: SE-HUDDINGE * 193.183.253.2 * TOTAL 1 for *na: SE-HUDDINGE * * *na: SE-NB * 193.234.191.242 * 193.234.191.244 * TOTAL 2 for *na: SE-NB * * *na: SE-CAPMEL * 193.234.247.10 * TOTAL 1 for *na: SE-CAPMEL * * *na: UNISOURCE-BB * 194.151.224.7 * 194.151.231.130 * 194.151.231.194 * 194.151.234.18 * TOTAL 4 for *na: UNISOURCE-BB * * *na: EU-EUNET-19960315 * 193.68.143.254 * 193.68.172.1 * 193.68.203.74 * TOTAL 3 for *na: EU-EUNET-19960315 * * *na: EU-EUNET-19950315 * 193.126.4.65 * 193.126.4.67 * 193.126.8.65 * 193.126.16.230 * 193.126.18.189 * 193.126.90.1 * TOTAL 6 for *na: EU-EUNET-19950315 * * *na: EU-EUNET-19940215 * 193.95.100.6 * TOTAL 1 for *na: EU-EUNET-19940215 * * *na: FR-FTH * 193.252.251.253 * TOTAL 1 for *na: FR-FTH * * *na: SE-SKOPRI * 193.235.16.226 * TOTAL 1 for *na: SE-SKOPRI * * *na: SE-THORSMAN-2 * 193.235.17.3 * 193.235.17.33 * TOTAL 2 for *na: SE-THORSMAN-2 * * *na: SE-TIPS-2 * 193.235.21.40 * TOTAL 1 for *na: SE-TIPS-2 * * *na: SE-SDS * 193.235.48.53 * TOTAL 1 for *na: SE-SDS * * *na: SE-ADA * 193.235.76.171 * TOTAL 1 for *na: SE-ADA * * *na: SE-NORRKOM * 193.235.87.109 * 193.235.88.87 * 193.235.89.1 * 193.235.89.27 * 193.235.89.122 * 193.235.95.250 * TOTAL 6 for *na: SE-NORRKOM * * *na: SE-PRESSB2 * 193.235.118.30 * 193.235.118.37 * TOTAL 2 for *na: SE-PRESSB2 * * *na: SE-DIGEST * 193.235.223.10 * TOTAL 1 for *na: SE-DIGEST * * *na: SE-PHARMDATA * 193.235.229.100 * TOTAL 1 for *na: SE-PHARMDATA * * *na: FR-WANADOO * 193.252.126.150 * 193.252.127.165 * 193.252.130.165 * 193.252.131.155 * 193.252.131.201 * 193.252.134.38 * 193.252.135.250 * 193.252.136.30 * 193.252.136.141 * 193.252.138.55 * 193.252.139.68 * 193.252.139.240 * 193.252.139.252 * 193.252.141.5 * 193.252.141.109 * 193.252.141.125 * 193.252.141.248 * 193.252.143.243 * 193.252.144.48 * ... * TOTAL 115 for *na: FR-WANADOO * * *na: FR-WANADOO * 194.51.238.1 * 194.51.238.2 * TOTAL 2 for *na: FR-WANADOO * * *na: IPPNET * 130.183.1.21 * 130.183.70.10 * 130.183.72.185 * TOTAL 3 for *na: IPPNET * * *na: SE-SMART * 194.14.81.162 * 194.14.81.174 * 194.14.81.175 * 194.14.81.181 * 194.14.81.182 * TOTAL 5 for *na: SE-SMART * * *na: SE-PRIVGIRO * 194.14.98.17 * TOTAL 1 for *na: SE-PRIVGIRO * * *na: CH-PETREL-961017 * 195.15.82.115 * 195.15.83.231 * 195.15.196.11 * 195.15.196.41 * 195.15.196.51 * TOTAL 5 for *na: CH-PETREL-961017 * --------------------------------------------------------------------- -- * * -- * Poul-Henning Kamp FreeBSD coreteam member * phk at FreeBSD.ORG "Real hackers run -current on their laptop." * FreeBSD -- It will take a long time before progress goes too far! * From pault at ripe.net Thu Feb 11 14:08:02 1999 From: pault at ripe.net (Paul Tate) Date: Thu, 11 Feb 1999 14:08:02 +0100 Subject: lowering maximum assignment window In-Reply-To: Your message of Wed, 10 Feb 1999 14:06:35 GMT. References: Message-ID: <199902111308.OAA26889@x24.ripe.net> Stephen Burley writes: * Can I make a suggestion: * * We leave the maximum as a /19 and for a period of time lower the registries * assignment window to a reasonable level i.e. a /22 or /23 which will give ea * ch * registry the time to prove their procedures and expose them to RIPE policies * again. This could be done on a rotational basis so each registry could prove * to * RIPE that they have good working practice. Once RIPE was happy with the * registry they would raise the assignment window to the original size. This * could be done on a 2 year basis. So within a 2 year period RIPE would be hap * py * that any given registry is applying RIPE policy and DB correctly. Of course * this would not need to be done to registries who RIPE are already in regular * contact with. I think the above comments defeat the purpose of the suggestion to cap the size of a maximum assignment window to, say a /21. I cannot imagine the increase in workload on registries like yourself who have a /19 aw to be all that great. Customers requesting a /20 and /19 worth of address space must be in a minority and besides a turnaround time of three days for such requests is pretty reasonable. Your comments about monitoring registries on a two year basis would, I feel, seriously increase the burden on us here at RIPE NCC. I think you should also bear in mind that the suggestion to lower the maximum aw is also an attempt to make the playing field more even so to say. Paul Tate Hostmaster RIPE NCC From zsako at banknet.net Thu Feb 11 14:58:13 1999 From: zsako at banknet.net (Janos Zsako) Date: Thu, 11 Feb 1999 14:58:13 +0100 (MET) Subject: lowering maximum assignment window Message-ID: <199902111358.OAA25996@banknet.banknet.net> > From owner-lir-wg at ripe.net Thu Feb 11 14:38:31 1999 > From: "Bernard Steiner" > > Just for reference, I ran over 12-14h worth of trafic data (cisco > > NetFlow), starting at jan27 midnight, looking for source IP numbers > > which have a RIPE record of status "ALLOCATED" but not one of > > "ASSIGNED". > > > *na: EU-EUNET-950315 > > 193.73.103.80 > > Note: AFAIK, this is actually EUnet's PA address space. > Unfortunately, the customer ran away with it and refused to give it back. > I don't see why EUnet should be held responsible for keeping the database > up-to-date in this case. I also wonder how many cases like this one there > are out there (people running off with PA address space). > > Just my \(= 0.02 worth. This is not EUnet's fault then (if what you state above is correct), however it IS the access provider's fault who allows them to connect to the Internet with UNREGISTERED addresses! UUNet-GW>sho ip bg 193.73.103.80 BGP routing table entry for 193.73.103.0 255.255.255.0, version 8341409 Paths: (1 available, best #1, advertised over EBGP) 701 1833 3303 8408 157.130.33.17 from 157.130.33.17 (137.39.2.154) Origin IGP, valid, external, best aut-num: AS8408 descr: AS for MediaConnect SA descr: Joint network Company descr: Agence Telegraphique Suisse (SDA-ATS) and Groupe Publicitas descr: Avenue des Mousquines 4 - CH-1005 Lausanne descr: AS created by union of access by ISPs of both mother companies descr: (UBN for Publicitas - Eunet for SDA-ATS as-in: from AS3303 100 accept ANY as-in: from AS286 100 accept ANY as-out: to AS3303 announce AS8408 as-out: to AS286 announce AS8408 default: AS3303 100 admin-c: YD31-RIPE admin-c: DD227-RIPE tech-c: YD31-RIPE tech-c: DD227-RIPE mnt-by: AS8408-MNT changed: ddurand at mediaconnect.ch 970804 source: RIPE Ooops... Who said it was unregistered? inetnum: 193.73.72.0 - 193.73.103.0 netname: PUBLICITAS-BLOCK-32 descr: Publicitas-Holding AG descr: Lausanne country: CH admin-c: DD17-RIPE tech-c: DD17-RIPE changed: huber at switch.ch 950713 source: RIPE I suspect this is a registration error or more probably a legacy problem of the database... It seems to me that quite some time ago the above assignment was what we now mean by 193.73.72.0 - 193.73.103.255 ^^^ Therefore, It may be useful to slightly modify Poul's program to cope with this anomaly (since I suspect quite some LEGAL addresses fall in such INCORRECTLY REGISTERED assignments)... Janos From paula at ripe.net Thu Feb 11 15:53:53 1999 From: paula at ripe.net (Paula Caslav) Date: Thu, 11 Feb 1999 15:53:53 +0100 Subject: lowering maximum assignment window In-Reply-To: Your message of Thu, 11 Feb 1999 17:16:05 +0300. <009301be55c9$1f6b3660$0501000a@sysadm.ptt.ru> References: <009301be55c9$1f6b3660$0501000a@sysadm.ptt.ru> Message-ID: <199902111453.PAA16997@x30.ripe.net> Hello Andrei, I'm not talking about lowering the allocation size. An allocation would still be at least a /19. I'm talking about the assignment window- the maximum a registry can assign without comming to the RIPE NCC for approval. Please see http://www.ripe.net/docs/ripe-185.html#toc39 for more information. Kind regards, Paula Caslav RIPE NCC "Andrei V Masalov" writes: * -----Original Message----- * From: Paula Caslav * To: lir-wg at ripe.net * Date: Wednesday, February 10, 1999 4:50 PM * Subject: lowering maximum assignment window * * * > * >Hi all, * > * >As we discussed in our audit report at the Local IR working group at * >the RIPE 32 meeting, we would like to propose a change in the maximum * >assignment window that a Registry can have. Currently an assignment * >window for a Registry can be anything between a 0 and a /19. The /19 * >assignment window, is a historical legacy. * > .... * * >Actually for most Registries, a /24 or /23 assignment window is * >enough, since they rarely make larger assignments than that. However, * >for the Registries that make more large customer assignments, having * >up to a /21 assignment window would allow them room to make most of * >these larger assignment without coming to us for approval. * > * >Please think about this proposal and give us any comments by the end of * >next week. * * * What about BGP announces which are less then /19? Many (if not all) of * the major providers (like C&W, SprintLink) are filtering them out, at least * for * the 195/8 block. * * ??? * * Kind regards, * Andrei Masalov * PTTNET. * * From hakan at defero.net Thu Feb 11 15:13:33 1999 From: hakan at defero.net (Hakan Hansson) Date: Thu, 11 Feb 1999 15:13:33 +0100 Subject: lowering maximum assignment window In-Reply-To: <200102111104.MAA08813@eunet.ch> References: Message-ID: <4.1.19990211151112.00afd170@mail.defero.net> At 12:04 2001-02-11 , Bernard Steiner wrote: >> *na: EU-EUNET-950315 >> 193.73.103.80 > >Note: AFAIK, this is actually EUnet's PA address space. Not according to RIPE DB: inetnum: 193.72.0.0 - 193.73.255.255 - - - status: ALLOCATED UNSPECIFIED If it had been PA address space I would have filtered inbound announcements for it. /Hakan From amasalov at na.ptt.ru Thu Feb 11 15:16:05 1999 From: amasalov at na.ptt.ru (Andrei V Masalov) Date: Thu, 11 Feb 1999 17:16:05 +0300 Subject: lowering maximum assignment window Message-ID: <009301be55c9$1f6b3660$0501000a@sysadm.ptt.ru> -----Original Message----- From: Paula Caslav To: lir-wg at ripe.net Date: Wednesday, February 10, 1999 4:50 PM Subject: lowering maximum assignment window > >Hi all, > >As we discussed in our audit report at the Local IR working group at >the RIPE 32 meeting, we would like to propose a change in the maximum >assignment window that a Registry can have. Currently an assignment >window for a Registry can be anything between a 0 and a /19. The /19 >assignment window, is a historical legacy. > .... >Actually for most Registries, a /24 or /23 assignment window is >enough, since they rarely make larger assignments than that. However, >for the Registries that make more large customer assignments, having >up to a /21 assignment window would allow them room to make most of >these larger assignment without coming to us for approval. > >Please think about this proposal and give us any comments by the end of >next week. What about BGP announces which are less then /19? Many (if not all) of the major providers (like C&W, SprintLink) are filtering them out, at least for the 195/8 block. ??? Kind regards, Andrei Masalov PTTNET. From phk at critter.freebsd.dk Thu Feb 11 15:47:19 1999 From: phk at critter.freebsd.dk (Poul-Henning Kamp) Date: Thu, 11 Feb 1999 15:47:19 +0100 Subject: lowering maximum assignment window In-Reply-To: Your message of "Thu, 11 Feb 1999 14:58:13 +0100." <199902111358.OAA25996@banknet.banknet.net> Message-ID: <20813.918744439@critter.freebsd.dk> >Ooops... Who said it was unregistered? > >inetnum: 193.73.72.0 - 193.73.103.0 >I suspect this is a registration error or more probably a legacy problem >of the database... It seems to me that quite some time ago the above >assignment was what we now mean by 193.73.72.0 - 193.73.103.255 > >Therefore, It may be useful to slightly modify Poul's program to >cope with this anomaly (since I suspect quite some LEGAL addresses >fall in such INCORRECTLY REGISTERED assignments)... Well, I'd rather not change it to DWIM broken database entries, clearly the above database entry should be fixed. But if the script flags entries which should not be complained about for valid reasons, let me know and I'll deal with it. Anyway, I have made a HTML version of the report available at: http://stat.cybercity.dk/ripe It will be put in the daily run so it will be updated every night. (Paula: Feel free to add a link from the RIPE pages) I have added the maintainer to the output as well, I guess that is a better search key for many of you. I will write a README file and wrap up the sources when I have a bit more time. Poul-Henning PS: If there is interest in more work of this kind I'll happily take a contract for it: I'm free-lance wizard and I have to make a living... -- Poul-Henning Kamp FreeBSD coreteam member phk at FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! From jhma at EU.net Thu Feb 11 17:58:42 1999 From: jhma at EU.net (James Aldridge) Date: Thu, 11 Feb 1999 17:58:42 +0100 Subject: lowering maximum assignment window In-Reply-To: Your message of "Wed, 10 Feb 1999 14:33:10 GMT." Message-ID: <199902111658.RAA26186@aegir.EU.net> Stephen Burley wrote: > There was no mention in my email of not filling in 141 info for assignments > or even gathering the information. All i said was to reduce a registries > windows for a short time, so the info you already gather gets sent to ripe > then when the window is raised once RIPE is happy we go back to not sending > the request to RIPE but keep all the relavent data on file. We do large > assignments so i do not agree that a /19 is too large, for most ISP's (small > to medium) it is. Yes, you do make large assignments don't you... | % whois -h whois.ripe.net -r 202.103.132.138 | | % Rights restricted by copyright. See http://www.ripe.net/db/dbcopyright.html | | inetnum: 193.132.195.64 - 255.255.255.224 | netname: DATAGROUD1-1 | descr: Datagroup Plc | country: GB | admin-c: DL774-RIPE | tech-c: DL774-RIPE | status: ASSIGNED PA | mnt-by: AS1849-MNT | changed: stuartw at uk.uu.net 19990211 | source: RIPE ;-) James ----- ___ - James Aldridge, Senior Network Engineer, ---- / / / ___ ____ _/_ -- EUnet Communications Services BV --- /--- / / / / /___/ / --- Singel 540, 1017 AZ Amsterdam, NL -- /___ /___/ / / /___ /_ ---- Tel: +31 20 530 5327; Fax: +31 20 622 4657 - ----- 24hr emergency number: +31 20 421 0865 From stephenb at uk.uu.net Fri Feb 12 10:08:08 1999 From: stephenb at uk.uu.net (Stephen Burley) Date: Fri, 12 Feb 1999 09:08:08 -0000 (GMT) Subject: lowering maximum assignment window In-Reply-To: <199902111308.OAA26889@x24.ripe.net> Message-ID: On 11-Feb-99 Paul Tate wrote: > > Stephen Burley writes: > * Can I make a suggestion: > * > * We leave the maximum as a /19 and for a period of time lower the > registries > * assignment window to a reasonable level i.e. a /22 or /23 which will give > ea > * ch > * registry the time to prove their procedures and expose them to RIPE > policies > * again. This could be done on a rotational basis so each registry could > prove > * to > * RIPE that they have good working practice. Once RIPE was happy with the > * registry they would raise the assignment window to the original size. > This > * could be done on a 2 year basis. So within a 2 year period RIPE would be > hap > * py > * that any given registry is applying RIPE policy and DB correctly. Of > course > * this would not need to be done to registries who RIPE are already in > regular > * contact with. > > I think the above comments defeat the purpose of the suggestion to cap the > size of a maximum assignment window to, say a /21. I cannot imagine the > increase in workload on registries like yourself who have a /19 aw to be all > that great. Customers requesting a /20 and /19 worth of address space must > be > in a minority and besides a turnaround time of three days for such requests > is > pretty reasonable. Not really. This not an academic arena, people are paying for the best service they can get and want their connection tomorrow i am not joking. This reminds me of the UK name space requests which had a 3 to 5 day turn around which was unacceptable so nominet was created and took over the UK name space, we now have instant registration. Just an example of why 3 days is not an acceptable delay in installation time i think your comment was a little naive. Your comments about monitoring registries on a two year > basis would, I feel, seriously increase the burden on us here at RIPE NCC. I > think you should also bear in mind that the suggestion to lower the maximum > aw > is also an attempt to make the playing field more even so to say. > I disagree, the lowering of the largers registries aw to a lower size will probably generate just as much work for ripe. Also if you only apply this to the largest aw's then what about the registries with aw of less than /21, they could be making as many mistakes and not applying policies, all registries must be equaly treated. By rotating the lowering as in Paula's last email then all registries are checked for policy compliance. > Paul Tate > Hostmaster > RIPE NCC > > ---------------------------------- Stephen Burley Senior Hostmaster for UUNET Date: 12-Feb-99 Time: 08:50:07 http://www.uk.uu.net ---------------------------------- An MCI WorldCom Company From curtis at brookfield.ans.net Thu Feb 11 18:37:48 1999 From: curtis at brookfield.ans.net (Curtis Villamizar) Date: Thu, 11 Feb 1999 12:37:48 -0500 Subject: Fwd: RE: Database security In-Reply-To: Your message of "Tue, 05 Jan 1999 17:26:58 +0700." <009D1C59.0FBC5CEC.5@cc.univie.ac.at> Message-ID: <199902111737.MAA21127@brookfield.ans.net> > [ lengthy discussion from db-wg at ripe.net on the issue of exposing > contact information and descriptions deleted. ] As an RPS WG geek I feel that the issue of how much personal contact information to expose should not be decided in the WG. (I don't expect any argument from the ripe community on that point. :) In order to facilitate local decision on how to protect the people and role objects, I'd like to make a proposal that would allow for standardization of the exchange between repositories but also make the decision as to how much data to expose an entirely local decision. The people and role objects would *NOT* be redisributed in the the distributed registry model. They are not needed to configure routers. The need to get people or role information is an exception that can be handled by contacting the authoritative registry (query instructions would be found using the repository objects in the registry itself). Each registry would be free to impose any restrictions that they felt their clients favor and change them since the restrictions would be implemented solely in the query interface. Part of the db-wg discussion suggested that the descr attribute should be restricted. This would be ineffective if the descr had to be included in the flooded information in order to keep the signature on the submission accurate. If it is desirable to have similar local control over access to the description information, then a new "identity" object should be created. The descr can still be placed inline for backward compatibility. Alternately a reference to an identity object can be placed in any object that now allows a descr. The reference can be called "detail" just to be different from descr. [Please separate arguments about the proposal from arguments about the choice of the names "identity" and "detail".] If we decide to do an identity object, the identity object should *NOT* be flooded just as the person and role objects are not flooded. Decisions on whether and how to restrict access to person, role, and identity would be registry local decisions and could be changed by any one registry as they felt it neccesary to do so. Do we have agreement on: 1. don't flood person and role objects (needs to be in rps-dist). 2. add a "identity" object and "detail" attribute (if so, should be added to rpsl-v2 before last call ends). Not flooding identity should be mentioned in rps-dist. 3. the names "identity" and "detail" are resonable choices. Please feel free to continue your argument (on db-wg not rps :) about how RIPE will protect the and person and role objects, and the descr (as an identity object if you decide to protect it). As long as we can make this a registry local decision RPS need not be involved. Thanks. Curtis From maldwyn at ripe.net Thu Feb 11 21:27:56 1999 From: maldwyn at ripe.net (Maldwyn Morris) Date: Thu, 11 Feb 1999 21:27:56 +0100 Subject: Web141 update Message-ID: <199902112027.VAA20069@birch.ripe.net> Hi, Following two good suggestions on this list we have updated the Web141 form at: http://www.ripe.net/cgi-bin/web141/webdebug.pl.cgi You can now enter your current address space usage and addressing plans in a single text field, making it easier to cut and paste multiple lines, and an existing nic-hdl in the person template will be looked up and the details filled in. A bug with the phone: line in the person template has also been fixed. Thanks for the comments, and more are very welcome. Tomorrow we will put the source to Web141 on our FTP site. Cheers, Maldwyn Morris Software Manager RIPE NCC From neil at COLT.NET Fri Feb 12 10:27:56 1999 From: neil at COLT.NET (Neil J. McRae) Date: Fri, 12 Feb 1999 09:27:56 +0000 Subject: lowering maximum assignment window In-Reply-To: Your message of "Fri, 12 Feb 1999 09:08:08 GMT." Message-ID: <199902120927.JAA23635@NetBSD.noc.COLT.NET> On Fri, 12 Feb 1999 09:08:08 -0000 (GMT) Stephen Burley wrote: > Not really. This not an academic arena, people are paying for the best servic e > they can get and want their connection tomorrow i am not joking. This reminds > me of the UK name space requests which had a 3 to 5 day turn around which was > unacceptable so nominet was created and took over the UK name space, we now > have instant registration. Just an example of why 3 days is not an acceptable > delay in installation time i think your comment was a little naive. Stephen you are talking absolute rubbish. For an assignment greater than a /21 it is acceptable that this may take longer, any customer would understand, if you are saying that you can make UUNET out to be better because you can arrange a /19 quicker than we can, then I intend to protest to the RIPE about this, as it is clearly unfair. What would you do for a customer that wanted a /18? How is this any different to a customer who wants a /19 or a /24 ? You aren't making any sense. In anycase, my experience of getting responses from UUNET usually takes atleast 5 working days [thats on a good week] [as both a customer and non-customer] so it looks like you have much bigger issues to solve before this really impacts on your service ability. > I disagree, the lowering of the largers registries aw to a lower size will > probably generate just as much work for ripe. Also if you only apply this to > the largest aw's then what about the registries with aw of less than /21, the y > could be making as many mistakes and not applying policies, all registries mu st > be equaly treated. By rotating the lowering as in Paula's last email then all > registries are checked for policy compliance. Its still sound awfully like you just don't want the hassle of having to email the ripe about allocations, how many greater than /21 blocks have you given out? Regards, Neil. -- Neil J. McRae - Alive and Kicking. C O L T I N T E R N E T neil at COLT.NET NetBSD-1.3.3 released! ftp://ftp.uk.netbsd.org/pub/NetBSD Free the daemon in your computer! From rol at oleane.net Fri Feb 12 12:18:49 1999 From: rol at oleane.net (Paul Rolland) Date: Fri, 12 Feb 1999 12:18:49 +0100 Subject: lowering maximum assignment window In-Reply-To: <199902120927.JAA23635@NetBSD.noc.COLT.NET>; from Neil J. McRae on Fri, Feb 12, 1999 at 09:27:56AM +0000 References: <199902120927.JAA23635@NetBSD.noc.COLT.NET> Message-ID: <19990212121849.Q31458@riri.oleane.net> Hello, What about trying to do it this way : - RIPE keeps track of all the request, - RIPE knows what is the aw of people. It could be very simple (from my point of view) to decide to lower the aw of people if they don't make any record corresponding or bigger than their aw... For example, xx.abcd has an aw of /19. For one year, they don't make (and record) any assignment being /19 or larger, then RIPE change their aw to /20 automagically... Just have to define what are the trigger to decide to lower the aw, and to make it larger... Just my $0.00000000001 worth ;-) Paul Dans son message (In his/her message), Neil J. McRae ecrivait (wrote) : > On Fri, 12 Feb 1999 09:08:08 -0000 (GMT) > Stephen Burley wrote: > > > Not really. This not an academic arena, people are paying for the best servic > e > > they can get and want their connection tomorrow i am not joking. This reminds > > me of the UK name space requests which had a 3 to 5 day turn around which was > > unacceptable so nominet was created and took over the UK name space, we now > > have instant registration. Just an example of why 3 days is not an acceptable > > delay in installation time i think your comment was a little naive. > > Stephen you are talking absolute rubbish. For an assignment greater than > a /21 it is acceptable that this may take longer, any customer > would understand, if you are saying that you can make UUNET out to > be better because you can arrange a /19 quicker than we can, then > I intend to protest to the RIPE about this, as it is clearly unfair. > What would you do for a customer that wanted a /18? How is this > any different to a customer who wants a /19 or a /24 ? You aren't making > any sense. In anycase, my experience of getting responses from UUNET > usually takes atleast 5 working days [thats on a good week] > [as both a customer and non-customer] so it looks like you have much bigger > issues to solve before this really impacts on your service ability. > > > I disagree, the lowering of the largers registries aw to a lower size will > > probably generate just as much work for ripe. Also if you only apply this to > > the largest aw's then what about the registries with aw of less than /21, the > y > > could be making as many mistakes and not applying policies, all registries mu > st > > be equaly treated. By rotating the lowering as in Paula's last email then all > > registries are checked for policy compliance. > > Its still sound awfully like you just don't want the hassle of having > to email the ripe about allocations, how many greater than /21 > blocks have you given out? > > Regards, > Neil. > -- > Neil J. McRae - Alive and Kicking. C O L T I N T E R N E T > neil at COLT.NET NetBSD-1.3.3 released! ftp://ftp.uk.netbsd.org/pub/NetBSD > Free the daemon in your computer! > > > Paul Rolland, rol at oleane.net France Telecom Oleane/Direction Technique/Directeur France Telecom Oleane/Technical Direction/Director -- Please no MIME, I don't read it - Pas de MIME, je ne le lis pas Please no HTML, I'm not a navigator - Pas d'HTML, je ne suis pas un navigateur "I hope some day you'll join us, and the world would be as one" - J. Lennon From barak at netvision.net.il Mon Feb 15 13:16:02 1999 From: barak at netvision.net.il (Barak Engel) Date: Mon, 15 Feb 1999 14:16:02 +0200 Subject: Question: AS number preservation Message-ID: <002001be58dc$f451bf00$de64cbc7@shitty.network.org.il> Hello, I hope this is the right forum for asking this question... if not, please direct me to the right place. TIA. I have a question which I was hoping someone could answer: let us assume that an organization already has an AS number, due to, say, a multihomed connection to two other AS's. This organization now removes one of these connections, and is left with a single-homed connection. However, the organization may still wish to regain a multihomed connection in the future, and therefore would like to keep their AS number. What are the rules governing such a case? Will the AS number be preserved? Will it be taken from the organization? If so, how long does the organization have to reestablish a multihomed connection? Is there any document that deals with this issue (I havent found anything relevant in RIPE-181 or RIPE-185) Many 10x, Sincerely, \'"'/ Barak Engel ( o o ) ---------------------ooOO-^-oOOo--------------------------- barak at netvision.net.il Network Expert BE-RIPE BE174 Phone/Fax: +972 48 560600/551132 Cellular: +972 50 469 341 ----------------------------------------------------------- From maldwyn at ripe.net Thu Feb 18 16:27:40 1999 From: maldwyn at ripe.net (Maldwyn Morris) Date: Thu, 18 Feb 1999 16:27:40 +0100 Subject: ANN: Web141 source release Message-ID: <199902181527.QAA14026@x40.ripe.net> Hi, I am pleased to announce the public release of the source code to the plain-text formatting part of Web141, the European IP Address Space Request Syntax Checker. It is a simple, but large, perl script using the CGI module, designed to be run in the cgi-bin directory of a web server. It needs some customisation by users, but nothing too tricky and comments at the top of the code explain what needs doing. You can get the single source file at: ftp://ftp.ripe.net/tools/web141.pl.cgi You can see our local copy running at: http://www.ripe.net/cgi-bin/web141/web141.pl.cgi Note that this code only formats into plain text a request entered in the html form, and does *not* perform the syntax checks. We will release the source code to autohm, the syntax checker, in two weeks time. Please let us know your comments and suggestions. Cheers, Maldwyn Morris Software Manager RIPE NCC From paula at ripe.net Tue Feb 23 16:44:04 1999 From: paula at ripe.net (Paula Caslav) Date: Tue, 23 Feb 1999 16:44:04 +0100 Subject: policy change: static verification methods Message-ID: <199902231544.QAA05673@x30.ripe.net> Hello all, A few weeks ago I send the following proposal to the lir-wg mailing list for comments. Since no comments were received, we are assuming that nobody has objections to change the policy. We have therefore decided to implement it starting immediately. Kind regards, Paula Caslav RIPE NCC ------- Forwarded Message Date: Wed, 10 Feb 1999 14:38:52 +0100 From: Paula Caslav Sender: owner-lir-wg at ripe.net To: lir-wg at ripe.net Subject: static verification methods Hello all, At the Local IR working group at RIPE 32, the issue was raised about changing the policy for applying verification methods to cable connections. Here is our proposal on how to change this policy. First some background: A few years ago, the IANA asked the Regional Registries to keep an eye on "very small assignments to individuals". This means cases like static dial-up where a registry has to use one IP address per dial-up customer. Since these kinds of assignments could potentially use up a lot of address space, it was decided to strongly discourage using static addresses for this and that that we should monitor these assignments more closely. To do this, any Local Registry that assigns a lot of addresses for this purpose (more than 1024 addresses), was requested that they would have to enter each of these customers in the database individually (as is the case with all assignments to end-users). Later when some Local Registries had a problem with entering all their dial-up customers in the database for confidentiality problems, it was decided to add an alternative method that they could instead send us a weekly report showing the customers they added that week. This is so that the Regional Registries could still keep track of these kinds of assignments. In the last few years, more and more technologies have come along that fall under this procedure. Aside from static dial-up, other services such as web hosting (when not using http 1.1), cable connections, ADSL connections, some ISDN connections, etc.. often need to assign one IP address per customer. In many of these cases, using one IP address per customer is necessary because the host is usually permanently connected to the Internet. The issue was raised that applying these verification methods to technologies that are permanently connected to the Internet and need one IP address per customer, is too cumbersome and adds a lot of extra administrative overhead for the provider. We also realise that there are inconsistencies between the Regional Registries in dealing with these technologies. For these reasons, we would like to change the policy and make a distinction between technologies that are usually connected to the Internet permanently and those that are connected only temporarily. Here is the proposal for the new policy, please give us your comments by the end of next week. Permanently online: This includes technologies such as cable, ADSL, and various server (web, ftp, etc..) connections that are usually permanently connected to the Internet. It can also include analogue or digital (ISDN) dial-up connections if they are used for a service that needs to be permanently online and for services like dial-out on demand. For most of these connections, you need to assign one IP address per connection, even if using DHCP (which we recommend because it makes renumbering easier). We propose to change the policy and to not apply the verification methods to these types of connections. For these technologies, we still need to keep track of the amounts of addresses being assigned, however we would do this whenever the customer requests a new assignment for this purpose. Since these services are permanently connected to the Internet, we will probe these addresses to verify whether the assigned addresses really are in use. It must therefore be made clear to the RIPE NCC exactly which block of IP addresses is used for this purpose. We would expect to see that a high percentage are reachable. We might at this point request additional information to show that they have really used the addresses that were assigned for this purpose in the past- this could be in the form of a list of all URLs assigned, their DNS records, config files, etc.. something to show that the IP addresses are all in use. Virtual web hosting is the only one that has an alternative available (http 1.1) that would allow assigning one IP address for several hosts. Since we want to encourage that people use http 1.1, we propose to continue applying the special verification methods to virtual web hosting that doesn't use http 1.1. Temporarily online: This includes technologies that only need to be connected to the Internet temporarily, such as most telephone dial-up connections. We recommend the use of DHCP and assigning IP addresses based on the number of modem ports. We will therefore continue to apply the special verification methods to any organisation that assigns IP addresses based on the number of customers instead. ------- End of Forwarded Message From paula at ripe.net Tue Feb 23 17:13:44 1999 From: paula at ripe.net (Paula Caslav) Date: Tue, 23 Feb 1999 17:13:44 +0100 Subject: lowering maximum assignment window Message-ID: <199902231613.RAA05824@x30.ripe.net> Hi all, Below is my original message with a proposal to lower the maximum assignment window to a /21 instead of a /19. There was much discussion about this on the lir-wg mailing list. Here is our final proposal that tries to take all the comments into consideration: All registries that currently have a /20 or /19 assignment window will be at a rotating interval (doing them all at once would put too much of a load on an already large wait queue) set to a /23 assignment window temporarily. They will then need to start sending a few requests to show that they understand the assignment policies and procedures. If these requests are fine, we will raise their assignment window to a size that matches the requests we have seen from them (therefore not necessarily to a /19). Hopefully this will get these registries on an equal footing with other LIRs. The reason we need to review the assignment window for all of these registries is that they started out with a /19 assignment window in the beginning of the RIPE NCC. Whereas younger registries started out with a 0 assignment window and have since then proven that they can handle assignents of a certain size and have therefore had their assignment window raised. For all of the younger registries we already have a procedure in place of doing random audits and we will continue doing this. By the way, one of the results of this discussion was that Poul-Henning Kamp wrote a script that checks for inconsistencies between addresses that are in use but are not registrered in the RIPE database. These statistics can be found at: http://stat.cybercity.dk/ripe/ Please check this page for your own registry ID to see whether your registry has any inconsistencies to fix. Of course the RIPE NCC will also be contacting the Registries with the largest list of inconsistenceis as well, but we don't have the resources to systematically contact every registry on the list. Kind regards, Paula Caslav RIPE NCC ------- Forwarded Message Date: Wed, 10 Feb 1999 14:41:17 +0100 From: Paula Caslav Sender: owner-lir-wg at ripe.net To: lir-wg at ripe.net Subject: lowering maximum assignment window Hi all, As we discussed in our audit report at the Local IR working group at the RIPE 32 meeting, we would like to propose a change in the maximum assignment window that a Registry can have. Currently an assignment window for a Registry can be anything between a 0 and a /19. The /19 assignment window, is a historical legacy. These Registries were for the most part free to assign up to 8192 addresses to a customer without coming to the RIPE NCC for approval. Since some of them are still operating as Local Registries, and they still have a /19 assignment window, this means that we have very little contact with them and we have seen in doing audits on these Registries that many of them are out of date with the procedures for assigning IP addresses, and using the database. We also notice that most of them do not really use this large assignment window fully- meaning that most of their assignments are smaller. The router technology has changed much in the last few years, which means that assignments to customers in general are much smaller. Given the fact that most Registries rarely make such large assignments, and the fact that having such a large assignment window makes it easy for them to lose touch with the RIPE NCC policies, we would like to propose having a lower maximum assignment window. We think a /21 maximum assignment window would be more reasonable. Actually for most Registries, a /24 or /23 assignment window is enough, since they rarely make larger assignments than that. However, for the Registries that make more large customer assignments, having up to a /21 assignment window would allow them room to make most of these larger assignment without coming to us for approval. Please think about this proposal and give us any comments by the end of next week. Kind regards, Paula Caslav Registration Services Manager RIPE NCC ------- End of Forwarded Message From paula at ripe.net Tue Feb 23 17:27:53 1999 From: paula at ripe.net (Paula Caslav) Date: Tue, 23 Feb 1999 17:27:53 +0100 Subject: allocation sizes Message-ID: <199902231627.RAA05871@x30.ripe.net> Hello all, A few weeks ago a mail was send to the lirl-wg mailing list to start a discussion about increasing the maximum assignment size to something larger than a /16. I have included the original message from Guy Davies below. There didn't seem to be much consensus on the issue and some further issues were raised that the RIPE NCC needs to consider. The main reason for the proposal was that some larger registries feel that the /16 allocation size is too small and that for internal routing reasons they would sometimes need more than one allocation. The issue was raised that Registries also sometimes need additional allocations for external routing reasons and in the past they've always needed to open separate registries for this. The RIPE NCC needs to think about this issue some more, but in general we feel that opening a new registry for external routing reasons is usually a good idea because often the other network has different needs and is maintained by a different group of people, so it's best so keep them separate. When a registry needs additional address space for internal routing reasons however, we feel that the best solution for now is to consider each case individually and try to come to an agreement that gives the Registry extra flexibility with their internal routes, but still considers the goal of conservation. We'll be talking to the other Regional Registries about comming up with a better policy in the future. We'll keep you informed on this. Kind regards, Paula Caslav RIPE NCC ------- Forwarded Message To: lir-wg at ripe.net Subject: Proposal to raise the maximum allocation to a single LIR From: Guy Davies Date: Tue, 2 Feb 1999 10:06:48 +0000 (BST) Sender: owner-lir-wg at ripe.net Hi All, Following on from my comments at the LIR wg, I'd like to describe the issues we have and some possible solutions for these problems for the longer term. Our primary problem is that we wish to have administrative boundaries within our network separating the Backbone, LL Customers and Dial pools. It is usual to aggregate routing announcements at these administrative boundaries which is essential for the network's scalability and stability. Unfortunately, the current policy decided by the LIR working group states that the maximum amount of total free address space held by any single LIR is a /16. This can be really problematic due to the differing rates at which addresses for customers, backbone addressing and dial space are used up. It is possible to have a serious shortage of addresses for one aspect of your network while there is quite a lot of space remaining for the other areas. The restriction of a /16 means that it may not be possible to acquire more addresses for the area which has the need. It has also been generally noted that the RIPE NCC have not taken internal aggregation of routes into account when making allocations. While it may have been OK to ignore this aspect of network address allocation in the past, this is no longer the case and the decision must now be based also on realistic internal aggregation model. Below are some possible solutions to this problem. 1) Increase the maximum free space available for all LIRs to a shorter prefix. This has the disadvantage that it is contrary to RIPE's aim of conservation of address space. It sets a general precedent that any large or rapidly growing LIR can cite when requesting larger allocations. However, the advantage is that it doesn't make any specific differentiation between those LIRs who make use of the larger allocations and is, therefore, easier for the RIPE NCC to administer. 2) Devise some scheme to differentiate the maximum simultaneous available addresses for large registries from that for the small and medium registries. This has the disadvantage that it adds to the administrative load on the RIPE NCC. It is more difficult to manage exceptions. However, it means that the scope of the availability of more addresses is limited which more closely matches RIPE's aims of conservation of address space. 3) Make a specific exception for those organisations who can show evidence of a need for more than a /16 of address space simultaneously available. This adds even more administrative load on the RIPE NCC because it is based on single exceptions each of which could have a different agreement with the RIPE NCC. However, it matches more closely still the aims of conservation. 4) Setup a registry for each function which needs to be separately administered. This adds more administrative load (and cost) to the LIR and to RIPE NCC because there are more independent registries. The primary benefit is that this solution doesn't require any new policies to be made (unless it's contrary to policy for a single entity to have multiple registries for administrative convenience ;-) I'd like this to be the catalyst for some discussion of this subject on the lir-wg list. If anyone has similar concerns or issues, I'd be particularly keen to hear that. Regards, Guy --- Guy Davies UUNET, an MCI WorldCom company European Network Specialist 332 Science Park, Cambridge, CB4 4BZ, UK e: Guy.Davies at uk.uu.net t: +44 (0)1223 250457 f: +44 (0)1223 250412 ------- End of Forwarded Message From admin at linkline.be Tue Feb 23 16:37:37 1999 From: admin at linkline.be (Nicolas Jungers) Date: Tue, 23 Feb 1999 17:37:37 +0200 Subject: policy change: static verification methods In-Reply-To: <199902231544.QAA05673@x30.ripe.net> Message-ID: At 16:44 +0100 23/02/99, Paula Caslav wrote: >Hello all, > >A few weeks ago I send the following proposal to the lir-wg mailing >list for comments. Since no comments were received, we are assuming >that nobody has objections to change the policy. We have therefore >decided to implement it starting immediately. > >Kind regards, > >Paula Caslav >RIPE NCC > I agree mostly on the proposal. But please bear in mind that in most european places, local connection are not free. So another use of static IP is the setup of MX records on dialup connection that are down most of the time. I understand also your concern to push http 1.1, but you _can't_ sell the virtual web hosting without a fixed IP. The percentage of non http 1.1 compliant browser is just too high for a business customer to accept that is vanity name will not be seen by those. -- don't send mail to this account! It's a not often checked mail account. use support at linkline.be instead. From ip at sonera.se Tue Feb 23 17:04:17 1999 From: ip at sonera.se (IP) Date: Tue, 23 Feb 1999 17:04:17 +0100 Subject: policy change: static verification methods Message-ID: <31B34E7B124DD211BA95006008571E360E347E@pigeon.sonera.se> Hi Paula et al. I, and as far as I know, a couple of other LIR:s, have no objections for the proposed policy, on the contrary. The proposal has a pretty fine tune in balancing the end-customer need as stated as one of our assigning goals in RIPE-185, and the not-that-good policy comment of CATV-network customers as beeing as any dial-up customers, just becouse they are using a modem. As far as I recon, one have to use a 'modem' when going for a Leased Line as well, though signalling would not be analog. Any way, I think it perfectly ok to implement the policy right away. Best regards Per Lundberg/Sonera Registry/RSS11-RIPE > -----Original Message----- > From: Paula Caslav [mailto:paula at ripe.net] > Sent: Tuesday, February 23, 1999 4:44 PM > To: lir-wg at ripe.net > Cc: local-ir at ripe.net > Subject: policy change: static verification methods > > > > Hello all, > > A few weeks ago I send the following proposal to the lir-wg mailing > list for comments. Since no comments were received, we are assuming > that nobody has objections to change the policy. We have therefore > decided to implement it starting immediately. > > Kind regards, > > Paula Caslav > RIPE NCC > > ------- Forwarded Message > > Date: Wed, 10 Feb 1999 14:38:52 +0100 > From: Paula Caslav > Sender: owner-lir-wg at ripe.net > To: lir-wg at ripe.net > Subject: static verification methods > > > Hello all, > > At the Local IR working group at RIPE 32, the issue was raised about > changing the policy for applying verification methods to cable > connections. Here is our proposal on how to change this policy. > > First some background: A few years ago, the IANA asked the Regional > Registries to keep an eye on "very small assignments to > individuals". This means cases like static dial-up where a registry > has to use one IP address per dial-up customer. Since these kinds of > assignments could potentially use up a lot of address space, it was > decided to strongly discourage using static addresses for this and > that that we should monitor these assignments more closely. To do > this, any Local Registry that assigns a lot of addresses for this > purpose (more than 1024 addresses), was requested that they would have > to enter each of these customers in the database individually (as is > the case with all assignments to end-users). Later when some Local > Registries had a problem with entering all their dial-up customers in > the database for confidentiality problems, it was decided to add an > alternative method that they could instead send us a weekly report > showing the customers they added that week. This is so that the > Regional Registries could still keep track of these kinds of > assignments. > > In the last few years, more and more technologies have come along that > fall under this procedure. Aside from static dial-up, other services > such as web hosting (when not using http 1.1), cable connections, ADSL > connections, some ISDN connections, etc.. often need to assign one IP > address per customer. In many of these cases, using one IP address per > customer is necessary because the host is usually permanently > connected to the Internet. > > The issue was raised that applying these verification methods to > technologies that are permanently connected to the Internet and need > one IP address per customer, is too cumbersome and adds a lot of extra > administrative overhead for the provider. We also realise that there > are inconsistencies between the Regional Registries in dealing with > these technologies. > > For these reasons, we would like to change the policy and make a > distinction between technologies that are usually connected to the > Internet permanently > and those that are connected only temporarily. Here is the > proposal for > the new policy, please give us your comments by the end of next week. > > Permanently online: > > This includes technologies such as cable, ADSL, and various server > (web, ftp, etc..) connections that are usually permanently > connected to the Internet. It can also include analogue or digital > (ISDN) dial-up connections if they are used for a service that needs > to be permanently online and for services like dial-out on demand. > > For most of these connections, you need to assign one IP address per > connection, even if using DHCP (which we recommend because it makes > renumbering easier). We propose to change the policy and to not apply > the verification methods to these types of connections. > > For these technologies, we still need to keep track of the amounts of > addresses being assigned, however we would do this whenever the > customer requests a new assignment for this purpose. Since these > services are permanently connected to the Internet, we will probe > these addresses to verify whether the assigned addresses really are in > use. It must therefore be made clear to the RIPE NCC exactly which > block of IP addresses is used for this purpose. We would expect to see > that a high percentage are reachable. We might at this point request > additional information to show that they have really used the > addresses that were assigned for this purpose in the past- this could > be in the form of a list of all URLs assigned, their DNS records, > config files, etc.. something to show that the IP addresses are all in > use. > > Virtual web hosting is the only one that has an alternative available > (http 1.1) that would allow assigning one IP address for several > hosts. Since we want to encourage that people use http 1.1, we propose > to continue applying the special verification methods to virtual web > hosting that doesn't use http 1.1. > > Temporarily online: > > This includes technologies that only need to be connected to the > Internet temporarily, such as most telephone dial-up connections. We > recommend the use of DHCP and assigning IP addresses based on the > number of modem ports. We will therefore continue to apply the special > verification methods to any organisation that assigns IP addresses > based on the number of customers instead. > > > > > > > > ------- End of Forwarded Message > > > From phk at critter.freebsd.dk Tue Feb 23 17:58:32 1999 From: phk at critter.freebsd.dk (Poul-Henning Kamp) Date: Tue, 23 Feb 1999 17:58:32 +0100 Subject: policy change: static verification methods In-Reply-To: Your message of "Tue, 23 Feb 1999 17:37:37 +0200." Message-ID: <26235.919789112@critter.freebsd.dk> In message , Nicolas Jungers writes: >I understand also your concern to push http 1.1, but you _can't_ sell >the virtual web hosting without a fixed IP. The percentage of non >http 1.1 compliant browser is just too high for a business customer >to accept that is vanity name will not be seen by those. I disagree, this is just the same kind of "ancient uptodate information" which makes people insist they get a C class worth of addresses for their firewall. But it would help of course, if somebody would write a document and stick it on the RIPE webserver saying "this is why you have to run http 1.1" and another one saying "this is why you only get the addresses you can prove you need" which ISPs could point such customers at to take the air out of the "...or somebody else will get my business!" argument. -- Poul-Henning Kamp FreeBSD coreteam member phk at FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! From ck at toplink.net Tue Feb 23 20:54:41 1999 From: ck at toplink.net (Christian Kratzer) Date: Tue, 23 Feb 1999 20:54:41 +0100 (CET) Subject: policy change: static verification methods In-Reply-To: from Nicolas Jungers at "Feb 23, 99 05:37:37 pm" Message-ID: <199902231954.UAA24641@mail.toplink.net> Hi, > At 16:44 +0100 23/02/99, Paula Caslav wrote: > >Hello all, > > > >A few weeks ago I send the following proposal to the lir-wg mailing > >list for comments. Since no comments were received, we are assuming > >that nobody has objections to change the policy. We have therefore > >decided to implement it starting immediately. > > > >Kind regards, > > > >Paula Caslav > >RIPE NCC > > > > I agree mostly on the proposal. But please bear in mind that in most > european places, local connection are not free. So another use of > static IP is the setup of MX records on dialup connection that are > down most of the time. this is true. We use static ip's for commercial dialup customers who use privat ip internally with a nat capable router and run perhaps their own mailsevers. They often also want to be able to telnet,ssh back into their networks through port forwarding on the nat router. It would be a waste to start making entries in the ripe database for these single ip's. Any non router dialup users or client only users (small network with nat capable router without any mailservers) will do just fine with a dynamic ip address. The difference here lies in client only setups and setups with local mail etc... servers. > I understand also your concern to push http 1.1, but you _can't_ sell > the virtual web hosting without a fixed IP. The percentage of non > http 1.1 compliant browser is just too high for a business customer > to accept that is vanity name will not be seen by those. this is a hot one and I have the need to share some thoughts on this: The large bulk of the web sites we and propably anybody hosts are of the "homepage" kind of variety of which there are loads on one server. Managing ip address allocation for these kind of low end web servers is a major pita. Which alone is reason engough that we are successively converting all these kinds of servers to name based virtual hosting. The point is not having a http1.1 compliant browser. The point is that the browser sends the http "Host:" header which the absolute majority of browsers already do. This has nothing to do with http1.1 Larger sites running on dedicated servers will always get their separate ip's and might even have a /29 bound to the loopback interface for additional sub websites. But this is totally different from what wee see in the typical virtual web hosting market where we are seeing ip's burned by the truckload. It is especially sad the the majority mass web hosters seem to have loads of /24's with thousands of ip's full of "homepages". They get their address space from upstreams with large aw's who don't ask many questions but prefer to please the customers. They also seldomly reuse those adresses as they seem to concentrate on price dumping and thus don't have the manpower or any intention to cleanup. These are the same kind of people that register truckloads of domains and always create new ripe handles for the contacts. We have even seen one major web hoster and ripe lir enter single ip inetnum objects for each and every web hosting customer. This sort of defeats the whole purpose of assignment windows. Neat trick: become a registry, get yourself a /28 or /27 aw. Then bind a /22 to the loopback of some linux box. All you need to do is add an inetnum object each time you setup a new webserver. All of the above is why I am very happy ripe is now also giving the larger registries a bit of attention. We should all get an even chance in this game of being an ISP/IPP/Iwhatever It is our impression that because of such practices the smaller registriers often have to subnet their networks perhaps a bit too tightly with not too much spare when on the other hand others burn ip's by the truckload..... ---- ok timeout..... thats enough thoughts for the first round. I will now step back and wait to be flamed ..... ;) Greetings Christian Kratzer Toplink -- TopLink Internet Services GmbH ck at 171.2.195.in-addr.arpa Christian Kratzer http://www.toplink.net/ Phone: +49 7032 2701-0 Fax: +49 7032 2701-19 FreeBSD spoken here! From mlelstv at xlink.net Tue Feb 23 23:54:21 1999 From: mlelstv at xlink.net (Michael van Elst) Date: Tue, 23 Feb 1999 23:54:21 +0100 Subject: policy change: static verification methods In-Reply-To: <199902231954.UAA24641@mail.toplink.net>; from Christian Kratzer on Tue, Feb 23, 1999 at 08:54:41PM +0100 References: <199902231954.UAA24641@mail.toplink.net> Message-ID: <19990223235420.A21248@xlink.net> On Tue, Feb 23, 1999 at 08:54:41PM +0100, Christian Kratzer wrote: Hi, > > I understand also your concern to push http 1.1, but you _can't_ sell > > the virtual web hosting without a fixed IP. The percentage of non > > http 1.1 compliant browser is just too high for a business customer > > to accept that is vanity name will not be seen by those. > > The point is not having a http1.1 compliant browser. The point is > that the browser sends the http "Host:" header which the absolute > majority of browsers already do. This has nothing to do with http1.1 I can only agree. We run several ten thousands of name based virtual web servers, mostly "private" homepages but also a significant percentage of business customers. There hasn't been a single complaint that you cannot access those sites with an ancient browser, mostly because you need a slightly recent browser anyway to use 'modern' features like tables or forms :) Regards, -- i.A. Michael van Elst / phone: +49 721 6635 330 Xlink - Network Information Centre \/ fax: +49 721 6635 349 Vincenz-Priessnitz-Str. 3 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster at xlink.net [ Xlink Internet Consulting GmbH, Sitz Koeln ] [ Amtsgericht Koeln HRB 3526, Geschaeftsfuehrer: Michael Rotert ] From cor at xs4all.net Wed Feb 24 00:21:41 1999 From: cor at xs4all.net (cor at xs4all.net) Date: Wed, 24 Feb 1999 00:21:41 +0100 Subject: policy change: static verification methods In-Reply-To: <19990223235420.A21248@xlink.net>; from Michael van Elst on Tue, Feb 23, 1999 at 11:54:21PM +0100 References: <199902231954.UAA24641@mail.toplink.net> <19990223235420.A21248@xlink.net> Message-ID: <19990224002140.A1197@xs4all.nl> > I understand also your concern to push http 1.1, but you _can't_ sell > the virtual web hosting without a fixed IP. The percentage of non > http 1.1 compliant browser is just too high for a business customer > to accept that is vanity name will not be seen by those. This is nonsense. About two years ago we switched to virtual websites without a static IP#. We did a lot of testing beforehand, and found < 0.5% of the webbrowsers not sending Host:. This was over two years ago. This number surely has dropped significantly since, and I bet it's below 0.1% now. These stats were made on our website, which gets about 4 to 5 million hits a day. Imho this is no longer a valid reason to keep using static ip#s for virtual websites. And like my collegue (;)) from Xlink, we havent had a single complaint in the two years we've been doing this. Regards, Cor ps: actually we did get a complaint ;) The first virtual website happened to be a sexually oriented site, and another customer with a faulty browser was really confused why he didnt see his own site, but some sex site :) So ever since we set up a dummy site as the first virtual website. ------------------------------------------------------------------------------ | Cor Bosman | XS4ALL | tel: +31-(0)20-398-7654 | | cor at xs4all.net | Technical Manager | fax: +31-(0)20-398-7601 | ---------------------Living on the edge of chaos-------------------------SP6-- From uffe at swip.net Tue Feb 23 18:48:50 1999 From: uffe at swip.net (Ulf Vedenbrant) Date: Tue, 23 Feb 1999 18:48:50 +0100 (MET) Subject: policy change: static verification methods In-Reply-To: <26235.919789112@critter.freebsd.dk> Message-ID: On Tue, 23 Feb 1999, Poul-Henning Kamp wrote: > In message , Nicolas Jungers writes: > > >I understand also your concern to push http 1.1, but you _can't_ sell > >the virtual web hosting without a fixed IP. The percentage of non > >http 1.1 compliant browser is just too high for a business customer > >to accept that is vanity name will not be seen by those. > > I disagree, this is just the same kind of "ancient uptodate > information" which makes people insist they get a C class worth of > addresses for their firewall. Yep! We are running a large number of webservers per ip-address and we have not recieved any big complaints about this.. And if someone complains they normally understand why we do it this way when we explain why. Dont waste adress-space today that you might need tomorrow! /Uffe From ekb at ivm.net Tue Feb 23 23:24:09 1999 From: ekb at ivm.net (Elmar K. Bins) Date: Tue, 23 Feb 1999 23:24:09 +0100 Subject: Poul-Henning's statistics (was: lowering maximum assignment window) In-Reply-To: <199902231613.RAA05824@x30.ripe.net>; from Paula Caslav on Tue, Feb 23, 1999 at 05:13:44PM +0100 References: <199902231613.RAA05824@x30.ripe.net> Message-ID: <19990223232409.63200@ivm.net> Hi Paula, > By the way, one of the results of this discussion was that Poul-Henning > Kamp wrote a script that checks for inconsistencies between addresses > that are in use but are not registrered in the RIPE database. These > statistics can be found at: http://stat.cybercity.dk/ripe/ These statistics are a very valuable contribution to the community. I'd be even more delighted, were they not cramped into one 3 Megabyte file. I didn't even try any graphical browser on this. Good old lynx did the job anyway ;-) But you know I just don't like to wait... So my idea to Poul-Henning: Just split it down to the country codes. That will decrease traffic to your website I suppose Best regards, Elmar. -- | \ / |\/| Gesellschaft fuer Internet, Vernetzung und Mehrwertdienste mbH | \/ | | Zissener Str. 8 - D-53498 Waldorf - +49 2636 9769-0 - Fax -999 The Net People. Elmar K. Bins (ekb at ivm.net) http://www.ivm.net/ From czmok at ipf.net Tue Feb 23 23:39:37 1999 From: czmok at ipf.net (Jan Czmok) Date: Tue, 23 Feb 1999 23:39:37 +0100 Subject: policy change: static verification methods In-Reply-To: ; from Nicolas Jungers on Tue, Feb 23, 1999 at 05:37:37PM +0200 References: <199902231544.QAA05673@x30.ripe.net> Message-ID: <19990223233937.A28590@darwin.ipf.de> Thus spoke Nicolas Jungers: > At 16:44 +0100 23/02/99, Paula Caslav wrote: > >Hello all, > > > >A few weeks ago I send the following proposal to the lir-wg mailing > >list for comments. Since no comments were received, we are assuming > >that nobody has objections to change the policy. We have therefore > >decided to implement it starting immediately. > > > >Kind regards, > > > >Paula Caslav > >RIPE NCC > > > > I agree mostly on the proposal. But please bear in mind that in most > european places, local connection are not free. So another use of > static IP is the setup of MX records on dialup connection that are > down most of the time. > > I understand also your concern to push http 1.1, but you _can't_ sell > the virtual web hosting without a fixed IP. The percentage of non > http 1.1 compliant browser is just too high for a business customer > to accept that is vanity name will not be seen by those. Also mostly customers would like to have the microsoft server as "virtual web hostings" and therefore (unfortunately) an ip address per customer is needed. To put the acceptance of http1.1 in the net is a good idea, but first you need to tell the global players to implement it correctly with all possibilities ( i am talking about microsoft ). I know that apache exists for windows nt and some good ftp servers; but most of the time customers would like to have a "Frontpage Web" like click-and-fun desktops and webs. It's the customer which is driven by microsoft. I dislike Windows NT and like Linux of its stability and flexability (just to tell) Jan > -- > don't send mail to this account! It's a not often checked mail account. > use support at linkline.be instead. From mlelstv at xlink.net Wed Feb 24 11:17:54 1999 From: mlelstv at xlink.net (Michael van Elst) Date: Wed, 24 Feb 1999 11:17:54 +0100 Subject: policy change: static verification methods In-Reply-To: <19990223233937.A28590@darwin.ipf.de>; from Jan Czmok on Tue, Feb 23, 1999 at 11:39:37PM +0100 References: <199902231544.QAA05673@x30.ripe.net> <19990223233937.A28590@darwin.ipf.de> Message-ID: <19990224111754.A2043@xlink.net> Hi, > Also mostly customers would like to have the microsoft server as "virtual > web hostings" and therefore (unfortunately) an ip address per customer > is needed. it isn't. As of IIS4.0 name based virtual web servers are supported. -- i.A. Michael van Elst / phone: +49 721 6635 330 Xlink - Network Information Centre \/ fax: +49 721 6635 349 Vincenz-Priessnitz-Str. 3 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster at xlink.net [ Xlink Internet Consulting GmbH, Sitz Koeln ] [ Amtsgericht Koeln HRB 3526, Geschaeftsfuehrer: Michael Rotert ] From paula at ripe.net Wed Feb 24 11:38:39 1999 From: paula at ripe.net (Paula Caslav) Date: Wed, 24 Feb 1999 11:38:39 +0100 Subject: policy change: static verification methods In-Reply-To: Your message of Tue, 23 Feb 1999 20:54:41 +0100. <199902231954.UAA24641@mail.toplink.net> References: <199902231954.UAA24641@mail.toplink.net> Message-ID: <199902241038.LAA07623@x30.ripe.net> Dear Christian, With things like static IPs for commmercial customers, we would consider the reason for using static IP addresses and if there is a good technical reason for it (as it seems to be in this case), then we would also not apply the verification methods to it. Kind regards, Paula Caslav RIPE NCC Christian Kratzer writes: * Hi, * * > At 16:44 +0100 23/02/99, Paula Caslav wrote: * > >Hello all, * > > * > >A few weeks ago I send the following proposal to the lir-wg mailing * > >list for comments. Since no comments were received, we are assuming * > >that nobody has objections to change the policy. We have therefore * > >decided to implement it starting immediately. * > > * > >Kind regards, * > > * > >Paula Caslav * > >RIPE NCC * > > * > * > I agree mostly on the proposal. But please bear in mind that in most * > european places, local connection are not free. So another use of * > static IP is the setup of MX records on dialup connection that are * > down most of the time. * * this is true. We use static ip's for commercial dialup customers who * use privat ip internally with a nat capable router and run perhaps * their own mailsevers. They often also want to be able to telnet,ssh * back into their networks through port forwarding on the nat router. * * It would be a waste to start making entries in the ripe database * for these single ip's. * * Any non router dialup users or client only users (small network with * nat capable router without any mailservers) will do just fine with * a dynamic ip address. * * The difference here lies in client only setups and setups with * local mail etc... servers. * * > I understand also your concern to push http 1.1, but you _can't_ sell * > the virtual web hosting without a fixed IP. The percentage of non * > http 1.1 compliant browser is just too high for a business customer * > to accept that is vanity name will not be seen by those. * * this is a hot one and I have the need to share some thoughts * on this: * * The large bulk of the web sites we and propably anybody hosts are of * the "homepage" kind of variety of which there are loads on one server. * * Managing ip address allocation for these kind of low end web servers * is a major pita. Which alone is reason engough that we are successively * converting all these kinds of servers to name based virtual hosting. * * The point is not having a http1.1 compliant browser. The point is * that the browser sends the http "Host:" header which the absolute * majority of browsers already do. This has nothing to do with http1.1 * * Larger sites running on dedicated servers will always get their * separate ip's and might even have a /29 bound to the loopback * interface for additional sub websites. * * But this is totally different from what wee see in the typical * virtual web hosting market where we are seeing ip's burned * by the truckload. * * It is especially sad the the majority mass web hosters seem to * have loads of /24's with thousands of ip's full of "homepages". * * They get their address space from upstreams with large aw's who * don't ask many questions but prefer to please the customers. They * also seldomly reuse those adresses as they seem to concentrate on * price dumping and thus don't have the manpower or any intention * to cleanup. These are the same kind of people that register * truckloads of domains and always create new ripe handles for * the contacts. * * We have even seen one major web hoster and ripe lir enter single * ip inetnum objects for each and every web hosting customer. * This sort of defeats the whole purpose of assignment windows. * * Neat trick: become a registry, get yourself a /28 or /27 aw. * Then bind a /22 to the loopback of some linux box. All you need * to do is add an inetnum object each time you setup a new * webserver. * * All of the above is why I am very happy ripe is now also * giving the larger registries a bit of attention. We should all * get an even chance in this game of being an ISP/IPP/Iwhatever * * It is our impression that because of such practices the smaller * registriers often have to subnet their networks perhaps a bit * too tightly with not too much spare when on the other hand * others burn ip's by the truckload..... * * ---- * * ok timeout..... thats enough thoughts for the first round. * I will now step back and wait to be flamed ..... ;) * * * Greetings * Christian Kratzer * Toplink * * * -- * TopLink Internet Services GmbH ck at 171.2.195.in-addr.ar * pa * Christian Kratzer http://www.toplink.net/ * Phone: +49 7032 2701-0 * Fax: +49 7032 2701-19 FreeBSD spoken here! * From barak at netvision.net.il Wed Feb 24 11:39:29 1999 From: barak at netvision.net.il (Barak Engel) Date: Wed, 24 Feb 1999 12:39:29 +0200 Subject: Poul-Henning's statistics (was: lowering maximum assignment window) In-Reply-To: <19990223232409.63200@ivm.net> Message-ID: <000601be5fe1$f5255f20$de64cbc7@shitty.network.org.il> > > By the way, one of the results of this discussion was that Poul-Henning > > Kamp wrote a script that checks for inconsistencies between addresses > > that are in use but are not registrered in the RIPE database. These > > statistics can be found at: http://stat.cybercity.dk/ripe/ Btw, Im not sure how this was determined... for example, Netvision has over 600 of its dial-in IP's listed over there - the only ones listed - from the 62.0.128.0/18 block. These IPs are registered as one block in the RIPE DB, and the IPs are used in our POPs. What is the nature of the inconsistency? Just wondering. Sincerely, \'"'/ Barak Engel ( o o ) ---------------------ooOO-^-oOOo--------------------------- barak at netvision.net.il Network Expert BE-RIPE BE174 Phone/Fax: +972 48 560600/551132 Cellular: +972 50 469 341 ----------------------------------------------------------- From paula at ripe.net Wed Feb 24 11:48:15 1999 From: paula at ripe.net (Paula Caslav) Date: Wed, 24 Feb 1999 11:48:15 +0100 Subject: Poul-Henning's statistics (was: lowering maximum assignment window) In-Reply-To: Your message of Wed, 24 Feb 1999 12:39:29 +0200. <000601be5fe1$f5255f20$de64cbc7@shitty.network.org.il> References: <000601be5fe1$f5255f20$de64cbc7@shitty.network.org.il> Message-ID: <199902241048.LAA07700@x30.ripe.net> Dear Barak, I think the problem is this: inetnum: 62.0.128.0 - 62.0.191.255 netname: NV-POPS descr: Netvision POPs country: IL admin-c: NN105-RIPE tech-c: NN105-RIPE status: ALLOCATED PA mnt-by: NV-MNT-RIPE mnt-lower: NV-MNT-RIPE changed: barak at netvision.net.il 19981228 source: RIPE You have "ALLOCATED" in the status attribute. A registry can only make assignments, therefore it should say "ASSIGNED" only the RIPE NCC can make allocations. I think this will be the cause of many of the inconsistencies on the list. If you have an inconsistency like this, please change the status attribute to say ASSIGNED instead of ALLOCATED. Kind regards, Paula Caslav RIPE NCC "Barak Engel" writes: * > > By the way, one of the results of this discussion was that Poul-Henning * > > Kamp wrote a script that checks for inconsistencies between addresses * > > that are in use but are not registrered in the RIPE database. These * > > statistics can be found at: http://stat.cybercity.dk/ripe/ * * Btw, Im not sure how this was determined... for example, Netvision has over * 600 * of its dial-in IP's listed over there - the only ones listed - from the * 62.0.128.0/18 block. These IPs are registered as one block in the RIPE DB, a * nd * the IPs are used in our POPs. What is the nature of the inconsistency? * * Just wondering. * * Sincerely, \'"'/ * Barak Engel ( o o ) * ---------------------ooOO-^-oOOo--------------------------- * barak at netvision.net.il Network Expert BE-RIPE BE174 * Phone/Fax: +972 48 560600/551132 Cellular: +972 50 469 341 * ----------------------------------------------------------- * * From phk at critter.freebsd.dk Wed Feb 24 11:55:58 1999 From: phk at critter.freebsd.dk (Poul-Henning Kamp) Date: Wed, 24 Feb 1999 11:55:58 +0100 Subject: Poul-Henning's statistics (was: lowering maximum assignment window) In-Reply-To: Your message of "Tue, 23 Feb 1999 23:24:09 +0100." <19990223232409.63200@ivm.net> Message-ID: <28678.919853758@critter.freebsd.dk> In message <19990223232409.63200 at ivm.net>, "Elmar K. Bins" writes: >Hi Paula, > >> By the way, one of the results of this discussion was that Poul-Henning >> Kamp wrote a script that checks for inconsistencies between addresses >> that are in use but are not registrered in the RIPE database. These >> statistics can be found at: http://stat.cybercity.dk/ripe/ > >These statistics are a very valuable contribution to the community. >I'd be even more delighted, were they not cramped into one 3 Megabyte >file. I didn't even try any graphical browser on this. Good old lynx >did the job anyway ;-) > >But you know I just don't like to wait... > >So my idea to Poul-Henning: Just split it down to the country codes. >That will decrease traffic to your website I suppose You know, I thought about that, but then I thought: The people most incovenienced by the size are the same people who has most work to do... :-) -- Poul-Henning Kamp FreeBSD coreteam member phk at FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! From phk at critter.freebsd.dk Wed Feb 24 12:06:28 1999 From: phk at critter.freebsd.dk (Poul-Henning Kamp) Date: Wed, 24 Feb 1999 12:06:28 +0100 Subject: Poul-Henning's statistics (was: lowering maximum assignment window) In-Reply-To: Your message of "Wed, 24 Feb 1999 11:48:15 +0100." <199902241048.LAA07700@x30.ripe.net> Message-ID: <28791.919854388@critter.freebsd.dk> In message <199902241048.LAA07700 at x30.ripe.net>, Paula Caslav writes: Would it be an idea to go throught he database for all "ALLOCATED" objects not maintained by RIPE and change them to ASSIGNED and then have the database software reject such records in the future ? >A registry can only make >assignments, therefore it should say "ASSIGNED" only the RIPE NCC can >make allocations. I think this will be the cause of many of the >inconsistencies on the list. If you have an inconsistency like this, >please change the status attribute to say ASSIGNED instead of ALLOCATED. -- Poul-Henning Kamp FreeBSD coreteam member phk at FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! From ck at toplink.net Wed Feb 24 12:22:28 1999 From: ck at toplink.net (Christian Kratzer) Date: Wed, 24 Feb 1999 12:22:28 +0100 (CET) Subject: policy change: static verification methods In-Reply-To: <199902241038.LAA07623@x30.ripe.net> from Paula Caslav at "Feb 24, 99 11:38:39 am" Message-ID: <199902241122.MAA10550@mail.toplink.net> Hi Paula, > > Dear Christian, > > With things like static IPs for commmercial customers, we would > consider the reason for using static IP addresses and if there is a > good technical reason for it (as it seems to be in this case), then we > would also not apply the verification methods to it. I never suspected ripe would not approve usage of ip's for a legit. techincal purpose. Rather I was a little upset about the way people burn ip's by the truckload for very simple web mass web hosting. Greetings Christian -- TopLink Internet Services GmbH ck at 171.2.195.in-addr.arpa Christian Kratzer http://www.toplink.net/ Phone: +49 7032 2701-0 Fax: +49 7032 2701-19 FreeBSD spoken here! From zeidler at xlink.net Wed Feb 24 14:48:52 1999 From: zeidler at xlink.net (Petra Zeidler) Date: Wed, 24 Feb 1999 14:48:52 +0100 Subject: Poul-Henning's statistics (was: lowering maximum assignment window) In-Reply-To: <28791.919854388@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Feb 24, 1999 at 12:06:28PM +0100 References: <199902241048.LAA07700@x30.ripe.net> <28791.919854388@critter.freebsd.dk> Message-ID: <19990224144852.A20844@xlink.net> Hi, Thus wrote Poul-Henning Kamp (phk at critter.freebsd.dk): > In message <199902241048.LAA07700 at x30.ripe.net>, Paula Caslav writes: > > Would it be an idea to go throught he database for all "ALLOCATED" > objects not maintained by RIPE and change them to ASSIGNED and then > have the database software reject such records in the future ? That would probably be a good idea. BTW, the statistic also happened to find non-CIDR ClassC.0 - ClassC.0 entries, but I fear the ones you found weren't all of these from our (Xlinks) allocations. :-} db-scrubbingly yours, Petra Zeidler -- i.A. Petra Zeidler, Neukundenanschluss Xlink Internet Service GmbH [X] zeidler at xlink.net [X] Tel: 0721/9652-220 [X] Fax: 0721/9652-209 [X] Geschaeftsfuehrer: Michael Rotert. Amtsgericht Karlsruhe HRB 8161. [X] Auftraege erledigen wir zu unseren Allgemeinen Geschaeftsbedingungen. From stephenb at uk.uu.net Thu Feb 25 09:11:56 1999 From: stephenb at uk.uu.net (Stephen Burley) Date: Thu, 25 Feb 1999 08:11:56 -0000 (GMT) Subject: policy change: static verification methods In-Reply-To: Message-ID: On 23-Feb-99 Nicolas Jungers wrote: > At 16:44 +0100 23/02/99, Paula Caslav wrote: > >Hello all, > > > >A few weeks ago I send the following proposal to the lir-wg mailing > >list for comments. Since no comments were received, we are assuming > >that nobody has objections to change the policy. We have therefore > >decided to implement it starting immediately. > > > >Kind regards, > > > >Paula Caslav > >RIPE NCC > > > > I agree mostly on the proposal. But please bear in mind that in most > european places, local connection are not free. So another use of > static IP is the setup of MX records on dialup connection that are > down most of the time. > > I understand also your concern to push http 1.1, but you _can't_ sell > the virtual web hosting without a fixed IP. The percentage of non > http 1.1 compliant browser is just too high for a business customer > to accept that is vanity name will not be seen by those. I disagree we have created a whole product using http1.1 and get no complaints about not being able to reach the site. It might encourage people to upgrade to a newer version browser and so speed up the use of http1.1. > -- > don't send mail to this account! It's a not often checked mail account. > use support at linkline.be instead. ---------------------------------- Stephen Burley Senior Hostmaster for UUNET Date: 25-Feb-99 Time: 08:08:47 http://www.uk.uu.net ---------------------------------- An MCI WorldCom Company From Anela.Lovric at tel.hr Thu Feb 25 11:55:32 1999 From: Anela.Lovric at tel.hr (Anela Lovric) Date: Thu, 25 Feb 1999 11:55:32 +0100 Subject: Another AS No. Message-ID: <001f01be60ad$619fbda0$82fe1dc3@anela.tel.hr> Hello all, We are ISP and local-ir too, and we have 4 links (bgp) to other ISP. We are thinking about dividing our network in two AS. Reason for that is to divide network and customers so we could announce AS-es different to different bgp peers. I know that we can use route-map in bgp to announce different IP addreses, but it seems simpliest with two different AS No. So my question is : Is it possible to ask another AS Number from RIPE within existing IP space or with new IP addresses allocation? I did not find anything about another AS in ripe documents. Maybe this is stupid idea, maybe not I do not know, so I would appreciate any suggestion or advice. Thanks in advance, Anela Lovric HiNet From akoch at sgh-net.de Thu Feb 25 13:33:58 1999 From: akoch at sgh-net.de (Alexander Koch) Date: Thu, 25 Feb 1999 12:33:58 +0000 Subject: policy change: static verification methods In-Reply-To: <19990224111754.A2043@xlink.net>; from "Michael van Elst" on Wed, 24 Feb 1999 11:17:54 +0100 References: <199902231544.QAA05673@x30.ripe.net> <19990223233937.A28590@darwin.ipf.de> <19990224111754.A2043@xlink.net> Message-ID: <19990225123358.B17495@nuss.hannover.sgh-net.de> Hello. > > Also mostly customers would like to have the microsoft server as "virtual > > web hostings" and therefore (unfortunately) an ip address per customer > > is needed. > > it isn't. As of IIS4.0 name based virtual web servers are supported. But it only works if you explicitely enter the same IP over and over again where the typical "eNTe admin" would not even think of not entering unique IPs for every web servers. It works. But you have to search for it. We found out as a customer wanted two /24s for vhosting. What fun it was telling him it will work with just one... oh well. Regards, Alexander Koch -- SGH Internet Division, Alexander Koch, Systems Administration Hannover, Germany, Phone +49 511 909198 0, Fax +49 511 391307 From jee at alcom.aland.fi Thu Feb 25 10:45:15 1999 From: jee at alcom.aland.fi (Jan-Erik Eriksson) Date: Thu, 25 Feb 1999 11:45:15 +0200 (EET) Subject: policy change: static verification methods In-Reply-To: Message-ID: On Thu, 25 Feb 1999, Stephen Burley wrote: > >On 23-Feb-99 Nicolas Jungers wrote: >> At 16:44 +0100 23/02/99, Paula Caslav wrote: >> >Hello all, >> > >> >A few weeks ago I send the following proposal to the lir-wg mailing >> >list for comments. Since no comments were received, we are assuming >> >that nobody has objections to change the policy. We have therefore >> >decided to implement it starting immediately. >> > >> >Kind regards, >> > >> >Paula Caslav >> >RIPE NCC >> > >> >> I agree mostly on the proposal. But please bear in mind that in most >> european places, local connection are not free. So another use of >> static IP is the setup of MX records on dialup connection that are >> down most of the time. >> >> I understand also your concern to push http 1.1, but you _can't_ sell >> the virtual web hosting without a fixed IP. The percentage of non >> http 1.1 compliant browser is just too high for a business customer >> to accept that is vanity name will not be seen by those. > >I disagree we have created a whole product using http1.1 and get no complaints >about not being able to reach the site. It might encourage people to upgrade to >a newer version browser and so speed up the use of http1.1. I agree, we have been using IP-less virtual hosting with HTTP 1.1 for over a year and not received a single complaint. It is more a choice of webserver technology I would say. -- Janne ------------- ELCOM ------------- Network Operations Center --------- Jan-Erik Eriksson mailto: jee at alcom.aland.fi ELCOM phone: +358 18 23500 PB 233, Torggatan 10 fax: +358 18 14643 FIN-22100 Mariehamn URL: http://www.alcom.aland.fi From BERI at etf.bg.ac.yu Thu Feb 25 16:08:00 1999 From: BERI at etf.bg.ac.yu (Berislav Todorovic) Date: Thu, 25 Feb 1999 16:08 +0100 Subject: Another AS No. Message-ID: <619ADEAE08000D12@etf.bg.ac.yu> >> We are ISP and local-ir too, and we have 4 links (bgp) to other ISP. >> We are thinking about dividing our network in two AS. Reason for that >> is to divide network and customers so we could announce AS-es different >> to different bgp peers. >> ... (snip) >> Is it possible to ask another AS Number from RIPE within existing IP space >> or with new IP addresses allocation? According to the RFC 1930: An AS is only needed when you have a routing policy which is different from that of your border gateway peers. Here routing policy refers to how the rest of the Internet makes routing decisions based on information from your AS. Since your new AS will use different prefixes and different routing policies than your current AS, that may be a solid argument to ask the regional registry to assign you a separate number. At least - all huge ISP's in the world have several AS numbers. ;-) Regards, Beri .-------. | --+-- | Berislav Todorovic, B.Sc.E.E. | E-mail: BERI at etf.bg.ac.yu | /|\ Hostmaster of the YU TLD | |-(-+-)-| School of Electrical Engineering | Phone: (+381-11) 3221-419 | \|/ Bulevar Revolucije 73 | 3218-350 | --+-- | 11000 Belgrade SERBIA, YUGOSLAVIA | Fax: (+381-11) 3248-681 `-------' -------------------------------------------------------------------- From paula at ripe.net Thu Feb 25 16:14:43 1999 From: paula at ripe.net (Paula Caslav) Date: Thu, 25 Feb 1999 16:14:43 +0100 Subject: Another AS No. In-Reply-To: Your message of Thu, 25 Feb 1999 11:55:32 +0100. <001f01be60ad$619fbda0$82fe1dc3@anela.tel.hr> References: <001f01be60ad$619fbda0$82fe1dc3@anela.tel.hr> Message-ID: <199902251514.QAA12151@x30.ripe.net> Dear Anela, If the 2nd AS will have a different routing policy from the first one then you can go ahead and request it from us. As for what block of IP addresses to use- you can either use your existing address space, or if this AS will really grow and you expect to use a lot of IP addresses for it in the future, you might want to set up a separate registry for it. By the way, there was a request about returning of AS numbers. If you received an AS number and the plans changed so that it is no longer needed, please contact hostmaster at ripe.net to return it. If however, you do have plans to re-establish a multihomed connection in the near future, you can hold on to the number until then. I'd recommend contacting hostmaster anyway to explain the situation. Kind regards, Paula Caslav RIPE NCC "Anela Lovric" writes: * Hello all, * * We are ISP and local-ir too, and we have 4 links (bgp) to other ISP. * We are thinking about dividing our network in two AS. Reason for that is to * divide network and customers so we could announce AS-es different to * different bgp peers. * I know that we can use route-map in bgp to announce different IP addreses, * but it seems simpliest with two different AS No. * * So my question is : * Is it possible to ask another AS Number from RIPE within existing IP space * or with new IP addresses allocation? * I did not find anything about another AS in ripe documents. * * Maybe this is stupid idea, maybe not I do not know, so I would appreciate * any suggestion or advice. * * Thanks in advance, * * Anela Lovric * HiNet * * * From joao at ripe.net Thu Feb 25 18:09:25 1999 From: joao at ripe.net (Joao Luis Silva Damas) Date: Thu, 25 Feb 1999 18:09:25 +0100 Subject: Adding nic handles to contact objects without one Message-ID: <199902251709.SAA00968@x41.ripe.net> Dear all, during the last RIPE meeting, in Amsterdam, the database working group discussed a proposal to automatically add NIC Handles to all person and role objects in the RIPE Database that don't yet have one (new objects can't be created without nic handles anymore). This proposal was supported by the working group and it was agreed that it should be circulated to the mailing lists to give people not attending a chance to provide input. This does not affect how other objects reference these person or role objects. This is only intended to bring old objects into conformance with the current object definitions and does not mean that data provided by the user will be modified. Only the nic handle attribute will be given a value when the object lacks one. No other attributes will be touched. Objects which already have nic handles will not be touched. The nic handle is a tag conveying no information about the user or role described in the object. It is an identifier for the object. This addition would make data more uniform and could be a benefit for everyone. For more information on nic handles, please read RIPE 157 and RIPE 189 available at http://www.ripe.net/docs Best regards, Joao Damas Database Group RIPE NCC From chris at hiway.co.uk Thu Feb 25 13:45:51 1999 From: chris at hiway.co.uk (Chris Arnold) Date: Thu, 25 Feb 1999 12:45:51 -0000 Subject: policy change: static verification methods In-Reply-To: <19990225123358.B17495@nuss.hannover.sgh-net.de> References: <19990224111754.A2043@xlink.net>; from "Michael van Elst" on Wed, 24 Feb 1999 11:17:54 +0100 Message-ID: <199902251246.MAA13343@mailsrv.hiway.co.uk> Hello Its not so much the virtual Web sites, they I agree can be run on a single IP server However When it comes to giving each individual customer FTP access to mange their site or have an FTP site in its own right IIS4 demands that you have unique IP's Unless of course someone knows a better method that is not an administrative nightmare. > Hello. > > > > Also mostly customers would like to have the microsoft server as "virtual > > > web hostings" and therefore (unfortunately) an ip address per customer > > > is needed. > > > > it isn't. As of IIS4.0 name based virtual web servers are supported. > > But it only works if you explicitely enter the same IP over and > over again where the typical "eNTe admin" would not even think > of not entering unique IPs for every web servers. > > It works. But you have to search for it. We found out as a > customer wanted two /24s for vhosting. What fun it was telling > him it will work with just one... oh well. > > Regards, > Alexander Koch > > -- > SGH Internet Division, Alexander Koch, Systems Administration > Hannover, Germany, Phone +49 511 909198 0, Fax +49 511 391307 __ | Best Regards |_ /\ /**\ Chris Arnold (Charlie Alpha) Director - Hiway Communications Ltd Internet e-mail: chris at hiway.co.uk Tel +44 (0)1635 573300 FAX: +44 (0)1635 573329 URL= http://www.hiway.co.uk From mlelstv at xlink.net Thu Feb 25 20:37:05 1999 From: mlelstv at xlink.net (Michael van Elst) Date: Thu, 25 Feb 1999 20:37:05 +0100 Subject: policy change: static verification methods In-Reply-To: <199902251246.MAA13343@mailsrv.hiway.co.uk>; from Chris Arnold on Thu, Feb 25, 1999 at 12:45:51PM -0000 References: <19990224111754.A2043@xlink.net>; <19990225123358.B17495@nuss.hannover.sgh-net.de> <199902251246.MAA13343@mailsrv.hiway.co.uk> Message-ID: <19990225203704.A17968@xlink.net> On Thu, Feb 25, 1999 at 12:45:51PM -0000, Chris Arnold wrote: > Hello > > Its not so much the virtual Web sites, they I agree can be run on a > single IP server > > However > When it comes to giving each individual customer FTP > access to mange their site or have an FTP site in its own right > IIS4 demands that you have unique IP's > > Unless of course someone knows a better method > that is not an administrative nightmare. FTP identifies a user with a username and password. BTW, if you want to host many servers on a single machine you should learn about scripting. This usually solves all administrative nightmares. Greetigns, -- i.A. Michael van Elst / phone: +49 721 6635 330 Xlink - Network Information Centre \/ fax: +49 721 6635 349 Vincenz-Priessnitz-Str. 3 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster at xlink.net [ Xlink Internet Consulting GmbH, Sitz Koeln ] [ Amtsgericht Koeln HRB 3526, Geschaeftsfuehrer: Michael Rotert ] From wolf at profi.net Thu Feb 25 22:22:55 1999 From: wolf at profi.net (Wolfgang Mair) Date: Thu, 25 Feb 1999 22:22:55 +0100 (MET) Subject: Another AS No. In-Reply-To: <001f01be60ad$619fbda0$82fe1dc3@anela.tel.hr> Message-ID: Hi Anela, I would highly recomment to use route-maps and communities to do so. It looks more difficult on the first view, but gives you much more flexibility in the future. regards, Wolfgang On Thu, 25 Feb 1999, Anela Lovric wrote: > Hello all, > > We are ISP and local-ir too, and we have 4 links (bgp) to other ISP. > We are thinking about dividing our network in two AS. Reason for that is to > divide network and customers so we could announce AS-es different to > different bgp peers. > I know that we can use route-map in bgp to announce different IP addreses, > but it seems simpliest with two different AS No. > > So my question is : > Is it possible to ask another AS Number from RIPE within existing IP space > or with new IP addresses allocation? > I did not find anything about another AS in ripe documents. > > Maybe this is stupid idea, maybe not I do not know, so I would appreciate > any suggestion or advice. > > Thanks in advance, > > Anela Lovric > HiNet > > > ------------------------------------------------------------------------------ P R O F I . N E T A G * Wolfgang Mair * Vorstand/CEO ------------------------------------------------------------------------------ profi.net | Aindlinger Str. 7 | Voice +49 821 27062-0 Hassler & Mair AG | 86167 Augsburg | Fax +49 821 27062-99 | Germany | Email wolf at profi.net From Adam.Morris at onyx.net Fri Feb 26 11:58:10 1999 From: Adam.Morris at onyx.net (Adam Morris) Date: Fri, 26 Feb 1999 10:58:10 -0000 (GMT) Subject: policy change: static verification methods In-Reply-To: <199902251246.MAA13343@mailsrv.hiway.co.uk> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- On 25-Feb-99 Chris Arnold wrote: > Hello > > Its not so much the virtual Web sites, they I agree can be run on a > single IP server > > However > When it comes to giving each individual customer FTP > access to mange their site or have an FTP site in its own right > IIS4 demands that you have unique IP's > > Unless of course someone knows a better method > that is not an administrative nightmare. > AFAIK there is no alternative. FTP cannot distinguish between a request for one domain or another based on the contents of the protocol. There are two alternatives here... either we rewrite the protocol to send the hostname as part of the address or you give static IP addresses to all of your ftp sites. Adam - ---------------------------------- If this message isn't signed, it probably isn't me. Adam Morris - Systems Engineer - Onyx Internet If you just try long enough and hard enough, you can always manage to boot yourself in the posterior. -- A. J. Liebling - ---------------------------------- -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQCVAwUBNtZ+QjxztoTO1QFNAQEfWQP+NcjkSHZtEA/UNRRHgggefjF89gkJO6fP MAODN7D76mmnKnmLkBbpf+z5FIxjyqaYFRhLz0uLeiWNgQ+9GX+obVwAY4gG37dq r+PZDtQEulaTAsSZgbWY9aVx5OkVsvNisKoAAqZZhFJcOGclhXA7q0Q7w8v/t9i7 qwkucpqVj7E= =pwMP -----END PGP SIGNATURE----- From Eamonn at ripe.net Fri Feb 26 15:54:25 1999 From: Eamonn at ripe.net (Eamonn) Date: Fri, 26 Feb 1999 15:54:25 +0100 Subject: Adding nic handles to contact objects without one In-Reply-To: Your message of Thu, 25 Feb 1999 18:09:25 +0100. <199902251709.SAA00968@x41.ripe.net> References: <199902251709.SAA00968@x41.ripe.net> Message-ID: <199902261454.PAA03104@x14.ripe.net> Hi Joao, I'd like to know what exactly are the advantages (and to whom) to adding a nic-hdl to person objects which don't already have one ? In some cases a person (without a nic-hdl) has their name referenced in other Db objects. This was before nic-hdls were mandatory. So if you add a nic-hdl to such a person's person object what can be done to those objects which reference his/her name ? There is no way of distinguishing the names referenced in the contact attributes of these objects since a similar name can refer to different people. Then you have the problem where these people created a new person object for themselves when nic-hdls became mandatory and left their old person object for dead. How will you overcome these old person objects ? Lots of questions which were not discussed at RIPE32. Regards, Eamonn McGuinness RIPE NCC Hostmaster In message <199902251709.SAA00968 at x41.ripe.net>you write: >Dear all, >during the last RIPE meeting, in Amsterdam, the database working group >discussed a proposal to automatically add NIC Handles to all person and role >objects in the RIPE Database that don't yet have one (new objects can't be >created without nic handles anymore). This proposal was supported by the >working group and it was agreed that it should be circulated to the mailing >lists to give people not attending a chance to provide input. > >This does not affect how other objects reference these person or role objects. >This is only intended to bring old objects into conformance with the current >object definitions and does not mean that data provided by the user will be >modified. >Only the nic handle attribute will be given a value when the object lacks one. >No other attributes will be touched. Objects which already have nic handles >will not be touched. >The nic handle is a tag conveying no information about the user or role >described in the object. It is an identifier for the object. > >This addition would make data more uniform and could be a benefit for everyone >. > >For more information on nic handles, please read RIPE 157 and RIPE 189 >available at http://www.ripe.net/docs > >Best regards, >Joao Damas >Database Group >RIPE NCC > > > From joao at ripe.net Fri Feb 26 17:09:02 1999 From: joao at ripe.net (Joao Luis Silva Damas) Date: Fri, 26 Feb 1999 17:09:02 +0100 Subject: Adding nic handles to contact objects without one In-Reply-To: Your message of Fri, 26 Feb 1999 15:54:25 +0100. <199902261454.PAA03104@x14.ripe.net> References: <199902261454.PAA03104@x14.ripe.net> Message-ID: <199902261609.RAA03687@x41.ripe.net> Hello, "Eamonn" writes: * * Hi Joao, * * I'd like to know what exactly are the advantages (and to whom) to * adding a nic-hdl to person objects which don't already have one ? * I think there are benefits for everyone. The database becomes more coherent, ambiguity between different people with the same name disappears (especially if as you say below, references by name are then substituted by references to NIC Handles). * In some cases a person (without a nic-hdl) has their name referenced * in other Db objects. This was before nic-hdls were mandatory. So if * you add a nic-hdl to such a person's person object what can be done to * those objects which reference his/her name ? That, I think, is a discussion for these lists. Either the user does it or the RIPE NCC can do it if users wish to. Of course this can only be done for references by name corresponding to names that are unique in the database, otherwise we wouldn't know who to assign the object to and we shouldn't. * * There is no way of distinguishing the names referenced in the contact * attributes of these objects since a similar name can refer to * different people. * Indeed. * Then you have the problem where these people created a new person * object for themselves when nic-hdls became mandatory and left their * old person object for dead. How will you overcome these old person * objects ? * Yes, that happened in the past. The software can cope with that now so we shouldn't see cases like those any more. The cleanup I think is best done within the consistency project which is right now regaining speed (more on that soon...) Regards, Joao Damas RIPE NCC From stephenb at uk.uu.net Fri Feb 26 17:05:23 1999 From: stephenb at uk.uu.net (Stephen Burley) Date: Fri, 26 Feb 1999 16:05:23 -0000 (GMT) Subject: policy change: static verification methods In-Reply-To: Message-ID: On 26-Feb-99 Adam Morris wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > > On 25-Feb-99 Chris Arnold wrote: > > Hello > > > > Its not so much the virtual Web sites, they I agree can be run on a > > single IP server > > > > However > > When it comes to giving each individual customer FTP > > access to mange their site or have an FTP site in its own right > > IIS4 demands that you have unique IP's > > > > Unless of course someone knows a better method > > that is not an administrative nightmare. > > > > AFAIK there is no alternative. FTP cannot distinguish between a request for > one domain or another based on the contents of the protocol. There are two > alternatives here... either we rewrite the protocol to send the hostname as > part of the address or you give static IP addresses to all of your ftp > sites. > > Adam > Surley you can assign a root directory based on an account/password sequence (like you can with most UNIX versions of FTP), I have accounts on machines which only allow me access to certains parts or file system. Is this another rewrite of the protocol by that large software vendor. > > - ---------------------------------- > If this message isn't signed, it probably isn't me. > Adam Morris - Systems Engineer - Onyx Internet > > If you just try long enough and hard enough, you can always manage to > boot yourself in the posterior. > -- A. J. Liebling > > - ---------------------------------- > > -----BEGIN PGP SIGNATURE----- > Version: 2.6.3ia > Charset: noconv > > iQCVAwUBNtZ+QjxztoTO1QFNAQEfWQP+NcjkSHZtEA/UNRRHgggefjF89gkJO6fP > MAODN7D76mmnKnmLkBbpf+z5FIxjyqaYFRhLz0uLeiWNgQ+9GX+obVwAY4gG37dq > r+PZDtQEulaTAsSZgbWY9aVx5OkVsvNisKoAAqZZhFJcOGclhXA7q0Q7w8v/t9i7 > qwkucpqVj7E= > =pwMP > -----END PGP SIGNATURE----- > ---------------------------------- Stephen Burley Senior Hostmaster for UUNET Date: 26-Feb-99 Time: 16:02:09 http://www.uk.uu.net ---------------------------------- An MCI WorldCom Company From lmb at teuto.net Fri Feb 26 17:06:04 1999 From: lmb at teuto.net (Lars Marowsky-Bree) Date: Fri, 26 Feb 1999 17:06:04 +0100 Subject: policy change: static verification methods In-Reply-To: ; from "Adam Morris" on 1999-02-26T10:58:10 References: <199902251246.MAA13343@mailsrv.hiway.co.uk> Message-ID: <19990226170604.A4766@pointer.teuto.de> On 1999-02-26T10:58:10, Adam Morris said: > AFAIK there is no alternative. FTP cannot distinguish between a request for > one domain or another based on the contents of the protocol. There are two > alternatives here... either we rewrite the protocol to send the hostname as > part of the address or you give static IP addresses to all of your ftp sites. Or embed the host identifier in the path. Nothings wrong with "look for our files at ftp://ftp.domain.com/domain/" is there? Sincerely, Lars Marowsky-Brie -- Lars Marowsky-Brie Network Management teuto.net Netzdienste GmbH - DPN Verbund-Partner From clive at demon.net Fri Feb 26 17:32:56 1999 From: clive at demon.net (Clive D.W. Feather) Date: Fri, 26 Feb 1999 16:32:56 +0000 Subject: policy change: static verification methods In-Reply-To: ; from Stephen Burley on Fri, Feb 26, 1999 at 04:05:23PM -0000 References: Message-ID: <19990226163256.D18702@demon.net> Stephen Burley said: >>> When it comes to giving each individual customer FTP >>> access to mange their site or have an FTP site in its own right >>> IIS4 demands that you have unique IP's >> AFAIK there is no alternative. FTP cannot distinguish between a request for >> one domain or another based on the contents of the protocol. > Surley you can assign a root directory based on an account/password sequence > (like you can with most UNIX versions of FTP) Yes, but they aren't separate sites. If you want to offer anonymous FTP to each site under its own name, they need separate IP addresses. -- Clive D.W. Feather | Work: | Tel: +44 181 371 1138 Director of | Home: | Fax: +44 181 371 1037 Software Development | WWW: http://www.davros.org | Mobile: +44 973 377646 Demon Internet Ltd. | From Adam.Morris at onyx.net Fri Feb 26 17:55:33 1999 From: Adam.Morris at onyx.net (Adam Morris) Date: Fri, 26 Feb 1999 16:55:33 -0000 (GMT) Subject: policy change: static verification methods In-Reply-To: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- On 26-Feb-99 Stephen Burley wrote: >> > Surley you can assign a root directory based on an account/password sequence > (like you can with most UNIX versions of FTP), I have accounts on machines > which only allow me access to certains parts or file system. Is this another > rewrite of the protocol by that large software vendor. > > > No... I was thinking about anonymous FTP sites... (I want a web site and an ftp site www.domainname.co.uk and ftp.domainname.co.uk) Yes, if it is private access only then there is nothing wrong with saying just ftp to www.yourdomainname.co.uk and login with the following username and password. Now hopefully people will understand why I said what I said... :-) Adam - ---------------------------------- If this message isn't signed, it probably isn't me. Adam Morris - Systems Engineer - Onyx Internet He looked at me as if I was a side dish he hadn't ordered. - ---------------------------------- -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQCVAwUBNtbSBTxztoTO1QFNAQHG+wP9F+8yJPsw1YVpP+OBmwcnHukbBD5V1JO0 1I5mSl1XvZZ8rzWb/GHYm3/OGTrMmYzFum0x6Mb81f0lJs3BJsrELR2Qt8iSmI9Y 8UTgTBZ7a0jVQ+BVsr4ZCawtzOdgmN1rUSxz/PRoFwJkGVFlc30etVZcAbR31TYk nSJx0zvcu0w= =2eO2 -----END PGP SIGNATURE----- From jhma at EU.net Fri Feb 26 19:56:38 1999 From: jhma at EU.net (James Aldridge) Date: Fri, 26 Feb 1999 19:56:38 +0100 Subject: Poul-Henning's statistics (was: lowering maximum assignment window) In-Reply-To: Your message of "Wed, 24 Feb 1999 12:06:28 +0100." <28791.919854388@critter.freebsd.dk> Message-ID: <199902261856.TAA21769@aegir.EU.net> Poul-Henning Kamp wrote: > In message <199902241048.LAA07700 at x30.ripe.net>, Paula Caslav writes: > > Would it be an idea to go throught he database for all "ALLOCATED" > objects not maintained by RIPE and change them to ASSIGNED and then > have the database software reject such records in the future ? > > >A registry can only make > >assignments, therefore it should say "ASSIGNED" only the RIPE NCC can > >make allocations. I think this will be the cause of many of the > >inconsistencies on the list. If you have an inconsistency like this, > >please change the status attribute to say ASSIGNED instead of ALLOCATED. Personally I think that LIRs *should* be allowed to give objects a status of "ALLOCATED" in some circumstances. Imagine, if you can, your typical supernational registry which gets multiple address blocks allocated by the NCC for redistribution amongst the LIR's 20 or or more associated organisations. Here a lower level "ALLOCATED" inetnum could be used to keep track of this redistribution (if only the NCC's auditing tools didn't automatically assume that these - carefully labelled - allocations were duplicate assignments. Another possible use for LIR "ALLOCATED" inetnum objects would be to keep track of where a range of addresses was being used for assignments to VSE customers connected at a particular point of presence. ... just my thoughts from several years of running a large supernational registry and currently being in the middle of a lengthy registry audit by the RIPE NCC... ;-) James ----- ___ - James Aldridge, Senior Network Engineer, ---- / / / ___ ____ _/_ -- EUnet Communications Services BV --- /--- / / / / /___/ / --- Singel 540, 1017 AZ Amsterdam, NL -- /___ /___/ / / /___ /_ ---- Tel: +31 20 530 5327; Fax: +31 20 622 4657 - ----- 24hr emergency number: +31 20 421 0865 From mlelstv at xlink.net Fri Feb 26 22:43:08 1999 From: mlelstv at xlink.net (Michael van Elst) Date: Fri, 26 Feb 1999 22:43:08 +0100 Subject: Poul-Henning's statistics (was: lowering maximum assignment window) In-Reply-To: <199902261856.TAA21769@aegir.EU.net>; from James Aldridge on Fri, Feb 26, 1999 at 07:56:38PM +0100 References: <28791.919854388@critter.freebsd.dk> <199902261856.TAA21769@aegir.EU.net> Message-ID: <19990226224308.A28193@xlink.net> On Fri, Feb 26, 1999 at 07:56:38PM +0100, James Aldridge wrote: > Another possible use for LIR "ALLOCATED" inetnum objects would be to keep > track of where a range of addresses was being used for assignments to VSE > customers connected at a particular point of presence. *chuckle* We tried to explain this kind of usage to the NCC about two years ago. No chance. Now we just keep such objects in an internal database and carefully screen them out when updating the RIPE database. Greetings, -- i.A. Michael van Elst / phone: +49 721 6635 330 Xlink - Network Information Centre \/ fax: +49 721 6635 349 Vincenz-Priessnitz-Str. 3 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster at xlink.net [ Xlink Internet Consulting GmbH, Sitz Koeln ] [ Amtsgericht Koeln HRB 3526, Geschaeftsfuehrer: Michael Rotert ]