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

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

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

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

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