- address-policy-wg - mailman.ripe.net

RIPE NCC allocations to African LIRs
by leo vegoda 15 Oct '03

15 Oct '03

Dear Colleagues, The RIPE NCC received the IPv4 address range 196.200.0.0/13 from ARIN in October 2003. This range will be used to make allocations and assignments to organisations based in African countries served by the RIPE NCC. This block is part of a /8 also used by ARIN. In order to reduce confusion the RIPE NCC will not assign prefixes longer than a /24 from it. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: <http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html> Kind regards, -- leo vegoda RIPE NCC Registration Services Manager

1 0

Some questions regarding the NRO proposal
by Hans Petter Holen 15 Oct '03

15 Oct '03

Dear all, First of all I would like to congratulate the RIRs with a constructive and solid proposal to move forward. I think the formalization of an organization to help the RIRs act in a coordinated manner is lomg overdue. As a general comment I think the detailed specification of the global policy making process is a step forward. Under the current MOU this is not well defined and clarification of the process should be much welcomed to all involved. In reading the proposal I have some questions, first to the NRO Agreement: 6. NRO Executive council Is there a clear enough division between legislative and executive roles? One of its roles is to ratify and reject global IP number policies. (Legislative), at the same time the Executive council is empowered to sign documents and contracts (executive). Maybe it needs some clarification in the language to make it clearer that the EC simply ratifies that polices has been formed according to process. 7 NRO Number Council ii Composition What is the reason for the proposed composition? The Board of the RIRs are elected by the members of the RIR and the current procedures for electing ASO AC members are that mostly the members elect the council members. The proposal is in reality a combination between a direct and indirect election. What is the advantage of this? Why not revert to just one approach direct or indirect election? a) Election by RIR members b) Election by RIR boards The Council shall under the agreement elect a chair. It may also be necessary to elect co-chairs and a secretary for the Council to maximize its ability to conduct its tasks. Regarding the composition of the two councils: what conflicts of interests exists between the two and the bodies of the RIRs? Are there global conflicts of interests or should this be left to the individual RIRs to decide? Then to the ASO MOU Attachment A: Global Policy Development Process: 4. For some RIRs (RIPE NCC) this introduces a new role to the Board in ratif ying policy proposals. While this may be a good idea - it does require some changes to the regional policy process to be aligned. Best Regards, Hans Petter Holen

2 1

Draft minutes: RIPE 46 Address Policy WG session
by leo vegoda 14 Oct '03

14 Oct '03

Dear Colleagues, Draft minutes from the Address Policy Working Group session at RIPE 46 can be found at: http://www.ripe.net/ripe/wg/address-policy/r46-minutes.html Please check the minutes for errors or omissions. Comments and corrections can be sent directly to this list or to one of the WG chairs personally. Additionally, draft minutes from the LIR Working Group at RIPE 45 are can be found at: http://www.ripe.net/ripe/wg/lir/r45-minutes.html These have not yet been approved and can still be corrected if appropriate. Kind regards, -- leo vegoda RIPE NCC Registration Services Manager

1 0

Call for volunteers: editorial group to revise "Charging by Local Internet Registries" document
by leo vegoda 13 Oct '03

13 Oct '03

Dear Colleagues, Last month at RIPE 46 the RIPE Address Policy Working Group (AP WG) discussed the RIPE document "Charging by Local Internet Registries" (ripe-152). The document was published in 1996 and describes "charging for services by Internet registries and indicates acceptable practice for such charging". It can be found at: <http://www.ripe.net/ripe/docs/chargingbylirs.html> Particular attention was given to the statement that "registries may charge for their administrative and technical services, they may not charge for name space or address space as such; no unit cost or price tag can be attached to a domain name or to an IP address, public or private." It was agreed that an editorial group of volunteers from the community should be formed discuss the document and suggest changes to its text and content. A mailing list has been created for this discussion. The list is open to anyone wishing to participate. If you want to subscribe to the list you can do so via the web interface at: <http://www.ripe.net/mailman/listinfo/ripe-152bis> Additionally, a web archive of the discussion can be found at: <http://www.ripe.net/ripe/mail-archives/ripe-152bis> Kind regards, -- leo vegoda RIPE NCC Registration Services Manager

