- lir-wg - mailman.ripe.net

Local IR Training Course - Registration Closed
by RIPE NCC Training 19 Feb '96

19 Feb '96

Dear Local IR's, The registration for the Local IR Training course in Paris, 25th February 1996 has now been closed. As the course was oversubscribed, we were regrettably, not able to accept everyone. As soon as we have scheduled additional Training Courses, we will announce them to <local-ir(a)ripe.net>. If your registration could not be accepted this time, please register again for the next course to confirm your continued interest in attending. 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 <training(a)ripe.net>. Kind regards, Mirjam Kuehne RIPE NCC Training Team

1 0

None
by Josef Ptacnik 16 Feb '96

16 Feb '96

Jedine co Vam mohu nabidnou k okamzitemu odberu je publikace InternetROADMAP - Pruvodce svetem Internetu, kterou si u nas muzete vyzvednout za 150,-Kc+DPH.

2 1

Announcement for Local IR Training Course in Lisbon
by RIPE NCC Training 16 Feb '96

16 Feb '96

* * * Announcement * * * Local Internet Registries Training Course Date: Monday, 25th March, 1996 Time: 0900 - 1700 Venue: RCCN Fundacao Calculo Cientifico Nacional (FCCN) Rede da Comunidade Cientifica Nacional Av. do Brasil, 101 1799 Lisboa Codex Portugal Course Audience --------------- The target audience for this course is personnel of European Local Internet Registries that contribute to the RIPE NCC. Material Covered ---------------- The course is a one day introduction on Internet name, address and routing policy registration procedures in Europe. It also teaches 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. 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 <training(a)ripe.net> 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: 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 ;-). %%%%%%%%%%% 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 <training(a)ripe.net>. 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 <training(a)ripe.net>. 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.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) The course you plan to attend (date and location) # COURSE [ ] %END

1 0

Announcement for Local IR Training Course in Paris
by RIPE NCC Training 16 Feb '96

16 Feb '96

* * * Announcement * * * Local Internet Registries Training Course Date: Monday, 26th February 1996 Time: 0900 - 1700 Venue: Hyatt Hotel Airport Charles de Gaulle Paris France Course Audience --------------- The target audience for this course is personnel of European Local Internet Registries that contribute to the RIPE NCC. Material Covered ---------------- The course is a one day introduction on Internet name, address and routing policy registration procedures in Europe. It also teaches 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. 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 <training(a)ripe.net> 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: 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 ;-). %%%%%%%%%%% 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 <training(a)ripe.net>. 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 <training(a)ripe.net>. 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.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) The course you plan to attend (date and location) # COURSE [ ] %END

1 0

Local IR Training Courses
by RIPE NCC Training 16 Feb '96

16 Feb '96

Dear Local IR's, There are still places for the Training Courses in Paris at the 26th February 1996 and in Lisbon the 25th March 1996. Please find the announcements in separate mails. If you would like to attend, please send the attached registration form to <training(a)ripe.net> asap. If you have further questions, please don't hesitate to contact us. Kind regards, Mirjam Kuehne RIPE NCC Training Team ------------------------

1 0

Re: Policy Statement on Address Space Allocations
by jnc＠ginger.lcs.mit.edu 15 Feb '96

15 Feb '96

From: Geoff Huston <G.Huston(a)aarnet.edu.au> it will be economically infeasible IF we continue with this strange system of zero dollar interconnections we use as a peering model. ... In the same way that giving away IP addresses and giving away IP routing can only be described as a very bad case of irrational behaviour, especially when the underlying resource is under stress ... then I'd also note that giving away transit is similarly a case completely irrational behaviour! All this points to a desperate need for a more realistic economic structure to be used within a number of key aspects of Internet infrastructure. Geoff, while I sort of agree with you, please note that the current "free" models in all these areas do have one real advantage, which is that they are simple. Perhaps we will need "more realistic economic structure[s]", but I can more or less guarantee you that those will be more complex as well. Also, that complexity has a cost, which also has to be figured in. (The classic example is long-distance telephone service, where the cost of creting the bill is said to be far larger than the cost of the underlying service.) Finally, given past history, I suspect that the 'Net community, and particularly the 'Net technical community, is going to have a painful transition, on the emotional level and others, to this brave new world of more commercial structures, and the inevitable technical impacts that causes. That has certainly been the case in every such step in the past... Noel

14 23

