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

New IPv6 Address Block Allocated to RIPE NCC
by leo vegoda 14 Jun '04

14 Jun '04

Dear Colleagues, The RIPE NCC received the IPv6 address range 2001:4000::/23 from the IANA in June 2004. 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: <https://www.ripe.net/ripe/docs/smallest-alloc-sizes.html> Regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

Re: [address-policy-wg] Policy Change Request - Allow address allocations for anycast DNS operation
by Wilfried Woeber, UniVie/ACOnet 11 Jun '04

11 Jun '04

Hi Andreas! >I have don't think that this should be an imperative. Do you really think >that LIRs should not be able to request such an allocation on behalf of >a customer that would like to do that? Sorry, my question was meant "the-other-way-'round": that a request has to come by way of an established LIR "in good standing" (this of course includes "friendly" existing LIRs offering the service for the project :-). I just wanted to be sure that we don't open a by-pass channel to the LIR structure. >If someone finds it cumbersome to renumber because he has to return the >resources granted to do dns anycasting he probably should not apply for >this resource ;-) Well, the picture might be a bit more complex, in particular for TLDs, when they have to "please" the IANA and/or ICANN to get a re-delegation at a certain point in time ;-) And I haven't yet thought to the bottom of how thing would look like if this becomes a service for supporting many zones, and all of them have to be renumbered because of an interaction with this "special assignment requirement"... >Cheers >Andreas Cheers/Servus, Wilfried. PS: and slightly off-topic: I honestly dislike special arrangements in general - when they are meant to punch holes into too restrictive general resource management rules. We have built too many cans of worms in the past doing so...

1 0

Re: [address-policy-wg] Policy Change Request - Allow address allocations for anycast DNS operation
by Wilfried Woeber, UniVie/ACOnet 09 Jun '04

09 Jun '04

>> I would suggest a slight re-phrase: > >> "Operators providing DNS for a zone served by a number of name servers >> such that the total response size when including the list of >> nameservers for the zone is close to the UDP packet >> size limit may be assigned PI network prefixes for the purpose of >> anycasting name servers, as described on RFC 3258. These shall be: a >> /24 IPv4 prefix and/or a /32 IPv6 prefix." > >> Given that the issue is the will to anycast due to the operational >> impact of adding more servers to the list, not just the size of the NS >> RRSET itself. > >I see your point and it's the same thing I had in mind when I wrote the >policy down. I don't think that it makes sense to work to hard on an exact >definition when someone classifies for an allocation. It depends on how tight we want to knit the mesh (and emphasise conservation et.al. :-) > As well it is >impractical to say you have to cross the limits first (and prove that >your clients are suffering from it) before you can get your allocation. Agreed. >I thought that those who are attracted by the policy will have no problem >justifying it and RIPE would have no problem to ask people returning the >networks if they do not use them as stated in the policy. But maybe >my thinking is too positive here. I guess everything which essentially gives you easy access to a PI /24 (/32 for that matter in the long run) is going to attract interest, at least eventually. Thus here are my questions for double-checking my own mental picture and assumptions: - the applicant has to be an established LIR - correct? - as setting up a server and finding slaves, plus anycast in general is not really rocket science: is there any closer definiton of "Operators providing DNS for a zone served by a number of name servers..." - would my own domain (say - netcraft.at) qualify as well? - and trying to reclaim that address space would be pretty cumbersome for both parties, I guess, unless the zone (all zones on those servers?) go(es) away _completely_ ?! Cheers, Wilfried.

3 2

RIPE NCC Regional Meeting, Nairobi 28-30 July 2004
by Membership Liaison Officer 07 Jun '04

07 Jun '04

