- ripe-list - mailman.ripe.net

Re: RIPE Documents Modified
by RIPE NCC Staff 04 May '01

04 May '01

Dear Colleagues, The RIPE NCC is aware that the changes made to the RIPE documents ripe-141, ripe-142 and ripe-191 were not in keeping with the practices for updating RIPE documents as agreed by the RIPE community. The original versions of the documents in question have been replaced in the RIPE doc. store and new versions of these documents will be published and announced. Again, I apologise for this. Regards, Paul Rendek Communications Manager RIPE NCC

2 1

Re: RIPE Documents Modified
by Nigel Titley 03 May '01

03 May '01

> Can anyone explain why the ripe-141, ripe-191 and ripe-142 documents have been > modified recently on the RIPE NCC ftp server rather than having new documents > issued with new numbers? It's also interesting to note that the Postscript > versions of these documents seem unchanged. > > And, yes, I realise that there is a requirement to bring database objects > described in the documents in line with the new database implementation but > shouldn't this have been done by issuing new documents? Is it helpful to have > (potentially) different versions of the same document lying around with the > same name? If this has, indeed, happened then I for one would be very disturbed. The only way to modify a RIPE document should to be up-issue it. I recall Rob getting very heated about this at the Budapest RIPE meeting. Nigel

6 5

Re: RIPE Documents Modified
by Nigel Titley 02 May '01

02 May '01

Paul, > Thank you for pointing out the minor changes made to ripe-141, > ripe-142, ripe-191. Apologies are extended and we realise that this > is not the agreed procedure for updating RIPE documents. We assure you > that these changes will not set a precedent for future modifications > made to RIPE documents. A couple of points: 1. It was James who spotted the changes, not Marc 2. Although the changes involved are pretty sensible, one or two at least are not minor. I'm thinking particularly of the change of mnt-by from optional to mandatory. However, apology accepted (by me at any rate), and no doubt Rob will be visiting to make sure that this doesn't happen again :-) Nigel > Regards, > > Paul Rendek > RIPE NCC > > > > Marc Roger <marc(a)belnet.be> writes: > * This message is in MIME format. The first part should be readable text, > * while the remaining parts are likely unreadable without MIME-aware tools. > * Send mail to mime(a)docserver.cac.washington.edu for more info. > * > * ---559023410-341603450-988799134=:8747 > * Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > * Content-ID: <Pine.GSO.4.33.0105021226201.8747@dagesh> > * > * Nigel, > * > * James is right, these documents have changed. I attach the differences > * found for ripe-141, 142 and 191, for info. > * > * On Wed, 2 May 2001, Nigel Titley wrote: > * > * > > Can anyone explain why the ripe-141, ripe-191 and ripe-142 documents have been > * > > modified recently on the RIPE NCC ftp server rather than having new documents > * > > issued with new numbers? It's also interesting to note that the Postscript > * > > versions of these documents seem unchanged. > * > > > * > > And, yes, I realise that there is a requirement to bring database objects > * > > described in the documents in line with the new database implementation but > * > > shouldn't this have been done by issuing new documents? Is it helpful to have > * > > (potentially) different versions of the same document lying around with the > * > > same name? > * > > * > If this has, indeed, happened then I for one would be very disturbed. > * > The only way to modify a RIPE document should to be up-issue it. I > * > recall Rob getting very heated about this at the Budapest RIPE meeting. > * > * -- > * Marc.Roger(a)belnet.be, BELNET

1 0

Re: RIPE Documents Modified
by Nigel Titley 02 May '01

02 May '01

And the amusing thing is that your diffs show the line "Each revised document will receive a new document number" in RIPE-191 Nigel

1 0

Re: RIPE Documents Modified
by James Aldridge 02 May '01

02 May '01