Local IR minutes, 29-30 Jan 1996
by Mike Norris 12 Feb '96

12 Feb '96

Lo and behold, the Local IR minutes which Anne had produced ages ago, but which got delayed by.... ...your humble servant, Mike Norris Local IR working group Minutes RIPE 23 Amsterdam, 30th January 1996 Chair: Mike Norris Scribe: Anne Lord At the working group meeting there were 111 attenders. 1. Preliminaries A scribe was volunteered :) and the agenda which was previously circulated to the Local IR mailing list was agreed with some modifications to the order of the discussion. The minutes will reflect the order in which items appeared on the agenda. 2. RIPE 22 2.1 Minutes The minutes of the 22nd RIPE meeting had been circulated shortly after that meeting to the Local IR mailing list for comment and minor corrections were made to the text. The minutes were then accepted. 2.2.Review of actions Action 21.3 on Daniel Karrenberg, Mike Norris To draft a recommendation on charging by local IRs until September. Action is still open. A first outline had been written but needed further study and elaboration before a draft would be sent to the list. 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++. This action was closed. In addition to the RIPE NCC, the members of the editorial committee were: Mike Norris Wilfried Woeber Sabine Dolderer Hans Petter Holen Holger Weinhardt Janos Zsako 3. Reports from registries 3.1 European Regional Registry (RIPE NCC) As the formal report from the European IR was presented in the RIPE meeting plenary, the report to the working group was brief. The shortened report was as follows: * there are now 308 local IR`s. * the predictions for the workload for 1995 were accurate. * new staff are now fully trained. * the "wait" queue is now empty ("wait" queue is non-assigned requests). * approximately one new registry per working day is now being signed up. 3.2 Other Registries There were no comments from other local registries. It was suggested that this might be a good opportunity to organise a local IR workshop in conjunction with the next meeting. There was consensus within the group that this should not be organised in parallel with the EOF meeting. An action item was taken on by the RIPE NCC. Action: RIPE NCC To organise a Local IR workshop in conjunction with RIPE24. 4. Registry Procedures 4.1 European registries - ripe-104++ The draft document "European Internet Registry, Policies and Procedures" (ftp://ftp.ripe.net/ripe/drafts/ripe-104++.{txt,ps} was previously circulated to the Local IR mailing list for comment. There has been and still was considerable discussion on the mailing list. Within the working group the aim was to isolae the salient points and to resolve any differences of opinion so that consensus could be agreed and the document progressed. The following points were discussed: Assignment procedures VSE's - - It was commented that the assignment procedures are too complicated for VSE's. The common situation being one or two externally facing hosts and the rest behind a firewall. It was suggested that the end customer does not necessarily have to complete a network number application form in such cases, but the information might be collected by the Local IR. The important point is however, that the information is archived. PI/PA address space issues - - There was a discussion about PA (Provider Aggregatable) and PI (Provider Independent) address space. If your customer insists, PI address space can be allocated. Local IR's can apply on a per case basis for PI address space from the EU IR or they can apply for a PI block. As specified in ripe-127, there will be no guarantees over the routability of such blocks assigned and using such address space is *strongly* discouraged. - - It was also suggested that ripe-104++ could include a sentence to strongly recommend that ISP's/Local IR's should *not* accept PA address space from new customers which is outside their own CIDR address space. This was agreed. - - There was a question about the existing allocation registration information in the RIPE database. It was agreed that unless a contractual arrangement existed with the customer, assignments in the RIPE database without the "status" attribute marked as PA are considered PI (Provider Independent). If local IR's can make such contractual arrangements retrospectively, then such allocations can be considered PA and marked as such. Agreed. - - Assignments of address space are only valid as long as the assignment criteria under which the original addresses were allocated are still true. Agreed. - - It was suggested that the assignment messages from the RIPE NCC could be made clearer to reflect the significance of the PA assigned address space. Renumbering - - There was some discussion around the procedures for renumbering. It was agreed, that this would be encouraged by making the procedures as easy as possible for those who had agreed to renumber and words to the effect that the size of the previous assignment would not be questioned unless the efficiency was extremely low. Reservations Policy - - It was agreed to base assignments on a 2 year plan from the requestor. No reservations policy was endorsed. Static assignments for dial up - - The document strongly discourages the use of static IP assignments for dial up service. Strongly discourages means that if a strong technical reason is given and accepted, then assignments will be made for a vastly shortened time scale - 3 months was mentioned. Assignment window anomaly - - The largest current assignment window for any local IR is /19 -1. This refers to the amount of address space that they can assign without referring first to the RIPE NCC. The proposal in ripe-104++ was to reduce this to /20. After some discussion and by way of compromise, it was agreed to make the new maximum /19 rather than /20. However, for every local IR with a /19 -1 assignment window, the current value of it's assignment window will be set to /20, with the understanding that it can be increased to a /19 based on the usual criteria (as specified in ripe-104++). It was agreed that this would come into effect immediately after the meeting. Work remaining on ripe-104++ Sections 5,6,7 and 8 remain to be drafted. Section 5 will be drafted shortly after the RIPE meeting when the editorial committee meet and the draft will be circulated to the list shortly after the meeting. 5. Registry services and charges 5.1 RIPE NCC charging model The contributors committee had agreed on a charging model for 1996. All documents relating to the Contributors Committee meetings and revenue and expenditure documents can be found in: ftp://ftp.ripe.net/ripe/new-registry/ncc-co/ 5.2 Charging by local IR's As reported under item 2.2 a draft outline had been prepared. The reviewed document will be circulated to the mailing list after the RIPE meeting, once it has been reviewed and edited. The main emphasis of the document is that it is acceptable practise for Local IR's to charge for their services. There will probably also be some wording included to the effect that any remaining Last Resort Registries should not charge for profit. 6. Tools All Local IR's were encouraged to make any tools developed for local use available to the wider community if they thought that they could be useful to others. The RIPE NCC offered to "house" these tools and make their location visible. 7. Input from other Working Groups 7.1 DNS Ripe-105 will be incorporated into ripe-104++. 7.2 Database A proposal was made to the Database WG mailing list to incorporate the functionality of <auto-inaddr(a)ripe.net> into the general database update procedure. In future, it was proposed that in-addr updates could be sent to <auto-dbm(a)ripe.net> with a special tag which could be something like "INADDRREQUEST". 8. AOB 8.1 Reverse delegation of networks for partially assigned class B networks There was a question about in-addr.arpa delegations for assigned portions of class B address space. It was suggested that either you could ask the Internic to delegate 128 zones to the Local IR or to channel this request through the RIPE NCC. It was suggested that it might be useful to include a reference to this in ripe-104++. Action: RIPE NCC To include a paragraph on procedures for the reverse delegation of partially assigned class B networks. 8.2 Handing back of networks from block 192.0.0.0/8 In a mail of the PIER working group it was proposed that by 1997 users of non-aggregatable 192 address space should consider renumbering. There was a question concerning where 192 address space should be returned to. It was suggested to return it to the RIPE NCC in all cases, and the RIPE NCC will handle it as appropriate. Any queries can be sent to the RIPE NCC <hostmaster(a)ripe.net>.

1 0

Re: Classless in-addr.arpa delegation
by Havard.Eidnes＠runit.sintef.no 09 Feb '96

09 Feb '96

> IBM AIX 4.1.4 with the shipped BIND 4.9.3 and resolver library has > the very same problem.(earlier AIX versions do not(old BIND version)). If I am not much mistaken there is an update available from IBM which fixes this problem. The beta versions of BIND 4.9.3 should be exterminated and replaced with the release version as soon as possible. - Håvard

1 0

Classless in-addr.arpa delegation
by Andres Bauman 07 Feb '96

07 Feb '96

Hi There is at least one operating system, where this method described in draft-degroot-classless-inaddr-00.txt, and supposed by RIPE, does not work. It is FreeBSD. Their resolver libarary cannot handle CNAME answers for PTR queries. In their case you just see on console something like: Feb 7 16:53:00 cache traceroute: gethostby*.gethostanswer: asked for "177.96.40.193.in-addr.arpa", got "177.128.96.40.193.in-addr.arpa" Regards, ANdres ----------------------------------------------------------- Andres Bauman | Internet: andresb(a)uninet.ee AS Nosper Ltd. | Phone: +372 6308858 Ravala pst. 10 | Fax: +372 6317984 EE0001, Tallinn, Estonia |

3 2

Re: Policy Statement on Address Space Allocations
by Paul Ferguson 07 Feb '96

07 Feb '96

At 01:11 PM 2/5/96 -0600, Alan Hannan wrote: > > Learn how to renumber. It really is possible, you know. > > -alan > So, Alan, are you volunteering to help us out in PIER? ;-) - paul

1 0