- ripe-list - mailman.ripe.net

New Document available: RIPE-167
by RIPE NCC Document Annoucement Service 03 Oct '97

03 Oct '97

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-167 Title: A Regional Internet Registry for the CIS Author: R. Blokzijl, D.Karrenberg, A. Platonov Date: 02 October 1997 Format: PS=47638 TXT=2153 Obsoletes: Obsoleted by: Updates: Updated by: See also: Short content description ------------------------- This memorandum is intended to focus discussion about the establishment of a Regional Internet Registry serving the CIS and surrounding areas. Public comments are invited. The ultimate aim of this process is to achieve rough consensus about the issue within the region concerned. This memo represents the views of the individual authors only. It has not been endorsed by any organisation. 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-167.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-167.txt plain text version You can also access the RIPE documents in HTML format via WWW. RIPE-167 is not available from the WWW at this moment, but will be soon, at the following URL: http://www.ripe.net/docs/ripe-167.html 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.

3 2

Re: New Document available: RIPE-167
by Dmitri Bourkov 03 Oct '97

03 Oct '97

-----Original Message----- From: Albertas Ramanauskas <albertas(a)taide.lt> To: RIPE NCC Document Annoucement Service <ncc(a)ripe.net> Cc: ripe-list(a)ripe.net <ripe-list(a)ripe.net> Date: 3 �� 1997 �. 11:18 Subject: Re: New Document available: RIPE-167 > >Dear authors, > >before starting the live discussion about this document I would appreciate >to get explanation regarding geografical region which be covered by this >document (and by Registry repectively). In particular: > >1. >> Title: A Regional Internet Registry for the CIS > *** >2. >> Short content description >> ------------------------- >> >> This memorandum is intended to focus discussion >> about the establishment of a Regional Internet >> Registry serving the CIS and surrounding areas. > *************************** >3. >excerpt from RIPE-167: > Background > > Since the start of the RIPE NCC as a regional Inter- > net registry in April 1991 Russia and the other > countries of the CIS (former USSR) have been served I think, that you shouldn't worry - CIS don't include Baltic states. I agree with you - it's not the same and should be corrected - as "(part of former USSR)" or simply excluded. > **************** > by the RIPE NCC. > >To my knowledge these 3 statements are totaly not the same. Even more, CIS >never had meaning adequate to USSR. > >Thanks and best regards, > >//Albertas >==================================================== >Albertas Ramanauskas ph. +370 2 72 12 89 >Manager, Taide NOC fax. +370 2 72 76 52 >Liepyno 7, Vilnius mob. +370 99 3 56 01 >Lithuania albertas(a)taide.lt > http://www.taide.net >==================================================== > >P.S. >Excerpt from RIPE-167: > If has been suggested more than once that the coun- > tries of the CIS in fact form a separate region from > Europe that needed special regional support. > >IMHO this doesn't sound very gentle. > > Regards, Dmitri Bourkov Head of Service Development Comstar

1 0

RIPE NCC, Amsterdam - Vacancies
by RIPE NCC Staff 01 Oct '97

01 Oct '97

