- lir-wg - mailman.ripe.net

Re: New Status of Last Resort Registries
by miguel.sanz＠rediris.es 17 Jan '96

17 Jan '96

On Jan 4, 10:08, RIPE NCC Hostmaster wrote: > Subject: New Status of Last Resort Registries > Dear hostmaster, I don't see any reference in the letter to in-addr.arpa delegation being passed from Last Resort Registries to RIPE NCC. It should be included and also the procedure for this transfer (for instance, copy of the primary servers files). Regards, Miguel A. Sanz +---------------------------------------------------------------+ | ES-NIC (Delegated Internet Registry for Spain) | | Centro de Comunicaciones CSIC RedIRIS | | Serrano 142 Tel: + 34 1 5855150 | | 28006 Madrid Fax: + 34 1 5855146 | | SPAIN Email: nic(a)rediris.es | +---------------------------------------------------------------+ > Dear Colleagues, > > Seasons Greeting and the best wishes for the New Year from all of the > RIPE NCC. > > As announced earlier the status of the Last Resort Registries will > change from 1996 on. > > We appologise for not sending this message earlier. We kindly ask you > to respond as soon as possible. Our target to have these matter > resolved is the beginning of February, right after the next RIPE > Meeting. > > The NCC Contributors Comittee decided during the last meeting in > September that all Local IRs need to contribute to the RIPE NCC to > receive registration service. > > This has implications for the Local IRs that currently run a Registry > of Last Resort. There are two possiblities for these LIR's: > > 1. Contribution to the RIPE NCC > 2. Closure of the Last Resort Registry > > In order to facilitate aggregation of routing information and therefor > a stable Internet routing the closure of the Last Resort Registries is > the preferred solution. > > If the first possibility is chosen, the size of the registry needs to > be determined and an "Agreement on the provision and use of the RIPE > NCC services" needs to be signed and send to the RIPE NCC. For more > details please refer to > > ftp://ftp.ripe.net/ripe/new-registry > > or contact <billing(a)ripe.net>. > > If the Last Resort Registry will be closed, please read and edit the > following form letter and send it back to <hostmaster(a)ripe.net> > > The closure of a LIR can only be effective after the issues below are > resolved. > > If you plan to continue the Last Resort Registration Service, please > notify us before January 15th. Otherwise your registry will receive no > service. > > In case you run two registries a Last Resort Registry and a Provider > Registry, please note, that the operation of the Provider Registry is > not effected by this matter. > > Kind regards, > > Mirjam Kuehne > RIPE NCC > > > ---------------------------------------------------------------------- > > Dear colleagues, > > We formally request to close the local Internet Registry operated by > XXXXX-Organisation under registry ID xxx.zz effective at <date>. > > We enclose a final summary of all address space assigned by and > through our registry as enclosure A. > > We also enclose a list of all address space allocated (delegated) to > our registry but not yet assigned as enclosure B. We understand that > we are not allowed to make any further assignments from this address > space after the closure and that this address space can be > re-allocated and re-assigned by the RIPE NCC as necessary. > > We will guarantee that the RIPE NCC can at any time access all records > concerning customers's requests for address space as per the "IP > Address Space Assignment Procedures" (ripe-104): "IRs will keep > records of correspondence and information exchanges in conjunction > with the registry function for later review and the resolution of > disputes. IRs will hold this information in strict confidence and use > it only to review requests and in audit procedures or to resolve > disputes." > > If access can not or will no longer be guaranteed, we will transfer > the records to the RIPE NCC after prior agreement on the procedure. > > The RIPE NCC will hold this information in strict confidence and use > it only to review requests, audit procedures or to resolve disputes. > > Currently ongoing requests for IP address space will either be > finished before closing the registry or the requester will be referred > to the list of local Internet registries that can be found at > > ftp://ftp.ripe.net/ripe/registries/ > > after he/she has been informed about the issues related with PA/PI > address space outlined in ripe-127. > > We understand that the closure of our registry has the following > consequences: > > - The registy entry xxx.zz will be removed from the directory > of Local Internet Registries (ftp://ftp.ripe.net/ripe/registries/) > > - The e-mail addresses registered for registry xxx.zz will be removed > from the mailing lists ip-provs(a)ripe.net, ncc-co(a)ripe.net and > local-ir(a)ripe.net automatically. Note that it is possible to > re-subscribe to local-ir(a)ripe.net on an individual basis. > > - All registry requests from XXX-Organisation directly to the RIPE NCC > will henceforth be treated as requests from an individual and will > not receive registration service unless they are channeled through > another local IR. > > We understand and agree to the above. > > For the xxx.zz registry operated by XXX-Organisation > > <signature of xxx.zz administrative contact(s)> > > > > Enclosure A: > > EXAMPLE EXAMPLE EXAMPLE > > ------- Allocation record ----------- > > 193.0.0.0 - 193.0.255.255 > ----------------------------------------------------------------- > > > 193.0.0.0 - 193.0.1.255 1-Dec-94 Internal Infrastructure > 193.0.2.0 - 193.0.2.127 1-Dec-94 ABC Organisation > 193.0.2.128 - 193.0.2.255 1-Dec-94 ABC Organisation Int. > 193.0.3.0 - 193.0.3.255 2-Dec-94 XYC-Organisation > 193.0.4.0 - 193.0.7.255 11-Dec-94 AB Network Inc. > 193.0.8.0 - 193.0.15.255 11-Dec-94 XY Net-Institute > ... > > > > Enclosure B: > > EXAMPLE EXAMPLE EXAMPLE > > Non-assigned IP addresses: > ----------------------------------------------------------------- > > 193.0.104.0 - 193.0.127.255 > 193.0.160.0 - 193.0.168.255 > > 193.0.213.0 - 193.0.213.255 > 193.0.216.0 - 193.0.216.255 > 193.0.221.0 - 193.0.221.255 > 193.0.244.0 - 193.0.244.255 > 193.0.245.0 - 193.0.245.255 > > >-- End of excerpt from RIPE NCC Hostmaster