Nigel Titley wrote: > If this has, indeed, happened then I for one would be very disturbed. The > only way to modify a RIPE document should to be up-issue it. I recall Rob > getting very heated about this at the Budapest RIPE meeting. I notice that the RIPE NCC have now "tidied up" ftp.ripe.net but my mirror on ftp.mcvax.org shows: -r--r--r-- 1 root ftp 66229 Jan 18 1999 ripe-141.ps -r--r--r-- 1 root ftp 5939 May 1 10:17 ripe-141.txt -r--r--r-- 1 root ftp 5973 Sep 19 1997 ripe-141.txt~ -r--r--r-- 1 root ftp 244618 Sep 19 1997 ripe-142.ps -r--r--r-- 1 root ftp 40467 May 1 10:34 ripe-142.txt -r--r--r-- 1 root ftp 40666 Sep 19 1997 ripe-142.txt~ -r--r--r-- 1 root ftp 52071 Oct 9 2000 ripe-191.ps -r--r--r-- 1 root ftp 11488 May 1 10:22 ripe-191.txt -r--r--r-- 1 root ftp 11284 Feb 4 1999 ripe-191.txt~ I too would very much prefer that ripe documents (like RFCs) remained completely unchanged once assigned a number and published. In this case the changes were minor but this MUST NOT set a precedent for future modifications. James

1 0

RIPE Documents Modified
by James Aldridge 02 May '01

02 May '01

Can anyone explain why the ripe-141, ripe-191 and ripe-142 documents have been modified recently on the RIPE NCC ftp server rather than having new documents issued with new numbers? It's also interesting to note that the Postscript versions of these documents seem unchanged. And, yes, I realise that there is a requirement to bring database objects described in the documents in line with the new database implementation but shouldn't this have been done by issuing new documents? Is it helpful to have (potentially) different versions of the same document lying around with the same name? James -- James Aldridge, Senior Network Engineer (IP Architecture) KPNQwest, Singel 540, 1017 AZ Amsterdam, NL GSM: +31 653 708 707

1 0

"IP tutorial" during the RIPE 39 meeting
by RIPE NCC Staff 26 Apr '01

26 Apr '01

Dear colleagues, During the RIPE 39 Meeting in Bologna, an "IP Requests Tutorial" will be held on Friday, 4th May, 14-17 PM. The "IP Requests Tutorial" contains selected sections of the LIR Training course that RIPE NCC provides to its members: - How to Request Address Space - Completing the Request Form - Evaluation of Address Space Requests - Registering Address Space in the RIPE Database - How to Request New Allocation Registration for this tutorial is not necessary. All RIPE meeting participants are more than welcome to attend this tutorial. The slides from the Tutorial will be shortly available at: http://www.ripe.net/ripe/meetings/archive/ripe-39/presentations/ip-tutorial/ Kind regards, Vesna Manojlovic RIPE NCC Trainer

1 0

Announcement DISI BOF
by Henk Uijterwaal (RIPE-NCC) 25 Apr '01

25 Apr '01

Dear Colleagues, (sorry for duplicate copies). This mail is to inform you about the DISI BOF that will be organized next week during the RIPE39 meeting, on Wednesday 2/5, 9:00-12:30. The purpose of the BOF is to discuss the plans for the DISI project at the RIPE NCC as well as related projects. A draft agenda for the BOF as well as some background material, can be found at the bottom of this mail If you have any additional topics for the BoF, comments or questions, please send me an email. Depending on the outcome of the BoF a mailing list will be set up. I hope to see you in Bologna, Henk Uijterwaal Proposed agenda for the DISI BOF -------------------------------- Wednesday, 9.00-12.30. A. Introduction. - What is this BoF about? B. Administrative Matters - Appointment of a scribe - List of participants - Agenda bashing C. DISI and the deployment of DNSSEC on the reverse DNS tree. - Plans, deadlines and milestones. Olaf Kolkman (RIPE NCC) A draft document describing the plans for the DISI project exists. The abstract of this document can be found below, the current draft of the full document is available at: http://www.ripe.net/ripencc/pub-services/np/Notes/DISI-project-note.ps D. CSIRT coordination for Europe and Extended Incident Handling - standardisation - Overview of TERENA's TF-CSIRT activity Yuri Demchenko (Terena) E. .... F. Discussion G. The Future - Is there sufficient interest in this topic and if so, how should we proceed from here? Z. AOB DISI and the deployment of DNSSEC on the reverse DNS tree. ---------------------------------------------------------- Abstract The Deployment of Internet Security Infrastructure (DISI) project is a new effort at the RIPE NCC. Within the context of DISI we will study, raise awareness and support the use of protocols and techniques that can make the Internet more secure and that need mutual effort of ISPs to be successful. Within the DISI project context we will concentrate on suitable technologies and will try to get these technologies accepted and implemented by ISPs. We will do so by raising awareness, providing documentation, giving courses and, most important, giving and receiving feedback on implementation experience at the RIPE NCC and at the ISPs. The first technology we are concentrating on is the deployment of DNS Security on the reverse tree. We will describe what DNSSEC can do, why DNSSEC is a mutual ISP effort and what DISI's deliverables are. ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(a)ripe.net RIPE Network Coordination Centre WWW: http://www.ripe.net/home/henk Singel 258 Phone: +31.20.5354414 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ As long as you don't tell your friends how I played the hand, then I won't tell my friends how you defended it. (Anonymous)