Dear Colleagues, The RIPE NCC is pleased to announce the RIPE NCC Regional Meeting in Nairobi, to be held 28-30 July 2004. Details of the venue will follow shortly. Attendance to the RIPE NCC Regional Meeting is open and free of charge. However, attendees are responsible for covering their own travel and accommodation costs. Registration for the Regional Meeting is open. To register, please see: http://www.ripe.net/cgi-bin/nairobi-reg The RIPE NCC Regional Meeting will focus on Internet resource allocation and Internet management issues including: - The industry self-regulatory open structures and processes used by the RIPE NCC and the global Internet community; - How to participate in and influence IP address management policy-making; - AfriNIC - The emerging RIR; - Peering and Exchange Points; - Are we running out of IPv4 address space?; - An update on IPv6; - Domain Name management on the Internet; - Root Server Operations. The Regional Meeting draft agenda can be found at: http://www.ripe.net/ripencc/regional-meetings/nairobi-2004/agenda.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 region. The current draft meeting agenda reflects our intentions. However, it requires active participation from the local community to discuss specific issues of the region. 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. Further information about the RIPE NCC and RIPE can be found at: http://www.ripe.net More information about the RIPE NCC Regional Meeting, Nairobi is available from: http://www.ripe.net/ripencc/regional-meetings/nairobi-2004/ Any further questions can be sent directly to: <contact(a)ripe.net>. Regards, Nathalie Dougall Membership Liaison Officer RIPE NCC

1 0

Registration Deadline - RIPE NCC Regional Meeting, Moscow 16-18 June 2004
by Membership Liaison Officer 07 Jun '04

07 Jun '04

[Apologies for duplicate mails] Dear Colleagues, This is a final reminder that the RIPE NCC Regional Meeting in Moscow will be held 16-18 June 2004 at the Hotel Metropol, Moscow, Russia. Attendance to the RIPE NCC Regional Meeting is free of charge. However, attendees are responsible for covering their own travel and accommodation costs. REGISTRATION Please note that registration for the Regional Meeting closes on 9 June 2004. To register, please see: http://www.ripe.net/cgi-bin/moscow-reg AGENDA The agenda has been recently updated with more information about speakers and presentations. For the full agenda, please see: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/agenda.html MORE INFORMATION More information about the RIPE NCC Regional Meeting, Moscow is available from: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/ Any further questions can be sent directly to: <contact(a)ripe.net>. Regards, Nathalie Dougall Membership Liaison Officer RIPE NCC

1 0

RIPE 48 Meeting Report
by Nick Hyrka 27 May '04

27 May '04