RIPE NCC Employment Opportunities We are currently soliciting applications for the following positions: Hostmasters The general duties of NCC hostmasters include: - handle all address space related requests - help maintain the databases the RIPE NCC keeps - propose new activities, where needed - report to the Registration Services manager Network Engineers The duties of the network engineer are to: - participate in the maintenance and development of the NCC computing environment - provide support and training to users - maintain and extend software tools currently in use by NCC - staff and customers - identify areas in which automation will reduce work and/or errors - develop and document new software tools Purchasing Officer The duties of the purchasing officer are to: - Negotiation with suppliers and purchasing with special emphasis given to the purchasing of computer, telecommunication, and other technical equipment - Cultivation of and maintenance of supplier relations - Support to engineering staff in warranty and support procedures with suppliers - Maintenance of inventory tracking and stock control system - Pro-active reporting to management of market developments Office Manager The duties of the office manager are to: - Supervision of general administrative activities - Responsible for maintenance and running of one, soon to be two, office locations in Amsterdam. - Purchasing responsibility for administrative supplies within laid down budgets - Maintenance of all organisational supplier contracts - Maintenance and updating of all insurances for the organisation - Assist and possibly take on supervisional role in the organising of conferences - Management team assistance - Health and safety at work supervision How to Apply Please apply via electronic mail to <openings(a)ripe.net>. Please note that we do not feel obliged to read messages encoded in proprietary formats and very much prefer nicely formatted plain ASCII messages. So if you create your application using a proprietary word processor it is advisable to send an ASCII version and possibly a PostScript version for us to print. We do of course accept MIME encoded messages with alternative body parts. For more information about these vacancies and the RIPE NCC, please see: http://www.ripe.net/ Bredo Oeveraas RIPE NCC

1 0

The Cidr Report
by Tony Bates 26 Sep '97

26 Sep '97

1 0

RIPE NCC in Danger
by Daniel Karrenberg 24 Sep '97

24 Sep '97

Dear colleagues, more than a week ago we have published the RIPE NCC Activity Plan and Charging Scheme. We have also asked for nominations of persons to serve on the RIPE NCC Association's Executive Board. Up to now there has been very little feedback to us and no public discussion whatsoever. A total of 1 (one) person has been nominated for the Executive Board. Only 13 of currently 796 contributors have so far registered for the contributors committee meeting; that is less than 2% of the contributors. I tend to interpret this data optimistically and conclude that you all are basically happy with what the NCC is doing and how it is done. Thus you see no point to make the time it takes to take part in the governance of the RIPE NCC. If this interpretation is true the vote of confidence is flattering. However it would be very nice to hear it explicitly rather than implicitly. This would make the NCC stand stronger and make the concept of industry self-regulation all the more stronger. Given the low number of nominations, there is a real danger now that we will not be able to elect a strong and competent executive board. It has become very likely that the executive board will be elected in an ad-hoc fashion at a meeting of a very few contributors and that there is no public discussion prior to that election. This bears the danger of electing persons who do not really have the necessary time and/or expertise available to them. This will make the NCC weaker. NCC management needs the executive board as a strong partner in developing the NCC. I am personally quite concerned that the lack of interest in the governance of the NCC may lead to difficulties in the long run. Minorities and/or special interests might gain disproportionate influence. The NCC itself may take up momentum in directions the majority of the contributors do not want. Once this has happened it is can be very difficult to correct. The amount of effort needed to keep something on track is far less than to put it back on track after it has derailed. I urge all of you to take more of an active interest in these matters and to nominate proficient people to serve on the executive board. We would also appreciate feedback and discussion about the documents published, in particular the 1998 Activity Plan and Charging Scheme. More information can be found at http://www.ripe.net/meetings/contrib/ which contains meeting details and pointers to the relevant documents and at ftp://ftp.ripe.net/ripe/archives/ncc-co/current which contains an archive of the relevant e-mail messages in case you have missed them. Thank you very much for your consideration. Daniel Karrenberg RIPE Community Member RIPE NCC Manager

4 6

Re: Plenary minutes RIPE27
by Steven Bakker 23 Sep '97

23 Sep '97