2 1

NCC#963329 Re: New Status of Last Resort Registries
by RIPE NCC Acknowledgements 17 Jan '96

17 Jan '96

Dear "Miguel A. Sanz. RedIRIS/CSIC", ------------------------------------------------------------------- Your message From: miguel.sanz(a)rediris.es (Miguel A. Sanz. RedIRIS/CSIC) Date: Tue, 16 Jan 1996 19:22:33 +0100 Message-ID: <9601161922.ZM13693(a)rediris.es> Subject: Re: New Status of Last Resort Registries has been received at the RIPE NCC. We have extracted the following information from it: NCC Ticket Number: Your Registry ID: ------------------------------------------------------------------- This message concerns a n e w request which we will process under ticket number NCC#963329. Your message did not specify a registry ID for this request. We have determined manually that the correct registry ID is es.zz. This has lead to some delay and some unnecessary work. Please include your registry ID in your requests by adding a X-NCC-RegID: <regid> line in the header or near the beginning of the body of your message. Putting the registry ID in the subject line is not sufficient because our automated procedures will not be able to determine them reliably. The request will be processed for registry es.zz. The service level for registry es.zz is 'normal'. The process will be processed normally. Please make sure that you specify the ticket number in all correspondence regarding this particular request and this particular request only. See ripe-183 for details about ticketising and request tracking. With kind regards The RIPE NCC Hostmaster Team ------------------------------------------------------------------- The body text of your message started as follows: On Jan 4, 10:08, RIPE NCC Hostmaster wrote: > Subject: New Status of Last Resort Registries > Dear hostmaster, I don't see any reference in the letter to in-addr.arpa delegation being passed from Last Resort Registries to RIPE NCC. It should be included and also the procedure for this transfer (for instance, copy of the primary servers files). Regards, Miguel A. Sanz +---------------------------------------------------------------+ | ES-NIC (Delegated Internet Registry for Spain) | | Centro de Comunicaciones CSIC RedIRIS | | Serrano 142 Tel: + 34 1 5855150 | | 28006 Madrid Fax: + 34 1 5855146 | | SPAIN Email: nic(a)rediris.es | +---------------------------------------------------------------+ > Dear Colleagues, > > Seasons Greeting and the best wishes for the New Year from all of the > RIPE NCC. > > As announced earlier the status of the Last Resort Registries will > change from 1996 on. > > We appologise for not sending this message earlier. We kindly ask you > to respond as soon as possible. Our target to have these matter > resolved is the beginning of February, right after the next RIPE > Meeting. > > The NCC Contributors Comittee decided during the last meeting in > September that all Local IRs need to contribute to the RIPE NCC to > receive registration service. > > This has implications for the Local IRs that currently run a Registry > of Last Resort. There are two possiblities for these LIR's: > > 1. Contribution to the RIPE NCC > 2. Closure of the Last Resort Registry > > In order to facilitate aggregation of routing information and therefor > a stable Internet routing the closure of the Last Resort Registries is > the preferred solution. > > If the first possibility is chosen, the size of the registry needs to > be determined and an "Agreement on the provision and use of the RIPE > NCC services" needs to be signed and s