1 0

Proposed Open Letter to ICANN and Related Documents
by Axel Pawlik 13 Oct '03

13 Oct '03

Dear Colleagues, The Regional Internet Registries (RIR) have published three (3) documents: a. Proposed Open Letter to ICANN from the Regional Internet Registries b. Proposed Agreement between the RIRs to create the Number Resource Organization c. Proposed Agreement between the RIRs (acting through the NRO) and ICANN concerning the Address Supporting Organization These documents are available on a single web page at: http://www.ripe.net/ripencc/about/regional/draft-public-comment.html In order to ensure that RIR members and address communities in every region have the opportunity to comment, the Board of the RIRs have requested that RIRs post the documents for a period of 30 days. The comment period closes at midnight (UTC) on the 22nd October 2003. Each of the RIR Boards will consider the comments as they are received, and each RIR Board intends to make a decision whether to adopt these documents following this comment period. If these documents are adopted by all the RIR Boards, it is the present intention to formally pass the following open letter to ICANN on the 24th of October. On the same date the Boards of the RIRs currently intend to direct their CEOs to sign the MoU concerning the establishment of the Number Resource Organization. All comments should be addressed to: nro-comments(a)apnic.net. The comments will be passed to all the Boards of the RIRs, and will also be published on the web site http://www.apnic.net/nro-comments. Any dialogue that arises from such comments will also be published on this site. Subscription information for the nro-comments mailing list is available at: http://mailman.apnic.net/mailman/listinfo/nro-comments All postings to this mail address (nro-comments(a)apnic.net) are public, and will be published at the following URL: http://www.apnic.net/nro-comments kind regards, Axel Pawlik Managing Director RIPE NCC

2 1

RIPE NCC Regional Meeting, Middle East, Dubai, 7-9 December 2003
by Membership Liason Officer 08 Oct '03

08 Oct '03

Dear Colleagues, The RIPE NCC is pleased to announce the RIPE NCC Regional Meeting, Middle East, to be held 7-9 December 2003 at the Metropolitan Palace Hotel, Dubai, U.A.E. Registration for the Regional Meeting opens 8 October 2003. Attendance to the RIPE NCC Regional Meeting is open and free of charge. However, attendees are responsible to cover their own travel and accommodation costs. To register, please see: http://www.ripe.net/cgi-bin/dubai-reg The RIPE NCC Regional Meeting will focus on Internet resource allocation and Internet management issues including: - How to participate in and influence IP address management policy-making; - The industry self-regulatory open structures and processes used by the RIPE NCC and the global Internet community; - Are we running out of IPv4 address space? - Root name server operations: who is involved? - Domain Name management on the Internet; - The internationalisation of Domain Names. The Regional Meeting draft agenda can be found at: http://www.ripe.net/ripencc/regional-meetings/dubai-2003/plan.html RIPE and the RIPE NCC will explain their roles in the administration of the Internet infrastructure as well as specific aspects in managing and operating the Internet infrastructure. The discussions will be directly related to the particular needs and concerns surrounding these issues in the Middle East region. The current meeting agenda reflects our intentions. However, it requires active participation from the local community to discuss specific issues of the region. The RIPE NCC has reserved several presentation opportunities for those with local knowledge of Internet management and operational issues affecting the Middle East. If your organisation wishes to provide a presentation or suggest a relevant topic, please send your proposal by e-mail to: <contact(a)ripe.net> The RIPE NCC is one of four Regional Internet Registries (RIRs) that provide Internet resource allocation, registration services and co-ordination activities that support the operation of the Internet globally. The RIPE NCC is an independent, not-for-profit membership organisation that provides services to members in its service region currently covering Europe, the Middle East, Central Asia and African countries located north of the equator. Any further questions about the RIPE NCC Regional Meeting, Middle East can be sent directly to: <contact(a)ripe.net>. Regards, Sabrina Wilmot Membership Liaison Officer RIPE NCC

