- ripe-list - mailman.ripe.net

Draft Document: Policy Development Process in RIPE
by Rob Blokzijl 22 Dec '04

22 Dec '04

Policy Development Process in RIPE R.Blokzijl 21 December 2004 1. Introduction Since its creation in 1989, RIPE has from time to time agreed on common practices. These common practices may come in different forms and/or under different names: - best common practice (or BCP), - recommendations to the community, - requests to the RIPE NCC, - recommendations to the RIPE NCC, - or just policy. In this document they are all called 'Policy'. The process that results in a policy has a few important and fundamental principles: a. it is open to all. Everyone interested in the wellbeing of the Internet may propose a policy, and take part in the discussions. b. it is transparent. All discussions and results are documented and freely available to all. c. conclusions are reached by consensus. This process has worked quite well over the years. This document does not seek to change that. What this document does try to accomplish is a description of the process that will improve its management. 2. The Process. In the process of developping a policy several distinct phases are identified: 1. Proposal Phase 2. Discussion Phase 3. Review Phase 4. Concluding Phase Each of these phases are detailed below. The whole process is summarised in a diagram, attached as Appendix A. This diagram contains timelines for the various stages of the process. These timelines are meant as defaults, or minimum timelines: individual proposals may define their own timelines. 2.1 Proposal Phase Discussions may be started by anyone at any time. Participants are welcome to discuss broad ideas as well as make detailed policy proposals. Proposals are made using a Policy Proposal template [TEMPLATE Appendix B]. The template forms a structure for the proposal. It details the reason for the proposal and any perceived consequences of the proposal. The RIPE NCC (the RIPE community's secretariat) identifies proposals with a number and publishes them in the appropriate section of the relevant working groups web pages. The page will indicate the version history and status of proposals: - Open for Discussion; - Agreed or - Withdrawn. Anyone that wants to draft a policy proposal may seek assistance from the RIPE NCC. The RIPE NCC will provide relevant facts, statistics and an assessment of the work involved in implementation of a proposal. The RIPE NCC will also assist with the drafting of text if its editorial services are required. A proposal is usually submitted via the chair of the relevant working group of RIPE. In case a working group can not easily be identified, the proposal may be submitted to the RIPE Chair. 2.2 Discussion Phase. Once a proposal has been submitted it will be announced on a dedicated mailing list to which anybody can subscribe: <policy-announce(a)ripe.net>. This announcement will also indicate where discussion on this proposal will take place. Usually this will be the relevant working group mailing list. Where a policy change would result in an amendment to a published policy document, the textual changes are initially published as a draft document for community review and comment. There may be multiple iterations of a draft document if there is significant comment and change suggested. The discussion phase will have a limited time period, but not less then four weeks. 2.3 Review Phase Following the conclusion of the comment period the RIPE Working Group Chair determines whether the working group has reached consensus. If consensus has not been reached then the proposer may decide to withdraw the proposal. Alternatively, a new round of discussion and documentation may occur. 2.4 Concluding Phase When the RIPE Working Group Chair determines that the working group has reached a consensus, s/he moves the proposal to a Last Call for comments. The Last Call announcement is posted to the working group mailing list, the Last Call announcements mailing list and Chairs of all working groups. At the end of the Last Call period the working group chairs will decide together whether a consensus has been achieved If a consensus has been achieved, the RIPE NCC will announce the decision of the RIPE Working Group Chairs and implement the policy, if needed. If consensus has not been achieved the proposer (or anyone else) is free to return the proposal to the working group for further discussion. [TEMPLATE Appendix B] 1. Number (assigned by the RIPE NCC) 2. Policy Proposal Name: 3. Author a. name: b. e-mail: c. telephone: d. organisation: 4. Proposal Version: 5. Submission Date: 6. Suggested WG for discussion and publication 7. Proposal type: a. new, modify, or delete. 8. Policy term: a. temporary, permanent, or renewable. 9. Summary of proposal 10. Policy text a. Current (if modify): b. New: 11. Rationale: a. Arguments supporting the proposal b. Arguments opposing the proposal

2 1

RIPE NCC closed on December 24
by Saskia van Gorp 22 Dec '04

22 Dec '04

Dear Colleagues, Our offices are closed on Friday 24 December 2004. We will reopen on Monday 27 December 2004. Our offices close on all Dutch public holidays listed at: http://www.ripe.net/ripencc/about/public-holidays.html Regards, Saskia van Gorp Front Office Manager RIPE NCC

1 0

Announcement: Policy Development Process in RIPE
by Rob Blokzijl 21 Dec '04

21 Dec '04

To the RIPE Community, later today I will publish a draft document that describes the policy making process in RIPE. It is draft, so your input is requested in order to come to a generally accepted final document. Logistics: - deadline for comments on the first draft: 1 Februari 2005 - discussion takes place on ripe-list(a)ripe.net - if you are not subscribed to ripe-list(a)ripe.net yet, go to http://www.ripe.net/mailman/listinfo/ripe-list#subscribers - for any questions, don't hesitate to contact chair(a)ripe.net As always, apologies for receiving multiple copies of this announcement. Best regards, Rob Blokzijl RIPE Chairman

2 1

about ripe.db on ftp.ripe.net
by Francisco Guerreiro 15 Dec '04

15 Dec '04

Hi, I'm doing a statistic work on ripe.db for my University (Faculty of Science of the Lisbon University) and I downloaded ripe.db.inetnum (from the split files directory) so I can do statistics on several portuguese speaking countrys and Portugal itself. The ripe.db.inetnum suits my needs exactly but the admin-c: and tech-c: objects refer to person: objects which can't be found on ripe.db. I've googled a bit and found reference (back in 1993) of a split of ripe.db named ripe.db.person which probably had the additional information I need. Since I don't see that ripe.db.person anywhere on the ftp and the other .db files don't have person: objects, I was wondering if they were removed due to spam issues or something, since they're accessible through normal whois.ripe.net query's (which are bound to massive querying limits). Could someone shed some light into this matter? regards, Francisco Guerreiro

3 6

Re: about ripe.db on ftp.ripe.net
by Wilfried Woeber, UniVie/ACOnet 15 Dec '04

15 Dec '04

>> objects, I was wondering if they were removed due to spam issues or=20 >> something, since they're accessible through normal whois.ripe.net=20 >> query's (which are bound to massive querying limits). >> Could someone shed some light into this matter? > >Afaik they where removed because people used them for mass marketing >(thus including spam). Exactly. There's probably more than one way to still do what you think is useful or necessary: - try to select from the inet[6]num split files those entries which are "interesting" and query the contacts from the live DB (subject to Q limits - see next bullet) - talk to the DB operators (ripe-dbm(a)ripe.net), explain to them what you inted to do, and why, and get an exemption from the Q-limit - talk to the DB operators and explain what your want to do, and why, and ask for access to the "missing" person,... split file. This might solve your problem if you want to perform a snapshot analsys - if you want to run your analysis on a more regular basis, then getting an NRTM[1] set up at your site might be a better solution. This requires a formal agreement with the NCC about the DO's and DON'Ts, again talk to ripe-dbm. [1] Near(ly) Real Time Mirror. Hth, Wilfried ( https://cert.aco.net/ ) _________________________________:_____________________________________ 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ...there's no place like 127.0.0.1 (or 0::1/128 ?)

2 1

Re: about ripe.db on ftp.ripe.net
by Wilfried Woeber, UniVie/ACOnet 15 Dec '04

15 Dec '04

>On 15 Dec 2004, at 08:57, Jeroen Massar wrote: > >> If you want to see the amount of 'same persons' you >> can also compare the handles themselves... > >To some extent. A number of individuals have multiple handles. >Possible reasons include: > - no housekeeping after someone moved to a new job, > - automatic introduction of new handles during bulk operations. - and ERX :-( As an example, submit a query on "Walter Kunft" ... >Best regards, > >Niall O'Reilly > >PGP key ID: AE995ED9 (see www.pgp.net) >Fingerprint: 23DC C6DE 8874 2432 2BE0 3905 7987 E48D AE99 5ED9 Wilfried.

1 0

NRO Response to ITU Comments on the Management of Internet Protocol (IP) Addresses
by Axel Pawlik 15 Nov '04

15 Nov '04

Dear Colleagues, As part of the World Summit on the Information Society (WSIS) process, a proposal has been made that could dramatically affect the way Internet number resources are distributed and managed. On 21 October 2004, the Director of ITU-TSB published a memorandum, "ITU and Internet Governance" for public comment. This memorandum includes a proposal to create a new IPv6 address space distribution process, based solely on national authorities. This could have a serious impact on RIPE NCC Members, Internet operators and the global Internet community at large. The Number Resource Organization (NRO), on behalf of the Regional Internet Registries, has prepared a public response to the ITU memorandum detailing the flaws of the proposal and the negative impact it would have on Internet operations. A summary of this response is available at: http://www.nro.net/documents/nro18.html The full response is available at: http://www.nro.net/documents/nro17.html The original ITU memorandum is available at: http://www.itu.int/ITU-T/tsb-director/itut-wsis/files/zhao-netgov01.doc We urge our members and others in the Internet community to make their views about this issue known. Without your support being *visible* and *explicit* the bottom-up, consensus based model on which the success of the Internet has been founded may be replaced by the top-down bureaucracy of "Internet Governance". To show your support: - RIPE NCC Members: Log in to the LIR Portal and tick the support box. If you do not have an LIR Portal account, please email your expression of support to: contact(a)ripe.net - Non-members: Please email to: im-support(a)ripe.net. An email archive of expressions of support will be available at: http://www.ripe.net/maillists/ncc-archives/im-support/ - ITU-TSB Members: Please also contact your ITU member state representative to voice your concerns you might have. Internet number resource distribution is fair and accessible to all. Its policy development process is open and transparent. It works. Let us keep it that way. Regards, Axel Pawlik Managing Director RIPE NCC

1 0

(no subject)
by abeer siraj 23 Oct '04

23 Oct '04

_________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.com/

1 0

ICANN and the NRO sign ICANN ASO MoU
by Paul Rendek 21 Oct '04

21 Oct '04

Dear Colleagues, I am happy to inform you that on 21 October 2004, the Number Resource Organization (NRO) and the Internet Corporation for Assigned Names and Numbers (ICANN) signed a formal Memorandum of Understanding (MoU) on the Address Supporting Organization (ASO). This MoU stipulates how the NRO will fulfil the role, responsibilities, and functions of the ASO as outlined in the ICANN Bylaws. The signing ceremony took place at the biannual Public Policy Meeting of the American Registry for Internet Numbers (ARIN). More information on the MoU is available at: http://www.nro.net/archive/press-releases/aso-mou.html The full text of the MoU is available at: http://www.nro.net/documents/aso-mou.html Regards, Paul Rendek Head of Member Services and Communications RIPE NCC

1 0

RIPE 49 Meeting Report
by Nick Hyrka 18 Oct '04

18 Oct '04

[Apologies for duplicate mails.] RIPE 49 MEETING REPORT Dear Colleagues, The RIPE 49 Meeting was held from 20 - 24 September 2004 at the Renaissance Hotel, Manchester, United Kingdom. There were 301 participants at the meeting. Attendees also included government representatives and representatives from AfriNIC, APNIC, ARIN, LACNIC and ICANN. HIGHLIGHTS Highlights of RIPE 49 included an update on the Number Resource Organization from Axel Pawlik, Managing Director, RIPE NCC; a discussion on the RIPE policy development process; a proposal to restructure RIPE Meetings into three days on operational/technical content followed by two days on policy related issues. The ASO held an election for a seat on the ASO Address Council. Hans Petter Holen was re-elected. Geoff Huston, APNIC, gave a report on the routing table status for IPv4 and IPv6. This presentation is available at: http://www.ripe.net/ripe/meetings/ripe-49/presentations/ripe49-plenary-bgp.… The European Operators Forum (EOF) featured presentations on peering and core network security. EOF presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-49/eof.html The RIPE NCC, LINX, TeleCity, Telecomplete and XChange Point Europe are thanked for the support they provided to the meeting. BT Net are thanked for the excellent provision of the meeting Internet connectivity. SUMMARY ADDRESS POLICY WORKING GROUP - It was agreed that IPv6 allocations from IANA to the RIRs had to be increased in terms of block size, and that /12 was the best allocation size to use. - RIPE Chair, Rob Blokzijl, announced that he would publish a draft of the policy development process for the RIPE region. - There was discussion on the usage of HD ratio for IPv4 and the forthcoming formal proposal regarding this. - The 200 End Users requirement for receiving an IPv6 allocation was discussed and it was agreed that a formal proposal to remove it should be sent to the community. Address Policy Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-49/presentations/index.html#ap DATABASE WORKING GROUP - It was agreed that the RIPE NCC should implement the 'abuse-c:' attribute in the 'irt', 'person', 'role' and 'inet[6]num' object classes. - It was agreed that the RIPE NCC should implement the 'poem' object in the RIPE Database. Database Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-49/presentations/index.html#db TEST TRAFFIC MEASUREMENT (TTM) WORKING GROUP - It was noted that ten test boxes, throughout the RIPE region, have been added to the RIPE NCC Test Traffic Measurements matrix in 2004. Test Traffic Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-49/presentations/index.html#tt ANTI-SPAM WORKING GROUP - A tutorial on message headers was given by Rodney Tillotson, Working Group Chair. - The group discussed the issue of improving the RIPE Database for abuse contacts. There was a majority support for a combination of 'irt' objects with some modifications, and for changes to the default Whois behaviour. Anti-Spam Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-49/presentations/index.html#anti-spam IPv6 WORKING GROUP - The RIPE NCC announced that K-root has been IPv6-enabled since August 2004. - Geoff Huston, APNIC, gave an update on multihoming in IPv6. - There was discussion about IPv6 glue for root name servers. IPv6 Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-49/presentations/index.html#ipv6 EIX WORKING GROUP - It was noted that the switching wish list is in last call and that the final review will take place at the Euro-IX meeting in Athens (October 2004). - It was noted that an Inter Providers Traffic Analyzer tool is available from the Milan Internet Exchange. EIX Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-49/presentations/index.html#eix ENUM WORKING GROUP - There was a presentation from the United Kingdom's Department of Trade and Industry (DTI) on an ENUM Consultation regarding how ENUM should be operated in the UK. - There was a presentation on ENUM deployment in Sweden. ENUM Working Group Presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-49/presentations/index.html#enum DNS WORKING GROUP - It was agreed that the DNS Working Group should take up responsibility for documenting the issues around DNS server migration. - It was noted that the DNS Working Group Chair would collect requirements for the DNS samples and statistics. - It was noted that the DNS Working Group Chair would coordinate the production of a RIPE Document based on Fernando Garcia's DNS Server Migration document. DNS Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-49/presentations/index.html#dns ROUTING WORKING GROUP - It was announced that the maintenance of the IRR Toolset has been transferred from the RIPE NCC to the Internet Systems Consortium (ISC). - There was discussion on securing the network through hiding the core. - There was an overview of the RIS project and discussion on the various uses of the myASn BGP monitoring tool. Routing Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-49/presentations/index.html#routing RIPE NCC SERVICES WORKING GROUP - It was agreed that the RIPE Chair would look at the possibilities of reworking the framework of RIPE meetings, so that operational content would come at the beginning of the meeting week and policy discussions would come at the end of the week. - It was agreed that the RIPE NCC would generate statistics on the quantity of spam on the RIPE NCC servers. RIPE NCC Services Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-49/presentations/index.html#ncc-serv… TUTORIALS The RIPE NCC Training Team 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-49/lir-course/index.html RIPE 49 WEBCASTING AND ARCHIVES During RIPE 49, 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 49 are available at: http://www.ripe.net/ripe/meetings/ripe-49/sessions-archive.html HOSTMASTER CONSULTATION CENTRE (HCC) The RIPE NCC Hostmaster Consultation Centre was open at RIPE 49, allowing RIPE NCC Members to discuss issues relating to their business directly with RIPE NCC Hostmasters. "MEET & GREET" The RIPE NCC's "Meet & Greet" was available for first-time RIPE Meeting attendees at RIPE 49. "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 49 REFERENCE PAGE A complete list of RIPE 49 sessions, tutorials and presentations can be found at: http://www.ripe.net/ripe/meetings/ripe-49/index.html RIPE 50 RIPE 50 will be held in Stockholm, Sweden from 2 - 6 May 2005. Information on RIPE 50 will soon be made available at: http://www.ripe.net/ripe/meetings/ripe-50/ If you have any questions about RIPE Meetings, please contact <meeting(a)ripe.net>. -- end --

1 0