1 0

Developments at the RIPE NCC
by Daniel Karrenberg 15 Jan '96

15 Jan '96

Dear customers and colleagues, once again it is time for one of my (ir)regular messages about the latest developments at the RIPE NCC. I hope it is one of the last ones serving as an informal report as we plan to start the formal quarterly reports again soon. See below for more details. European Internet ----------------- During 1995 the European Internet has roughly doubled in terms of DNS registered hosts as you can see from the excerpt of the RIPE NCC hostcount below. The number of hosts at the end of December 1995 is 2.14 times larger than the number at the end of December 1994. These are exciting times! For details see ftp://ftp.ripe.net/ripe/hostcount/. Count Delta Delta % Q Delta Q Delta % ------------------------------------------------------------------- Dec 1994 1029270 + 56170 + 5.8% +140872 +15.9% Jan 1995 1106077 + 76780 + 7.5% Feb 1995 1197911 + 91807 + 8.3% Mar 1995 1326078 +128116 + 10.7% +296703 +28.8% Apr 1995 1375921 + 49805 + 3.7% May 1995 1463816 + 87896 + 6.4% Jun 1995 1550520 + 87287 + 5.9% +224988 +16.9% Jul 1995 1694978 +144472 + 9.3% Aug 1995 1773680 + 79205 + 4.7% Sep 1995 1830389 + 56709 + 3.2% +280386 +18.1% Oct 1995 1928380 + 97991 + 5.4% Nov 1995 1999997 + 71617 + 3.7% Dec 1995 2206360 +199419 + 10.0% +369027 +20.2% Local Registries ---------------- The number of local registries has also roughly doubled in 1995; there are 2.18 times more registries than last year: Q4 Q1 Q2 Q3 Q4 Projected 1994 1995 1995 1995 1995 1995 Large ISP 17 17 19 25 28 22 Medium ISP 28 31 35 36 40 42 Small ISP 51 84 119 159 196 188 Enterprise 14 15 17 15 16 20 Last Resort 31 32 32 30 28 32 TOTAL 141 179 222 265 308 304 It is remarkable that the growth of the number of registries so closely follows the growth of the net as measured by the hostcount. From these measures one cannot deduce concentration tendencies in Internet service provision. We are also quite satisfied that the actual numbers are quite close to the predictions we made in Q2 of the year. This gives us some confidence in our planning. For the NCC staff, as for anyone else in the Internet business, this growth has meant a tremendous amount of work, not least in training and integrating new colleagues and working with all those new customers. Luckily the financial position of the NCC has also become much more stable than at this time last year; this provides sufficient material resources to cope with the growth. While final figures for 1995 are not available yet, we expect to close the year with financial reserves which provide a good basis for NCC operations in the foreseeable future. In December last year we have issued invoices for 1996 fees to all established registries. We have been pleasantly surprised by the considerable amounts we have already received. Thank you to those of you paying in time. Will the others please follow that example. ;-) Registration Services --------------------- The junior hostmasters who started in the second half of 1995 are now fully up-to-speed in handling requests. Ticketing and the first manual implementation of work flow management are paying off. In the beginning of December we succeeded to eliminate the permanent queue of requests not yet assigned to a hostmaster which had been in operation since early in the year. Customers started to make pleasant remarks about the turn-around time of requests again. This was a major milestone for registration services. We are using this breathing space to further train the registration services staff, to convert some manually kept internal databases to machine processable format and to introduce the automated work flow management system. The latter changes should be fully transparent to the customers while the former should enable each hostmaster to take more personal responsibilities for allocation and assignment decisions. Because the number of people and resources used by registration services are substantial we have decided to make a start at changing the flat organisational structure of the NCC in this area. From January 1st this year Mirjam Kuehne has been appointed "Manager Registration Services". Mirjam is responsible for day to day operations in this area with all registration services staff reporting to her. Other Activities ---------------- A beta release of the database software has been produced. It includes code for running secondary (shadow) databases in almost real time as well as other improvements. Several local IR training courses have been presented and were received well. The RIPE NCC information servers are getting a total overhaul in a project executed by the school for communications systems of Utrecht university. Very little of that is visible at this point but much work is being done behind the scenes. If you would like to influence the work, consider completing the survey at http://www.ripe.net/ripe/usurv.html. In conjunction with this project address space assignment and allocation procedures are being re-written at this point in order to provide up to date documentation to local registries in a single document. An editing committee recruited from the local-IR working group is helping with this task. A draft is expected to appear shortly and will be discussed at the RIPE meeting. Behind the Scenes ----------------- The RIPE NCC computing infrastructure has seen a lot of necessary replacements as the original hardware is nearing the end of its useful life. We are in the process of re-implementing large parts of the workstation and server environments in order to keep up with changes at the NCC and in the Internet. The computer room servers have been moved to four large 19 inch racks which provides more room and improves reliability. New server hardware based on industrial PCs has been purchased and partially deployed. RAID systems are being tested. New Staff --------- After a long search the NCC finally has a business manager! The search has been longer and more difficult as expected even considering the current circumstances in the Internet world. Not so surprisingly two very promising candidates who had been offered the position decided to join Internet service providers at the last minute, one of them even at the last second. But all is well than ends well! Dr. Carol Orange has been appointed RIPE NCC business manager as of today and will be responsible for financial planning and control, general customer relations and the quarterly reports. Carol joins us from Utrecht university where she has led the abovementioned project to redesign the NCC's information servers. She will work part-time until the end of March when she will have completed long term commitments at Utrecht university. Carol who is originally from Portland Oregon has been living in Amsterdam since 1986. The list of her former employers includes Lucasfilm and CWI. She has been getting her fingers dirty with technical work in those positions and hopes to find an excuse to do that from time to time in the future. She has been teaching juggling to people working at the NCC campus since 1987. Also today Naomi de Bruyn joins the NCC as a full time secretary. Naomi will be our "receptionist" answering the phone and dealing with general messages to <ncc(a)ripe.net>. She will also be responsible for a number of internal administrative tasks and help with the organisation of meetings and courses. Naomi has previously worked for the TERENA secretariat on a temporary basis. Next Period ----------- During the first quarter of this year we plan to further consolidate registration services and finally begin starting other activities which have been dormant. We will also put effort into the development of alternative charging models and start to investigate areas where technical work by the NCC is needed. Finally we plan to present a real quarterly report for the first quarter sometime in April. All of us here at the RIPE NCC wish you a good and successful year. If you have any further questions, please do not hesitate to contact us. Regards Daniel Karrenberg RIPE NCC Manager