[Apologies for any duplicate mailings.] RIPE 48 Meeting Report Dear Colleagues, The RIPE 48 Meeting was held from 3 - 7 May 2004 at the Grand Hotel Krasnapolsky, Amsterdam, the Netherlands. There were a total of 267 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 48 included an update on the Number Resource Organization from Axel Pawlik, Managing Director, RIPE NCC; an open discussion on the proposed Memorandum of Understanding (MoU) between the Number Resource Organization and ICANN; the community consensus to create an ENUM Working Group. J. Scott Marcus, Transatlantic Fellow, The German Marshall Fund of the United States, gave a presentation on the deployment challenges involved with evolving the core of the Internet. This presentation can be viewed at: http://www.ripe.net/ripe/meetings/ripe-48/presentations/ripe48-plenary-marc… The European Operators Forum (EOF) featured presentations on lawful interception of IP traffic, managing a DoS attack, stable BGP routing, strategies for IP traffic engineering, analysing the Internet Routing Registries, IP Address Space and AS Number hijacking and applications of Bidirectional Forwarding Detection (BFD). EOF presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#eof The RIPE NCC, FLAG Telecom, Amsterdam Internet Exchange and Interoute are thanked for the support they provided to the meeting. Global Voice Networks are thanked for the provision of the meeting Internet connectivity. SUMMARY ADDRESS POLICY WORKING GROUP - It was agreed that the issue of worldwide "shopping" for address space needs to be carefully considered before adopting different IPv4 additional allocation procedures (i.e. HD Ratio) in each region. - There were calls for the clarification and review of the initial allocation criteria for IPv6 allocations. The RIPE NCC will propose a rewrite of the IPv6 policy after the issue has been discussed in more detail on the mailing list. Address Policy Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#ap DATABASE WORKING GROUP - It was agreed that the 'country:' attribute should be either removed or be optional. - It was decided that the default behaviour of the RIPE Database will be changed to return the Incident Response Team (IRT) object if available, in order to make it easier for users to find relevant security contact information. Database Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#db TEST TRAFFIC MEASUREMENT (TTM) WORKING GROUP - Three presentations were given by Test Box users that offered useful tutorial information for all Test Box owners. - The Working Group Chair encouraged the RIPE NCC to investigate moving measurements into the O/S kernel and/or to hardware. - It was noted that the RIPE NCC has lowered the annual TTM service fee to 1000 euro/year for the first box, 500 euro/year for the second to ninth boxes and that a large company has offered to sponsor hardware for non-profit, research institutes. Test Traffic Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#tt ANTI-SPAM WORKING GROUP - The community was asked to look at the Anti-Spam Working Group charter and to suggest how it should be changed. - Fearghas McKay reported on the sender-pays stream and specifically on the 'camram' proposal which uses a well-documented system for generating cryptographic signatures ('hashcash'). - There was a proposal to establish a top level domain 'mail.' to be used as a type of DNS white-listing service. IPv6 WORKING GROUP - It was agreed that the Working Group Chair will seek consensus from the Working Group on whether the Minimum Technical IPv6 Peering Requirements (MIPP) document should become a RIPE document. - The community was asked to provide feedback on larger than default IPv6 allocations. - Pim van Pelt asked for members of the community who would like to run public 6to4 relays. IPv6 Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#ipv6 EIX WORKING GROUP - Kurtis Lindqvist presented his view from the IXP Customer View workshop. - Bijal Sanghani gave a presentation on the expectation an ISP has for an IXP. - European IXPs gave an update about the latest developments, including a presentation on the shared experience of engineers when they migrated their customers from one switch to another. EIX Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#eix DNS WORKING GROUP - It was agreed that the RIPE NCC will review the zone checks done by the reverse delegation robot. - DNS MODA was proposed by Jim Reid as a not-for-profit body to work on DNS protocol issues. - It was noted that the expansion of IPv6 makes the streamlining of IPv6 direct and reverse DNS even more necessary. DNS Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#dns ROUTING WORKING GROUP - It was agreed that the RIPE NCC should publish an IRR Toolset maintenance schedule. - There was a presentation on some of the technical issues of high-speed global roaming (flying an 802.11b wireless hot-spot at around 900 km/hr at altitudes around 10km). - There was a presentation on BGPlay, a tool that visualises Internet routing activity. Routing Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#routing RIPE NCC SERVICES WORKING GROUP - The RIPE NCC was asked to make a more detailed presentation on PGP encryption. - It was agreed that the RIPE NCC should start implementing the key-signing proposal. RIPE NCC Services Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#ncc-serv… TECHNICAL SECURITY WORKING GROUP - There was a presentation on security aware resolvers and discussion on the requirements for them. - There was discussion on 'server-side' protocol bits and the feeling that they are solid and ready for deployment; it was noted that validator/application communication and key-management issues need work. Technical Security Working Group presentations can be viewed at: http://www.ripe.net/ripe/meetings/ripe-48/presentations/index.html#techsec 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-48/tutorials/ip-request/index.html RIPE 48 WEBCASTING AND ARCHIVES During RIPE 48, 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 48 are available at: http://www.ripe.net/ripe/meetings/ripe-48/sessions-archive.html HOSTMASTER CONSULTATION CENTRE (HCC) The RIPE NCC Hostmaster Consultation Centre was open at RIPE 48, allowing RIPE NCC Members to discuss issues relating to their business directly with RIPE NCC Hostmasters. RIPE 48 REFERENCE PAGE A complete list of RIPE 48 sessions, tutorials and presentations can be found at: http://www.ripe.net/ripe/meetings/ripe-48/index.html "MEET & GREET" The RIPE NCC's "Meet & Greet" was available for first-time RIPE Meeting attendees at RIPE 48. "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 RIPE 49 will be held in Manchester, the United Kingdom, from 20 - 24 September 2004. Information on RIPE 49 will soon be made available at: http://www.ripe.net/ripe/meetings/ripe-49/ 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 For more information, contact <meeting(a)ripe.net>.

