June 2000 - lir-wg - mailman.ripe.net

Re: RIPE NCC CIDR blocks - smallest allocations
by Joao Luis Silva Damas 21 Jun '00

21 Jun '00

Ehem... Who said copy and paste was something useful... At 14:27 +0200 20/6/00, Joao Luis Silva Damas wrote: >During the RIPE 36 meeting in Budapest there was a request to >publish the list of CIDR blocks allocated by the RIPE NCC and the >smallest allocation issued from each of them. > >This is it. > >62/8: /19 >193/8: /29 # Contain small PI assignments >193/8: /29 # Contain small PI assignments >193/8: /29 # Contain small PI assignments the last 2 should read 194/8: /29 # Contain small PI assignments 195/8: /29 # Contain small PI assignments >212/8: /19 >213/8: /19 >217/8: /20 > >If this is what people are looking for, we will add it to our >ftp/website as a permanent resource. > >regards, > >Joao Damas >Head of External Services >RIPE NCC Joao

2 1

RIPE NCC CIDR blocks - smallest allocations
by Joao Luis Silva Damas 20 Jun '00

20 Jun '00

During the RIPE 36 meeting in Budapest there was a request to publish the list of CIDR blocks allocated by the RIPE NCC and the smallest allocation issued from each of them. This is it. 62/8: /19 193/8: /29 # Contain small PI assignments 193/8: /29 # Contain small PI assignments 193/8: /29 # Contain small PI assignments 212/8: /19 213/8: /19 217/8: /20 If this is what people are looking for, we will add it to our ftp/website as a permanent resource. regards, Joao Damas Head of External Services RIPE NCC

1 0

RIPE NCC ADDRESS POLICY CHANGES
by Joao Luis Silva Damas 20 Jun '00

20 Jun '00

*** CHANGES IN RIPE NCC ADDRESS POLICY *** During the RIPE 36 meeting in Budapest (16-19 May 2000) the LIR working group agreed that the RIPE NCC will: - lower the minimum allocation from a /19 to a /20. - this change will take effect starting August 1 Allocations of this size will initially be issued from CIDR block 217/8. Minimum allocations do not constrain requests for address space that can justify bigger blocks of addresses. ** If you use prefix based filtering in your routers, please note this change ** regards, Joao Damas Head of External Services RIPE NCC

1 0

(Message resent) Registration Services status update
by Nurani Nimpuno 16 Jun '00

16 Jun '00

* Apologies for the formatting of previous message. Dear Colleagues, As reported at the RIPE 36 meeting in Budapest, the RIPE NCC has been going through a difficult period with an ever increasing workload over the last year. As a direct result of this the response time for IP Address requests has increased to longer than what is normally considered acceptable. At RIPE 36 the RIPE NCC reported several short, medium and long-term actions in order to improve the Registration Services. Increasing the resources in the Registration Services, improving efficiency, further automation of processes, increasing the level of expertise and strengthening staff's technical awareness are concrete examples of actions we reported to initiate on both a short and long-term basis. As a short term measure we temporarily increased the staffing level in the Registration Services dramatically by utilising resources drawn throughout the organisation. It was clear that this action had a positive effect on the wait queue which rapidly decreased to a couple of days. As you may have noticed the wait queue has again increased over the last couple of weeks. We are in the process applying the actions mentioned above and are also hiring new staff to cope with the considerable workload. However, it will take quite some time before the new hostmasters are trained and working efficiently. In addition to hiring new staff we are continuing to use the resources in the organisation in a more flexible and efficient manner. We have also asked our colleagues at APNIC for additional resources that they have very kindly agreed to provide. The RIPE NCC will thus have two APNIC hostmasters for a short period this summer who will contribute to the processing of IP Address requests. This will help reduce the current workload while we continue to realise our long-term improvement goals. I intend to further discuss these goals with the May 17 Task Force set up at RIPE 36 and look forward to any input they may have. Please rest assured that we are doing our utmost to reduce the current wait queue and that we are determined to improve the quality of service in the Registration Services. Kind regards, Nurani Nimpuno Registration Services Manager RIPE NCC