1 0

Revised Draft Document for review: "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region"
by Dominic Spratley 05 Oct '03

05 Oct '03

Dear Colleagues, The RIPE NCC is pleased to announce an updated draft of the revised RIPE IPv4 policy document, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" (currently ripe-234). The major change from the draft published on 21st July is that the existing "status:" attribute values are kept for inetnum objects with the addition of a new value for sub-allocations. The updated draft can be downloaded from the "Drafts" section in the RIPE Document Store, found at: <http://www.ripe.net/ripe/draft-documents/> The major updates to the current policy text in this draft IPv4 policy document are: - Recent policy changes have been incorporated, including the policy allowing assignments for Internet experiments and the sub-allocation policy. - Wording has been improved to make it easier to read. - The explanation of how to use the database has been removed as a separate "RIPE Database User Manual: Getting Started" was published in September last year. - The document now incorporates the text from "Provider Independent vs Provider Aggregatable Address Space" (ripe-127). If the community accepts this document it will replace the existing IPv4 Policy document (ripe-234) and the "Provider Independent vs Provider Aggregatable Address Space" document (ripe-127). Feedback on this document should be sent to the address-policy-wg@localhost mailing list for a period of two weeks. This review period will end on TWO WEEKS FROM ANNOUNCEMENT. Dominic Spratley Registration Services Manager RIPE NCC

2 1

RIPE 46 Meeting Report
by Nick Hyrka 02 Oct '03

02 Oct '03