1 0

RIPE23: reminder
by RIPE NCC Staff 15 Jan '96

15 Jan '96

Dear people, This is a reminder that there will be a RIPE meeting soon. If you have missed the previous announcement and want to attend: please do not forget to register. You can find all relevant information at: ftp://ftp.ripe.net/ripe/Next-Meeting/ All further (and previous) discussion on the meeting will be held on the 'ripe-list' mailinglist. To subscribe, please send mail to <majordomo(a)ripe.net> with 'subscribe ripe-list' in the message body. The mailing list archives can be found at ftp://ftp.ripe.net/ripe/archives/ripe-list/ Appended below is the original announcement for the meeting, but without all the other documents that were appended. ------ R I P E meeting announcement ============================ (This announcement can also be viewed using "finger meeting(a)ncc.ripe.net") This is to announce that the 23rd RIPE meeting will take place: Dates: 29th January, 1996 start: 10:00 (*) 30th January, 1996 31st January, 1996 end: 15:30 (*) * times subject to change (may vary +/- 1 hour). For exact times, look at ftp://ftp.ripe.net/ripe/Next-Meeting/announcement shortly before the meeting Venue: CWI Kruislaan 413 1098 SJ Amsterdam The Netherlands Host: NIKHEF Registration: Please use the registration form (which will follow in a separate mail) to give notice of your coming as soon as possible. General meeting overview: ------------------------- - Before the working group meetings, on Monday 29th, there will be an EOF (European Operators Forum) meeting. The exact starting time will probably be known shortly before the RIPE meeting. It will end 12:30. - Monday 29th, 14:00-18:00 and Tuesday 30th, 09:00-12:30, there will be various RIPE working groups sessions. The schedule of the previous meeting follows below for reference; the schedule of this meeting is not known yet. - Tuesday 30th, 14:00-18:00 and Wednesday 31st, 09:00-15:30 (*), the plenary session will take place, with reports from the RIPE NCC, reports from the working group meetings and other presentations. General information: -------------------- Currency (checked 18 December 1995): 1 UK pound = Hfl 2.5 1 ECU = Hfl 2.1 1 US$ = Hfl 1.6 More information about Amsterdam: --------------------------------- Websurfers may take a look at: <> http://www.xxlink.nl/cities/amsterdam <> http://www.channels.nl/ Appended to this announcement: ------------------------------ <> directions to the meeting place Documents to follow (separate mail messages): --------------------------------------------- <> details of hotels in Amsterdam close to meeting venue <> registration form for attendance at the meeting <> getting visa for the meeting, if you need one ==================================================================