1 0

Reminder - RIPE NCC Regional Meeting, Moscow 16-18 June 2004
by Membership Liaison Officer 19 May '04

19 May '04

[Apologies for duplicate emails] Dear Colleague, We would like to remind you that the RIPE NCC Regional Meeting in Moscow will be held 16 - 18 June 2004 at the Hotel Metropol, Moscow, Russia. 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. REGISTRATION To register, please see: http://www.ripe.net/cgi-bin/moscow-reg Please note that registration closes on 7 June 2004. AGENDA The Regional Meeting draft agenda has been updated and can be found at: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/agenda.html MORE INFORMATION More information about the RIPE NCC Regional Meeting, Moscow is available from: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/ Any further questions can be sent directly to: <contact(a)ripe.net>. Regards, Nathalie Dougall Membership Liaison Officer RIPE NCC http://www.ripe.net

1 0

Result of ASO AC selection to the ICANN Board
by Paul Rendek 18 May '04

18 May '04

At the recent meeting on Thursday, 6 May 2004, in Amsterdam, the Address Council of the ASO selected Raimundo Beca to fill the ASO position on the ICANN Board to be vacated by Lyman Chapin. Raimundo Beca will immediately start to serve on the ICANN board for a term of three years. The minutes of the meeting will be available shortly on the ASO website at: http://www.aso.icann.org/meetings/ Regards, Paul Rendek Head of Member Services and Communications RIPE NCC

1 0

Draft minutes: RIPE 48 Address Policy WG session
by leo vegoda 17 May '04

17 May '04

Dear Colleagues, Draft minutes from the Address Policy Working Group session at RIPE 48 can be found at: http://www.ripe.net/ripe/wg/address-policy/r48-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. Kind regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

AfriNIC Transition: IPv4 allocation Policy change for African LIRs
by Andrea Cima 17 May '04

17 May '04

Dear Colleagues, On Friday 14 May 2004, Hans Petter Holen, Address Policy Working Group Chair, confirmed the consensus on the proposal to change the minimum IPv4 allocation size to /22 in the African countries in the RIPE NCC service region. http://www.ripe.net/ripe/mail-archives/address-policy-wg/2004/msg00212.html A larger allocation block will be made when justified by the Local Internet Registry. No comments were made and consensus was reached. The RIPE NCC will implement this policy on 17 May 2004. The supporting documentation will be updated as soon as possible. Please note that /22 allocations will only come from the 196.200.0.0/13 block. Best regards, Andrea Cima Snr. Hostmaster RIPE NCC -

1 0

AfriNIC Transition: IPv4 allocation Policy change for African LIR
by Adiel A. AKPLOGAN 14 May '04

14 May '04

Dear WG, I would like to make a last call for consensus on the proposal to modify the IPv4 allocation policy in the African portion of the RIPE NCC service region. The detailed proposal was posted to this list on 18 January and can be found at: http://www.ripe.net/ripe/mail-archives/address-policy-wg/2004/msg00123.html It was also discussed at RIPE 47 later in January. A copy of the presentation made to the Address Policy WG can be found at: http://www.ripe.net/ripe/meetings/ripe-47/presentations/ripe47-ap-afrinic-p… and minutes of the discussion that took place can be found at: http://www.ripe.net/ripe/wg/address-policy/r47-minutes.html (See section E). If there are no major objections to the policy proposal We would like to see the policy implemented as soon as possible. _______________________________________________________________________ Adiel A. AKPLOGAN Tel. +27 (0)12 841 2894 AfriNIC - Project Manager Fax: +27 (0)12 841 4720 2nd Floor, Les Jamalacs Building adiel(a)afrinic.org Vieux Conseil Street - Port-Louis MU www.afrinic.net

3 3

RIRs and IPv6 Groups Pledge Support of Global IPv6 Deployment
by Paul Rendek 12 May '04

12 May '04