==> On Fri, 19 Sep 1997, ==> "RNMR" == RIPE NCC Meeting Registration wrote: RNMR> Please accept my apologies for sending these out so late. Please accept my apologies for replying so late :-) Couple of comments: RNMR> 9. Technical Reports RNMR> - TEN-34 (Steven Bakker) RNMR> Impromptu presentation by Steven Bakker. I believe that's putting it friendly :-) RNMR> A map of the current TEN-34 network was shown. RNMR> Many countries now connected, network is operational and works. RNMR> see http://www.dante.org/ for more information That should be: http://www.dante.org.uk/ten-34 or http://www.dante.net/ten-34 RNMR> plans to start a new project done by smaller subset of RNMR> National Research Networks (NRN's) RNMR> Questions: RNMR> Peter Galvaby: what are the peering policies? RNMR> Steven Bakker: basically no policies, no real peering. RNMR> Must be careful to coordinate with European Commission on RNMR> peering agreements. RNMR> European Commission has restrictions on usage of network. RNMR> AT&T Unisource gives them transit as part of IP service they offer. RNMR> BT also gives them transit. Many of networks themselves have RNMR> bi-lateralarrangements with other networks. In discussion RNMR> too peer with EBONE. Latest news on that is that EBONE withdrew from the discussions. They are no longer interested in direct peerings with TEN-34, since they get the routes through their AT&T-Unisource peerings. RNMR> This will replace the European network RNMR> 2 remaining "customers" in Czech Republic and Hungary. RNMR> How many overhead from ATM? RNMR> Steven Bakker: about 17% RNMR> Marten Terpstra: Will the network actually reach 34Mbps in all countries RNMR> before the project will finish (2 year project) RNMR> Mike Norris: they reached "10" :-) Depends on whether you count access speed or backbone speed. Most of the backbone is >20M. Access speeds vary, but the majority is >20M. Given the cost of international high-speed circuits (see below) and the fact that the current bandwidth is not exhausted yet, upgrading for the sake of upgrading is not very wise. RNMR> Steven explained main problem is to do with prices/availability of RNMR> 34Mbps RNMR> in each country. In some cases this doesn't make sense since ACONEt is RNMR> hooked up to DFN who have to share this with other networks... I'd like to qualify that statement: the problem is not with price/ availability of _national_ circuits, but _international_ circuits out of certain (many) countries. Also, there is a cost distribution model within TEN-34, so the cost of _backbone_ (i.e. shared) lines is shared amongst all the participants. I though I did mention this, but given the short preparation time I had it may not have been a very clear story. RNMR> Rob Blokzijl: Too little, too late. Took 2 year organisation to get a RNMR> network going for a year..what about a follow-up? Organising too late. RNMR> commercial business is moving ahead with the development of bandwith RNMR> in Europe before R&D organisations are.. Rob says there are RNMR> plans for 622Mbps to come into AMS-IX My reply to that was that there is currently no pan-European high speed network on the scale of TEN-34. Sure, there are high speed islands all over Europe, many NRNs have a high speed national infrastructure. The problem is getting a *pan-European* high-speed network. In that respect, I believe TEN-34 is a first. Cheers, Steven

1 0

The Cidr Report
by Tony Bates 19 Sep '97

19 Sep '97

1 0

RIPE 28 - plenary agenda
by k13＠nikhef.nl 19 Sep '97

19 Sep '97

Dear Colleagues, please find below the draft agende for the RIPE 28 meeting. As always - comments and suggestions are more than welcome. Greetings, Rob Blokzijl R I P E 2 8 ------------- 24-26 September 1997 Amsterdam draft AGENDA ------------ 1. Opening 2. Agenda 3. From the Chair 4. Minutes RIPE 27 5. Action points RIPE 27 6. Report from the RIPE NCC contributers meeting 7. New Activity Plan & Charging Schedule 8. Database Security Task Force 9. RIPE NCC report 10. Test Traffic Measurement progress report 11. Towards a regional Registry for the COS 12. Spammers hapless fate = ISP toil and sweat 13. RIPE WG reports 14. Next meetings: + RIPE 29: January 1998 Amsterdam + RIPE 30: May 1998 Stockholm + RIPE 31: September 1998 Amsterdam 15. A.O.B. 16. Close

1 0

RIPE
by Stephanie Wickihalder 19 Sep '97

19 Sep '97

