- lir-wg - mailman.ripe.net

(Fwd) Last Call: INTERNET REGISTRY IP ALLOCATION GUIDELINES to BCP
by Mike Norris 20 Apr '96

20 Apr '96

------- Forwarded Message Return-Path: owner-cidrd(a)aarnet.edu.au Received: from IETF.cnri.reston.VA.US (ietf.cnri.reston.va.us [132.151.1.35]) by nico.aarnet.edu.au (8.6.10/8.6.10) with SMTP id DAA00357 for <cidrd(a)iepg.org>; Sat, 20 Apr 1996 03:08:03 +1000 Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa15673; 19 Apr 96 13:00 EDT To: ;@IETF-Announce; Cc: cidrd(a)iepg.org From: IESG Secretary <iesg-secretary(a)ietf.org> Subject: Last Call: INTERNET REGISTRY IP ALLOCATION GUIDELINES to BCP Reply-To: iesg(a)ietf.org Date: Fri, 19 Apr 96 13:00:30 -0400 Sender: scoya(a)CNRI.Reston.VA.US Message-Id: <9604191300.aa15673(a)IETF.CNRI.Reston.VA.US> The IESG has received a request from the CIDR Deployment Working Group to consider "INTERNET REGISTRY IP ALLOCATION GUIDELINES" <draft-hubbard-registry-guidelines-01.txt> for the status of BCP. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg(a)cnri.reston.va.us or ietf(a)cnri.reston.va.us mailing lists by May 3, 1996. ------- End of Forwarded Message

1 0

New Document available: ripe-128++
by cis 18 Apr '96

18 Apr '96

---------- Forwarded Message ---------- From: RIPE NCC Document Annoucement Service, INTERNET:ncc@ripe.net TO: "Local IR Working Group", INTERNET:LOCAL-IR@RIPE.NET CC: (unknown), INTERNET:STAFF@RIPE.NET (unknown), INTERNET:ORANGE@RIPE.NET DATE: 17/04/96 21:03 RE: New Document available: ripe-128++ Sender: owner-local-ir(a)ripe.net Received: from ncc.ripe.net (ncc.ripe.net [193.0.0.129]) by arl-img-3.compuserve.com (8.6.10/5.950515) id UAA18686; Wed, 17 Apr 1996 20:22:30 -0400 Received: by ncc.ripe.net id AA26355 (5.65a/NCC-2.33); Wed, 17 Apr 1996 21:42:44 +0200 Received: from voldragen.ripe.net by ncc.ripe.net with SMTP id AA26347 (5.65a/NCC-2.33); Wed, 17 Apr 1996 21:42:39 +0200 Message-Id: <9604171942.AA26347(a)ncc.ripe.net> To: "Local IR Working Group" <local-ir(a)ripe.net> Cc: staff(a)ripe.net, orange(a)ripe.net From: RIPE NCC Document Annoucement Service <ncc(a)ripe.net> Subject: New Document available: ripe-128++ Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0" X-Phone: +31 20 592 5065 X-Fax: +31 20 592 5090 Date: Wed, 17 Apr 1996 21:42:39 +0200 Sender: Carol.Orange(a)ripe.net ------- =_aaaaaaaaaa0 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. Short content description ------------------------- ripe-128++ is the new set of forms local IRs should use when submitting IP address space assignment requests to the RIPE NCC for review. They implement the policies written up in the ripe-104++ document in which which local IR address space assignment policies are defined. The forms are accompanied by a set of instructions and examples. Please review these forms as soon as possible and send your comments to <orange(a)ripe.net>, or bring them to the RIPE-24 Local IR Working Group meeting in Berlin where they will be on the agenda for comment/approval. ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-Description: Retrieval Methods 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/drafts/" followed by the command "get filename". The relevant filenames for this document are: ripe-128++.txt for the ASCII version ripe-128++.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(a)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". 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. ------- =_aaaaaaaaaa0 Content-Type: message/external-body; access-type="anon-ftp"; name="ripe-128++.txt"; directory="ripe/drafts"; site="ftp.ripe.net" Content-Type: text/plain; type="text" Content-Description: FTP ASCII version ------- =_aaaaaaaaaa0 Content-Type: message/external-body; access-type="mail-server"; server="mail-server(a)ripe.net" Content-Type: text/plain; type="text" Content-Description: Have mail-server send document SEND ripe/drafts/ripe-128++.txt ------- =_aaaaaaaaaa0 Content-Type: message/external-body; access-type="anon-ftp"; name="ripe-128++.ps"; directory="ripe/drafts/"; site="ftp.ripe.net" Content-Type: application/postscript; type="postscript" Content-Description: FTP PostScript version ------- =_aaaaaaaaaa0--

1 0

New Document available: ripe-128++
by RIPE NCC Document Annoucement Service 17 Apr '96