1 0

FYI: RIPE DB and Domain Names
by Daniel Karrenberg 15 Jan '96

15 Jan '96

------- Forwarded Message Date: Mon, 15 Jan 1996 10:23:15 +0100 From: Daniel Karrenberg <Daniel.Karrenberg(a)ripe.net> Sender: dfk(a)ripe.net To: Domain registration staff <hostmaster(a)sztaki.hu> cc: ripe-op(a)ripe.net Subject: Unauthorized modifications of RIPEDB > Domain registration staff <hostmaster(a)sztaki.hu> writes: > Dear NCC, > > > Last week the following new 219 domains appeared in RIPEDB. > I can't believe that all of European TLD administrators > registered this domains at the same time. Moreover with and without CO. There are two basic problems here: 1) Confusion about the role of the RIPE database in *domain names*. The database is not authoritative about domain names. It is just informational for these. The authoritative registry of domain names for TLDs is kept by TLD administrators. They are encouraged use the ripe database to make their registry accessible. This is *not* mandatory. 2) Lack of authorisation in the RIPE database for the *creation* of objects. As David Kessens has pointed out already we are working on this. Once this is implemented TLD administrators can control the creation of objects within their namespace. This is the top priority database development item at the moment. We are also working on a simple referral method so that TLD administrators can run their own whois services, as the NL TLD administrator does. Until these problems are solved the RIPE database can be nothing more than informational about TLDs. Oncve they are solved TLD administrators have the means to keep their data clean if they wish. Daniel ------- End of Forwarded Message

1 0

Re: RIPE23: outstanding action items
by Mike Norris 12 Jan '96

12 Jan '96