Dear Colleagues, The RIRs, the IPv6 Task Forces, and the IPv6 Forum have issued a joint press release detailing co-operative efforts in support of global IPv6 deployment. The press release is available on the RIPE NCC website at: http://www.ripe.net/ipv6/ipv6-support-20040512.html Regards, Paul Rendek Head of Member Services and Communications RIPE NCC

1 0

Call for volunteers for Policy Development Process
by Hans Petter Holen 11 May '04

11 May '04

Dear Address Policy Working Group, At recent RIPE meetings we have discussed how to better document the RIPE policy development process. This will not only improve openness and transparency, but may also encourage participation from a wide audience, including those that are not able to attend RIPE meetings. At the Address Policy working group meeting last week, I called for volunteers to help writing the documentation for this process. I further proposed a timeline for the task to result in drafts to be delveopled before the next wg meeting. A mailing list has been set up, to discuss the process. It is open to everyone. You can subscribe at the URL below. http://www.ripe.net/mailman/listinfo/ripe-pdp The list is publicly archived at: http://www.ripe.net/ripe/mail-archives/ripe-pdp/ We'd like to start the discussion from 17 May[1], to continue over the summer. Our goal is to have completed work by mid November. The proposed timeline and more information can be found in last week's presentation to the Address Policy WG, available from: http://www.ripe.net/ripe/meetings/ripe-48/presentations/ripe48-ap- policy-dev.pdf Webcasts of last week' Address Policy WG sessions can be found on the web site at: mms://webcast.ripe.net/ripe-48/ap-1.wmv mms://webcast.ripe.net/ripe-48/ap-2.wmv Looking forward to your participation, Hans Petter [1]Norway's Independence Day

1 0

ASO AC Announces ICANN Board Nominees: Expressions of Support Welcome
by Axel Pawlik 05 May '04

05 May '04

The Address Supporting Organization (ASO) has announced the following nominees for election to the ICANN Board of Directors: Lyman Chapin Raimundo Beca Statements of support for the nominees are welcome prior to the ASO General Assembly meeting on 5 May 2004, in Amsterdam, The Netherlands. To view the nominee bios and send expressions of support please visit: http://aso.icann.org/board/2004elections/index.html Regards, Axel Pawlik Managing Director RIPE NCC

2 2

Last Call for Comment: ICANN Address Supporting Organization (ASO) MoU
by Axel Pawlik 05 May '04

05 May '04

Dear Colleagues, The RIPE NCC has issued a call for comments on the proposed Memorandum of Understanding (MoU) between the Number Resource Organization (NRO) and ICANN. This MoU details the conditions under which and the manner in which the NRO will act as the ICANN Address Supporting Organization (ASO). As outlined in a signed Letter of Intent, each Regional Internet Registry (RIR) is required to have a public comment period. The Letter of Intent and draft MoU can be found on the NRO website at: http://www.nro.org/news/loi.html The RIPE NCC invites any interested parties to send comments to the nro-comments(a)nro.org mailing list. Subscription information for this list is provided at: http://www.nro.org/mailman/listinfo/nro-comments The closing date for the public comment period is Friday, 7 May 2004. Regards, Axel Pawlik Managing Director RIPE NCC

2 2

RE: [address-policy-wg] http://www.ietf.org/internet-drafts/draft-hain-1918bis-00.txt
by Wilfried Woeber, UniVie/ACOnet 26 Apr '04

26 Apr '04

Hi Joao, >A new draft requesting expansion of RFC 1918 space by adding 3 /8s to >space reserved for private use. > >Given the presented justification (see introduction): > >"Given the policies for acquiring additional public > space it is not reasonable for them to acquire such space for use in > their private networks. " what is the word "them" referring to? Or should I just read this draft (on top of some other MByte of stuff that should be read ;-) >I am left a bit confused about the statement and would like to have the >wg request the RIPE NCC to ask the author for further clarification > >Regards, >Joao Damas Thanks, 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 ::1 ?)

9 8

http://www.ietf.org/internet-drafts/draft-hain-1918bis-00.txt
by Joao Damas 23 Apr '04

23 Apr '04