17 Apr '96

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Short content description ------------------------- ripe-128++ is the new set of forms local IRs should use when submitting IP address space assignment requests to the RIPE NCC for review. They implement the policies written up in the ripe-104++ document in which which local IR address space assignment policies are defined. The forms are accompanied by a set of instructions and examples. Please review these forms as soon as possible and send your comments to <orange(a)ripe.net>, or bring them to the RIPE-24 Local IR Working Group meeting in Berlin where they will be on the agenda for comment/approval. 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/drafts/" followed by the command "get filename". The relevant filenames for this document are: ripe-128++.txt for the ASCII version ripe-128++.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(a)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". 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. SEND ripe/drafts/ripe-128++.txt

1 0

RIPE24: reminder
by RIPE NCC Staff 17 Apr '96

17 Apr '96

Dear RIPE members, If you want to attend the 24th RIPE meeting, please subscribe to <meeting(a)ripe.net> before Friday morning 9:00 if you haven't done so yet! Thank you! more info available from ftp://ftp.ripe.net/ripe/Next-Meeting. Appended below are the announcement with some changes and the registration form. **************************************************************** Changes: - Starting time is 14:00 instead of 10:00! - More information about directions to the venue - Info about public transport tickets - More pointers to WWW information 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 24th RIPE meeting will take place: Dates: 22nd April, 1996 start: 14:00 23rd April, 1996 24th April, 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: Mathematics building of the Technical University of Berlin Strasse des 17. Juni 136 10623 Berlin (Plenary session will take place in room # MA005) Host: DFN 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: ------------------------- - Monday 22nd from 14:00-18:00, and Tuesday 23rd from 09:00-12:30, there will be various RIPE working groups sessions. The schedule of this meeting is not known yet. - Tuesday 23rd, 14:00-18:00 and Wednesday 24th, 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. Directions to the meeting venue: -------------------------------- The closest bus- and 'U-Bahn' (subway) stop is 'Ernst-Reuter-Platz'. From airport Berlin-Tegel, you can take express bus X9 there. (X9 leaves very close to the most right exit of the main hall of Tegel airport.) From airport Berlin-Schoenefeld, you can best first go to the international railway station 'Zoologischer Garten'. (Taking train S9 is probably the best way.) From the station 'Zoologischer Garten', you can take the subway U2 in direction Ruhleben; Ernst-Reuter-Platz is the first stop. (Or you could also walk from 'Zoologischer Garten' to the meeting venue.) The mathematics building where the meeting is held, is on the north side of the 'Strasse des 17. Juni'. Public Transport tickets: ------------------------- Tickets can be bought from machines at every station. 'Kurzstrecke' (short ride) tickets are only vald for a certain number of stops; the exact area should be specified at the bus/U-Bahn stops. Prices: Kurzstrecke einfach (1 ride): DM 2,50 Sammelkarte (4 rides): DM 8,50 2-hours-ticket (1 ride): DM 3,90 Sammelkarte (4 rides): DM 13,00 24-hours-ticket: DM 16,00 48-hours-ticket: DM 29,00 7-days-ticket: DM 40,00 General information: -------------------- Currency : 1 UK pound = DM 2.25 1 ECU = DM 1.85 1 US$ = DM 1.47 More information about Berlin on the Web: ----------------------------------------- A lot of information can be found at: <> http://www.city.net/countries/germany/berlin/ <> http://www.kulturbox.de On http://www.kulturbox.de/cgi-bin/berlininfo?&pq=m11 you will find a map of the direct vincinity of the meeting site, which is marked 'Grosser Horsaal'. <> http://www.informatik.hu-berlin.de/BIW/ is all in German, but http://www.informatik.hu-berlin.de/BIW/verkehr gives a nice map of public transport facilities *********************************************************************** 24th RIPE meeting Registration reservation form Berlin, Germany April 22nd-24th, 1996 %%%%%%%%%%% PLEASE NOTE %%%%%%%%%%% Our handling of ALL meeting registrations is fully automated. To register for the meeting, please complete the registration form and send it to <meeting(a)ripe.net>. PLEASE FILL THIS OUT AS SPECIFIED. Please add in a value in the `box' area marked between the square brackets (i.e. "[" and "]" s). Note this is what will be used for your badge if you have requested one and for the attendee list so please take care to fill it in correctly. You will receive a notification message that your request has been processed. If however, you have any questions about the meeting or your registration form, please send your completed form to <ncc(a)ripe.net>. ============================================================================== %START PART 1 - Registration 1) Your name Enter First name, Last name in FULL (remember this is on list and badge) e.g. John Doe Mary-Beth Walton %NAME [ ] 2) I will need the RIPE NCC staff to come up with a badge for me (Fill in Y if you do not have a badge yet, or if you have given it to the NCC staff to keep until the next meeting. Fill in N if you will bring your old badge to the meeting yourself.) %BADGE [ ] 3) Your Organisation/Institution %ORG [ ] 4) Your e-mail address %EMAIL [ ] 5) Country code of organisation e.g. IT FR DE %CTRY [ ] %END

