From training at ripe.net Thu Jun 1 16:16:21 1995 From: training at ripe.net (RIPE NCC Training) Date: Thu, 01 Jun 1995 16:16:21 +0200 Subject: Local IR Training Course - Registration Closed Message-ID: <9506011416.AA19511@ncc.ripe.net> Dear Colleagues, Local IR Training Course, Amsterdam, June 26th 1995 The registration for the Local IR Training course has now been closed. As the course was oversubscribed, we were regrettably, not able to accept everyone. Those who were not able to attend this course, will automatically be placed on the waiting list. They will also be given priority for the next course - but will need to re-register to confirm their continued interest in attending. We would still only like one person from any single organisation to register. If you are interested in having a course in your country for a number of local IR's, we would be happy to do this. To discuss this further, please send mail to . Kind regards, Anne Lord and Mirjam Kuehne RIPE NCC From mak at aads.net Tue Jun 6 06:58:48 1995 From: mak at aads.net (Mark Knopper) Date: Tue, 6 Jun 1995 00:58:48 -0400 Subject: PI vs PA Address Space Message-ID: At 18:06 5/25/95, Sean Doran wrote: >It's not so much a conspiracy theory as a general wondering >why Kent took the position he did. I like knowing about motivations, >that's all. Call it a hobby. > > Sean. Well Sean, you should know that phone companies are a good place to be right now in terms of rapid Internet development and deployment. However, not all such organizations are perfect. See the latest round of Dilbert strips (the cartoonist apparently works for Pac Bell). Mark From Daniel.Karrenberg at ripe.net Tue Jun 6 14:15:34 1995 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 06 Jun 1995 14:15:34 +0200 Subject: Dalays in RIPE NCC Registration Services Message-ID: <9506061215.AA03656@ncc.ripe.net> Dear customers, as some of you will unfortunately have noticed, the response time of the RIPE NCC registration services has increased considerably compared to the very short times most of you were used to. 'Hostmaster' currently has a queue of more than 200 requests, 'in-addr' is above 70. This is mainly due to increased load. 'time permitting' requeste are not processed at all at this time. Please consider the following graph which plots the total number of mesages received by registration services per quarter: 3500++---------------------------------------------------+ | | | A | 3000++ * | | ** | | * | 2500++ * | | *A | | *** | 2000++ *A* | | *** | | *A* | 1500++ *** | | *A* | | ** | 1000++ ** | | ***A | | *A** | 500++ *** | | A* | | | 0++----+-----+-----+-----+-----+-----+-----+-----+----+ Q2/93 Q3/93 Q4/93 Q1/94 Q2/94 Q3/94 Q4/94 Q1/95 Unfortunately during the last 12 months we have not been able to increase staff resources in accordance with expected load because problems with 1994 revenue and the initially unclear revenue situation for 1995 did not allow that. Fortunately we can now be confident again about sufficient revenue and the hiring of three additional staff for registration services has been authorised. We have already signed a contract with a person from Turkey who will start this month, as soon as her visa becomes available. We will hire two more junior hostmasters as quickly as possible drawing from the response from our announcement in March. This step will very quickly more than double the staff time available for registration services. Hiring and training the new staff will take some time. This means we will have to live with larger backlogs and increased response times for some weeks to come. I ask you to bear with us for a few weeks and to show some understanding to NCC registration services staff who are working very hard to process your requests as quickly as possible. We expect to see a gradual improvement during July and to be able to return to our usual level of response times by late August. If you have any further questions, please do not hesitate to contact me. Regards Daniel Karrenberg RIPE NCC Manager From hostmaster at ripe.net Wed Jun 7 16:16:42 1995 From: hostmaster at ripe.net (RIPE NCC Hostmaster) Date: Wed, 07 Jun 1995 16:16:42 +0200 Subject: message from es.medusa Message-ID: <9506071416.AA16441@ncc.ripe.net> Medusa have asked us to make clear to other local IR's that they are not connected with the recent discussions over multiple address space requests from ICL. Their mail is appended below. Anne Lord RIPE NCC ------- Forwarded Message Date: Mon, 22 May 1995 13:18:15 +0100 From: enrique at medusa.es (Enrique Garcia Sanchez) To: RIPE NCC Hostmaster cc: otero at medusa.es Subject: NCC#950389 Re: Caution: assignments to ICL >This problem does not affect medusa as you are assigning address space >to your customers,=20 Hi,=20 It's good to know this problem does not affect Medusa. The thing is, Medusa is fully identified in Spain with ICL, and this message has arrived to many spanish mailboxes, I suppose. It would be very good for us if you just send a mail to the same people, noting this problem does not affect to Medusa, and we are not "shopping" around with the IP addrress space. I'm sure this is not a problem for you. Thank you very much in advance. ___________________________________________________________________ Enrique Garc=EDa S=E1nchez e_mail: enrique at medusa.es Director T=E9cnico MEDUSA tel: +34 (9) 1 3848180 Servicios de Acceso a INTERNET fax: +34 (9) 1 3848210 I.C.L. Espa=F1a S.A. C/Arturo Soria, 245 28033 MADRID SPAIN ___________________________________________________________________ Web Server http://www.medusa.es/ Medusa is member of PIPEX International and RIPE (Reseaux IP Europeen). ------- End of Forwarded Message From mnorris at dalkey.hea.ie Tue Jun 13 12:08:50 1995 From: mnorris at dalkey.hea.ie (Mike Norris) Date: Tue, 13 Jun 95 11:08:50 +0100 Subject: Minutes of mtg at RIPE 21 Message-ID: <9506131008.AA03116@dalkey.hea.ie> RIPE Meeting 21, Rome May, 8-10th, 1995 Chairman: Mike Norris Local IR Working Group Minutes Agenda 1. Select scribe 2. Agree agenda 3. Minutes ripe meeting 20 4. Actions outstanding 5. Reports from registries - local registries - RIPE NCC - global coordination 6. Charging for services - report of position for 1995 - billing procedures - model for future years - ticketing system 7. Training of (new) registries 8. Tools 9. Others - ripe-104 - database issues - reverse domains 10. AOB 1. Select scribe The meeting was held in two sessions, on 8th and 9th May 1995. Mike Norris, chairman of the WG, presided. Mirjam Kuehne kindly volunteered to take a record of the proceedings. There were about 110 people in attendance. 3. Agree agenda and 4. Actions outstanding Referring to the minutes of RIPE 20, it was noted that all actions for the working group had been completed. 5. Report from registries 5.1. Global Registries Mike Norris reported on a meeting of the three regional registries (RIPE NCC, APnic, InterNIC) held in January 1995 in Amsterdam after the last RIPE Meeting. Mike Norris attended this meeting as a representative of the local IR's in Europe. His report was sent to the local-ir mailing list at 29 Apr 1995. This meeting and another held in San Diego confirmed the good working relations and close cooperation between these registries at worldwide level. Daniel Karrenberg reported that procedures and criteria were being harmonised. The three regional registries are singing from the same hymn-sheet, and contacts between them were being intensified. 5.2. NCC Daniel Karrenberg reported on the activities of the RIPE NCC as the regional IP registry for Europe. A big change had been the introduction of a ticketing system to track transactions. He outlined the formalities this system required of people mailing queries to the NCC and urged all to read ripe-183 where these were documented. Daniel Karrenberg gave some reasons for the introduction of a ticketing system at the RIPE NCC: - Since the RIPE NCC receives more and more requests multiple hostmasters work on one mailbox. The ticketing system helps coordinating this activity. - Sometimes aditional information is sent by the requestor and not by the local IR that sent the requests originally. Ticketing system helps tracking requests. - Statistics will be included in the ticketing system that shows how long a requestis pending and why. This is not implemented yet. - Ticketing system can help supporting the model of usage based charging. Another new prodecure has been introduced at the RIPE NCC: the Reg ID that every registry is assigned must be mentioned in every request sent to the RIPE NCC, preferably in the form of X-NCC-RegID: regID. Please read ripe-183 for more details. Currently ticketing is still done by hand, but it will soon be overtaken by a robot. This requires strict adherence to the new formats. If the registry ID is not mentioned in a request sent to the RIPE NCC the ticketing procedure has to be done manually. This will produce delay in processing the request. A new request can be sent with a new ticket line: NCC#new-request-number This is not specified yet in ripe-183. *Action Daniel Karrenberg: Daniel Karrenberg will specify exact format of NCC#new-request-number and send it to the local IR mailing list. Details of growth in the activities of the NCC and of the Internet in Europe would be reported to the plenary session. Daniel Karrenberg reported the current staff situation at the RIPE NCC. He noticed a tremendous increase in number of registries and requests. Unfortunately there is not the same increase in the number of staff. But in June Hatice Kuey will join the RIPE NCC as Junior Hostmaster staff. 5.3. Reports from Local Registries No workshop has been organised between local IR's before the RIPE Meeting as usual. None of the present local registries had a report about unusual occurencies in the registries. Daniel Karrenberg mentioned a problem that occured with requests from large organisations that had large address space assigned in the past. These assignments were justified by the number of subsidaries. The address space was meant to be distributed among the subsidaries. The situation has often changed so that the subsidaries do not receive address space from the mother organisation and submit requests for address space to local IR's or directly to the RIPE NCC. Daniel Karrenberg suggested the following procedure: Ask the subsidary to provide a letter (or e-mail) with a statement that no address space can be received from mother organisation and why. This could help to ask address space back from mother organisation since original conditions are not held anymore. Daniel Karrenberg said he understands problem for provider to refuse address space to customers but the community needs to avoid that organisations are stockpiling addresses. The RIPE NCC wants to know where addresses are and if they are used. Maybe addresses can be asked back in the future when we run out of address space. 6. Charging for Services Details of commitments and payments for NCC services in 1995 were circulated. Daniel Karrenberg said that the problem of contributions from EUnet constituents had been resolved. This, together with natural growth in the number of new registries, meant that the current financial position was quite healthy, with 67% of the budget for the year already banked after four months. *Action Daniel Karrenberg: to put billing information in the database. The meeting discussed charging arrangements for 1996 and subsequent years. In September 1994, the RIPE NCC Contributors' Committee, representing the paying customers, had decided that from 1996 onwards, charging should be related in some way to the volume of service provided. The Committee would meet again in September 1995 to agree on a charging model, which would be prepared by the NCC and discussed on the list beforehand. It was agreed that the model should be transparent, with subscribers being able to find out what their bills were going to be. Automated transactions would not be counted for billing purposes. The fixed charges for small, medium and large subscribers would probably account for 50% of the budget in order to provide for financial stability and continuity. *Action Daniel Karrenberg and Mike Norris: to draft a recommendation on charging by local IRs until September The RIPE NCC will restart the publication of Quartely Reports. Production has been simplified. Questions: Q: Do last resort registries run by EUnet remain? A: Yes, but RIPE NCC will watch carefully that addresses are really assigned as last resort. Q: What is the difference between the prices on the list? A: Different prices for different sized registries; registries determine their size themselves. The size and the price is published and can be seen and compared by all registries. Size can be changed over the time. Q: Some registries have higher billing/income than committed. What does this mean? A: These are new registries and the sign-up fee is added in the income column. Q: How is the time-permitting procedure working (has it effect)? A: Is works excellent! Q: How long is the delay? A: Technically the RIPE NCC maintains two queues of requests (normal-service queue and time-permitting queue). Hostmasters can proceed with a request in the time-permitting queue when the normal-service queue is empty. This has not happen too often (not at all). Q: How much resources take referrals to service providers? A: The RIPE NCC doesn't advertise itself as such a service and doesn't answer end user questions in general. When the RIPE NCC receives requests for service providers, requester will be pointed to the ip-provs mailing list. We should continue doing this. This does not require too much resources. We don't spend local IR's money to provide consultancy for customers of the competitor. Q: If RIPE NCC could publish referral information, this would relief the NCC. A: Referral service is not a problem yet. The RIPE NCC receives 2 of such questions per week. When it becomes a remarkable amount of time, we will find a solution. Q: Couldn't we take the amount of e-mail messages registry sends to the RIPE NCC as indicator for usage based charging? A: This is not such a good idea. It discourages registries to ask questions. What, if the RIPE NCC has a question about a request and the registry sends the answer back, should they be charged for this message? No. Q: Shouldn't we improve a model that combines the size of a registry with with the usage? A: This is a good idea. Q: Couldn't we take inetnum objects in DB as criteria? A: This could also be a possibility. Q: What is the current relation between the RIPE NCC and TERENA? A: The RIPE NCC is still under the umbrella of TERENA. Staff of RIPE NCC is employed by TERENA. But the NCC does all dealings with the registries on its site, apart from the real billing process. We pay 10,000 ECU to TERENA for administrative work. current problem: TERENA is shrinking, RIPE NCC is growing, problems with hiring more staff. Q: Can local IR charge customer for their services? If yes, who has implemented it? A: Yes, local IR's can charge for their services. The RIPE NCC does not know who has implemented it, since no registry informs us about it. Note: It is only allowed to charge for services, it is not allowed to sell address space! Q1: Should the RIPE NCC publish a document with charging recommendation? Q2: Should the RIPE NCC publish a list about charging registries? A1: Yes, some recommendations would be useful: For what services can be charged and for which not; helping with the right language. A2: No, this is not a good idea. This could be interpreted as selling addresses. 7. Training On the last ncc-co meeting was agreed to produce a training course to help new registries to fulfil their function as Local Internet Registry. This was coppeled with the charging model: New registries pay a sign-up fee that will be used to produce such a course. But while the course were intended primarily to help new registries, "old" IRs were welcome to attend if places were available (those registries that have payed sign-up fee will be preferred). Mike Norris encouraged all registries to avail of this valuable training/ re-training resource for their staff. A lot of procedures and guidelines have changed in the past. The RIPE NCC has started in March to produce a training course. A project framework has been published to the local-ir mailing list. Some help and input has been offered to the RIPE NCC. Anne Lord and Mirjam Kuehne are running the project. They are currently busy to prepare the course. Please note that they have only two hours per day to do so. The first course will be held at 26 June 1995 and a training guide would soon be published. After this first course as much course as necessary will be held. The RIPE NCC is also prepared to give courses abroad, when enough registries come together in one country. 8. Tools The monthly host count condicted by the NCC had been further delegated, with sixteen European top-level domains now doing the count locally and making the results available to the NCC. The NCC had refined existing tools in order to analyse the reverse DNS for IP networks in European blocks. The results showed a very poor picture, with low coverage and lots of errors. People were urged to avail of the tools and to try to improve the situation. 8.1. Geert Jan de Groot produced tools that check for errors in reverse delegations and complains if they sustain for a week or more. The tools are available at: ftp://ftp.ripe.net/ripe/local-ir/{inaddrcount, revcheck} 8.2. David Kessens from the RIPE NCC has written a tool to automize requests for reverse domain delegations. It checks the zone that asks for reverse delegation and produces a fairly long output containing all errors found. The requests sent to the RIPE NCC still contain 70% errors but usually the errors are removed at the second time the RIPE NCC receives the request (that was not always the case in the past). The output that is send back to the requestor helps to correct the request and the zone. The tool is still in the test period at the RIPE NCC. After it is stable, it will be published. 9. Other Issues 9.1. ripe-104 Daniel Karrenberg has circulated his draft about VSE's again. He also reported on the current discussion about address space allocation and assignment procedures: On the IETF has been agreed to distinguish between two different kinds of address space: - provider agreegatable address space (PAS) - povider independent address space (PIS) Daniel Karrenberg summarized other topics in the current discussion: The exhaustion of IPv4 address space is not the main problem. The main issue is the growth of the routing tables. On average there are 4000 hosts per route. This shows that CIDR works, but still not enough. Some routers begin to fall over. Service Provider and local IR's should only use and assign PAS (see draft from Yakov Rekhter: ftp://ftp.ripe.net/internet-drafts/draft-ietf-cidrd-ownership-01.txt) The current debate mentiones sizes of address space for PIS and PAS: smaller and equal than /19 (32 C's): PIS greater than /19 (32 C's): PAS This discussion delayed the revision of ripe-104. The providers should decide what prefixes they will route and for what price. It should not be the regional registrie's task to make this decision. The registries should clarify the implications of PIS and PAS but not regulate. Daniel Karrenberg has written a draft that lists the possible implications: If customers receives PAS they may have to renumber when they change service provider. If they receives PIS the addresses might not be routable in the future. There must be a clear contractual agreement between customers and registries, when registries assign PAS. The IANA has been asked to circulate this draft. Questions, Comments: Suggestion: RIPE should provide recommendation about prefix length. It is not clear yet where the boundary between PIS and PAS will be (/19?). PAS must be easy to renumber (rather short prefix). But this issue needs more discussion in the Local IR group. Comment against recommendation: The recommended prefix length will probably change over the time. A recommendation would produce false security. DFK: This has to be clear in the recommendation. Q: Problem with large multinational organisations that contact varies last resort registries to request address space. A clear statement or recommended guidelines from RIPE is needed. A: The basic principle is already included in ripe-104: If the multinational organisation is connected only in one place, addresses should be received from this one service provider. If the multinational organisation is connected in varies places/countries it should receive address space from these different service providers. The problem is rather that it is easier for these organisations to ask for small amounts of addresss space at different registries than for a large amount of address space at one place. It is easier to provide an addressing plan for small parts of a network than for the whole network. There is no clear procedure how this can be prevented apart from being careful and asking carefully for detailed documentaion. Q: Can't the RIPE NCC make a clear recommendation that these kind of organisations should contact the RIPE NCC for address space? A: There are clear guidelines in ripe-104: 4. Organisations operating a network which spans several countries may obtain address space from a service provider, the RIPE NCC, or the global NIC, as is appropriate to their network confi- guration. In many cases it will be best to obtain addresses for the whole network from the provider operating the main connection of the multi-national network to the Internet. When in doubt, contact the RIPE NCC for guidance. 9.2. DB issues On the last RIPE Meeting it has been agreed that the technical contact in an object can also be a role, e.g. a NIC instead of a person. Harvard Eidnes has written a draft about tyhis issue and circulated to the local-ir mailing list in advance to the 21. RIPE Meeting. 9.3. Reverse Domains The group endorsed the recommendation of the DNS WG that the reverse domains of connected IP networks be name served. *Action Mirjam Kuehne and Anne Lord: to incorporate strong recommendation regarding reverse DNS in training materials. ------- End of Forwarded Message From inaddr at ripe.net Mon Jun 19 18:36:58 1995 From: inaddr at ripe.net (RIPE NCC IN-ADDR. ARPA Role Account) Date: Mon, 19 Jun 1995 18:36:58 +0200 Subject: Announcement: new procedure for in-addr.arpa reverse delegations Message-ID: <9506191636.AA08848@ncc.ripe.net> Dear all, As of today the RIPE NCC offers an automated method for the submission of reverse zone delegations in 193.in-addr.arpa and 194.in-addr.arpa. Your delegation requests and the zone files on all nameservers will be checked automatically. The diagnostics generated by these checks will be returned to you automatically too. This will make you aware of any problems very quickly, so that you can correct them and re-submit your request. When the automated procedure does not detect any errors, the request is forwarded to the inaddr role account person for some additional manual checks and the processing of the delegation itself. Of course, you will receive an acknowledgement when this has been done. To use the new automated procedure send your request in ripe-105 format to: You can use some keywords in the 'Subject:' line of your E-mail to control the checking process. The use of the LONGACK keyword is very recommended. HELP - will send you a (patched) ripe-105 document CHANGE - is needed if you want to change an existing reverse delegation LONGACK - will give you the most verbose output as possible RIPE document ripe-105 requires you to send in a RIPE database 'inetnum' object with a 'rev-srv' attribute for each nameserver for single/multiple C's reverse delegation requests and for whole blocks 'domain' objects with 'nserver' attributes for each nameserver. I recommend to use the following procedure for doing your request: Send an E-mail to with LONGACK in the 'Subject:' line and an appropriate RIPE database object as described in ripe-105 in the body of the message. We still accept the old method for reverse delegation requests (ripe-105 format request to ), however it might take some more time to process them. After some time, when the software doesn't change daily anymore, the source code will be published. I am neither a DNS expert or native English writer ;-) so all your comments are welcome! Please send them together with complaints, bug reports or special requests to . Kind regards, David Kessens RIPE NCC From Nigel.Titley at bt.net Mon Jun 26 18:10:09 1995 From: Nigel.Titley at bt.net (Nigel Titley) Date: Mon, 26 Jun 1995 17:10:09 +0100 Subject: New release of tree Message-ID: <9506261610.AA13660@ncc.ripe.net> A new release of tree is available which fixes a bug causing it to crash when exiting prematurely from 'list'. Details are: ftp://ftp.bt.net/pub/networking/tools/tree/tree-2.1.1.tar.Z There is still a known bug in the subinit command which results in a subinit issued without a specific address grabbing the whole tree. I'll fix this when I have time, but in the meantime always use a specific address with subinit (this is the usual practice anyway). I'd be interested in any feedback by anyone that is using it. Nigel -------------------------------------------------------------------- Nigel Titley --- BTnet E-mail: Nigel.Titley at bt.net Tel: +44 1442 237674 "Well I'm disenchanted too, we're all disenchanted." (James Thurber) From Nigel.Titley at bt.net Tue Jun 27 11:45:47 1995 From: Nigel.Titley at bt.net (Nigel Titley) Date: Tue, 27 Jun 1995 10:45:47 +0100 Subject: Whoops! Message-ID: <9506270946.AA20001@ncc.ripe.net> Today's prize to Antonio Blasco of GARR for spotting a major bug in tree resulting in segmentation faults when more than one tree is initialised. I've fixed this as it was such a major one and re-released. New version is 2.1(2) and is in ftp://ftp.bt.net/pub/networking/tools/tree/tree-2.1.2.tar.Z Apologies to anyone who retrieved yesterday's version. Nigel -------------------------------------------------------------------- Nigel Titley --- BTnet E-mail: Nigel.Titley at bt.net Tel: +44 1442 237674 "Well I'm disenchanted too, we're all disenchanted." (James Thurber) From training at ripe.net Thu Jun 29 11:39:28 1995 From: training at ripe.net (RIPE NCC Training) Date: Thu, 29 Jun 1995 11:39:28 +0200 Subject: Announcement for Local IR Training Course Message-ID: <9506290939.AA11511@ncc.ripe.net> Due to very high demand from participants from Germany to the first course here in Amsterdam, ECRC very quickly offered to host a course to accomodate the high demand. The course is almost full, but there are still some places left. Please register quickly! * * * Announcement * * * Local Internet Registries Training Course Date: Monday, 10th July, 1995 Time: 0900 - 1700 Venue: ECRC GmbH Arabellastrasse 17 81925 Muenchen Germany http://www.ecrc.de/misc/travel/travel.html -------------- next part -------------- Course Audience The target audience for this course is personnel of European Local Internet Registries or ISPs planning to set up a local IR. Material Covered The course is a one day introduction on Internet name, address and routing policy registration procedures in Europe. It also teaches students how to query and use the information registered for operational purposes. This includes the following material and activities: o Overview of name, address and routing registration procedures. o Responsibilities of both RIPE NCC and Local IR's to each other. o Wider context of the Delegated Registry system and relevant issues (IPv4 address depletion, CIDR) and how this relates to IP requests. o How to use the RIPE NCC Database. o Use of AS numbers, Routing Registry concepts and an introduction to using PRIDE tools. o DNS feedback on commor errors, how to request delegations, and pointers to useful tools. o Practical experience and feedback on how to create, maintain and update various types of information stored in the RIPE database. We again stress that this course will *not* teach Local Registries on how to run their business as Internet Service Providers. It is clearly focussed on registration procedures and the interaction between the RIPE NCC and local IR's. A detailed outline is appended below. The course itself will include lunch and will be free. This of course does not include your travel and subsitence ;-). How to Register Please send an RSVP to if you would like to attend the course. If you have previously approached us about attending this course, we ask you to confirm that you (or a colleague) will be attending. Registrations will be accepted on a first come, first served basis. If the course is oversubscribed, we will give priority to local IRs who have paid the signup fee in 1995. If it is still oversubscribed, we will accept only one person per new local registry. We will provide additional course dates in Amsterdam as necessary. If a number of local registries so request, we will present courses at other European locations. If you would like a local course or have any questions or suggestions, please do not hesitate to contact us. The RIPE NCC Training Team: Anne Lord, Mirjam Kuehne, Daniel Karrenberg --- Course Outline For this second course, we will provide a slidebook and a reader on the day of the course, as well as electronically. Once feedback is received, it is planned to make detailed documentation available in the form of a guide much like the PRIDE guide. The program will divide the actual content into the following sections: 1. Introduction For those unfamiliar with the Delegated Internet Registry system and the RIPE NCC, this section will give a historical overview of how we have arrived at today's model of operation and why training of local IR's is a much needed activity. 2. IP Registry procedures This section will clarify the procedures between the RIPE NCC and local IR's with respect to requests for IP address space. It will take a step by step approach on how to complete documentation, the kind of information that is required, what the "handholding" procedure is, how to deal with very large requests, and very small requests, and more generally what criteria the RIPE NCC and local IR's use for their customers in the context of CIDR and IPv4 address depletion. 3. RIPE NCC Database This section will explain what the RIPE NCC Database is and how it fits into the scheme of other registry databases. It will cover how to create and update RIPE NCC Database objects and will explain how to query the database. 4. Routing Registry procedures This section will examine AS numbers, when you need them and how to request them. This will be set within the context of how AS numbers are used as part of the RIPE Routing Registry. Understanding the basic principles behind the Internet Routing Registry and how registering your policy is an important element in the global schema. This section will also include a brief introduction to the PRIDE tools and how they can be useful to you. 5. DNS procedures Where to request forward and reverse domain delegation. Which documentation should be completed. How reverse domain delegation requests are processed at the RIPE NCC (with a useful tool). We will also take a look at common errors in setting up DNS with respect to relevant RFCs and RIPE recommendations. Feedback Please! Throughout the course there will be ample chance for feedback and discussion with an emphasis for you to tell us how we can improve ;-). -------------- next part -------------- %%%%%%%%%%% PLEASE NOTE %%%%%%%%%%% Our handling of ALL course registrations is fully automated. To register for the course, please complete the registration form and send it to . Please send only the registration form in your reply and edit out all other text. Add in a value in the `box' area marked between the square brackets (i.e. "[" and "]" s). If you have any questions about the training course or your registration form, please contact us at . You will receive a notification message that your request has been processed. Many thanks, and look forward to seeing you, RIPE NCC Training Team ---------------------------------------------------------------------------- %START PART 1 - Registration 1) Your name Enter First name, Last name in FULL e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.) # REG [ ] 3) Your e-mail address # EMAIL [ ] %END From training at ripe.net Thu Jun 29 11:53:48 1995 From: training at ripe.net (RIPE NCC Training) Date: Thu, 29 Jun 1995 11:53:48 +0200 Subject: Slides from 1st training course available Message-ID: <9506290953.AA11623@ncc.ripe.net> Dear Local IR's Following the first training course for Local IR's held here in Amsterdam on Monday 23rd June, we are happy to announce that the slides from the course are available for ftp from the directory: ftp//ftp.ripe.net/ripe/local-ir/training/ The slides are available as one complete course: master-course-slides-AMS-950623.ps.Z or individually per session: intro-slides-AMS-950623.ps.Z ip-slides-AMS-950623.ps.Z db-slides-AMS-950623.ps.Z routing-slides-AMS-950623.ps.Z dns-slides-AMS-950623.ps.Z The slides from the Munich course will incorporate the feedback received from participants at this course and will be available after 10th July. kind regards, Anne Lord & Mirjam Kuehne RIPE NCC Trainming Team. From mnorris at dalkey.hea.ie Thu Jun 29 17:05:48 1995 From: mnorris at dalkey.hea.ie (Mike Norris) Date: Thu, 29 Jun 95 16:05:48 +0100 Subject: Slides from 1st training course available In-Reply-To: Your message of "Thu, 29 Jun 95 11:53:48 +0200." <9506290953.AA11623@ncc.ripe.net> Message-ID: <9506291505.AA27161@dalkey.hea.ie> Sounds like the first course was a great success and that there's lots of demand for more of the same - well done, NCC! Thanks, too, for the excellent slides. Mike From ncc at ripe.net Fri Jun 30 11:39:20 1995 From: ncc at ripe.net (RIPE NCC Document Annoucement Service) Date: Fri, 30 Jun 1995 11:39:20 +0200 Subject: New Document available: ripe-127 Message-ID: <9506300939.AA22230@ncc.ripe.net> New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-127 Title: Provider Independent vs Provider Aggregatable Address Space Author: Daniel Karrenberg, RIPE NCC Date: 30 Jun 1995 Format: PS=91858 TXT=17620 Obsoletes: Obsoleted by: Updates: ripe-126 Updated by: Old: Short content description ------------------------- The RIPE NCC receives an increasing amount of questions about the protability or provider independence of address space. This document provides guidance to European Internet registries concerning these issues. -------------- next part -------------- FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/" followed by the command "get filename". The relevant filenames for this document are: ripe-127.txt for the ASCII version ripe-127.ps for the PostScript version Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server at ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the RIPE document by FTP or mail server. -------------- next part -------------- SEND ripe/docs/ripe-127.txt From Daniel.Karrenberg at ripe.net Fri Jun 30 11:48:19 1995 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Fri, 30 Jun 1995 11:48:19 +0200 Subject: ripe-127 Message-ID: <9506300948.AA22392@ncc.ripe.net> Dear colleagues, all registries should take note of ripe-127. It is a slightly adapted version of a draft document circulated earlier. We are getting quite some questions and requests for guidance on this matter. This made it necessary to have a RIPE document on this quickly. Since the earlier discussion revealed no show stoppers and there was quite some support in Rome I have just published it without a further round of discussion. If you have any further questions, please do not hesitate to contact us. Regards Daniel Karrenberg RIPE NCC Manager From ncc at ripe.net Fri Jun 30 12:09:56 1995 From: ncc at ripe.net (RIPE NCC Staff) Date: Fri, 30 Jun 1995 12:09:56 +0200 Subject: Hoechst AG Message-ID: <9506301009.AA22615@ncc.ripe.net> Dear Local IR contacts, In the past few months, we have got requests for address space from affiliates of Hoechst Germany, all over Europe, who want to connect to Hoechst Germany. Hoechst has received quite a lot of address space already. If Hoechst companies knock at your door for address space, could you refer them to Hoechst Germany, or direct them to the RIPE NCC? Kind regards, Roderik Muit RIPE NCC From training at ripe.net Fri Jun 30 15:07:01 1995 From: training at ripe.net (RIPE NCC Training) Date: Fri, 30 Jun 1995 15:07:01 +0200 Subject: Registration for Munich Local IR Training course Message-ID: <9506301307.AA24654@ncc.ripe.net> Dear Local IR's Local IR Training Course July 10th, Munich, Germany Hosted by ECRC. The registration for this Local IR Training course has now been closed. The course was very quickly oversubscribed, so we were, regrettably, not able to accept everyone. If you are interested in hosting a course for local IR's, we would be happy to do this. To discuss this further, please send mail to . We are currently in discussion regarding the possibility of courses taking place in the UK, Italy and Austria. Kind regards, RIPE NCC Training Team From christian.huitema at sophia.inria.fr Fri Jun 30 21:34:04 1995 From: christian.huitema at sophia.inria.fr (Christian Huitema) Date: Fri, 30 Jun 1995 21:34:04 +0200 Subject: New Document available: ripe-127 Message-ID: <199506301934.VAA18696@pax.inria.fr> A (At) 11:39 AM 30/6/95 +0200, RIPE NCC Document Annoucement Service ecrivait (wrote): >Content-Type: text/plain; charset="us-ascii" >Content-Description: Document Announcement > > >New/Revised RIPE Document Announcement >-------------------------------------- >A revised/new document is available from the RIPE document store. > >Ref: ripe-127 > >Short content description >------------------------- > >The RIPE NCC receives an increasing amount of questions >about the protability or provider independence >of address space. This document provides guidance to European Internet >registries concerning these issues. > Given that interest for these matters spreads well outside Europe, could you please consider submitting this as an informational RFC? Christian Huitema