1 0

Registration Services status update
by Nurani Nimpuno 16 Jun '00

16 Jun '00

Dear Colleagues, As reported at the RIPE 36 meeting in Budapest, the RIPE NCC has been going through a difficult period with an ever increasing workload over the last year. As a direct result of this the response time for IP Address requests has increased to longer than what is normally considered acceptable. At RIPE 36 the RIPE NCC reported several short, medium and long-term actions in order to improve the Registration Services. Increasing the resources in the Registration Services, improving efficiency, further automation of processes, increasing the level of expertise and strengthening staff's technical awareness are concrete examples of actions we reported to initiate on both a short and long-term basis. As a short term measure we temporarily increased the staffing level in the Registration Services dramatically by utilising resources drawn throughout the organisation. It was clear that this action had a positive effect on the wait queue which rapidly decreased to a couple of days. As you may have noticed the wait queue has again increased over the last couple of weeks. We are in the process applying the actions mentioned above and are also hiring new staff to cope with the considerable workload. However, it will take quite some time before the new hostmasters are trained and working efficiently. In addition to hiring new staff we are continuing to use the resources in the organisation in a more flexible and efficient manner. We have also asked our colleagues at APNIC for additional resources that they have very kindly agreed to provide. The RIPE NCC will thus have two APNIC hostmasters for a short period this summer who will contribute to the processing of IP Address requests. This will help reduce the current workload while we continue to realise our long-term improvement goals. I intend to further discuss these goals with the May 17 Task Force set up at RIPE 36 and look forward to any input they may have! Please rest assured that we are doing our utmost to reduce the current wait queue and that we are determined to improve the quality of service in the Registration Services. Kind regards, Nurani Nimpuno Registration Services Manager RIPE NCC

1 0

RE: Privacy issues with RIPE Database
by Wilfried Woeber, UniVie/ACOnet 13 Jun '00

13 Jun '00

Dear Jules, >Date: Tue, 06 Jun 2000 12:40:55 +0100 >From: Jules Desforges <jules(a)vas-net.net> >To: lir-wg(a)ripe.net >Subject: Privacy issues with RIPE Database > >Hi, > >I would like to bring an issue to your attention, >which has caused VAS-NET some commercial harm. > >VAS-NET have been a local registry for over 3 years now. >VAS-NET are also an active member of RIPE, we usually >send delegates to participate in RIPE meetings, and we >make sure our staff are properly trained in RIPE procedures. > >We always endeavor to keep our entries in the RIPE database >up to date. I'm now finding that our diligence in keeping >the RIPE database up to date, is working in our detriment. > >We are finding that other companies who are in competition with >us, are using the RIPE database as a tool to extract a list >of our customer base and hence canvass our customers with marketing >information. I do not wish to make allegations or name the parties ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >involved, but we have witnessed this three times in the last 6 months. ^^^^^^^^^ This is one of our problems, i.e. most people "hit" by others' non-conformance to rules or copyright shy away from following up. My feeling is that nothing is going to change for the better, unless we, as a community, and individual parties start to have those rules *enforced*. Doing so a couple of times and indeed going public with the action is going to change the "public perception" of the problem. >The Ripe Database is the only publicly accessible source which >contains a list of our clients. I do not feel that these companies >could have gleaned this information from any other source. The >evidence is even more compelling when all of the mail shots have been >sent to the admin contacts listed in the RIPE database. > >As a company, VAS-NET endorse RIPE's open policy concerning IP >Registrations. In the past we've always had issues with other registries >for not containing information which is important for peering decisions. >(especially the American registries). > >I suppose the biggest problem, is finding a way of safeguarding our >customers from being targeted in this way. A solution to this problem, >doesn't seem likely with the way the RIPE NCC procedures are laid down >at the moment. But, I would appreciate any input from yourselves >regarding this matter. > >Best Regards, > >Jules Desforges >VAS-NET > Best regards, Wilfried. _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Competition Time
by Matthew Robinson 13 Jun '00

13 Jun '00