A new draft requesting expansion of RFC 1918 space by adding 3 /8s to space reserved for private use. Given the presented justification (see introduction): "Given the policies for acquiring additional public space it is not reasonable for them to acquire such space for use in their private networks. " I am left a bit confused about the statement and would like to have the wg request the RIPE NCC to ask the author for further clarification Regards, Joao Damas

2 1

Re: http://www.ietf.org/internet-drafts/draft-hain-1918bis-00.txt
by Wilfried Woeber, UniVie/ACOnet 23 Apr '04

23 Apr '04

>> ... I'm a bit confused about the politics here. > >who cares? why care? any idiot can publish an internet-daft; Hm, the author is Tony Hein, cisco (but the date is April 2004 ;-) >judge it on its merits, or lack thereof. imiho, it has no merit. After a quick read - it smells like there's a hidden agenda somewhere, at least for 1.0.0.0/8 >randy Wilfried.

1 0

RIPE NCC Regional Meeting, Moscow, 16-18 June 2004
by Membership Liaison Officer 19 Apr '04

19 Apr '04

[Apologies for duplicate emails] Dear Colleagues, The RIPE NCC is pleased to announce the RIPE NCC Regional Meeting, Moscow, to be held 16 - 18 June 2004 at the Hotel Metropol, Moscow, Russia. Registration for the Regional Meeting opens 19 April 2004. 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/moscow-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?; - An update on IPv6; - Local, Regional and Global Internet Working and Routing; - Domain Name management on the Internet; - Root Server Operations The Regional Meeting draft agenda can be found at: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/agenda.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 region. The current draft 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 region. 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. Further information about the RIPE NCC and RIPE can be found at: http://www.ripe.net More information about the RIPE NCC Regional Meeting, Moscow is available from: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/ Any further questions can be sent directly to: <contact(a)ripe.net>. Regards, Nathalie Dougall Membership Liaison Officer RIPE NCC

1 0

Address Policy WG Action List
by Andrea Borgato 14 Apr '04

14 Apr '04

Dears, Here in the following you can find Update Address Policy WG Action List, pubblic available at: http://www.ripe.net/ripe/wg/address-policy/action-list.html 46.1 Chairs-WG Revise RIPE 152 (not allowed to charge for Done domain names) 46.4 Chairs Summarize and propose updated description of Completed the policy process 47.1 Chair Policy Development Process Ongoing Form a task force to write a policy development process propposal 47.2 NCC RIPE 152 to Historical and recomed to the RIPE NCC to make a clear statement that they do not charge for IP addresses 47.3 Andreas Bäß Anycast for CCTLD complete discussion on Ongoing mailinglist to form formal proposal 47.4 Chair Afrinic proposal for /22 mimimum allocation size. Seek final consensus on the list 47.5 Chair Changing the 80% rule for IPv4 allocations: start discussion on the mailing list Any comments will be apreciated. Regards, Andrea Borgato RIPE AP-WG co-chair

1 0

New IPv4 blocks allocated to RIPE NCC
by RIPE NCC Announcement 05 Apr '04

05 Apr '04

[Apologies for duplicate mails] Dear Colleagues, The RIPE NCC received the IPv4 address ranges 85.0.0.0/8, 86.0.0.0/8, 87.0.0.0/8 and 88.0.0.0/8 from the IANA in April 2004. We will begin allocating from these ranges in the near future. The minimum allocation size for these four /8s has been set at /21. 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> Additionally, please note that two "pilot" prefixes are being announced from each /8. The prefixes are: 85.192.0.0/16 & 85.255.248.0/21 86.192.0.0/16 & 86.255.248.0/21 87.192.0.0/16 & 87.255.248.0/21 88.192.0.0/16 & 88.255.248.0/21 They all originate in AS12654. More information on this "pilot" activity is available in the draft document "De-Bogonising New Address Blocks" which can be found at: <http://www.ripe.net/ripe/draft-documents/deboganising-draft.html> Best regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

Fwd: New IPv4 Allocations to the RIPE NCC
by Andre Chapuis 05 Apr '04