------- Forwarded Message Date: Thu, 18 Sep 1997 13:11:00 +0200 From: RIPE NCC Meeting Registration <meeting(a)ripe.net> To: Reseaux IP Europeens <ripe-list(a)ripe.net> Subject: Reminder: RIPE28 *new* meeting place Dear Colleagues, This just to remind you that registration for the RIPE 28 meeting in Amsterdam is still open and that the meetings will *no longer* be held at CWI/the Kruislaan. The address of the new meeting venue is: Park Plaza Rokin 78 1012 KW Amsterdam The Netherlands Kind regards, Naomi de Bruyn RIPE Meeting registration ------------------------------------------------------------------------------- %START % MTG [ ripe28 ] 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 name in FULL. First name first, surname last. e.g. John Doe Mary-Beth Walton %NAME [Mr. Marcel Schneider] 2) Your Organisation/Institution %ORG [SWITCH, Limmatquai 138, CH-8001 Zuerich] 3) Your e-mail address %EMAIL [schneider(a)switch.ch] 4) Country code of organisation e.g. IT FR DE %CTRY [CH] 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. If you wish to pay in cash at the meeting you can also pay in IEP. (please delete all choices except one) %PMETH [in advance; credit card] 2) Type of credit card (please delete all choices except one) %CTYPE [American Express] 3) Card number %CCNUM [3758 807837 01008] 4) Expiry date %CCDATE [04/99] 5) Card holders name %CCNAME [Marcel Schneider] 6) Card holders address %CCADDR [Staffelackerstrasse 31, CH-8953 Dietikon] 7) Amount to be paid Only meeting ECU = 100, NLG = 220 Meeting plus RIPE dinner ECU = 145, NLG = 320 %AMT [NLG 220] %END ------- End of Forwarded Message

1 0

Plenary minutes RIPE27
by RIPE NCC Meeting Registration 19 Sep '97

19 Sep '97