As announced at the RIPE meeting in Hungary we have decided to hold a small competition to design a new logo for the Test Traffic Project. This is for companies who are participating in the project to place on web sites, in brochures etc. We are also looking for a new name for the TT project when it becomes a pay service. The competition is split into two sections: 1. The logo 2. A new name for the TT project. There will be prizes. Winners will be decided by voting in the working group session. Entries should be submitted to me no later than the 1st of September. These will then be available on the web for viewing. Kind regards Matthew

1 0

Re: Privacy issues with RIPE Database
by Nigel Titley 06 Jun '00

06 Jun '00

> We are finding that other companies who are in competition with > us, are using the RIPE database as a tool to extract a list > of our customer base and hence canvass our customers with marketing > information. I do not wish to make allegations or name the parties > involved, but we have witnessed this three times in the last 6 months. If you've got proof of this (or even reasonable suspicion) then inform the RIPE-NCC immediately. The information in the database is copyright and only to be used for operational purposes. The RIPE-NCC will follow this up with the member concerned. Nigel -- Tel: +44 171 864 4450 Fax: +44 171 864 4488 Well I'm disenchanted too. We're all disenchanted (James Thurber) (http://www.seanet.com/~thurber/disenchanted.gif)

1 0

Privacy issues with RIPE Database
by Jules Desforges 06 Jun '00

06 Jun '00

Hi, I would like to bring an issue to your attention, which has caused VAS-NET some commercial harm. VAS-NET have been a local registry for over 3 years now. VAS-NET are also an active member of RIPE, we usually send delegates to participate in RIPE meetings, and we make sure our staff are properly trained in RIPE procedures. We always endeavor to keep our entries in the RIPE database up to date. I'm now finding that our diligence in keeping the RIPE database up to date, is working in our detriment. We are finding that other companies who are in competition with us, are using the RIPE database as a tool to extract a list of our customer base and hence canvass our customers with marketing information. I do not wish to make allegations or name the parties involved, but we have witnessed this three times in the last 6 months. The Ripe Database is the only publicly accessible source which contains a list of our clients. I do not feel that these companies could have gleaned this information from any other source. The evidence is even more compelling when all of the mail shots have been sent to the admin contacts listed in the RIPE database. As a company, VAS-NET endorse RIPE's open policy concerning IP Registrations. In the past we've always had issues with other registries for not containing information which is important for peering decisions. (especially the American registries). I suppose the biggest problem, is finding a way of safeguarding our customers from being targeted in this way. A solution to this problem, doesn't seem likely with the way the RIPE NCC procedures are laid down at the moment. But, I would appreciate any input from yourselves regarding this matter. Best Regards, Jules Desforges VAS-NET

1 0

RE: "ownership" on ancient network assignments?
by Pascal Gloor 02 Jun '00

02 Jun '00

Hi, Perhaps the best way is to split it in two /17 or 3 /18 and 1 /18 no ? (depending of the need of each ... ) Or on of the two should perhaps ask for a new assignement ... Any other suggestions ? Or perhaps get the /16 by playing a chess game ? :-P Cheers, Pascal Gloor Network Manager (AS6893) __________________________ SPAN(tm) / Petrel Communications SA A Cable & Wireless company Phone : +41 22 304 47 47 Fax : +41 22 304 47 99 Direct : +41 22 304 47 82 Mobile : +41 79 346 00 26 E-mail : <pgl(a)cw.span.ch> Web : <http://www.span.ch> > -----Original Message----- > From: Alexander Bochmann [SMTP:bochmann@freinet.de] > Sent: Wednesday, May 31, 2000 4:54 PM > To: lir-wg(a)ripe.net > Subject: "ownership" on ancient network assignments? > > Hi, > > we are currently noticing a dispute of two companies over a > /16 address range assigned to a predecessor of both of them > in 1991 (the original company was split some time ago). > > We're not a party in this quarrel, but I'm curious about the > status of a network that was assigned such a (comparatively) > long time ago. Can someone claim to be legally entitled to own > this IP address range? What is likely to happen? > > A. Bochmann > > -- > FreiNet Gesellschaft fuer Informationsdienste mbH > Loerracher Strasse 5a D79115 Freiburg

2 1