For info. Mike ------- Forwarded Message Return-Path: markk(a)internic.net Received: (markk@localhost) by slam.internic.net (8.7.3/SLAM-1) id KAA01025; Fri, 12 Jan 1996 10:37:03 -0500 (EST) From: Mark Kosters <markk(a)internic.net> Message-Id: <199601121537.KAA01025(a)slam.internic.net> Subject: Re: RIPE23: outstanding action items To: mnorris(a)dalkey.hea.ie (Mike Norris) Date: Fri, 12 Jan 1996 10:37:03 -0500 (EST) Cc: Roderik.Muit(a)ripe.net, ripe-list(a)ripe.net In-Reply-To: <9512220836.AA03744(a)dalkey.hea.ie> from "Mike Norris" at Dec 22, 95 08:36:15 am X-Mailer: ELM [version 2.4 PL24alpha4] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit rfc1466++ is now in draft - the rfc is to be out shortly. (ftp://ds.internic.net/internet-drafts/draft-hubbard-registry-guidelines-00.…) Regards, Mark > > > > Action 22.1 on Mike Norris and RIPE NCC > > To find volunteers from the Local IR working > > group to continue working on the revision of > > ripe-104++ without waiting for the publication > > of rfc1466++. > > Volunteers have been found, Daniel has drafted in some expertise > and an editorial group has been formed. The group met at the NCC > last week and continues its work of revising ripe-104 with a view > to circulating a document before RIPE 23. > > Cheers. > > Mike > > - -- Mark Kosters markk(a)internic.net +1 703 742 4795 Software Engineer InterNIC Registration Services ------- End of Forwarded Message

1 0

domain name registration
by saliba＠inco.com.lb 08 Jan '96

08 Jan '96

As an ISP, Is it possible to register a new domain (for a customer) having one IP address, knowing that that IP address belong to another domain? Regards

1 0

New Status of Last Resort Registries
by RIPE NCC Hostmaster 04 Jan '96

04 Jan '96

Dear Colleagues, Seasons Greeting and the best wishes for the New Year from all of the RIPE NCC. As announced earlier the status of the Last Resort Registries will change from 1996 on. We appologise for not sending this message earlier. We kindly ask you to respond as soon as possible. Our target to have these matter resolved is the beginning of February, right after the next RIPE Meeting. The NCC Contributors Comittee decided during the last meeting in September that all Local IRs need to contribute to the RIPE NCC to receive registration service. This has implications for the Local IRs that currently run a Registry of Last Resort. There are two possiblities for these LIR's: 1. Contribution to the RIPE NCC 2. Closure of the Last Resort Registry In order to facilitate aggregation of routing information and therefor a stable Internet routing the closure of the Last Resort Registries is the preferred solution. If the first possibility is chosen, the size of the registry needs to be determined and an "Agreement on the provision and use of the RIPE NCC services" needs to be signed and send to the RIPE NCC. For more details please refer to ftp://ftp.ripe.net/ripe/new-registry or contact <billing(a)ripe.net>. If the Last Resort Registry will be closed, please read and edit the following form letter and send it back to <hostmaster(a)ripe.net> The closure of a LIR can only be effective after the issues below are resolved. If you plan to continue the Last Resort Registration Service, please notify us before January 15th. Otherwise your registry will receive no service. In case you run two registries a Last Resort Registry and a Provider Registry, please note, that the operation of the Provider Registry is not effected by this matter. Kind regards, Mirjam Kuehne RIPE NCC ---------------------------------------------------------------------- Dear colleagues, We formally request to close the local Internet Registry operated by XXXXX-Organisation under registry ID xxx.zz effective at <date>. We enclose a final summary of all address space assigned by and through our registry as enclosure A. We also enclose a list of all address space allocated (delegated) to our registry but not yet assigned as enclosure B. We understand that we are not allowed to make any further assignments from this address space after the closure and that this address space can be re-allocated and re-assigned by the RIPE NCC as necessary. We will guarantee that the RIPE NCC can at any time access all records concerning customers's requests for address space as per the "IP Address Space Assignment Procedures" (ripe-104): "IRs will keep records of correspondence and information exchanges in conjunction with the registry function for later review and the resolution of disputes. IRs will hold this information in strict confidence and use it only to review requests and in audit procedures or to resolve disputes." If access can not or will no longer be guaranteed, we will transfer the records to the RIPE NCC after prior agreement on the procedure. The RIPE NCC will hold this information in strict confidence and use it only to review requests, audit procedures or to resolve disputes. Currently ongoing requests for IP address space will either be finished before closing the registry or the requester will be referred to the list of local Internet registries that can be found at ftp://ftp.ripe.net/ripe/registries/ after he/she has been informed about the issues related with PA/PI address space outlined in ripe-127. We understand that the closure of our registry has the following consequences: - The registy entry xxx.zz will be removed from the directory of Local Internet Registries (ftp://ftp.ripe.net/ripe/registries/) - The e-mail addresses registered for registry xxx.zz will be removed from the mailing lists ip-provs(a)ripe.net, ncc-co(a)ripe.net and local-ir(a)ripe.net automatically. Note that it is possible to re-subscribe to local-ir(a)ripe.net on an individual basis. - All registry requests from XXX-Organisation directly to the RIPE NCC will henceforth be treated as requests from an individual and will not receive registration service unless they are channeled through another local IR. We understand and agree to the above. For the xxx.zz registry operated by XXX-Organisation <signature of xxx.zz administrative contact(s)> Enclosure A: EXAMPLE EXAMPLE EXAMPLE ------- Allocation record ----------- 193.0.0.0 - 193.0.255.255 ----------------------------------------------------------------- 193.0.0.0 - 193.0.1.255 1-Dec-94 Internal Infrastructure 193.0.2.0 - 193.0.2.127 1-Dec-94 ABC Organisation 193.0.2.128 - 193.0.2.255 1-Dec-94 ABC Organisation Int. 193.0.3.0 - 193.0.3.255 2-Dec-94 XYC-Organisation 193.0.4.0 - 193.0.7.255 11-Dec-94 AB Network Inc. 193.0.8.0 - 193.0.15.255 11-Dec-94 XY Net-Institute ... Enclosure B: EXAMPLE EXAMPLE EXAMPLE Non-assigned IP addresses: ----------------------------------------------------------------- 193.0.104.0 - 193.0.127.255 193.0.160.0 - 193.0.168.255 193.0.213.0 - 193.0.213.255 193.0.216.0 - 193.0.216.255 193.0.221.0 - 193.0.221.255 193.0.244.0 - 193.0.244.255 193.0.245.0 - 193.0.245.255

1 0

Q: Delegation of CIDR less than /24
by hostmaster＠xlink.net 22 Dec '95

22 Dec '95

Dear colleagues, there was a paper on this list, how to delegate /28-networks .. But I could not find it im my archive nor the ripe-web-server :-( :-( Would someone please send me the URL? Thanx and session greetings, Wilhelm de.xlink Hostmaster -- Wilhelm Buehler email: hostmaster(a)xlink.net NTG Netzwerk und Telematic GmbH / fax: +49 721 9652 210 Geschaeftsbereich Xlink \/ phone: +49 721 9652 211 Vincenz-Priessnitz-Str. 3 /\ link http://www.xlink.net/~wb/ D-76131 Karlsruhe, Germany /_______ Freiheit verbindet. Weltweit.

2 1

Re: Q: Delegation of CIDR less than /24
by zsako＠banknet.net 22 Dec '95

22 Dec '95

> From owner-local-ir(a)ripe.net Fri Dec 22 00:59:26 1995 > From: hostmaster(a)xlink.net (Hostmaster NTG/Xlink) > Sender: wb(a)xlink.net Dear Wilhelm, > there was a paper on this list, how to delegate /28-networks .. > > But I could not find it im my archive nor the ripe-web-server :-( :-( > > Would someone please send me the URL? I think what you are looking for is: ftp://ftp.ripe.net/internet-drafts/draft-degroot-classless-inaddr-00.txt Best regards and Seasons Greetings, Janos Janos Zsako BankNet Kft. Budapest, Hungary

1 0