05 Apr '04

Hi Leo, Can you please update RIPE-296 ? What will the min-alloc be ? I guess /21, but just to be sure ! Thanks, André This is a forwarded message From: Steve Conte <conte(a)iana.org> To: nanog(a)merit.edu Date: Thursday, April 1, 2004, 11:59:33 PM Subject: New IPv4 Allocations to the RIPE NCC ===8<==============Original message text=============== Greetings, This is to inform you that the IANA has allocated the following four (4) IPv4 /8 blocks to the RIPE NCC: 85/8 86/8 87/8 88/8 For a full list of IANA IPv4 allocations please see: <http://www.iana.org/assignments/ipv4-address-space>. Thanks, Steve --------------- Steve Conte - IANA conte(a)iana.org PGP KeyID: 0x0972C473 ===8<===========End of original message text=========== -- Best regards, -------------------------------- André Chapuis IP+ Backbone engineering, AS3303 Swisscom Enterprise Solutions AG Genfergasse 14, CH-3050 Bern +41 31 893 89 61 chapuis(a)ip-plus.net CCIE #6023 --------------------------------

1 0

RIPE 48 Address Policy WG (Draft) Agenda v0.1
by Hans Petter Holen 29 Mar '04

29 Mar '04

Dear Address Policy WG, There is soon yet another RIPE meeting coming up. We have the usual two agenda slots and below is a very first draft agenda. We will try to focus on the IP v6 policy issues this time - hopefully to get a new globally coordinated revision process going - if needed. A. Administrative Matters - Welcome - Select a scribe - Distribute participants list - Finalise agenda - Approve minutes from RIPE 47: <http://www.ripe.net/ripe/wg/address-policy/r47-minutes.html> B. RIPE NCC (Stats) Update (Filiz Yilmaz, RIPE NCC) An update on RIPE NCC policy implementation and Internet Number Resource distribution statistics. C. ICANN ASO AC Update (TBD, ICANN ASO AC) D. ICANN ASO AC - A view from outside (TBD) E. Discussion resulting from ICANN ASO presentations F. Policy Development Process (HPH) G. IPv6 Policy Issues (TBD) [Coffee break here?] H. IPv6 Policy Discussion [...] Y. Open Microphone Z. AOB [Lunch]

1 0

DARPA get's it right this time, takes aim at IT sacred cows
by Jeff Williams 13 Mar '04

13 Mar '04

All former DNSO GA members or other interested stakeholders/users. Seems that the self styled "father of the internet", Vinton Cerf's IP [ Internet Protocol ] has finally begun to be recognized as obsolete for wireless networking. Not that this is all that unknown as several stakeholders/users on this forum reached that conclusion some three years ago now in discussions and debates on this forum. See article: http://www.gcn.com/vol1_no1/daily-updates/25240-1.html Regards, -- Jeffrey A. Williams Spokesman for INEGroup LLA. - (Over 134k members/stakeholders strong!) "Be precise in the use of words and expect precision from others" - Pierre Abelard "If the probability be called P; the injury, L; and the burden, B; liability depends upon whether B is less than L multiplied by P: i.e., whether B is less than PL." United States v. Carroll Towing (159 F.2d 169 [2d Cir. 1947] =============================================================== Updated 1/26/04 CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS. div. of Information Network Eng. INEG. INC. E-Mail jwkckid1(a)ix.netcom.com Registered Email addr with the USPS Contact Number: 214-244-4827

1 0

RE: [address-policy-wg] New Draft Document: De-boganising New AddressBlocks
by Michel Py 27 Feb '04

27 Feb '04

> Rob Thomas wrote: > The reality is that the miscreants are seeing a lower > return on the investment when spoofing from bogon prefixes. Because they are being filtered :-) If more people filtered bogons, the "ROI" would be even lower. Although it is clear that bogon filtering is not a complete cure for spoofing, it does help and it also helps for some spammers. The only negative effect of bogon filtering is not-up-to-date filters, which is why we have written this draft that will expand the applicability domain of bogon route servers and other filtering schemes. Michel.

1 0