1 0

Charging by local IRs - draft paper
by mnorris＠dalkey.hea.ie 16 Apr '96

16 Apr '96

This closes Action 21.3 on Daniel Karrenberg and me and is for discussion at next week's Local IR meeting. Cheers. Mike Norris ripe-xxx Charging by Local Internet Registries 1. Abstract ------------ This paper deals with charging for services by Internet registries, and indicates acceptable practice for such charging. It identifies name- and address-space as finite resources with no intrinsic value; as such, direct costs cannot be ascribed to such space. It also makes recommendations for the operation of European registries in general, and additionally for those with monopoly positions. 2. Internet services --------------------- In Europe as elsewhere, providers offer a range of services relating to Internet access. These include Internet connectivity, the provision of applications to end-users, design, consultancy and training services, as well as system services such as IP registration, DNS, routing and packet forwarding. With some identifiable exceptions (to which we shall return), there is generally an open market in the provision of such services. On the supply side, there is freedom to enter the market, to compete for business, and to charge for services in order to stay in business. In this context, it is acceptable practice for Internet service providers (ISPs) to charge for services such as domain registration, routing services, packet forwarding and IP services. On the demand side, the general plurality of service providers means that the customer has a choice; if not satisfied with the terms of one supplier, she can take her business to another. 3. Registries and Resources ---------------------------- Two of the above services involve the assignment of finite resources to customers; these are domain name space and IPv4 address space. They are managed and assigned by registration agencies, respectively domain name registries and IP registries. By themselves, these resources have no intrinsic value; their worth is only realised in conjunction with the provision of Internet access. Thus, while registries may charge for their administrative and technical services, they may not charge for namespace or address space as such; no unit cost or price tag can be attached to a domain name or to an IP address, public or private. This principle must be made clear to the market in general and to the customer in particular. The customer must be aware of precisely what she is getting from the registry, whether it is paid for or not. Where there is a charge, the customer must not be under the illusion that this translates into a unit cost per resource assigned. Finally, the customer must accept the terms under which name or address space is assigned. In the case of IP address space, these include the contractual term that the assignment is only valid for so long as the criteria of the assignment are valid [ref 1]. As soon as the original criteria no longer apply, the address space must be returned without penalty or premium to the assigning registry. 4. Special Case Registries --------------------------- As indicated above, there are certain exceptions to the market principle in the Internet registration services. These occur where, by virtue of their location in the hierarchy of Internet registration, certain registries find themselves in a monopoly position. In the case of namespace, this applies to top-level domain (TLD) registries (in Europe, these are all country registries), as well as certain administratively unique second-level domain registries (such as .co.uk, .ac.at etc). When it comes to IP address allocation, regional registries constitute monopolies within the communities they serve. In Europe, one instance is the RIPE NCC, registry for the European region [ref 2]. Other possible examples are the last resort (non-provider) IP registries, although nowadays the customer has an alternative to their services. It is important that there be transparency in the procedures and accounts of such "special case" registries. They must not generate, nor be seen to generate, excessive profits by virtue of their monopoly position. 5. Recommendations ------------------- To meet with the objectives outlined in this paper, it is recommended that **all** registries: - publish their operating procedures; - publish details of the services they offer and the conditions and terms that apply, including scales of tariffs if applicable; - explicitly publish the fact that they do not sell name or address space as such. As for **"special case"** registries as defined above, it is recommended that where such a registry charges for service, it should, in addition to complying with the recommendations listed above: - relate charges to costs of operation and apply all revenues to such costs; - regularly publish a budget of its anticipated operating costs and revenue; - publish guidelines and apply these uniformly; - ensure equality of access to registration services; - achieve consensus within the community it serves as to the disposal of any profits; - regularly publish accounts of income and expenditure; - refrain from using their unique position as leverage in any other business venture. Daniel Karrenberg and Mike Norris 15th April 1996 References ---------- [1] "European Internet Registry Policies and Procedures" by Orange, C., Kuehne, M., Karrenberg, D. (ripe-104, 1996) [2] "RIPE NCC - Delegated Internet Registry" (ripe-112, 1994)

1 0

Announcement for Local IR Training Course in Amsterdam
by RIPE NCC Training 16 Apr '96

16 Apr '96

* * * Announcement * * * Local Internet Registries Training Course Date: Monday 20th May, 1996 Time: 0900 - 1700 Venue: Amsterdam, The Netherlands Amsterdam Airport Schiphol Conference Centre 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 most recently paid the signup fee. If it is still oversubscribed, we will accept only one person per new local registry. We will provide additional course dates 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, Carol Orange --- Course Outline -------------- We will provide a slidebook and a reader on the day of the course, as well as electronically. 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 [ Monday 20th May 1996, Amsterdam, The Netherlands ] %END

