- ncc-services-wg - mailman.ripe.net

Re: [ncc-services-wg] Improved Secure Communication for Registration Services (RS) Mailboxes
by Wilfried Woeber, UniVie/ACOnet 25 Feb '04

25 Feb '04

Hi Shane! >Ignoring the "PGP versus X.509" question, does the membership want us to >support signed e-mail at all? What about encrypted e-mail? Of course I cannot speak for the membership, I can only do so for our LIR: Yes, signed email communication should be supported. In particular with the current situation that "from" and "to" lines are just "random text" in a "subset" of messages being sent on the net these days ;-) I think that encryption almost comes for free when we've got signatures, and should be offered as well, _but not be required_. >- -- >Shane Kerr >RIPE NCC Wilfried (at.aconet)

1 0

New Document available: RIPE-303
by RIPE NCC Document Announcement Service 25 Feb '04

25 Feb '04

New RIPE Document Announcement -------------------------------------- A new document is available from the RIPE document store. Ref: ripe-303 Title: Procedure for Becoming a Member of the RIPE NCC Author: Olivia Ruimwijk Ingrid Wijte Agata Peszkowska Emma Bretherick Leo Vegoda Dominic Spratley Date: February 2004 Format: PDF=142723 TXT=14811 Obsoletes: ripe-212, ripe-230, ripe-257 Obsoleted by: Updates: Updated by: Short content description ------------------------- This document aims to provide the necessary information for those who wish to become a member of the RIPE NCC by setting up a Local Internet Registry (LIR). In this document initial guidelines are given to organisations that are planning to set up an LIR. Further, the necessary steps to set up an LIR are described. Accessing the RIPE document store --------------------------------- You can access the RIPE documents in HTML format via our website at the following URL:. http://www.ripe.net/docs/new-lir.html The RIPE Document Store is also 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-303.pdf PDF version ftp://ftp.ripe.net/ripe/docs/ripe-303.txt plain text version

1 0

RE: Improved Secure Communication for Registration Services (RS) Mailboxes
by Wilfried Woeber, UniVie/ACOnet 25 Feb '04

25 Feb '04

> I object on making x.509 the sole method of authenticated > communication with RIPE. I would certainly object against the PGP technology _which is in place now_ being phased out (soon). However, the NCC has reported that for _some_ applications/interfaces the integration of PGP into the server environment and with scripts is cumbersome. Although I do not have first hand experience of my own, I do not have any reason to question that. If one/some of the document(s) needs re-wording to make that clear, then we should put our effort into that. And yes, I still have to find the spare time to read the text this is referring to. [ taking off my DB-WG hat ;-] On a more private side, I still think that PKI technology is not mature enough, and stable enough, to be used in a production environment which is NOT based on a "point and click on demand" interface. OTOH, unless we start trying to do that, this will never change. Wilfried. _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ the street finds its own use for technology...

2 1

Re: [address-policy-wg] New Draft Document: De-boganising New Address Blocks
by Wilfried Woeber, UniVie/ACOnet 25 Feb '04

25 Feb '04

[ cc: list trimmed ] >However, it will also allow spammers to announce this >space and get it through bogon filters. [ ... ] >Why can't ISPs subscribe to a feed of all new >RIPE allocations in near real-time? Do you have any simple and concise definition of "ISP" for this context which would solve your "hide the info from spammers" issue? >--Michael Dillon Wilfried. _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Re: [ncc-services-wg] Improved Secure Communication for Registration Services (RS) Mailboxes
by Michael.Dillon＠radianz.com 25 Feb '04

25 Feb '04

>I object on making x.509 the sole method of authenticated >communication with RIPE. >There's GPG, and it works, now. I think this is an exageration. The only form of authenticated communication which works now over the Internet is SSL combined with HTTP. The choice of which secure technology is irrelevant. The security features of the technology are irrelevant. The only thing that matters is how easy will it be to use the new technology and how will RIPE teach people to use the technology and what tools will RIPE make available to people to run on their Windows machines, Macintosh machines and UNIX workstations so that they can use this new technology as easily as they use the web or email today. GPG isn't necessarily any easier to learn and use than X.509 is. Remember, the audience for this is the LIR staff who administer IP address allocations. They are not necessarily engineers or technical people. They probably don't use UNIX workstations and they probably don't know how to write scripts or use a command line. --Michael Dillon