(Apologies for duplicate mails.) RIPE 46 Meeting Report Dear Colleagues: The RIPE 46 Meeting was held from 1 - 5 September 2003 at the Grand Hotel Krasnapolsky, Amsterdam, the Netherlands. There were a total of 307 attendees comprised of the RIPE NCC membership, the RIPE community and government representatives. Attendees also included representatives from APNIC, ARIN, AfriNIC, LACNIC and ICANN. HIGHLIGHTS ========== Highlights of RIPE 46 included the open discussion on the services of the RIPE NCC during the first session of the RIPE NCC Services Working Group; a presentation on current RIPE NCC services and plans for 2004 by Axel Pawlik, Managing Director, RIPE NCC; an AfriNIC update; and an update on the changes to Test Traffic Measurement. The European Operators Forum (EOF) featured a full-day tutorial on Voice over Internet Protocol (VoIP) and ENUM that included an overview of current technologies and a focus on practical deployment aspects such as gateways, security, provisioning and use of the new ENUM standards. Geoff Huston, Telstra, gave a presentation on IPv4 Address Lifetime Expectancy. The RIPE NCC would like to thank SURFnet, BIT, FLAG Telecom and KPN EuroRings for the support they provided to the meeting. SUMMARY ======== ADDRESS POLICY ============== - Hans Petter Holen, Chair, requested community involvement to help revise ripe-152 ("Charging by Local Internet Registries") if necessary. - The RIPE NCC will resubmit the IPv4 policy document for community review. - There was a discussion on PI/PA issues and whether the distinction is still valid. - It was agreed that a more formal process was needed for the policy development process. Address Policy Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#ap DATABASE ======== - Wilfried Woeber, Chair, will co-ordinate with the RIPE NCC to prepare a document summarising the basic assumptions about the use of the RIPE Database. - "status:" attribute values will change. Current efforts aim at consistency between the RIRs and having easy to understand values. - The organisation object proposal received positive feedback from the working group, with suggestions for other features. - The RIPE NCC will implement X.509 authentication before the next RIPE Meeting. Database Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#db TEST TRAFFIC MEASUREMENTS (TTM) ========================= - As of 1/1/2004 changes will be made to the TTM service contract: Fees will be lowered, all data will be made public with lightweight Acceptable Use Policy (AUP). - Bandwidth measurements: tests showed that results are not conclusive enough so the TTM service will wait before delivering this new product. TTM Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#tt ANTI-SPAM ========= - Rodney Tillotson, Chair, will post a proposal to the Anti-Spam mailing list regarding methods to improve finding abuse contacts in the RIPE Database. Anti-Spam Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#anti-spam IPv6 === - The 6BONE phase-out was discussed. The next milestone will be 01/01/2004 when new allocations stop. - Discussion on the separation of the identifier and locater functions of IP addresses in regards to IPv6 multihoming. IPv6 Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#ipv6 TECHSEC ======== - Community feedback was requested on the requirements needed to secure large scale IP infrastructure especially around CLI interface requirements. - The RIPE NCC presented a report on DNSSec status, DISI achievements since RIPE 45 and the impact of signing on zone size. - George Jones, Mitre, gave a presentation on operational security requirements including the history and current status of the requirements, related work, next steps and milestones. - Baiba Kaskina, TERENA, gave a presentation on Euro CSIRT developments that included details on the CSIRT Task Force, the countries involved, the projects and deliverables. - NLNetLab presented an update on Fonkey and PKI-related developments in IETF. TechSec Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#techsec EIX == - Support was expressed for aligning and harmonising IPv6 address space policy regarding IXPs with other RIRs and existing IPv4 policies. - Reports were presented by 11 European IXPs in Europe that showed a trend of steady growth, use of GE instead of FE and wide deployment of IPv6. - Discussion of the Inter-Provider Traffic Analyzer that uses past data and statistical calculations to detect anomalies in traffic patterns. - EIX presentations were given on the anycast deployments of the "F" and "K" root servers by ISC and the RIPE NCC. EIX Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#eix DN* === - From the merging of the former DNS Working Group and DNR Forum it was concluded that one working group is sufficient to deal with everything related to Domain Names. A new name/charter will be discussed on the mailing list. - Jaap Akkerhuis, DN* Co-Chair, will organise a "DNS Related Issues" document. - Peter Koch, DN* Co-Chair, talked about how firewall vendors could make mistakes handling DNS communication issues. DN* Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#dn RIPE NCC SERVICES ================ - Axel Pawlik noted that the RIPE NCC will present more details in next year's RIPE NCC budget. - There were comments on the current RIPE NCC services, whether they benefit the entire community and whether a 'pay per service' system could be an option. - There was discussion about the need for a more transparent evaluation of RIPE NCC activities and how they benefit the community. RIPE NCC Services Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/#ncc 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-46/tutorials/ip-request/ - A full-day tutorial on VoIP and ENUM was presented during the European Operators Forum (EOF). For more information about the EOF at RIPE 46 see: http://www.ripe.net/ripe/meetings/ripe-46/eof.html RIPE MEETING WEBCASTING ======================= - The third phase of RIPE Meeting webcasting trials was held at RIPE 46. Recordings of certain sessions from RIPE 46, including the Plenary, have been archived and can be accessed at: http://www.ripe.net/ripe/meetings/ripe-46/webcast.html HOSTMASTER CONSULTATION CENTRE (HCC) ==================================== - The RIPE NCC Hostmaster Consultation Centre was open at RIPE 46, allowing RIPE NCC Members to discuss issues relating to their business directly with RIPE NCC Hostmasters. Later consultation hours, as introduced at RIPE 44, were continued. "MEET & GREET" =============== - The RIPE NCC's "Meet & Greet" was available for first-time RIPE Meeting attendees at RIPE 46. "Meet & Greet" introduces newcomers to the meetings, to key attendees of the RIPE community and to social events throughout the week. More information can be obtained by contacting the RIPE NCC's Pepa Tejedor Carnicero at <meet-greet(a)ripe.net>. RIPE 46 REFERENCE PAGE ====================== - A complete list of RIPE 46 sessions, tutorials and presentations can be found at: http://www.ripe.net/ripe/meetings/ripe-46/index.html RIPE NCC GENERAL MEETING ======================= - The RIPE NCC General Meeting 2003 was held Friday, 5 September 2003, adjacent to the RIPE 46 Meeting, at the Hotel Krasnapolsky in Amsterdam. For the highlights from the RIPE NCC General Meeting 2003, please see: http://www.ripe.net/ripencc/about/gm/gm2003/highlights.html RIPE 47 ====== - RIPE 47 will be held in Amsterdam, the Netherlands, from 26 - 30 January 2004. Information on RIPE 47 will soon be made available at: http://www.ripe.net/ripe/meetings/ripe-47/ NEW LOCAL INTERNET REGISTRIES (LlRs) - PLEASE NOTE LIRs who signed up after 1 January 2002 are entitled to two (2) free tickets to attend the next 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 For more information, contact <meeting(a)ripe.net>. END