Dear Colleagues, Please accept my apologies for sending these out so late. Kind regards, Naomi de Bruyn ----- RIPE 27 plenary (22 May 1997) Chair: Rob Blokzijl <k13(a)nikhef.nl> Scribe: Mirjam Kuehne <Mirjam.Kuehne(a)ripe.net> Agenda 1. Opening 155 people registered Local Host: Business Center of DCU Opening words from local host John ### from DCU 2. Agenda 3. Minutes RIPE 26 4. Actions 22.10 on Joachim Schmitz trigger discussion in routing WG, which focus to choose for a future tool development project and come to consensus about it ... DONE 25.R1 on Daniel Karrenberg route aggreation analysis report at next meeting OPEN 26.R1 on the RIPE NCC add link to CIDRD FAQ on Web server DONE 26.R2 on Joachim Schmitz trigger discussion about implementation of first elements of hierarchical authorisation for route objects DONE 26.R3 on Joachim Schmitz finalise hierarchical authorisation for route objects together with RIPE routing WG ONGOING 26.R4 on Eric Jan Bos circulate URL of his analysis of routing table size: DONE ftp://ftp.surfnet.nl/surfnet/net-management/ip/nets.ps 26.R5 on Christian Panigel collect reasonable route dampening parameter values DONE on Geert Jan de Groot to write up recommendations for managing nameserver configurations OPEN on Lars Johan Liman To circulate a minimal set of requirements for TLDs on documenting their procedures OPEN on Daniele Bovio try to find ISP's that are willing to install test traffic measurement OPEN on RIPE NCC To create a mailinglist for discussing the definition of a network performance index, and to send out an announcement to the RIPE mailinglist DONE on Rob Blokzijl To restart activity in the Mbone WG DONE 5. TLD BoF report (Nial O'Reilly): 5.1 agenda reenigineered during meeting it was recognised that general things need to be clarified first: - - what should BoF be doing? - - what should WG be doing? - - what kind of cooperation of TLD admins in the RIPE community can and should be done? - - should we also discuss gTLD's? As result of this discussion it was decided to form a committee to produce terms of reference (on the committee are Marcel Schneider, Lars Johan Limann, Willi Black, Nial O'Reilly) Rob Blokzijl proposed to open a new WG with Nial O'Reilly as chairman; noone objected, everyone welcomed the WG During second half of BoF mainly two issues were discussed: 5.2.1 position of IANA concerned with 4 issues related to IANA: - funding - authority - legal protection - recognition of authority and importance of IANA (it is recognised by the Internet community, but not yet by governmental authorities) 5.2.2 reaction on IAHC, IPOC IPOC process needs to be visible to outside world, also to people who did not sign the MoU - we need to be involved in IPOC process: - 29th meeting in Brussel between respresentatives of EC and IPOC - next day hopefully meeting between IPOC and new WG representativs - some people from WG intend to participate in the WIPO meeting in Geneva Christopher Wilkinson from DG13 in EC welcomed RIPE to this new WG Wilfried Woeber: will you discuss issue of property of names? Peter Lothberg: What is the relation between RIPE and the EC? What conclusion will EC take home from this meeting? Rob Blokzijl: open platform, everybody is welcomed hopes, first contact is created to further discuss Internet issues Christopher Williamson: RIPE members have trained EC quite a lot, is not an exclusive EC thing, discussion are also done with US or other organisations and ISPs, there is program to support Internet developments There is still a lot to learn, it would be great if one or two from RIPE could come and give a quick inventory for the EC about what kind of WGs exist, what is discussed where (action point for Rob to appoint people to do this?) 6. RIPE NCC Report (RIPE NCC) explains meaning of T-Shirt not a complete detailed report, only highlights (see WWW) 6.1. registration issues: - - very stable service - - 691 LIR's (70% small, % medium, % large, % enterprise) - - quality management: - internal - better documentation - external auditing & monitoring (John appointed to this position, John also deputy registration service manager) - - LIR Training Courses: - 2 or more per months - new "no-show" policy - - new regional registries - some delay in white house (OMB) in ARIN developments - but everyone agrees that this should go forward - - IANA developments - assign Internet numbers - protocol identifiers - dot nameserver administration - run at ISI at USC - was funded by DARPA - end of March this suddenly was not continued - IANA asked regional registries to fund activities of IANA - APNIC contributed 50k$ - RIPE NCC contributed 25k$ - new structure is needed for IANA - summary/rough thinking: - US government? - ITU? - Bottom-Up? - Daniel's preferred solution - IP numbers and protocol identifiers task would be well funded and advised by the regional registries - however, there is also "." nameserver task (-> some representation for this (CORE?)) - advisory bodies Questions Keith Mitchell: do you still see the same growth in number of LIR's? Daniel Karenberg: difficult to answer; have the feeling that it is somewhat slowing down, but we can't really prove this because we cleaned up registry database and can't really compare old numbers with actual figures 6.2. enginering developments - - new database documentation - - fully automation of inaddr robot - - test traffic measurement activity started (see BoF on this) - - DNS root server at LINX - "." servers common resource - done on request of RIPE from last meeting - time schedule: - 22.1.1997 requested RIPE NCC to install nameserver - 24.3.1997 machines installed - 19.5.1997 operational 6.3. organisational issues - - seperate financial administration - own bookkeeper - procedures and accounts separable from TERENA - - admin support in place - for RIPE Meeting support - much better to have admin people doing admin stuff instead of engineers - - preparing separation from TERENA - see Pauls report - de-facto structure (see ripe-156) - - new RIPE NCC offices - no space at NIKHEF anymore - cheaper to go to center of Amsterdam, because no parking space - will move at 6th June and 9th June - NCC will be closed those two days 6.4. things to come, new activities - - new structure of NCC - revised document will be published - write tax plan - lawyers will draft articles of association - how to select initial executive board - elected by Contributors Committee in September - input from RIPE appreciated - - new developments in registration services, engineering and admin departememts Questions: Lars Johan Limann: for how long are you planning to grow? Daniel Karrenberg: the next 1 year probably Keith Mitchell: where will the next RIPE meetings in Amsterdam be helt? Daniel Karrenberg: first in NIKHEF, but if attendees grow we must find something else 7. RIPE NCC - New Structure (Paul Ridley) see http://www.ripe.net/### 8. Report from the IETF (Joyce Reynolds) see http:// (exact location will be published later) - - IANA web page has now an "announcement" link, where official statements of the IANA about all kind of issues can be found 9. Technical Reports - TEN-34 (Steven Bakker) Impromptu presentation by Steven Bakker. A map of the current TEN-34 network was shown. Many countries now connected, network is operational and works. see http://www.dante.org/ for more information plans to start a new project done by smaller subset of National Research Networks (NRN's) Questions: Peter Galvaby: what are the peering policies? Steven Bakker: basically no policies, no real peering. Must be careful to coordinate with European Commission on peering agreements. European Commission has restrictions on usage of network. AT&T Unisource gives them transit as part of IP service they offer. BT also gives them transit. Many of networks themselves have bi-lateralarrangements with other networks. In discussion too peer with EBONE. This will replace the European network 2 remaining "customers" in Czech Republic and Hungary. How many overhead from ATM? Steven Bakker: about 17% Marten Terpstra: Will the network actually reach 34Mbps in all countries before the project will finish (2 year project) Mike Norris: they reached "10" :-) Steven explained main problem is to do with prices/availability of 34Mbps in each country. In some cases this doesn't make sense since ACONEt is hooked up to DFN who have to share this with other networks... Rob Blokzijl: Too little, too late. Took 2 year organisation to get a network going for a year..what about a follow-up? Organising too late. commercial business is moving ahead with the development of bandwith in Europe before R&D organisations are.. Rob says there are plans for 622Mbps to come into AMS-IX Technical presentation: i-Pass (Glen Kowack) - - 80-120 million Internet users, user base growing - - global Internet roaming - instant local dial up access to Internet - - services from all urban centers worlwide; so they created: - i-pass wizard (in cooperation iwth microsoft) - i-pass authentification protocol - i-pass regional authentication servers - - works with all major authentication protocols and most of major platforms - - URL:http://www.ipass.com/ Has a box between home providers and roaming provider to pass authentication requests back and forth. Windows specific software for dialup, but based around userIDs of user(a)somewhere.co.uk - if local auth systems get a login from mail address, passes it back to the i-pass server. i-pass server is going to be major interconnect points around the world - right now at PAIX in the US and one in Asia, there will be one in Europe soon. 10. Test Traffic Measurements (Henk Uijterwaal) see http://www.ripe.net/test-traffic/Talks/9705_plenary/index.html 11. WG and BoF reports Netnews WG (Felix Kugler): - - 48 attendees - - minutes by Razo Rizvi - - presentation of Newsbone docs, WWW pages, templates http://www.switch.ch/switch/netnews/wg/nb/newsbone.html - - Newsbone deployment now! - announced: ACONET, DEMON, DFN, EASYNET, GARR-NIS, REDIRIS, SWITCH - required tools for INN-based servers mostly available ACTION on nwtnws-WG: - to share experiences with non-INN servers in backbone environment - to adopt existing tools to non-INN servers - optional access restriction to information and monitoring pages shall be based on IP addresses; all newsbone servers with published information page get access right ACTION on Newtnews-WG: - check if backbone servers can be integrated into Newsbone - upgrade Newsbone servers to fully meet the requirements - - Discussion about News Servers Software and Hardware confoguration Routing WG (Joachim Schmitz) - - 57 attendees - - minutes by Anne Lord - - see his slide - - three major topics: I. (hierarchical) authorisation/notification with route objects - presentation by Carol Orange on implementations of first results from the Routing WG - good discussion, new elements included - presented at Database WG, again input - final decisions on: - authorisation of route objects in aut-num objects - notification of overlapping route objects and there are still some minor open questions on notification. A proposal from the input from the WG session will be sent to the mailing list shortly after the meeting to cover the open issues. - The direction is clear and implementation will be done asap -> Still much work to do regarding hierarchical authorisation, we will continue on this II. A future tool development project - old action on the chairman of the Routing WG - presentation by Joachim Schmitz: - overview of what is currently available - identify areas for a possible tool development project - as it turned out after some discussion - Merit and the RA team (including ISI) have covered or are currently covering areas of interest - no real topics for a future tool development project could be found - this does not mean that this area should completely be closed We think that the area shall be reviewed regularily but no immediate action is needed III. Route Flap Dampening Parameters - presentation by Christian Panigl based upon action from last RIPE Meeting - compilation of issues regarding route flap dampening and values for parametrs - goal to come to recommendations - a small task force has been set up with Christian Panigl, Tony Barber, Sean Doran, Daniel Karrenberg. They will come up with a ripe document before the Munich IETF in August - - remaining actions for routing WG (5 previous actions closed) - 25.R1 on Daniel Karrenberg route aggregation analysis - 26.R3 on Joachim Schmitz finalise hierarchical authorisation for route objects together with Routing WG - 27.R1 on Carol Orange & the RIPE NCC implement authorisation and notification in the RIPE DB DNS-WG (Ruediger Volk) - - 49 attendees - - minutes by Wilhelm Koehler - - new root nameserver at the LINX - - report from carol Orange: new robot in in-addr - - report from Carol Orange; Planned DB Referral Mechanisms - - short report from DNSIND WG on the IETF (also RIPE WG should pay more attention on security) - - status of BIND - - review charter - - what are the possibilities and goals and activities - - review 'recommendations' in particular IPv6-WG (Francis Dupont) - - no chairman - - reports on the following issues - 6bone WG in IETF - 8+8 proposal discusseed last time, now called GSE? - two proposals to split A record in DNS: - aAA - with roputing part in address - new routing protocols - RIPng, OSPFng, BGP4+ - other earlier proposals seem to be dead - implementations - - RIPE & address assignments - - coordination with DB-WG on new IPv6 address object in RIPE DB - - IPv6 demo on JENC last week in Edinburgh - - summary of draft-ietf-ipng-unicast-aggr-00.txt - - RFC2073 provide based addressing (see his slide) Database WG (Wilfried Woeber) - - admin - participants: 17 (was in parallel with TLD BoF) - minutes by Joachim Schmitz - - reports - Gerald Winter (Merit): Merging rwhois demon SW as currently developed by Merit with the RIPE whois client - whois interface must be developed - Carol Orange (RIPE NCC): I. DB referral mechanism II. improvements of consistency in RIPE DB III. status report on RIPE DB - Joachim Schmitz: summary of security/authentication - - decisions: - implement referral mechanism for domain object - proceed with all necessary steps to improve consistency in DB - make inconsistency data publicly available - implement cross notification according to the concept as discussed in routing WG and as soon as some minor details are sorted out (waiting for final decision of routing WG on exact mechanism) - - things done recently: - better help facilities - some rules have been defined - others are to come very soon - updated DB documentation (new version ripe-157) - PLEASE: - get a copy - read it - think about it - comment on it (also when you are satisfied!!!) - person and role object require nic-hdl now! - - things to come - data consistency efforts in second half of 1997 - to define new security and authentication mechanisms - hopefully something ready for IETF in Munich and for RIPE-28 - - Feedback on RIPE-DB Workshop - ### participants (ask Carol or Ambrose) - should be repeated Question Philip Bridge: difficulties to express routing policies in RIPE DB. Will there be a transition from RIPE-181 to RPSL (IETF-WG) Answer Joachim Schmitz: new rpsl draft available, David Kessens from ISI is busy with implementation of test db, will probably be available in Munich Wilfried Woeber: touches also on issue of general coordination between RIPE and other developments like IETF Joachim Schmitz repeated his report from the db-wg on security: - - need for security? YES - - some history - - active security - maintainer - hierarchical authorisation - - passive security - AUP for use of database - restricted readaccess to prevent SPAMs - - this is not enough however - we must understand that this is an important issue - collect example incidents - RIPE NCC and routiong and DB-wg will put more effort in this - - (open) issues - strong authentication needed - inventory: PGP, MD5, PEM, alternatives - PGP implementation: http:// www.ra.net/RADB.tools.doc/pgp.html - PGP licensing: http://www.ascom.ch/Web/systec/policy/normal/policy.html - user platforms - key signing - ... - - problem of distributed databases (multiple routing registries like RADB, RIPE DB etc.) - what are possible security mechanisms - integrity and consistency - - how to make progress: - build a task force - collect information - define projects - next RIPE Meeting: present a proposal how to get this task force going - we still need people to join to this task force, specially people who have knowledge about security Paul Ridley thanked all local helpers and Mike Norris for organising the meeting Local-IR WG (Mike Norris): - - chairman: mn131 - - minutes by pc111-ripe - - attendees: 48 - - minutes of previous meeting accepted - - all actions done - - report from RIPE NCC - staffing: 9 full-time, 1 part-time - workload fine - activities: - training new staff, LIR courses - allocation of 62/8 - internal quality control started - external auditing started - plans - continue these efforts, specially w.r.t. quality - - report from local registries - Justin Kerry from Cerbernet about starting new registries in Kenya - - report from David Conrad from APNIC - incorporated last year - 3 full time staff plus contractors - membership distribution and fees similar to RIPE NCC - new category needed for confederations - will relocate because of 51.7 % tax - statistics about distribution of address space and AS numbers, also per country - - report from APRICOT circulated on local-ir(a)ripe.net and on ripe-list(a)ripe.net (not yet published as ripe document) - - report from Daniel Karrenberg about developments in US region - ARIN (American registry for Internet Numbers) will go ahead - very similar structure to RIPE NCC - currently delayed in White House, but consensus that it will be establihsed - IANA - DARPA funding stopped in March - APNIC and RIPE NCC contributed amount to continue operations - new structure of IANA is needed - - IP address space assignments - some loose ends will be removed from policy document (ripe-140) - describe procedures for de-assignment of address space and AS numbers - confidentiality statement slightly stronger - use of historic A space - supplemantary document (ripe-155) - there are problems with routing subnets of former A's, B's, however this is also the case with subnets of c space - monitoring and auditing - reports of non-compliance must be substantiated before investigations are taken - NCC has opportunities to take actions again non-compliant behaviour - NCC will report on incidents and actions taken - - Local IR Training Courses - schedules, past and future - new technololgies (Powerpoint) - no-show policy - registries get allocated places, you use the place, if you attend or not - FAQ on forms and other assignment and allocaion issues - web interface in preparation for form (ripe-141) - - Tools - betteer user interface needed - use web more - Justin Kerry will initiate discussion on list by making suggestions on better use of Web - - Reverse Delegations (previous action on Daniel Karrenberg) - no serious pollution in European DNS - - AOB - mailing list changed: - local-ir(a)ripe.net only open for contributing LIR's - lir-wg open for anyone - people can unsubscribe from lir-wg (also when they are mandatory on local-ir) - local-ir monitored now - advice on PA space and renumbering (grace period); will be written up in ripe-140 - web will be used for all announcements for RIPE Meetings and LIR Training Courses (venue of Meetings will also appear in announcement on mailing list) MBONE BoF (Wilfried Woeber) - - Goal: - investigate and propose changes to the european MBONE structure to achieve a better alignment with the line and unicast topology - Results: - lists of proposed changes - fan-out count - line load - other constraints - Implementation: - write up an circulation at mbone-eu-op(a)ripe.net - coordination of set-up (Nils den Otter, Steven Bakker) - additional issues: - coordination with non-### to be improved - we might want to have MBone-WG ### Report from secret limerick working group (Ambrose Magee) 12. Next Meetings - - September in Amsterdam - - KTH invited us for the spring meeting to Stockholm - - exact dates will be published 13. Closing

1 0