1 0

Local IR mtg - draft agenda
by mnorris＠dalkey.hea.ie 16 Apr '96

16 Apr '96

Please see the following draft agenda for the meeting of the Local IR WG meeting at RIPE 24. The meeting is scheduled for 14:00 - 15:30 on Monday 22nd April, but I will ask for more time if people feel we need it. Comments and ideas are very welcome. Cheers. Mike RIPE 24 - 22-24 April 1996 Local IR Working Group D R A F T A G E N D A 1. Preliminaries - (auto?)select a minute-taker - agree agenda, times 2. RIPE 23 - minutes - actions outstanding 3. Reports from registries - European regional (RIPE NCC) - other registries, significant events, war stories - other regionals 4. IP Address Space Assignment Procedures - ripe-104 - supporting documentation 5. Charging by Local IRs - RIPE NCC charging model - paper by Karrenberg and Norris 6. Training - RIPE training courses - Local IR workshop 7. Input/Output with other Working Groups - Database - Routing - DNS - NetNews - other 8. Global registry coordination 9. Reverse domains - counts, errors - administration 10. AOB

1 0

Reminder: Local IR Workshop in Berlin
by RIPE NCC Training 16 Apr '96

16 Apr '96

Dear Local IR's, We would like to remind you of the Local-IR workshop in Berlin next week. There are still some places free. ---------- At the last RIPE Meeting in Amsterdam it was decided to have a Local Internet Registries workshop again in addition to the normal Local IR WG Meeting. The purpose of this workshop is to discuss operational procedures and experiences among LIRs as well as between LIRs and the NCC. The workshop will not be minuted and details about experiences discussed will be kept in strict confidence. The workshop is *not* intended for formal discussions and decisions about procedures as these things are done by the Local-IR working group. This workshop will be organised in conjunction with the 24. RIPE Meeting in Berlin. It will be held on Monday, 24th of April approximately from 9am til 12 am. The workshop is open exlusively for Local IR staff. To have a useful and interactive workshop the attendance is limited to 40 people. In case the workshop is oversubscribed we will limit attendance to one attendee per LIR on a "first-come-first-served" basis. Therefor we advise you to reply asap if you are interested to attend this workshop. We will send out (electronic) tickets to registrants. Only people with ticket will be admitted to the workshop. Preliminary Agenda: - ripe-104++ - how to adopt policy changes in daily operations - reverse delegation - tools - war stories Details of the exact venue and schedule will be distributed later to the registrants. If you have further questions, please don't hesitate to ask. Kind Regards, Mirjam Kuehne Manager NCC Registration Services =========================================================================== Our handling of ALL meeting registrations is fully automated. To register for the workshop, please complete the registration form and send it to <training(a)ripe.net>. PLEASE FILL THIS OUT AS SPECIFIED. Please add in a value in the `box' area marked between the square brackets (i.e. "[" and "]" s). Note this is what will be used for your badge if you have requested one and for the attendee list so please take care to fill it in correctly. You will receive a notification message that your request has been processe d. If however, you have any questions about the meeting or your registration form, please send your completed form to <ncc(a)ripe.net>. %START PART 1 - Registration 1) Your name Enter First name, Last name in FULL (remember this is on list and badge) e.g. John Doe Mary-Beth Walton %NAME [ ] 3) Your Organisation/Institution %ORG [ ] 4) Your e-mail address %EMAIL [ ] 5) Country code of organisation e.g. IT FR DE %CTRY [ ] %END

1 0

Announcement for Local IR Training Course in Budapest
by RIPE NCC Training 10 Apr '96

10 Apr '96

* * * Announcement * * * Local Internet Registries Training Course Date: Friday 10th May, 1996 Time: 0900 - 1700 Venue: Budapest, Hungary (Further details about the location will be announced at a later time). 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 most recently paid the signup fee. If it is still oversubscribed, we will accept only one person per new local registry. We will provide additional course dates 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, Carol Orange --- Course Outline -------------- We will provide a slidebook and a reader on the day of the course, as well as electronically. 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 [ Friday 10th May 1996, Budapest, Hungary ] %END

1 0

RIPE23: Draft Minutes available: ripe-m-23
by RIPE NCC 09 Apr '96

09 Apr '96

RIPE Minutes Announcement ------------------------- The RIPE23 minutes are now available from the RIPE document store : FTP Access ---------- All RIPE minutes (and more) 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/minutes/" followed by the command "get filename". The relevant filenames for this document are: ripe-m-23.txt for the ASCII version ripe-m-23.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(a)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". 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. SEND ripe/minutes/ripe-m-23.txt

1 0