- ripe-list - mailman.ripe.net

RIPE NCC Activities, Expenditure and Charging Scheme 2001 - RIPE-213
by RIPE NCC Document Announcement Service 12 Sep '00

12 Sep '00

[apologies for the duplicate mails] New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. Title: RIPE NCC Activities, Expenditure and Charging Scheme 2001 (RIPE-213) Short content description ------------------------- This document contains the planned activities for the RIPE NCC and the associated expenditures for the year 2001 as well as the charging scheme to ensure the necessary revenues. Accessing the RIPE document store --------------------------------- The RIPE document store is available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-213.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-213.txt plain text version You can also access the RIPE documents in HTML format via WWW at the following URL: http://www.ripe.net/ripe/docs/ripe-213.html Kind Regards, Paul Rendek Communications Manager RIPE NCC

1 0

None
by NCC Role Account 12 Sep '00

12 Sep '00

Reply to: ncc(a)ripe.net From: RIPE NCC Document Announcement Service <ncc(a)ripe.net> Subject: RIPE NCC Activities, Expenditure and Charging Scheme 2001 (RIPE-213) X-Phone: +31 20 535 4444 X-Fax: +31 20 535 4445 Date: Tue, 12 Sep 2000 16:10:22 +0200 Sender: ncc(a)ripe.net New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. Title: RIPE NCC Activities, Expenditure and Charging Scheme 2001 (RIPE-213) Short content description ------------------------- This document contains the planned activities for the RIPE NCC and the associated expenditures for the year 2001 as well as the charging scheme to ensure the necessary revenues. Accessing the RIPE document store --------------------------------- The RIPE document store is available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-213.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-213.txt plain text version You can also access the RIPE documents in HTML format via WWW at the following URL: http://www.ripe.net/ripe/docs/ripe-213.html Paul Rendek Communications Manager RIPE NCC

1 0

Topics for todays ICANN ASO workshop at 1700
by Hans Petter Holen 12 Sep '00

12 Sep '00

Dear friends of RIPE; I have asked for a timeslot on this RIPE meeting to have a more informal Worksop style of environment were it is possible for those of you with particular interest in the work going on in the ICANN ASO and in the Address Council in particular. We will of course have a report from the AC in the lir-wg (as usual) and maybe even at the RIPE plenary at the RIPE chairs discretion. My thoughts behind this particular format at this particular meeting is to allow for the possibility of even more preparatory discussions in even more details than we usually have time for. Ideally I would have liked the meeting to happen later in the week, but not even the magic of the RIPE NCC meeting staff was enough for that to happen (we simply have to many competing for the same slots). The following rather broad topics lies on the Address Councils table, and will be discussed by the AC, ICANN and the RIRs at a physical AC meeting in Brisbane just after the APNIC meeting in October. This effort is thus an attempt to seek advice from the community before these discussions to satisfy the basic requirements for openness and transparency. 1) What is global policy ? There are several dimensions to this discussion: - replace RFC 2050 with a ICANN Address policy document - what is the distinction between regional and global policy - do we understand and appreciate the differences between the regional policies ? - differences between v4 and v6 with respect to the last item - what's the role/work mode of the AC ? to make the definite address policy, or to work on issues as they show up - were is the border between a service level contract and policy issues. - are there other operating guidelines for the ICANN - IANA than the global addressing policy ? 2) Revising the MOU In the widest sense: are there things in the present MOU that needs more work and needs to be changed ? 3) Addressing the essence of the ad Hoc committee, i.e. discussing how to best address new addressing needs emerging for 4) How to promote ipv6 ? 5) Emerging RIRs How to enable and support the emerging RIRs to establish regional policy processes ? The discussions in just above an hour needs not be limited to these topics. So, if you have a particular interest in influencing your AC members thinking on these or other matters, be there ! Sincerely, Hans Petter Holen Address Council Chair

1 0

Call for Nominations - ASO Address Council
by RIPE NCC Staff 12 Sep '00

12 Sep '00