2 1

New Draft Document: De-boganising New Address Blocks
by RIPE NCC WebMaster 25 Feb '04

25 Feb '04

(Apologies for duplicate mails) Dear Colleagues, The RIPE NCC has prepared a draft document titled "De-Bogonising New Address Blocks": <http://www.ripe.net/ripe/draft-documents/deboganising-draft.html> Abstract "This document describes an improvement in the notification process about new blocks of address space being distributed by the RIRs. It is a draft at this stage and your comments are solicited. However to gain experience before finalising the procedures, the RIPE NCC will shortly start announcing the routes from 84/8 described in the document under "pilot"." This document is published as a draft document in order to give RIPE NCC members time to read it and provide feedback. This draft document can be discussed on the RIPE NCC Services Working Group mailing list at <ncc-services-wg(a)ripe.net>. Regards, Webmaster RIPE NCC

2 1

RIPE 47 Meeting Report
by Nick Hyrka 24 Feb '04

24 Feb '04

(Apologies for any duplicate mails.) RIPE 47 Meeting Report Dear Colleagues, The <http://www.ripe.net/ripe/meetings/ripe-47/index.html>RIPE 47 Meeting was held from 26 - 30 January 2004 at the Grand Hotel Krasnapolsky, Amsterdam, the Netherlands. There were a total of 253 attendees comprised of the RIPE NCC membership, the RIPE community and government representatives. Attendees also included representatives from APNIC, ARIN, AfriNIC, LACNIC, ICANN and IANA. HIGHLIGHTS ========== - Highlights of RIPE 47 included the open discussion on the services of the RIPE NCC during the RIPE NCC Services Working Group; updates on the World Summit on the Information Society from Mirjam Khne, ISOC, and Axel Pawlik, Managing Director, RIPE NCC; an AfriNIC update; the proposal by the RIPE community to make RIPE 152 ( 'Charging by Local Internet Registries') a historical document. - As announced by Rob Blokzijl, RIPE Chair, two RIPE Meetings will be held in 2005. Based on the feedback from the community, this schedule will continue in 2006. The RIPE NCC will offer additional support to RIPE Working Groups to facilitate discussion and progress between RIPE Meetings. - Robin Tasker (CCLRC) gave a presentation on the European Commission-sponsored DataTAG project. - The European Operators Forum (EOF) featured an NSP Security BoF, a presentation on which types of SMTP flows should be blocked to prevent spam, a case study on the migration of AOL's backbone network from OSPF to IS-IS and discussion on the use of XML in network configuration. EOF presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/index.html#eof>http://www.ripe.net/ripe/meetings/ripe-47/presentations/index.html#eof - The RIPE NCC, Afilias, Cisco, NIKHEF, NOKIA, Riverhead and SURFnet are thanked for the support they provided to the meeting. Global Voice Networks are thanked for the provision of excellent Internet connectivity. SUMMARY ======== ADDRESS POLICY - It was proposed that RIPE 152 ('Charging by Local Internet Registries') should be made a historical document and that the RIPE NCC should make a clear statement on <http://www.ripe.net/>www.ripe.net that it does not charge for IP addresses. - Hans Petter Holen, Chair, will form a task force to write a policy development process proposal. - Consensus is needed on the mailing list on the AfriNIC proposal regarding /22 minimum allocation size. - Hans Petter Holen, Chair, will start a discussion on the mailing list on changing the 80% rule for IPv4 allocations. Address Policy Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ap>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ap DATABASE - The issue of CRISP versus joint Whois was discussed. - The proposal to introduce new attribute "abuse-c" in the inet(6)num objects was discussed. - A detailed proposal about "abuse-c" will be sent to Database Working Group mailing list. Database Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#db>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#db TEST TRAFFIC MEASUREMENT (TTM) - It was noted that as of 1/1/2004 changes were made to the TTM service contract: Fees were lowered (from 3000 EUR per year to 1000 EUR per year) and all data has been made public as specified in RIPE 300 ('Test Traffic Measurement Service Data Disclosure Policy'). - Two presentations made use of TTM delay data: a presentation on delay tomography used traceroute data from the TTM project; a presentation on the reordering of IP packets used delay data. TTM Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#tt>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#tt ANTI-SPAM - A proposal has been sent to the Database Working Group mailing list regarding the inclusion of an abuse-c attribute/object in the RIPE Database to help solve the problem of misdirected/multiple spam complaints. - It was noted that the European Commission Directive is now widely implemented and that in the United States CAN-SPAM is the first federal legislation. IPv6 - The anycast policy discussion was sent to the Address Policy Working Group. - There was discussion on how 6 to 4 is being used to spoof IPv4 origin addresses to make Distributed Denial of Service (DDoS) attacks anonymous. - There was a presentation on the security implications of IPv6 on IPv4 networks. IPv6 Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ipv6>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ipv6 EIX - An editorial group will be set up to revise the exchange point operator wish list for switches. - Operator-member charters for exchange points were discussed. - DE-CIX presented their experience migrating to new hardware and adding new premises. EIX Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#eix>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#eix DN* - The DNR Forum and the DNS Working Group were combined under the DNS Working Group heading. - It was noted that the ENUM RFC 2916bis has been approved by the IETF Working Group and is in the queue of the RFC editor. - It was noted that Internationalized Domain Names (IDN) are being deployed in more new regions. DN* Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#dn>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#dn ROUTING - There was a presentation on RISwhois, a tool that allows IP address to origin ASN mapping. - Case studies about convergence of IGP protocols were presented and discussed. Routing Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#routing>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#routing RIPE NCC SERVICES - Bijal Sanghani, FLAG Telecom, was appointed as the co-chair of the Working Group. - The RIPE NCC will explore the possibility of providing a service giving test statistics on the routability of new blocks. - The RIPE NCC will give a status update on the Activity Plan 2004 and request input for the Activity Plan 2005 during the RIPE NCC Services Working Group at RIPE 48. RIPE NCC Services Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ncc-services>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ncc-services TUTORIALS ========= The RIPE NCC staff presented the RIPE NCC IP Request Tutorial. It explained address space assignment and allocation procedures in the RIPE NCC region: <http://www.ripe.net/ripe/meetings/ripe-47/tutorials/ip-request/>http://www.ripe.net/ripe/meetings/ripe-47/tutorials/ip-request/ RIPE 47 WEBCASTING AND ARCHIVES ============================== During RIPE 47, the RIPE NCC held trials in collecting feedback from participants watching the webcast. The mediums used for this were IRC and Jabber. Archives of presentations, webcasts and IRC/Jabber feedback from RIPE 47 are available at: <http://www.ripe.net/ripe/meetings/ripe-47/sessions-archive.html>http://www.ripe.net/ripe/meetings/ripe-47/sessions-archive.html HOSTMASTER CONSULTATION CENTRE (HCC) ==================================== The RIPE NCC Hostmaster Consultation Centre was open at RIPE 47, allowing RIPE NCC Members to discuss issues relating to their business directly with RIPE NCC Hostmasters. RIPE 47 REFERENCE PAGE ====================== A complete list of RIPE 47 sessions, tutorials and presentations can be found at: <http://www.ripe.net/ripe/meetings/ripe-47/index.html>http://www.ripe.net/ripe/meetings/ripe-47/index.html "MEET & GREET" ============= The RIPE NCC's "Meet & Greet" was available for first-time RIPE Meeting attendees at RIPE 47. "Meet & Greet" introduces newcomers to the meetings, to key attendees from the RIPE community and to social events throughout the week. More information can be obtained by contacting: <meet-greet(a)ripe.net>. RIPE 48 ====== RIPE 48 will be held in Amsterdam, the Netherlands, from 3 - 7 May 2004. Information on RIPE 48 will soon be made available at: <http://www.ripe.net/ripe/meetings/ripe-48/>http://www.ripe.net/ripe/meetings/ripe-48/ New Local Internet Registries (LIRs) ========================== Please note: New LIRs are entitled to two (2) free tickets to attend a RIPE Meeting. The tickets cover the meeting fee only and do not apply to the RIPE dinner, travel or hotel accommodation. More information on the new LIR tickets can be found at: <http://www.ripe.net/ripe/meetings/new-lir.html>http://www.ripe.net/ripe/meetings/new-lir.html For more information, contact <meeting(a)ripe.net>. -- end --