1 0

Re: [address-policy-wg] Re: [ncc-services-wg] Request Forms: upda ted and available on LIR Portal
by Kinder, Klaus 02 Oct '03

02 Oct '03

Hi, Ludger Bornhorst is on vacation but we have discussed this matter before he send this mail. Here two notes from my point of view: you wrote: The RIR->LIR level has the AW to express a given level of trust. I quite agree with you: You could use policies in a narrow interpretation or in a scope of interpretation in addition with your know how in cases of ip-address management, both is possible and essential. But you couldn't find this scope in ripe-283 e.g. #[EQUIPMENT DESCRIPTION]#, I think that's the problem. Or is this scope in addition to your AW an unwritten policy? you wrote: please don't feed the buerocracy. I can assure you that's not our target. From our point of view policies should give all parties, here the LIR's, a general Framework and not a straitjacket. mit freundlichen Grüßen/with best regards Klaus Kinder _________________________________________ Deutsche Telekom T-Com Headquarters Network Information Center Local Internet Registry Ammerländer Heerstr. 138, D-26129 Oldenburg +49 441 234 - 4530 (phone) +49 441 234 - 4589 (fax) E-Mail: Klaus.Kinder(a)telekom.de

1 0

RE: [address-policy-wg] Re: [ncc-services-wg] Request Forms: upda ted and available on LIR Portal
by Bornhorst, Ludger 25 Sep '03

25 Sep '03

Hi Christian, > The question is how complex an evaluation must be? The facts needed to > evaluate a normal IP requests are simply the number of nodes needing a > public IP address. In case one or more nodes needs more than 1 IP address > then documentation is needed to explain why to exceed the normal rules, also > in case the expected growth pr. year exceeds 100%. Yes, but I don't have any problem to ask endusers about their (planned) hardware and to document their needs in the way we've done it since several years now, like "We have 20 PC's, 5 routers, 200 dial-in-ports and so on..." This general information will (in most cases) be sufficient to evaluate IP requests. > It would of course be easier to falsify the number of nodes than to falsify > the documentation, but in case an end user intends to falsify information in > order to get more IP addresses than justifyable, then I don't see any easy > way to prevent this. Right, but there are still enduser who don't know about classless addressing. That means they are asking for "Class-C" nets just because they think its hip. So I think it's responsibility of the LIR's to tell this endusers about CIDR and its outcomes. And, yes I agree: If an enduser wants to cheat at you, I can't see a way to prevent this. > I would find it reasonable if larger requests still required some form of > documentation, for example /24 and above. But it would of course still be > very important for all LIRs to stress that the information received from the > enduser must be correct. ACK! This way it would be possible to serve the main part of the customers at a simple level and only ask reasonable questions (hardware documentation) if the request exceeds a certain level. I would like to stress that the /24 border should be the maximum limit of "freedom" given here. Maybe it's better to decrease this "HW-documentation-border" down to /25 or /26 ? What do you think? mit freundlichen Gruessen/with best regards Ludger Bornhorst ______________________________________________________________________ Deutsche Telekom AG T-Com Headquarters Network Information Center Ammerlander Heerstr. 138, D-26129 Oldenburg Hotline +49 441 234 4581 (phone) +49 800 3301180 +49 441 234 4589 (fax) +49 800 3301179 ludger.bornhorst(a)telekom.de (mail) dk.call-center(a)telekom.de

2 1