Call for Nominations for Representatives to the ASO Address Council - RIPE NCC Region Dear colleagues, This is a call for nominations of individuals from the RIPE NCC region to serve on the ASO Address Council. During November 2000, one RIPE NCC Region Address Council seat will become vacant and will be filled for the next three years by an individual nominated through this open call. This document describes the functions of the ASO and the Address Council, as well as the nomination and selection processes. If you are interested in nominating an individual, or if you are interested in being nominated as a member of the Address Council, please read this document carefully. 1. The Address Supporting Organisation - -------------------------------------- The ASO was formed in August 1999 as a consensus-based advisory body within the ICANN framework, through a Memorandum of Understanding (MoU) signed by the current Regional Internet Registries and ICANN. The ICANN Bylaws (http://www.icann.org/general/bylaws.htm#VI-A) assign to the ASO the responsibility for the development of global policies relating to the distribution and registration of Internet address space, inter-domain routing identifiers and that part of the DNS name space that is used to name these addresses and identifiers. More information about the ASO is available at: http://www.aso.icann.org 2. The Address Council - ---------------------- The ASO Address Council co-ordinates the process of policy development in areas within the responsibility of the ASO, according to procedures defined within the MoU and by the Address Council itself. Specifically, these include the hosting of an annual open General Assembly meeting (the first of which was held in Budapest in May 2000) and attending regular meetings either by teleconference or face-to-face, at which policy issues and submissions may be considered. The other major responsibility of the Address Council is the appointment of individuals to fill ASO seats on the ICANN Board of Directors, according to procedures defined within the MoU. More information on the Address Council is available at: http://www.aso.icann.org/ac/ 3. The Role of Members of the Address Council - --------------------------------------------- Each member of the Address Council is expected to serve for a period of 3 years. The terms of appointment of the current initial AC members were staggered terms of 1, 2 and 3 years to allow one third of the Address Council to be replaced in each subsequent year. No member of the Address Council is entitled to any compensation from the ASO. No member of the Address Council can be indemnified by the ASO, nor can the ASO obtain insurance coverage relating to the liability of the actions of members of the Address Council. AC members do not represent any RIR, nor do they act as representatives of any other body. They are appointed in their individual capacity, and their membership cannot be proxied by any other individual or organisation. 4. Address Council Nominations Process - -------------------------------------- The term of Sabine Jaume who has served as an initial AC member for the past year has expired. One individual from the RIPE NCC Region will be selected to serve on the Address Council for a term of three years. The selection will be made through an open election process, from the set of individuals who have been nominated within this process. Any individual may be nominated, with the exception of any staff member of any Regional Internet Registry. Self-nominations are permitted. Nominations should be sent by email to <nominations(a)ripe.net>, by midnight CET on 30 September 2000. The information included with the nomination is to be in English, and should include: Name of Nominee: Country of residence: Organisation: Email Address: Postal Address: Biographical information: Motivation for nomination: Name of nominating individual: Organisation: Email Address: All nominees will be contacted via email to confirm their willingness to serve on the Address Council. If a nominee cannot be contacted via email, or does not respond, then their nomination will not be confirmed and they will not be eligible for election to the Address Council. All confirmed nominations will be listed on the RIPE NCC web site after they are confirmed. All nominees will have the opportunity to submit a written statement in support of their nomination for publication on the web site. In addition, others may express support for nominated individuals simply by completing and submitting the nomination form provided above. 5. Address Council Selection Process - ------------------------------------ The process for selection of the nominee to serve on the Address Council will involve an open election. Due to the 90 day lead time needed for a call for nominations prior to a RIPE NCC region policy meeting, the selection process will not be held at the RIPE 37 meeting, 12-15 September 2000, in Amsterdam. Two selection processes have been proposed. The first follows the voting process outlined in the MoU. The selection procedure would take place at the RIPE 38 meeting in January 2001 in Amsterdam. The second process currently being discussed involves implementing an electronic voting procedure as it would allow for more participation in the selection process and could bring the process forward. This procedure would be discussed prior to the RIPE 37 meeting and announced in the LIR-WG meeting. Hans Petter Holen, LIR-WG Chair, will initiate discussions about this procedure on the lir-wg mailing list. Important Dates: 30 September 2000 - deadline for Address Council nominations Regards, Hans Petter Holen

2 1

Hostmaster Center at RIPE 37!
by Nurani Nimpuno 02 Sep '00

02 Sep '00

Dear all, For all LIRs attending the coming RIPE meeting in Amsterdam, (12-15/09/00), the RIPE NCC is proud of offering a new service! At the week of the RIPE meeting, there will be a Hostmaster Center in the meeting area with two hostmasters constantly available to the LIRs! You will be able to drop by at any time during the meeting and you can also set appointments with hostmasters. The purpose of the Hostmaster Center is to make it possible for you to discuss an on-going request, policies and procedures or any other issues pertinent to the Registration Services, with a hostmaster. Furthermore, two workstations with connectivity will be in place, enabling the hostmasters to look at your particular request if necessary. The RIPE meetings have always been used as an opportunity for our members to meet up with the hostmasters handling their requests and we wish to further facilitate this by making ourselves more available to our members. We hope you find this service useful and we look forward to seeing you at RIPE37! Kind regards, Nurani Nimpuno Registration Services Manager RIPE NCC

1 0

ANNONCEMENT: LIR Tutorial at RIPE37
by Nurani Nimpuno 01 Sep '00

01 Sep '00

Dear all, We are happy to announce that the RIPE NCC will be holding an IP Request Tutorial at the coming RIPE Meeting. The tutorial is scheduled for Friday the 15th of September at 14.00-17.00. This tutorial contains selected parts from the LIR courses we provide to our members throughout the RIPE NCC service region and contains the following concentrated sections: - How to Request Address Space - Completing the Request Form - Evaluation - Specific Assignment cases - New Allocation It is not necessary to register and you are all more than welcome to attend this tutorial which is open for anyone attending the RIPE meeting! Kind regards, -- Nurani Nimpuno Registration Services Manager RIPE NCC

1 0

Final RIPE 37 Meeting Reminder
by RIPE NCC Meeting Registration 31 Aug '00

31 Aug '00

Dear Colleagues, [ Apologies for duplicate mails ] We would like to remind you that in order to benefit from the 50 EUR discount, we need to receive your registration with credit card details before or on Friday 1 September. The preregistration for RIPE 37 in Amsterdam will close on Wednesday, 6 September 2000. On-site registration will open on Tuesday, 12 September 2000. For RIPE 37 Meeting information, the schedule and hotel information, please visit the following web site: http://www.ripe.net/ripe/meetings/current/ripe-37/index.html We hope to see you all in Amsterdam. Kind regards, Sylvana Wenderhold RIPE Meeting Registration ----------- Confirmation of Registration: For your convenience you can register using our secure website at: https://www.ripe.net/cgi-bin/mtgreg (encrypted form) http://www.ripe.net/cgi-bin/mtgreg (non-encrypted form) If you still prefer not to send your credit card number using an encrypted transfer method, we have prepared a fax form. This form is attached to the acknowledgement of your registration. You will receive a second acknowledgement by e-mail as soon your payment has been processed. In addition, you will find the receipt for your payment in your conference envelope. Participants requiring a visa to enter the Netherlands are advised to begin the required procedures as soon as possible. The RIPE Meeting organisers are pleased to provide letters of invitation to those attendees requiring them. Should you have any further questions, please do not hesitate to contact us at <meeting(a)ripe.net>. --------------------------------------------------------------------------- Registration is also possible and easier online at: http://www.ripe.net/cgi-bin/mtgreg https://www.ripe.net/cgi-bin/mtgreg %START Do not change the following field %MTG [ ripe37 ] Please add a value in the 'box' area marked between the square brackets (i.e. "[" and "]" s). If values are already supplied between the brackets, please delete all values except one. PART 1 - Registration Note this is what will be used for your badge and for the attendee list, so please take care to fill it in correctly. 1) Your name Please enter your first name only. e.g. John , Mary B. %NAME [ ] Please enter your last name next e.g. Doe %SURNAME [ ] 2) Your Organisation/Institution %ORG [ ] 3) Your Organisation's Complete Postal Address e.g. Singel 258, 1016 AB Amsterdam, The Netherlands %ORGADDR [ ] 4) Your Organisation type e.g. Commercial (com), Government (gov), Association (aso), Educational (edu), Other (oth) (please delete one option so your choice is in the form) %ORGTYPE [ com / gov / aso / edu / oth ] 5) The NCC Reg-id of your Organisation %REGID [ ] (Only if you represent a Local Internet Registry) 6) Your e-mail address %EMAIL [ ] 7) Country code of organisation e.g. IT FR DE %CTRY [ ] 8) Do you want to attend the Newcomers Orientation Talk ? (please delete one option so your choice is in the form) %INTRO-MTG [ no / yes ] 9) Do you want to attend the EOF? (please delete one option so your choice is in the form) %EOF [ no / yes ] 10) Do you want to attend the Multicast Routing Workshop? (please delete one option so your choice is in the form) %MULTI [ no / yes ] 11) Do you want to attend the DNS-sec Workshop? (please delete one option so your choice is in the form) %DNS [ no / yes ] PART 2 - Payment of Registration Fees WARNING!! - Note that sending your credit card information via e-mail is in principle not secure. The payment information will be transmitted in clear via e-mail. If you do not want to do this, please leave your credit card details blank in this form, and send them to us by fax. Please do not forget to mention your name and organisation on the fax, so there will be no risk in us getting confused. Our fax number is: +31 20 535 44 45 1) Method of payment. Payment in advance is greatly preferred. (please delete all choices except one) %PMETH [in advance; credit card / at meeting; credit card / at meeting; cash ] ( *NB: please note aforementioned reduction when paying in advance *) 2) Type of credit card (please delete all choices except one) %CTYPE [ VISA / American Express / Mastercard / Eurocard ] 3) Amount to be paid %AMT [RIPE Meeting only incl. reduction; EUR 230 / RIPE Meeting only excl. reduction; EUR 280 / RIPE Meeting plus RIPE dinner incl. reduction; EUR 295 / RIPE Meeting plus RIPE dinner excl. reduction; EUR 345 ] Payment details sent online cannot be processed after, September 1, 2000 with this form. You are welcome to send in your personal data with this form to register, but the actual payment can then only be made at the meeting itself on September 12, 13, and 14, 2000. ( again: please choose reduction ONLY when paying in advance ) 4) If you are coming to the RIPE dinner, indicate if you want a vegetarian meal. (please delete one option so your choice is in the form) %VEGGIE [ no / yes ] %END

1 0

Draft Plenary Minutes RIPE 36
by RIPE NCC Meeting Registration 23 Aug '00

23 Aug '00

Dear Colleagues, [ Apologies for duplicate mails ] Please find below the RIPE 36 draft plenary minutes. The draft plenary minutes are also available on our website at: http://www.ripe.net/ripe/meetings/archive/ripe-36/plenary-minutes.html Kind regards, Sylvana Wenderhold --------- 36 RIPE Meeting Plenary Minutes - DRAFT RIPE 36 Budapest, 16-19 May, 2000 Plenary Session Chair: Rob Blokzijl Scribe: Sylvana Wenderhold 1. Opening and welcome 2. Agenda 3. Minutes from RIPE 35 4. From the Chair 5. News from ICANN - Mike Norris (MITF) - Mike Roberts (President and CEO) 6. Reports from the RIPE NCC 7. Reports from: - ARIN (Richard Jimmerson) - APNIC (Paul Wilson) - AfriNIC (Antony Brooks) - LacNIC (German Valdez) 8. New developments in Transatlantic cable systems (Daniele Bovio) 9. Reports from the Working Groups 10. Next RIPE meetings 11. AOB 12. Close 1. - Opening and welcome RIPE Chair Rob Blokzijl welcomed the participants to the RIPE 36 meeting. 2. - The agenda Agenda item 5 was shifted to a later time, as Mike Norris had not yet arrived. 3. - Minutes from RIPE 35 The minutes were approved. 4. - From the Chair Rob thanked Matav and Matav net very much for providing the connectivity for the meeting. He also thanked Elender for the computers supplied in the terminal room. The Chair urged participants to clearly state their names and use the microphone when asking questions. Louis Touton addressed the audience concerning the ICANN Independent Review Panel Nominating Committee. This Nominating Committee consists of two individuals appointed by the ICANN Address Council, along with two by the ICANN Names Council and two by the ICANN Protocol Council. The Address Council has been asked to identify its two appointments and is seeking recommendations from the community. The Nominating Committee to which appointments are being made is responsible for nominating the members of the ICANN Independent Review Panel, which addresses complaints from the community that ICANN is violating its bylaws, etc. Members of the Independent Review Panel should be current or retired judges, or people with the legal training to be judges. Since those serving on the Independent Review Panel will not be compensated, the Nominating Committee members appointed by the Address Council should be situated to persuade well-qualified individuals to volunteer to serve on the Independent Review Panel. Thus, ideal appointments to the Nominating Committee would be those people who know judges. One important condition is that the people appointed cannot be directly involved with the ICANN process (i.e. they cannot be ICANN Directors, staff, or advisors, members of the Address Council, etc.). 5. - News from ICANN - Mike Norris Please see the slides of Mike Norris's presentation at: http://www.ripe.net/ripe/meetings/archive/ripe-36/presentations/ Mike Norris informed the audience about the ICANN At Large structure and the ASO. The ASO is well represented with Hans Petter Holen, Wilfried Woeber and Sabine Jaume from this region together with three members from the Americas and three from the Asia Pacific region. Rob Blokzijl sits on the board of ICANN itself. ICANN board elections are coming up in November. Registration is open to anyone. Mike would like to see more people register for the At Large membership. For information about ICANN and the elections please visit: http://www.icann-ineurope.org - Mike Roberts (President and CEO) Rob was proud to introduce Mike Roberts who was one of the highest ICANN officials ever to visit a RIPE meeting. Mike Roberts provided a few words of where ICANN is today and where it is going. He explained that ICANN is a product of one of the Internet's many scaling crises, in fact created as a result of the major success of the Internet. He enlightened the audience with some background information about how ICANN was established as a non-profit corporation independent from the US government. It has become a very diversified organisation with an international perspective. The goal is an independent ICANN with very little government involvement. Mike Roberts pointed out three difficult issues for ICANN at this time: A. Manner in which new generic top level domain should be introduced. The question is not should there be more, but under what circumstances and conditions should there be more. B. Revisions to RFC 1591 ICP 1. (Domain Name System Structure and Delegation) This deals with the relationship between the US government and the top level domain administrators. These relationships need to be formalised. C. Internet addressing should receive as much attention as the names issue has received. 6. - Reports from the RIPE NCC Axel Pawlik provided the RIPE NCC status report: http://www.ripe.net/ripe/meetings/archive/ripe-36/presentations/ His presentation focused on three main areas: - Services - Co-ordination - RIPE NCC Priorities Registration Services: The workload around the allocation of IPv4 addresses is constantly increasing. Still there was good news; the wait queue is down to five days from seven days. IPv6: The revision of the policy document is still ongoing. Membership: A milestone of 2000 members has been reached. The membership is constantly increasing at a rate larger than expected. New members per region 1999: Europe 258 (551), Middle East, 8 (31), Africa 3 (8) Number of requests: This year the number of requests has not dropped under 1600 per month. RIPE NCC Hostcount: It is beyond 11.000.000 after the first quarter of this year. RIPE Database: There was a problem with the database in March. It was down for five hours. Updates were kept aside and handled later. There was a small incident the day before the RIPE 36 plenary session. However, in the event of such occurrences the spare server takes over, so these problems will go unnoticed in the future. Data protection: A lot of data is protected. PGP is the most secure way to protect data, yet only two percent is protected using PGP. Axel encouraged the members to start using PGP, particularly as it is offered for free. At the next RIPE meeting there will be additional effort to promote this mechanism. Database reimplementation: The project is nearly finished. Currently we have a server prototype. The RIPE NCC has set up a test database for users of the RIPE database to send trial updates to. External Communications: - RIPE NCC Annual Report 1999 The 1999 Annual Report has been sent to members. Copies are available at the RIPE NCC <ncc(a)ripe.net> - RIPE NCC awareness RIPE NCC receives many invitations to give presentations and participate in panels. The RIPE NCC has also been busy meeting with various new players in the industry. - New LIR course material successfully introduced The first five courses taught with the new material have been very well received. Locations for upcoming LIR Training Courses (courses up to September will be held in): - Athens - Prague - Amsterdam - Riyadh - Madrid - Geneva - Paris - Berlin - Vienna More information is available at: http://www.ripe.net/ripencc/mem-services/training/index.html New projects: - Routing Information Service (RIS) For more information, please see the following presentation: http://www.ripe.net/ripe/meetings/archive/ripe-36/presentations/ - Test Traffic Measurements (TTM) - Moving from an experimental project to a regular service - Preparing roll out the next series of test-boxes - Improving and adding components based on the TTM data Regional Internet Registry (RIR) Co-ordination: - RIR retreat - Attended ARIN, APRICOT and AfriNIC meetings Axel welcomed the various members of the other RIRs at the RIPE 36 meeting in Budapest. He reported that the co-ordination between the RIRs has been very successful so far. RIRs have decided to split on a split of the total amount of the contribution toward ICANN's first financial year that comes to an end at the end of June 2000. (RIPE NCC: 50%, ARIN: 35%, APNIC, 25%) The Address Supporting Organisation (ASO) general assembly meeting is gathering for the first time after the RIPE meeting in Budapest on Friday, 19 May 2000. Axel invited the RIPE NCC membership to join the meeting. RIPE NCC Priorities: - Continuing to ensure and further improve stable, reliable and high quality services The wait queue is down. However, the RIPE NCC will continue to work towards getting the queue down to a level that is acceptable to all members. - Respond to members' needs and develop and propose services as needed - Further increase RIPE NCC and RIPE awareness Question from Christian Panigl: Why does the RIPE NCC fund 50% of the ICANN-ASO budget intended for RIRs and ARIN only 35%? Axel: This is the first year's split between the registries. We have looked at the degree of establishment, budget and turnover. These numbers point to this split. Rob: The money comes from the RIPE NCC budget and has been approved by the membership. Axel introduces Joao Silva Damas who presented a proposal to revise the RIPE document store. Most documents are fairly static and do not require frequent updating. Some however, change frequently (policies and procedures document, the request forms etc.). If they are referenced in other documents and the document number changes, these documents need to be updated as well. This requires a lot of work. It would make it easier if the numbers would remain the same. Joao proposes to have an option to freeze the number of certain documents (the ones that change frequently). After lively discussion it was decided to keep the system as it is and review the RIPE NCC's internal procedures on document revision. Later a detailed proposal will be presented to the RIPE community. Generally there was agreement that more active use of the document titles rather than its numbers would make referencing these documents easier. 7. - Reports from: (ARIN, APNIC, AfirNIC and LacNIC) ARIN (Richard Jimmerson) Please see the presentation at: http://www.ripe.net/ripe/meetings/archive/ripe-36/presentations/ Richard Jimmerson introduced himself as the Registration Services Manager at ARIN. Structure of ARIN: - currently 1001 members - six board of trustees members - advisory committee of 15 members - president - executive assistant - four divisions 1. registration services group 2. member services division 3. engineering division 4. administration division ARIN currently has 23 staff members. ARIN activities are very much the same as other RIRs. Some highlights from the presentation: - Fees revised for registration category level upgrades ARIN no longer bills for upgrades. ARIN will now invoice the organisation at the new registration category level on their next anniversary date. - Maximum allocation size increased to /13 A handful of organisations outgrew the /14. To meet their requirements, the maximum allocation size has been increased to /13. - Postal address for residential reassignments may be omitted Individuals with a /29 or smaller still need to be listed in the ARIN database, but instead of listing the postal address they now use the ISP contact information. - ARIN training soon to be offered ARIN does not offer training, but will soon be offering training within their region on a request basis. One difference with the RIPE NCC is that ARIN issues address space based on an organisation's three month needs instead of a one year need. They require members to gives updates on their address space every three months. ARIN then reserves address space for one year. If the organisation does not need this space within one year, it will be allocated to another organisation. ARIN has a registration services helpdesk and saw a 74% increase in the number of phone calls received in the last year. The type of phone calls received are from people who need help filling out templates, and have questions about policies, guidelines and criteria. ARIN has received 6 requests for IPv6 allocation. They have approved and allocated 4 at this time. ARIN priorities: - Development of new tools to aid hostmasters in daily activities - Developments of external training materials - Increase level of customer service ARIN staff visits many meetings and conferences to increase awareness about their organisation. Questions: Jeroen Bet: How does ARIN ensure quality of customer services? Richard: We looks at the quality of mail that has been sent out. We also look at the performance of the individual hostmasters. Sometimes members are approached to discuss any problems. APNIC (Paul Wilson) For a presentation about APNIC please see: http://www.ripe.net/ripe/meetings/archive/ripe-36/presentations/ - APNIC staff has doubled in the last year. They have 16 staff at present but will grow to 21. - Almost doubled the membership. APNIC experienced a decrease growth during the Asia crisis, but now records are broken monthly in terms of membership growth. - They have issued an equivalent /8 in the last 16 months of operation. Allocation rate is picking up dramatically. - Paul explained that they align their charging model to the number of allocations to an organisation. This would naturally place the organisations into the small/ medium/ large/ very large categories. APNIC in 2000. - Software automation - to support resource and allocation processes - Customer support - help desk and member care programme - Documentation - improved user interface - on-line help with forms - translation of core documents Overall, all aspects of APNIC are clearly growing. APNIC meeting will take place 25-27 October, 2000 in Brisbane, Australia. APNIC welcomes all who are interested to participate in the APNIC meeting. Questions: Question: How many IPv6 allocation requests has APNIC received? Paul: We have had 14 requests, and allocated 12 subTLAS so far. Japan is very active in the IPv6 community. There has been a Chinese request as well and we expect a lot more requests in the future. AfriNIC (Antony Brooks) Please see Ant's presentation at: http://www.ripe.net/ripe/meetings/archive/ripe-36/presentations/ In his presentation, Ant Brooks elaborated on the challenges AfriNIC is facing. Despite a consensus in Africa about the establishment of AfriNIC, it has been difficult to realise any concrete structure. 1999 was the year of anti-progress. Among the reasons were the fact that they didn't have market representation and none of the submissions for a host country was workable. Particularly disastrous was the pull out of South Africa from the process, as 80% of the Internet activity is located in South Africa. Another problem has been the language barrier. There has been some Francophone and Anglophone tension in the region. This problem seems to have been solved now as much attention is given to simultaneous translation in French and English. Gladly, in 2000 there has been a great deal of progress. A lot of effort has been made to get South Africa involved once again. At the recent conference in Cape Town, AfriNIC reached a breakthrough. There was both strong geographic and market representation. The RIRs were all represented at the conference, leading to a warm support of AfriNIC. Where is AfriNIC today? - Structure Bylaws accepted by principle Membership structure (voluntary) Board of Trustees Executive staff Funding model (but without figures) - Representation Interim Board of Trustees accepted ASO observer selected (Antony Brooks) Two listeners chosen (Mouhamet Diop, Nii Quaynor) - Working groups BoT advisory committee Policy working group Antony pointed out that the only way AfriNIC would become a success is by creating stability. He explained that large ISPs worry about the success of AfriNIC specifically because they are concerned about the lack of stability as a regional registry. Small ISPs on the other hand, worry about the minimum allocations. Not many organisations need large allocations at this point in time. There is a propsal to have the initial AfriNIC staff be located at the RIPE NCC premises. This would ensure the desired stability as it offers both technical and financial solidity. The other RIRs strongly advise against the suggestion ofmultiple locations for the office in Africa. - Possible pit-falls Lack of a clear path to the final goal Financial viability Taking Africans out of Africa (there are not enough skilled people in the region) http://www.afrinic.org LacNIC (German Valdez) Due to German's late arrival, this presentation did not take place. German gave his presentation at the ASO meeting (Friday, 19 May 2000 in Budapest). Please see the ASO Meeting minutes when they become available on: http://www.aso.icann.org 8. - New developments in transatlantic cable systems (Daniele Bovio) Please see the presentation at: http://www.ripe.net/ripe/meetings/archive/ripe-36/presentations/ 9. - Reports from the Working Groups Database Working Group ---------------------- 48 participants Scribe: Nigel Titley Chair: Wilfried Woeber Wilfried will receive help from Nigel Titley and Ulf Kieber with the working group in the future. Nigel will take care of the PR part of it and Ulf will help co-ordinate the working group. The chair has received approval from the working group on this issue. Reports from RIPE NCC: - Operational update - Software re-implementation Report form APNIC by Paul Wilson: - CA activities, (ask for representation) Results and actions: - To work even more closely with CENTR to move the domain data to their own database. Ask CENTR to present a progress report regularly. - To arrange for a digital signature and certification course workshop for RIPE 37 - Activity plan for RIPE NCC in 2001 Input from other working groups is welcomed EIX "exchange" object => propsosal invited - Use of XML (for a common report template) => proposal invited There were no questions. IPv6 Working Group ------------------ 75 participants Scribe: Jeroen Bet Chair: David Kessens - A tutorial was given on Tuesday in addition to the regular working group meeting. It was very well attended. Participants had a chance to try IPv6 demo in terminal room. David reported on 6Bone developments. Status of IPv6 Allocation Guideline draft End-user assignments: It is currently discussed on which boundary end-user assignments should be made. Action on David: Summarise pro/cons to the findings and discussions and concerns brought forward to the list. There were no questions. LIR Working Group ----------------- 101 participants Scribe: Eamonn McGuiness Chair: Hans Petter Holen Wait Queue - Nurani and Joao presented substantial plans to improve the current situation - The wait queue is now down to eight days - The goal is to bring the queue down to two days - In order to complement the internal process a Task Force was formed comprised of members of the LIR WG. This task force will gather comment from the community on: - metrics such as the best possible delay - broken parts in the current process and policies - ways to improve communication flow They will report back to the working group in a short and clear document and deliver this to the RIPE NCC as input for the processes and policies review. Pre RIR address space - as a follow up question to the ARIN presentation the question on how to deal with address space predating the RIRs was raised. - The RIRs have a project to distribute the address space to the appropriate registry. Minimum allocation size Consensus on changing policy to: - The minimum allocation size will be /20 - Not before 01 August 2000 - Identify allocation size on RIPE address blocks and publish in a machine readably format by 15 June 2000 Please see the following URL for Hans Petter's complete presentation: http://www.ripe.net/ripe/meetings/archive/ripe-36/presentations/ Hans Petter also provided a glance at the agenda of the upcoming LIR working group in Amsterdam. There were no questions. Netnews Working Group --------------------- 13 participants Scribe: Felix Kugler Chair: Dave Wilson Two excellent presentations were given: Daniel Diaz (NHNS) Kai Siering (Flowmaps) The agenda for RIPE 37 will be very similar to the one for RIPE 36. The actions are being worked on. There were no questions. Anti-Spam Working Group ----------------------- Approximately 25 participants Scribe: Maldwyn Morris Chair: Rodney Tillotson Update spam: - I love you - not spam - Greeting card spam - Collateral spam -Anti-spam ORBS discredited -Legislation EC directives, some opt-ins Codes of conduct - RIPE-206 well-received -BCP on opt-in lists -AUPs; new end users, different expectations -ISPs support their customers Technical Measure -filtering products and services Interaction with CERTS -Advice on responses -Reading mail (headers?) Next agenda will be similar. There were no questions. DNR Working Group ------------------ Participants: ? Scribe: Sharon Bush Chair: Kevin Meynell (in absence of Fay Howard) New members (now 30 + 2 associates) - Croatia .hr - Russia .ru - Japan .jp (associate member) ccTLD Funding of ICANN - ccTLDs required to pay 35% of 99/00 budget ($1.49m) - ICANN proposing 'domain name based split' - CENTR Excom advocating fee bands - discussion ongoing - Formalisation of relationship between ICANN/cc TLDs required Kevin elaborated on some results from the DNSSEC working group meeting. Common Registration Templates - Supported by some (all?) registrars - XML? - CENTR collecting templates to determine commonalties Neteka - Developed as alternative to BIND - Supports multi-lingual character sets - Software for associated services (e.g. mail) - http://www.neteka.com/. Russian ccTLD - operated by RosNIIROS - Registration Policies - Fees DNR Forum Activities Common Template Task Force - Feasibility of common templates - Format (e.g. XML) Data Protection - Examine zone file access - Document uses (e.g. statistics, host count, searching) - Work in conjunction with CENTR Legal Forum For a complete presentation, please visit the following URL: http://www.ripe.net/ripe/meetings/archive/ripe-36/presentations/ New Chairperson Two individuals have come forward to chair the next meeting. For now at least it will be on a meeting by meeting basis. The two people are Hans Nicklasson from Swip.net and Mally McLane from Planet Online. Sharon Bush from NetNames has offered to be the Secretary for the next meeting. Comment from Mike Roberts about the ICANN funding. He emphasised that ICANN is not a governmental authority. The proposed ccTLD allocations are not a tax. Kevin answered that the proposed model is not the way forward according to many ccTLDs, specifically in CENTR. Rob said he experienced a 'd�j� vu' looking back at when the RIPE NCC had just started. The outcome for the RIPE NCC is a mixture between the two models. There were no questions. Routing Working Group --------------------- 70 participants Scribe: Marek Bukowy Tutor: Stefano Previdi (Cisco) Chair: Joachim Schmitz During RIPE 36 there was a Multicast Routing Tutorial with 30 participants. Wilfried Woeber felt the tutorial was a big success. ftp://ftpeng.cisco.com/ipmulticast The Routing working group was a bit shorter as usual, as some speeches had been cancelled. Update to RIPE-178 (C. Panigl) Transition to RPSL (Andrei) - close to finish reimplemention - Phase II to start end of June - Extensive testing - call for testers http://www.ripe.net/ripencc/pub-services/db/reimp/index.html RIS - Status and plans (A. Antony) - http://www.ripe.net/ris - test prototype available - investigating issues around production Actions 31.R1 on RIPE NCC, D. Kessens and J. Schmitz Basic design for an IPv6 IRR -postponed- 32R1 on RIPE NCC, JLS.Damas Prepare draft document on issues of RIPE-181 to RPSL transition - in progress - 34.R1 on C.Panigl For RPSL assure mirror/whois capability with RADB - new - Draft Agenda RIPE 37 RPSL transition, phase III RIS, BGP anomalies, ... There were no questions. EIX --- 52 participants Scribe: Henk Uijterwaal Chair: Fearghas McKay IX reports Sfinx Amsix Linx Vix Hamburg RIPE Activity Plan Database object for IXs Peering contact attribute for AS Allocated IP address range BCP -for IX operations- Nic Lewis Tools List Peering tree decision paper Switching wish list - Mike Hughes EIX Ops list Action Items: Present proposal to DB working group BCP - process underway Tools - needs a co-ordinator Wish list - process underway Invited IX members to come and share their experiences. Keith Mitchell noted that there are now work items within the working group. We may need to revisit the charter as it says that there will be no work items. There were no questions. DNS Working Group ----------------- 98 participants Scribe: Vesna Manojlovic Chair: Ruediger Volk David Conrad: BIND 9 Bill Manning: Whiter DNS ? Preparing for DNS evolution Stable specifications / stable code ensure feedback operational => Protocol designer communities NL netlab/CENTR DNSSEC workshop Paper on moving domain delegation There were no questions. Test Traffic Working Group -------------------------- Approximately 30 participants Scribe: Rene Wilhelm Chair: Matthew Robinson There was a presentation by Henk. The slides are available at: http://www.ripe.net/ripe/meetings/archive/ripe-36/presentations/ A paper should be produced about the test traffic project and a table of contents will be available and sent to the mailing list soon. The test traffic project is becoming self sufficient in terms of funding. There is now a contest to produce a new logo and name (instead of ' I'm a member of the test traffic project') for the test traffic web pages. Matthew will present a prize to the winner at RIPE 37. More information about this can be found in the Test Traffic WG meeting minutes when they become available. There were no questions. 10. - Next RIPE meetings: RIPE 37 Amsterdam 12-15 September, 2000 RIPE 38 Amsterdam 23-26 January, 2001 RIPE 39 Bologna May, 2001 Geza thanked the audience for coming to Budapest. He invited everyone to join him on a walking tour of the city on Saturday. 11. - AOB There was no other business to discuss. 12. - Close Rob took the opportunity between the working group reports to thank the local hosts in Budapest Geza Turchanyi and Balasz Martos of Matav, Hungary. Rob thanked everyone for attending and hopes to meet all the participants again at the next RIPE meeting in Amsterdam on 12-15 September, 2000.

1 0

RIPE 37 Meeting Reminder
by RIPE NCC Meeting Registration 18 Aug '00

18 Aug '00

Dear Colleagues, [ Apologies for duplicate mails ] We would like to remind you that the registration for RIPE 37 in Amsterdam is open. * Please note the 50 EUR discount for early registries until 1 September 2000. For RIPE 37 Meeting information, the schedule and hotel information, please visit the following web site: http://www.ripe.net/ripe/meetings/current/ripe-37/index.html Confirmation of Registration: For your convenience you can register using our secure website at: https://www.ripe.net/cgi-bin/mtgreg (encrypted form) http://www.ripe.net/cgi-bin/mtgreg (non-encrypted form) If you still prefer not to send your credit card number using an non-encrypted transfer method, we have prepared a fax form. This form is attached to the acknowledgement of your registration. You will receive a second acknowledgement by e-mail as soon your payment has been processed. In addition, you will find the receipt for your payment in your conference envelope. Participants requiring a visa to enter Hungary are advised to begin the required procedures as soon as possible. The RIPE Meeting organisers are pleased to provide letters of invitation to those attendees requiring them. Should you have any further questions, please do not hesitate to contact us at <meeting(a)ripe.net>. Kind regards, Sylvana Wenderhold RIPE Meeting Registrations --------------------------------------------------------------------------- Registration is also possible and easier online at: http://www.ripe.net/cgi-bin/mtgreg https://www.ripe.net/cgi-bin/mtgreg %START Do not change the following field %MTG [ ripe37 ] Please add a value in the 'box' area marked between the square brackets (i.e. "[" and "]" s). If values are already supplied between the brackets, please delete all values except one. PART 1 - Registration Note this is what will be used for your badge and for the attendee list, so please take care to fill it in correctly. 1) Your name Please enter your first name only. e.g. John , Mary B. %NAME [ ] Please enter your last name next e.g. Doe %SURNAME [ ] 2) Your Organisation/Institution %ORG [ ] 3) Your Organisation's Complete Postal Address e.g. Singel 258, 1016 AB Amsterdam, The Netherlands %ORGADDR [ ] 4) Your Organisation type e.g. Commercial (com), Government (gov), Association (aso), Educational (edu), Other (oth) (please delete one option so your choice is in the form) %ORGTYPE [ com / gov / aso / edu / oth ] 5) The NCC Reg-id of your Organisation %REGID [ ] (Only if you represent a Local Internet Registry) 6) Your e-mail address %EMAIL [ ] 7) Country code of organisation e.g. IT FR DE %CTRY [ ] 8) Do you want to attend the Newcomers Orientation Talk ? (please delete one option so your choice is in the form) %INTRO-MTG [ no / yes ] 9) Do you want to attend the EOF? (please delete one option so your choice is in the form) %EOF [ no / yes ] 10) Do you want to attend the Multicast Routing Workshop? (please delete one option so your choice is in the form) %MULTI [ no / yes ] 11) Do you want to attend the DNS-sec Workshop? (please delete one option so your choice is in the form) %DNS [ no / yes ] PART 2 - Payment of Registration Fees WARNING!! - Note that sending your credit card information via e-mail is in principle not secure. The payment information will be transmitted in clear via e-mail. If you do not want to do this, please leave your credit card details blank in this form, and send them to us by fax. Please do not forget to mention your name and organisation on the fax, so there will be no risk in us getting confused. Our fax number is: +31 20 535 44 45 1) Method of payment. Payment in advance is greatly preferred. (please delete all choices except one) %PMETH [in advance; credit card / at meeting; credit card / at meeting; cash ] ( *NB: please note aforementioned reduction when paying in advance *) 2) Type of credit card (please delete all choices except one) %CTYPE [ VISA / American Express / Mastercard / Eurocard ] 3) Amount to be paid %AMT [RIPE Meeting only incl. reduction; EUR 230 / RIPE Meeting only excl. reduction; EUR 280 / RIPE Meeting plus RIPE dinner incl. reduction; EUR 295 / RIPE Meeting plus RIPE dinner excl. reduction; EUR 345 ] Payment details sent online cannot be processed after, August 31, 2000 with this form. You are welcome to send in your personal data with this form to register, but the actual payment can then only be made at the meeting itself on September 12, 13, and 14, 2000. ( again: please choose reduction ONLY when paying in advance ) 4) If you are coming to the RIPE dinner, indicate if you want a vegetarian meal. (please delete one option so your choice is in the form) %VEGGIE [ no / yes ] %END

1 0

RIPE Region Hostcount for July 2000
by RIPE Hostcount Maintainer 17 Aug '00

17 Aug '00

Dear All, below is the hostcount for July 2000. The table shows an increase since last month of over 380,000 (or 3,4%) to a total of about 11,775,000 hosts in the DNS in Europe and surrounding areas. The es domain shows the highest increase for July with approximately 110,000 hosts more than in June. Background information and more statistics are available at http://www.ripe.net/hostcount/ - Brief Notes on this Hostcount - The January, 2000 data had to be reused for uk due to problems in the last months with co.uk. The uk data is therefore, unfortunately, severely outdated. - Credits - I would like to thank all people who help me to create the hostcount every month by running a local count: ad Joan Marc Lauga am Edgar D Danielyan at Gerhard Winkler be DNS-BE Registration Office ch Marcel Schneider cy Vasoula Papapetrou cz Jiri Orsag de Peter Koch dk Morten Christensen eg EUN Staff es Susana Gayo. CSIC-RedIRIS fr Annie Renard gr Dimitris Zisiadis hr Ivan Maric ie Mike Norris il Netvision NOC Staff is Marius Olafsson it Maurizio Martinelli Daniele Vannozzi li Marcel Schneider lt Daiva Tamulioniene lu Alain Frieden mk Goran Muratovski mt Robert Sultana no Havard Eidnes pl Mirek Luc pt Joao Pagaime ro Eugenie Staicut ru Andrey Dobrotsvetov sk Lubos Elias sm Maurizio Martinelli Daniele Vannozzi tr METU Staff uk Robert Stone Kevin Hoadley If you have any questions, please don't hesitate to contact me. Kind regards, Lee Wilmot RIPE NCC RIPE DNS Hostcount Previous Count : Thu Jul 13 2000 This Count : Mon Aug 14 2000 CY SOA COUNTED DUPL REAL CHANGE ============================================================== ad 512 1903 752 1151 + 2 ae 1652 37171 907 36264 + 7797 al 55 252 24 228 + 5 am 620 3426 979 2447 + 97 at 103996 580074 161354 418720 + 14829 az 302 883 205 678 - 8 ba 209 2745 328 2417 + 68 be 21117 334764 38192 296572 - 6582 bg 996 20014 1832 18182 - 228 bh 62 1876 340 1536 + 6 by 142 2599 355 2244 - 74 ch 123993 433379 182759 250620 + 891 ci 205 674 250 424 + 10 cm 24 289 21 268 + 3 cv 15 107 85 22 + 1 cy 714 7670 527 7143 + 121 cz 66487 203240 58994 144246 + 541 de 1608436 6608823 4741955 1866868 + 44906 dj 15 54 14 40 0 dk 148765 495889 190459 305430 - 128 dz 45 237 27 210 - 71 ee 5467 42515 8333 34182 + 902 eg 1491 2994 843 2151 - 35 er 1 4 0 4 0 es 20247 527961 31030 496931 +109047 fi 18002 564482 43035 521447 + 60217 fo 424 1110 84 1026 + 4 fr 75188 1489027 126277 1362750 + 20878 ga 22 58 30 28 + 1 gb 2 24 0 24 0 ge 225 1494 214 1280 - 47 gg 629 1689 444 1245 + 17 gh 33 389 54 335 + 31 gi 346 1112 84 1028 - 313 gl 570 2734 285 2449 + 28 gn 3 325 134 191 0 gr 14613 100003 14116 85887 - 1610 gw 2 21 1 20 0 hr 2810 21239 6716 14523 + 172 hu 28200 185221 67633 117588 - 1511 ie 13166 127500 18358 109142 - 854 il 19644 172191 38947 133244 + 1821 im 363 1764 236 1528 + 160 ir 137 1678 336 1342 + 220 is 4175 35519 4371 31148 - 2990 it 157862 598474 159977 438497 - 22498 je 651 1658 348 1310 + 17 ke 768 5357 606 4751 - 32 kg 253 4007 460 3547 + 828 kz 1270 7810 1220 6590 + 175 lb 845 2784 800 1984 - 1120 li 3297 7758 4091 3667 + 169 lr 6 0 0 0 0 lt 4832 19248 2680 16568 + 303 lv 3040 26961 7229 19732 + 8 ma 938 3206 1482 1724 + 56 mc 297 775 328 447 + 7 mk 544 1719 345 1374 - 554 ml 27 287 18 269 + 1 mt 752 7898 1292 6606 + 85 ng 251 1492 821 671 + 512 nl 283404 1818195 449084 1369111 + 95310 no 36823 492163 35184 456979 + 5721 om 53 5779 2900 2879 - 1 pl 62068 356814 91837 264977 + 36260 pt 7077 80491 15039 65452 - 15229 qa 13 35 9 26 - 31 ro 6427 45553 8583 36970 + 671 ru 61261 423899 151280 272619 + 10028 sa 1314 3382 1225 2157 - 2101 se 47009 695264 61731 633533 + 27750 si 4084 23803 4364 19439 - 2023 sj 1 0 0 0 0 sk 17423 48146 15182 32964 + 3880 sl 7 203 0 203 0 sm 219 647 130 517 + 3 sn 254 1813 325 1488 + 40 su 1466 24995 1753 23242 - 266 sy 3 16 8 8 + 1 tj 304 1706 1084 622 - 17 tm 508 1968 627 1341 + 555 tn 1 76 51 25 + 1 tr 11994 94332 11601 82731 - 2116 ua 10900 72682 40640 32042 - 832 ug 162 828 119 709 - 17 uk 478844 2502998 825052 1677946 0 va 2 9 0 9 0 yu 5568 18207 3706 14501 + 238 ============================================================== 88 3496944 19420561 7645131 11775430 +384106

1 0