4 3

Organisation object timeline
by Engin Gunduz 18 Feb '04

18 Feb '04

Dear Colleagues, [apologies for duplicate mails] Please find below the timeline for deployment of organisation object in the RIPE Whois Database. You can find the latest organisation object proposal at http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00689.html For questions and comments please contact me at <engin(a)ripe.net>. Best regards, -- Engin Gunduz RIPE NCC Software Engineering Department ================================ Timeline for Organisation Object ================================ 11 March 2004 Thursday : Pre-release of whois software with organisation object capability. (for tests by external parties, LIRs) 17 April 2004 Saturday : Deployment of whois software with organisation object capability. Creation of organisation objects for existing LIRs, update of existing allocation inetnums and inet6nums. 19 April 2004 Monday : The RIPE NCC starts using the new request forms updated for organisation object.

1 0

Membership Growth Survey 2004
by Axel Pawlik 17 Feb '04

17 Feb '04

Dear Colleagues, For member activities and budgeting purposes, the RIPE NCC relies on annual membership growth estimates. This is particularly important when setting membership fees. The RIPE NCC is dedicated to making sure we answer to the expectations and needs of our membership. With this in mind, we are currently looking at predictions for growth over the coming two years. Starting Tuesday 18 February, we will carry out a survey to estimate how many members we will have in your country over the next two years. We already look at past trends and our industry knowledge, but these figures can be significantly improved by using your knowledge of the market and local conditions. You know the local IT business and conditions far better than we do. The survey, which you can access through the LIR Portal, will be short and simple to complete and should take no more than a few minutes of your time. It will be available for six weeks. We are not asking you for exact predictions, but we would like you to give us your best estimate. Individual estimates provided will be held in strict confidence by the RIPE NCC and used only in connection with this survey. After the survey has ended, we will provide a report on how your estimates compare with the average in your country. To encourage members to give their input, the RIPE NCC will send each survey participant a small gift. To make sure that you receive this gift and it is not sent to the wrong address, we will ask you to ensure that the contact details we currently hold for you are correct. To take part, you will need to log into the LIR Portal. Once there you will find a link to the survey from Tuesday 18 February 2004 for six weeks: <https://lirportal.ripe.net/>https://lirportal.ripe.net Regards Axel Pawlik Managing Director RIPE NCC