1 0

RIPE Region Hostcount for March 2001
by RIPE Hostcount Maintainer 25 Apr '01

25 Apr '01

Dear All, below is the hostcount for March 2001. The table shows an increase since last month of over 470,000 (or 3,6%) to a total of almost 13,700,000 hosts in the DNS in Europe and surrounding areas. The ru domain shows the highest increase for March with approximately 175,000 hosts more than in February. 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 with co.uk. since that time. - the February, 2001 data had to be reused for tr, il, es, ch, li and fr due to an assortment of operational problems. - no new data could be collected for ci due to problems with transfer of the top-level zone. - 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 Hrant Dadivanyan 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 Hostcount Admin es ES NIC fr Annie Renard gr Dimitris Zisiadis hr Ivan Maric ie Mike Norris 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 Hostcount Admin 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 : Mon Mar 12 2001 This Count : Tue Apr 24 2001 CY SOA COUNTED DUPL REAL CHANGE ============================================================== ad 546 2398 755 1643 20 ae 2699 42524 2144 40380 79 al 82 193 30 163 3 am 1090 3733 1334 2399 -251 at 138085 756331 220366 535965 12646 az 681 1697 413 1284 -239 ba 364 3645 851 2794 121 be 46687 388790 60277 328513 13154 bg 1358 24720 3195 21525 1222 bh 22 125 69 56 1 by 345 2938 606 2332 -433 ch 170681 509332 246841 262491 0 ci 360 3452 463 2989 0 cm 48 365 32 333 8 cv 20 130 105 25 0 cy 833 8242 847 7395 27 cz 91890 263874 93296 170578 9289 de 2458398 9654943 7281986 2372957 136714 dk 186729 614875 236456 378419 44441 ee 6844 59232 15509 43723 2723 eg 1533 3392 1036 2356 112 er 31 227 22 205 5 es 29043 503247 53085 450162 0 fi 27792 792961 60248 732713 33527 fr 95219 1333420 172464 1160956 0 ga 31 57 13 44 5 gb 2 24 0 24 0 ge 503 2904 1075 1829 83 gg 1483 2330 915 1415 -239 gh 33 500 39 461 103 gi 547 1340 154 1186 -255 gl 816 2939 442 2497 -5 gn 15 337 135 202 1 gr 20830 162718 22149 140569 7029 gw 2 21 1 20 0 hr 4482 32103 12886 19217 1201 hu 34033 190555 61734 128821 13079 ie 17397 145732 22604 123128 1643 il 19496 130980 40337 90643 0 ir 255 2908 531 2377 315 is 6171 72139 26076 46063 6839 it 426759 1447764 574379 873385 -75625 je 1507 2427 957 1470 -239 jo 575 1540 692 848 21 ke 1187 5606 800 4806 10 kg 1215 6275 1875 4400 120 kz 2164 10564 2279 8285 387 lb 1191 5419 1134 4285 720 li 4621 8880 5062 3818 0 lr 11 0 0 0 0 lt 6800 33711 6083 27628 996 lu 4966 16965 4161 12804 1253 lv 5573 29121 7961 21160 394 ma 1483 4413 2420 1993 95 mc 389 946 508 438 4 mk 646 2084 483 1601 186 mt 975 8261 1710 6551 6535 ng 284 2491 1407 1084 259 nl 464845 2790434 901190 1889244 78981 no 57308 529571 63999 465572 13437 om 100 5895 2974 2921 5 pl 78933 565639 183194 382445 14795 pt 8588 129586 16157 113429 -43426 qa 20 2253 31 2222 0 ro 9753 59786 14855 44931 3558 ru 49447 338644 117432 221212 174301 sa 2047 11739 2263 9476 1957 se 63024 636717 64252 572465 10531 si 6869 29767 6698 23069 -3128 sj 1 0 0 0 0 sk 27706 71155 29166 41989 1127 sl 7 214 0 214 -1 sm 309 1546 243 1303 7 su 1013 28035 2850 25185 350 sy 3 18 9 9 0 tj 119 977 689 288 14 tm 1262 3087 1443 1644 447 tn 28 317 140 177 2 tr 13442 108598 18885 89713 0 ua 23459 117258 75598 41660 2350 ug 204 395 149 246 13 uk 478844 2502998 825052 1677946 0 va 2 9 0 9 0 yu 7790 20154 5746 14408 591 ============================================================== 84 5122945 25263632 11586447 13677185 +473995