1 0

RE: [ncc-services-wg] Minutes from RIPE NCC Services WG - RIPE 47
by Sanghani, Bijal 11 Feb '04

11 Feb '04

Sure, please see attached :o) -----Original Message----- From: Denesh Bhabuta [mailto:denesh@cyberstrider.net] Sent: Wednesday, February 11, 2004 3:04 PM To: Sanghani, Bijal; 'ncc-services-wg(a)ripe.net' Subject: Re: [ncc-services-wg] Minutes from RIPE NCC Services WG - RIPE 47 Hi Bijal Would it be possible to have the minutes in plain text rather than in MS Word? pretty please... :-) Regards Denesh --On Wednesday, February 11, 2004 12:16:54 +0000 "Sanghani, Bijal" <BSanghani(a)flagtelecom.com> wrote: > Hi All, > > Attached are the draft minutes for the RIPE NCC Services WG session for > RIPE 47 last month, please send details of any errors, corrections or > clarifications to Kurtis, myself or to this list. > > The theme for our session at RIPE 48 will be the RIPE NCC Activity Plan, > Axel Pawlik has agreed to give us an update on the progress made on the > 2004 plan and input into the 2005 Activity Plan is also welcome. > > If anyone would like to make a presentation or raise a topic for > discussion please let Kurtis and myself know and we'll arrange a spot in > the agenda. > > Best regards, > Bijal Sanghani > FLAG Telecom > > <<RIPE NCC Service WG minutes RIPE 47.doc>> > > > ********************************************************************** > This e-mail message is confidential and is intended only for the use of > the individual or entity named above and contains information which is or > may be confidential, non-public or legally privileged. Any dissemination > or distribution of this message other than to its intended recipient is > strictly prohibited. If you have received this message in error, please > notify us by email to postmaster(a)flagtelecom.com immediately and delete > the original message and all copies from all locations in your computer > systems. > > > This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG > Telecom cannot accept liability for any damage which you may sustain as a > result of software viruses. > ********************************************************************** > > > > > > This message has been scanned for viruses by MailControl - > www.mailcontrol.com This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0