1 0

Draft Plenary Minutes RIPE 38
by RIPE NCC Meeting Registration 23 Apr '01

23 Apr '01

Dear Colleagues, [ Apologies for duplicate mails ] Please find below the RIPE 38 draft plenary minutes. They are also available on our website at: http://www.ripe.net/ripe/meetings/archive/ripe-38/plenary-minutes.html Kind regards, Sylvana Wenderhold --------- 38th RIPE Meeting Plenary Session Minutes - Draft RIPE 38 Amsterdam, 22-26 January, 2001 Plenary Session Chairman: Rob Blokzijl Scribe: Sylvana Wenderhold 1. Opening and Welcome 2. Agenda 3. Minutes RIPE 37 4. From the Chair 5. Report from the RIPE NCC (Axel Pawlik) 6. DISI, a new project at the RIPE NCC 7. Reports from APNIC (Paul Wilson) and ARIN (Ray Plzak) 8. Report from LACNIC (German Valdez) 9. Report from ASO/AC (Hans Petter Holen) 10. Election of AC member 11. AS Number Exhaustion (Scott Marcus) 12. Report from ICANN (Andrew McLaughlin) 13. Reports from the Working Groups 14. Next Meetings - RIPE 39 Bologna 30 April - 4 May, 2001 - RIPE 40 Prague 1 - 5 October, 2001 15. AOB 16. Closing 1. Opening and Welcome Rob Blokzijl welcomed the attendees to the RIPE 38 meeting. 2. Agenda The RIPE meeting participants approved the agenda. 3. Minutes RIPE 37 The minutes were approved. 4. From the Chair Rob did not have any general remarks. 5. Report from the RIPE NCC (Axel Pawlik) Please see the following URL for his presentation. http://www.ripe.net/ripe/meetings/archive/ripe-38/index.html RIPE NCC Status Report There have been as few staff changes: - John Crain has left RIPE NCC and joined ICANN. - Joao Damas has become Chief Technical Officer and is now responsible for the engineering groups: Database, Software and Operations Department. - Nurani Nimpuno, the Registration Services manger, reports directly to Axel. - Daniel Diaz has become the manager of the Operations Department. - Olaf Kolkman, has joined the New Projects Group as Scientific Programmer. Registration Services The waitqueue is down to a level that may be considered normal. The week before the RIPE meeting the wait was four days and on the Monday of the meeting it was five days. Over Christmas it did shoot up again, but after the holidays it went right back down. At the RIPE 37 meeting the RIPE NCC introduced an IP tutorial at the end of the week. As it was well attended, it will take place again at RIPE 38. Also back by popular demand is the Hostmaster Centre. This year the RIPE NCC is planning to do 50 LIR training courses. We have found several dedicated trainers within the RIPE NCC who are a great addition to the existing training team. The RIPE NCC has new staff in the Registration Services department. Recruiting more employees to guard against a sudden rise of the waitqueue will still continue. There is still a steady growth in the number of LIRs. Most of the growth is in Europe and Central Asia with nearly 800 new LIRs in 2000. The middle East had 30 and the African region had 8 new LIRs in 2000. Address Space Usage The RIPE NCC has allocated more address space over the last months than in previous months. Even though this is not an immediate threat, Axel explained that the RIPE NCC will closely monitor this. Consumption Rates There is quite an increase in consumption between 1999 and 2000. The RIPE NCC has not found particular reasons for this increase. This will be closely monitored by the RIPE NCC and co-ordinated with the other RIRs. IPv6 There is activity, but it is still fairly slow. Germany and Sweden are the most active to date. The RIPE NCC has allocated approximately double the amount of IPv6 address space to commercial companies than it has to academic organisations. Achievements within Registration Services - RIPE NCC is giving some direct attention to correctly filled out requests. - More responsibility is put on the LIRs to fill out the requests properly. - The helpdesk, lir-help(a)ripe.net is used for general questions preventing these questions from being queued together with Internet resource requests. - The RIPE NCC tools have been continually updated. - The FAQ continues to be updated. - The RIPE NCC has worked on a form that will succeed RIPE-141. Our priorities are: - to continue to increase the staff in the Registration Services department. This is to ensure that the waitqueue remains at an acceptable level. - Build more tools to improve the service. Database Version 3.0 of the RIPE database will be launched in April 2001. The main change is the introduction of RPSL. New Projects The Test Traffic Measurements service is now available to the entire community.New hardware is easy to install. Axel expects substantial growth in the number of boxes that are distributed. Brochures have been designed and each attendee has received one in his/her package. Routing Information Service Currently two route collectors in operation. Two additional collectors are planned. Results and statistics are available at: http://www.ripe.net/ris/ris-index.html The PAM2001 workshop will be hosted in April 2001 in Amsterdam. Registration is open. In October, the general meeting of the RIPE NCC association was held. The members approved the financial figures for 1999 and the budget and activity plan for 2001. The RIPE NCC Executive board remains unchanged as Frode Greisen was re-elected to the Board during the AGM 2000. Communications - 50 training courses are planned for 2001 - Outreach activities / RIPE NCC awareness - ENUM ICANN ASO As the ASO secretariat function rotates among the RIRs, for the year 2001 the ASO secretariat will be located at the RIPE NCC. This includes the website, the hosting of the AC telephone conferences and general administrative tasks. Co-ordination between RIRs Axel welcomed staff from ARIN, LACNIC and APNIC. A small retreat has been planned again this year. RIPE NCC short term goals: - the migration to the new database - adding resilience to Registration Services - enlargement TTM network - finalising contract with ICANN RIPE NCC priorities: - Ensure and further improve stable, reliable and high quality services - Respond to members' needs and develop and propose services as needed - Further increase RIPE NCC and RIPE awareness Questions: Christian Panigl: Do you have any statistics on how many LIRs have left during the last years? Axel: We will have more data during the next meeting. We want to focus more on providing general statistics. 6. DISI, a new project at the RIPE NCC Henk Uijterwaal gave a presentation on DISI. The slides can be found on: www.ripe.net/disi DISI stands for Deployment of Internet Security Infrastructures. What is the purpose of DISI: - Security technologies need to be deployed in the Internet infrastructure and its operations. - Some of those technologies need to be deployed in a co-ordinated way to be effective at all. Goals: - DISI will help to deploy existing security technologies within the RIPE NCC and its operations to the outside world (i.e. PGP and DNSsec) - DISI will document deployment experiences of security technologies - DISI will assist the RIPE community in deployment of security technologies - DISI will co-ordinate deployment and operation of security technologies where necessary We may set up training courses to help the community use these tools, not unlike the LIR training courses. Initial focus: - DNSsec - Deployment on the in-addr tree - Deployment assistance - Implementation of PGP in communication between hostmasters and LIRs: "PGP4HM" - Public Key Infrastructure - Implementation of PGP in communication with HMs and LIRs: PGP4HM - Applicability of PKI in RIPE/RIPE NCC context Progress so far: - RIPE 36 first ideas - Summer 2000 - Hire Scientific Programmer to lead this effort - Proposal in the Activity Plan 2001 Plans: - April 2001: Draft Project Proposal - May 2001/RIPE 39: BOF - Securing the in-addr tree - DNSsec implementation - Public Key Infrastructure - Finish PGP4HM Project - RIPE document describing the implementation - Applicability statement - White paper on "how to use this in your organisation" Contact Information - Internal email alias: disi(a)ripe.net - Webpage: http://www.ripe.net/disi - Announcement on the RIPE list until there is a public mailing list 7. Reports from APNIC (Paul Wilson) and ARIN (Ray Plzak) Paul Wilson - APNIC For a fully detailed report on APNIC, please visit: http://www.ripe.net/ripe/meetings/archive/ripe-38/index.html Ray Plzak - ARIN For a fully detailed report on ARIN, please visit: http://www.ripe.net/ripe/meetings/archive/ripe-38/index.html 8. Report from LACNIC (German Valdez) For a fully detailed report on LACNIC, please visit: http://www.ripe.net/ripe/meetings/archive/ripe-38/index.html 9. Report from ASO/AC (Wilfried Woeber) For a fully detailed report on ASO/AC, please visit: http://www.ripe.net/ripe/meetings/archive/ripe-38/index.html 10. Election of AC member The term of Sabine Jaume expired in December 2000. The RIPE NCC issued a public Call for Nominations to fill the vacant seat on the Address Council. There were three candidates nominated for the AC elections: Sabine Jaume, Khaled Moh'd Abu Mallouh and Francesco Ravanelli. Sabine was the only candidate in attendence. She introduced herself. This is the result of the election: Sabine Jaume - 147 Khaled Moh'd Abu Mallouh - 1 Francesco Ravanelli - 5 Blank votes - 2 11. AS Number Exhaustion (Scott Marcus) Please see the presentation at: http://www.ripe.net/ripe/meetings/archive/ripe-38/index.html 12. Report from ICANN (Andrew McLaughlin) Andrew introduced John Crain as the new Technical Manager at ICANN and provided a status update. Questions: Fay Howard - During the presentation from people proposing to run a new registry in Brussels recently, some of them mentioned they were making a voluntary reservation in the second level of two letter codes. Others said they were in negotiations with ICANN. Has ICANN got a policy on this issue? Andrew - There are no hard and fast rules on this issue. Wilfried Woeber - We recently had to resolve the problem of duplicate names in the small backyard of a Local Registry. It is difficult to make those names unique. Does anybody have a good idea on how to solve this problem? Andrew - You want to take a look at the .name proposal on the ICANN website. 13. Reports from the Working Groups Routing Chair: Joachim Schmitz Scribe: Engin Gunduz Attendees: 96 For the report of the routing working group, please see: http://www.ripe.net/ripe/meetings/archive/ripe-38/index.html There were no questions. Database Chair: Wilfried Woeber Scribe: Nigel Titley Attendees: 50 DB-SW version 3 implementation and migration to RPSL is going to affect all users. Target date agreed: 23 April 2001 (unless there is a well-documented reason to postpone the transition) Current level of protection is preserved, the method might be different, though. Question: Retire orphaned person:/role: objects? Work Items: - IRT object spec & last call - Globally unique handles -> target: ARIN meeting, April 2001 - Finish preparations for RPSL/version 3 Question from Wilfried to the audience: Do you support the idea to simply get rid of these useless objects? There were no comments made. CENTR / DNR Chair: Fay Howard Scribe: Kevin Meynell Attendees: 48 For Fay's working group report, please see: http://www.ripe.net/ripe/meetings/archive/ripe-38/index.html There were no questions. LIR Chair: Hans Petter Holen Scribe: Roger Arcilla Attendees: 102 For Hans Petter's working group report, please see: http://www.ripe.net/ripe/meetings/archive/ripe-38/index.html There were no questions. DNS Chair: Ruediger Volk Scribe: Lee Wilmot Attendees: 81 There were no questions. IPv6 Chair: David Kessens Scribe: Vesna Attendees: 134 There were no questions. EIX Report by Nic Lewis Chair: Faerghas McKay Scribe: Vanessa Evans Attendees: 128 1. Switching wish list - Mike Hughes A document detailing the features desired in switch equipment with particular regard to use in Internet Exchanges. Draft version should be available on EIX-WG mailing list next week. Comments invited 2. IXP BCP - Nic Lewis A document to assist the IXP operators in running IXPs, and hence help ISPs wishing to connect to IXPs. It was noted that there are many aspects to this document, some of which may not fit as part of a BCP, and it was suggested that the work be documented and broken down into several BCPs, FYIs FAQs as appropriate. ACTION: to circulate an initial breakdown of the document(s) on EIX-WG Mailing list for discussion Comments asked from the community as to whether this was valuable work since it was turning into a wider project than originally scoped. Community agreed that it was 3. IX Reports - TIX - Andre Opperman Was Telehouse IX, now part of IXEurope - VIX - Christian Panigl ACTION: add multicast as an agenda item for net EIX-WG - DE-CIX - Arnold Nipper - AMS-IX - Job Witteman - NIX-CZ - Josef Chomyn Welcome presentations from Eastern Europe - SFINX - Franck Simon Two new pops finally up and running - Netnod IX (formerly Stockholm D-GIX) - Lars-Johan Liman Described the FDDI/DPT architecture - LONAP - Raza Rizvi First presentation at RIPE - LINX - Mike Hughes - XchangePoint - Keith Mitchell New IX roll out across EU There were no questions Anti spam Chair: Rodney Tillotson Scribe: Dave Wilson Attendees: about 40 Europe is quite good about spam. Need to make some difference elsewhere. Spamwhack http://www.spamwhack.com/ Track down spammers to individual people so that further action (i.e. lawsuits) could be taken if necessary. The service keeps anonymised checksum info on customer information provided on sign up. Developments on spam Little change UUNET dialups the biggest source. China, Korea, Japan increasing. Need active and relevant contacts in both places; will contact APNIC and some Far East CERTs, and UUNET's IRT. Collateral spam. Actual user addresses being used as from: or Reply to: forged in spam. Developments in spam No news Open Relay Products Nothing has changed very much. Exchange 5.5 ships relaying, you have to apply SP2 and then secure for relay. RIPE-206 BCP specifies relationships with your customers to enforce anti-relaying. Almost superfluous in the RIPE community. Discussion of open relay scanning and testing products, to be forwarded after meeting. Advise OPT-IN lists (work item) Advise for well-meaning bulk marketers, establishing what is good practice for direct mail. Will follow LINX BCP (coming soon; http://www.ja.net/mail/juk/save/lists.html is broadly similar). Marketers are the key audience, but they have opt-OUT tradition. Report spam Very few people report every single piece of spam they get. SpamCop will help them but is not ideal. Some evidence that ISPs take reports more seriously if they come from another ISP's abuse address. Response to spam reports Usually you hear nothing from the remote ISP; this doesn't mean they've done nothing, but it's hard to encourage our customers. The major (US) ISPs could do forensic work tracking down abusive individuals and, perhaps, taking legal action. Techical measures Signed messages or headers - hard to deploy Hashbusters seen - spam with gibberish characters on a line at the end or at the end of the subject line to try to beat checksum filtering. Port 25 (587) blocking - most IPSs prefer not to do this. UUNET? SMTP authentication - reported as not being difficult. POP-before-SMTP also simple and valuable. We should keep a list of contributed URLs on the RIPE NCC web as a central resource of email security. Advice on reading mail headers (work item) Ongoing; contributions still welcome. What are we actually doing? Should we describe the work of this group in more aggressive terms? Europe is fixing a problem it hasn't got; we need a broader consensus, including US ISPs. The other RIRs also need a platform to support this kind of work in their meetings. Considering adapting RIPE-206 to make it look more like a policy which we might encourage RIRs to accept. Follow up on the list. Might the RIPE NCC run its own RBL containing only RIPE addresses? Certainly not at this stage and probably not at all. However, it is a reminder of the second part of the WG charter, to produce a European mail abuse response centre. There were no questions Test Traffic Chair: Keith Godber Scribe: Rene Wilhelm Attendees: 50 TT boxes production service Since 10.10.00 46 boxes 30 active 5 new boxes The ease of setting up a test-box was demonstrated at RIPE 38 and only took 34 minutes to set-up. Future plans - Bandwith analysis - Trends There were no questions. Netnews Chair: Dave Wilson Scribe: Felix Kugler Attendees: 30 NHNS (Daniel Diaz) Daniel has submitted an Internet Draft about the NHNS system to the IETF. [1] is an individual publication and valid until April 2001. So far only one comment was received concerning the draft. Setup of the public NHNS cloud: * primary nameserver for usenet.nhns.net hosted by Satec (ES) * secondary nameserver hosted by Dave Wilson, HeaNet (IE) All info about NHNS is available on [2]http://nh.nhns.net. Next steps: * move primary nameserver to a RIPE platform and restart the public pilot * rewrite some of the tools, especially the dynamic update script * update the Internet draft * strive towards an operational, stable service Flowmaps (Kai Siering) No progress since RIPE-37 meeting. The flowmaps software is available for download on [3]http://newsbone.uu.org/RIPE-38, example pictures can be found there as well. The tool requires "inpath"-like raw data collected on a news server. Visualisation is done using Cyclic software. Processing one day of data needs approx. 10 minutes on a modern Pentium hardware. Real time visualisation would require a dedicated, very fast machine. Visualisation features: * 3D-view of news flows around the target machine where the raw data was collected * zoom in/out * change viewpoint * nodes and links are clickable, small windows pop up showing details It seems valuable to be able to visualise traffic volume instead of the number of articles in future. Other suggestions and comments from test users regarding new features are welcome. References: 1. http://sunsite.cnlab-switch.ch/ftp/mirror/internet-drafts/draft-diaz-nhns 2. http://nh.nhns.net/ 3. http://newsbone.uu.org/RIPE-38 There were no questions. Tool BoF Chair: Maldwyn Morris Attendees: 92 1. Existing tools - Net: :IP : Perl Library for the Manipulation of IPv4 and IPv6 Addresses (Manuel Valente, RIPE NCC) Look for Net: : IP on CPAN, or just go here: http://www.cpan.org/authors/id/M/MA/MANU/ A suggestion for added functionality was gratefully accepted, more comments are welcome at: swcontact(a)ripe.net - AS Request Checking and the Hostmaster Mail Robot (Timur Bakeyev, RIPE NCC) - Asused Allocation Checks (Timur Bakeyev, RIPE NCC) http://www.ripe.net/cgi-bin/webasused.pl.cgi 2. Tools in development - Robo-Bijal (Guy Vegoda, Level 3) Nice demonstration and explanation of a useful tool for IP address Management. - RIPE DB version 3.0 and RPSL Migration (Andrei Robachevski, RIPE NCC) Yes, you will be affected. http://www.ripe.net/ripencc/pub-services/db/rpsl/index.html - Secure Web pages (Maldwyn Morris, RIPE NCC) Demonstration of plans for RIPE NCC Member-only web pages. 3. Proposal for tools - Chair will bring up co-operative development of IP Address and Request Management Tool for LIRs in a mail on the lir-wg mailing list. http://www.ripe.net/ripe/about/maillists.html 4. Survey -Chair asked the attendees what they wanted from the BOF -Most seemed fairly happy with current level of presentations. -Members are encouraged to try the tools, especially asused and stt. They should all work on most modern, Unix-like OSes- bugs welcome at: swcontact(a)ripe.net http://www.ripe.net/ripencc/mem-services/tools/index.html There were no questions. Rob suggested creating a new working group: Tools-WG. 14. Next meetings - RIPE 39 Bologna 30 April - 4 May, 2001 - RIPE 40 Prague 1 - 5 October, 2001 15. AOB Rob sincerely thanked the RIPE 38 sponsors: Squire, Sanders and Dempsey / CentralNic BandX Exchange Xchange Point Carrier 1 16. Meeting Close

1 0