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

ICANN Call for Comments on Proposed Review Procedure for ASO Policy Proposals
by Axel Pawlik 06 Jun '05

06 Jun '05

Dear Colleagues, ICANN has called for a second round of public comments on the "Review Procedure to Handle Policy Proposals Submitted by the ASO Address Council in Line with the ASO MoU." Comments received from the first public comment period have been analysed and considered in the updated version of the procedure, which is posted for a second round of public comments on the ICANN website. All members of the Internet community are invited to submit their comments. For further information and to submit comments, please visit the ICANN website at: http://www.icann.org/announcements/announcement-31may05.htm The deadline for comments is 21 June 2005. Regards, Axel Pawlik Managing Director RIPE NCC

1 0

RIPE 50 Report
by Nick Hyrka 25 May '05

25 May '05

[Apologies for duplicate e-mails.] RIPE 50 Report Dear Colleagues, The RIPE 50 Meeting took place from 2 - 6 May 2005 at the Clarion Hotel, Stockholm, Sweden. There were over 375 participants at the meeting. Attendees also included government representatives and representatives from AfriNIC, APNIC, ARIN, LACNIC and ICANN. HIGHLIGHTS Highlights of RIPE 50 included: - The successful implementation of the new RIPE Meeting format into three days on operational and technical content followed by two days on policy related issues. - An update on the ICANN ASO Address Council. This presentation is available at: http://www.ripe.net/ripe/meetings/ripe-50/presentations/ripe50-plenary-fri-… - A commentary on the ITU-T Proposal for National Address Registries for IPv6 by Geoff Huston, APNIC. This presentation is available at: http://www.ripe.net/ripe/meetings/ripe-50/presentations/ripe50-plenary-wed-… - Final discussion on the RIPE Policy Development Process. More information about this will appear on www.ripe.net shortly. Afilias, Arbor Networks, Cisco Systems, Force10 Networks, Netnod, NIKHEF, Nokia, TeliaSonera and the RIPE NCC are thanked for the support they provided to the meeting. TeliaSonera are thanked for the provision of the meeting Internet connectivity. PRESENTATIONS All the Plenary and Working Group presentations from RIPE 50 can be viewed at: http://www.ripe.net/ripe/meetings/ripe-50/presentations/index.html SUMMARY ADDRESS POLICY WORKING GROUP - It was agreed that the Address Policy Working Group Chairs will make a formal proposal that global policies should go through the RIPE Policy Development Process. - There was discussion on the TLD anycast allocation policy proposal, the IPv6 proposal to remove the 200 customers requirement, the proposal for removal of the Africa Special Policy, the proposal to add regional boundaries to policy documents and the IPv4-HD-Ratio proposal. ANTI-SPAM WORKING GROUP - There was discussion on whether ripe-206 should be revised to reflect the updates to the LINX BCP document that was used as the base for the original ripe-206. - There was discussion about anti-spammers sometimes behaving worse than spammers, and action placed on the Working Group Chair to start work on a document for best practise for spam complaints. DATABASE WORKING GROUP - It was agreed that a proposal on the "country:" attribute should be prepared. This will be done by the RIPE NCC. - It was noted that changes to the RIPE Database for abuse are now in production. DNS WORKING GROUP - It was agreed that the DNS Working Group Chair will produce a proposal to solve the problem that changes to reverse DNS nameservers cannot have multiple names. - There was discussion on whether the DNS Working Group should take over the work to produce a RIPE Document on AAAA resolution issues. - It was agreed that the RIPE NCC will produce statistics on anycast placement for K-root and the RIPE region Hostcount in time for RIPE 51. - It was noted that DNSSEC RFCs have been published, and that DNSSEC is being tested in Sweden in the .se domain. EIX WORKING GROUP - It was noted that the Switching Wish-List Version 3.0 will be published soon by Mike Hughes, and that version 3.1 will be published after RIPE 51. - There was discussion about public versus private peering. ENUM WORKING GROUP - It was agreed that Niall O'Reilly and Carsten Schiefner will be the new ENUM Working Group Chairs. - It was noted that the IETF is continuing work on ENUM standards. - It was agreed that the ENUM Working Group will continue to work as it has in the past, with an emphasis on the exchange of operational experience. IPV6 WORKING GROUP - It was decided that the RIPE Whois Database will continue to include more services that run in native IPv6. - It was agreed that the community needs to produce a revised Internet draft before RIPE 51 to formally address the demands of RFC3177, particularly the /48 recommendation. - It was noted that the IPv6 Working Group needs to decide where it wishes to house the new, operational IPv6 mailing list. RIPE NCC SERVICES WORKING GROUP - There was discussion on the value of the Hostcount. It was agreed that the RIPE NCC should continue working on this, and that the RIPE NCC should write and put a new Hostcount into service. ROUTING WORKING GROUP - There was discussion on route flap damping and de-aggregation practices raised by Philip Smith in the RIPE 50 Plenary. - Lorenzo Colliti (RIPE NCC) presented the research work of Roma Tre University on active BGP probing to discover AS level topology of the Internet. TEST TRAFFIC WORKING GROUP - It was agreed that the community should provide a proposal on how TTM infrastructure could be used to certify the quality of service provided by ISPs and to verify Service Level Agreements. - Henk Uijterwaal gave an update on the status of the TTM project - Thomas Wana presented work done to improve the accuracy of TTM time measurements and a proposal to create even greater accuracy by using DAG cards for measurement. - There was discussion on the future directions for the TTM project and it was agreed that the TTM infrastructure and measurements could be leveraged to certify the quality of service provided by ISPs. The Working Group agreed that the RIPE NCC, as a trusted third party, could perform the measurements and publish the results. CO-LOCATED PEERING BoF Netnod, LINX and AMS-IX hosted a peering BoF co-located at RIPE 50 on Sunday, 1 May, where peering policies were presented. CO-LOCATED LOBSTER TUTORIAL A tutorial entitled "Passive Network Traffic Monitoring" was organised on Friday, 6 May, by the consortium of LOBSTER, a European IST Project on Large-Scale Monitoring of Broadband Internet Infrastructures. RIPE 50 WEBCASTING AND ARCHIVES During RIPE 50, the RIPE NCC collected feedback from participants watching the webcast and listening to the audiocasts. The mediums used for this were IRC and Jabber. Archives of presentations, webcasts and IRC/Jabber feedback from RIPE 50 are available at: http://www.ripe.net/ripe/meetings/ripe-50/sessions-archive.html HOSTMASTER CONSULTATION CENTRE (HCC) The RIPE NCC Hostmaster Consultation Centre was open at RIPE 50, 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 50. "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 50 REFERENCE PAGE A complete list of RIPE 50 sessions, tutorials and presentations can be found at: http://www.ripe.net/ripe/meetings/ripe-50 RIPE 51 RIPE 51 will be held in Amsterdam, the Netherlands from 10 - 14 October 2005. Information on RIPE 51 is available at: http://www.ripe.net/ripe/meetings/ripe-51 If you have any questions about RIPE Meetings, please contact <meeting(a)ripe.net>.

2 1

IPv4 allocation monitoring tool
by Iljitsch van Beijnum 23 May '05

23 May '05

Hi, I've been looking at the IPv4 allocations lately, in order to figure out how soon we're going to run out. I made a little tool to search the data in different ways: http://www.bgpexpert.com/addrspace.php It doesn't do anything fancy: just collect the public stats from the different RIR FTP servers once in a while and dump the records in a database, which can then be searched with the page above, with results such as: RIR Country Addresses Date 78.51 M 2000 89.02 M 2001 69.02 M 2002 87.67 M 2003 123.93 M 2004 79.86 M 2005 Another interesting one: RIR Country Addresses Date US 1305.90 M JP 138.33 M EU 114.01 M Let me know if you have any questions or suggestions. Iljitsch van Beijnum

2 1

RIPE DB: disclosure of commertial information
by Max Tulyev 20 May '05

20 May '05

Hi! I have very strange situation. One company I support, an ISP, wants to become a LIR. But they do not want to put information about their clients' assignments into the RIPE DB, because of there is a possibility to steal clients (most of them - major clients) using RIPE DB, and they says that there already was some incidents. Really, you can see RIPE DB for assignments of LIR to have its client list with name of organisation, size (larger client have larger assignment), address, phone, fax, email, and even administrative and technical contact persons. Only you need to do - is to send (or even talk with) better offer addressing it to certain people... What do you think about it? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

13 19

Allocation transfer
by David Bell 16 May '05

16 May '05

Hi all, uk.redwing is a small LIR, providing internet via satellite. We are in the process of hosting a new satellite platform, on behalf of another organisation, that is projecting a requirement for a /19 in the next 12 months. This partner is not currently an LIR, but is considering it as a future option. What I am trying to determine is if uk.redwing applies for this /19 address block, and assigns it as PA space, will it be possible in the future for us to hand it over to our partner, if/when they become an LIR themselves. Perhaps this is a case where PI addresses would be suitable, but I see warnings everywhere I look regarding the use of PI space. My apologies if this is not the correct place to post this question, please let me know the best place to go if I'm on the wrong list. Thanks very much, Dave Bell Redwing Satellite Solutions Ltd.

4 3

WGIG Questionnaire & Forum on Internet Governance
by Axel Pawlik 13 May '05

13 May '05

Dear Colleagues, This is an invitation and an opportunity to provide input directly into the current discussions on Internet Governance. The UN's Working Group on Internet Governance (WGIG) is conducting a survey to ask stakeholders for their thoughts on current Internet Governance arrangements. The questionnaire is available on the WGIG website at: http://www.wgig.org/docs/Questionnaire.09.05.05.pdf An online discussion forum has also been established. Instructions on how to access the forum and complete the questionnaire can be found at: http://www.wgig.org/Plone-instructions.html I would like to encourage you to take a few minutes to respond to this survey. As a stakeholder in Internet governance, and in IP address management in particular, your input is important and will be valued by the WGIG. Regards, Axel Pawlik Managing Director RIPE NCC

1 0

Correction: Call for Comments on Revised ICANN Strategic Plan
by Axel Pawlik 10 May '05

10 May '05

Dear Colleagues, Some of you may have noticed two URLs in our last announcement. The correct URL is: http://www.icann.org/strategic-plan/strategic-plan-v7_3.pdf Apologies for the confusion. Regards, Axel Pawlik Managing Director RIPE NCC

1 0

Call for Comments on Revised ICANN Strategic Plan
by Axel Pawlik 10 May '05

10 May '05

Dear Colleagues, The ICANN Strategic Plan has been revised. The comment period will be open until 13 May 2005 at 23:59 UTC. The revised Strategic Plan is available as a draft for public comment at: <http://www.icann.org/strategic-plan/strategic-plan-16nov04.pdf>http://www.icann.org/strategic-plan/strategic-plan-v7_3.pdf We encourage you to review the ICANN Strategic Plan document and send any comments you have to: <stratplan-revision(a)icann.org>. Regards, Axel Pawlik Managing Director RIPE NCC

1 0

infected e mails
by freeram 06 May '05

06 May '05

I receive infected e mails of these addresses is it possible to ascend has the author of its mails: or have I to address to send complaints thank you of well will to reply me Alain Bruneteau ---------------------------------------------------------------------------------------------------- 62.48.149.242 Return-Path: <info(a)sivaonline.pt> Delivered-To: online.fr-freeram(a)free.fr Received: (qmail 9962 invoked from network); 6 May 2005 10:41:25 -0000 Received: from adsl-62-48-149-242.ptprime.net (HELO tetfob.pt) (62.48.149.242) by mrelay2-2.free.fr with SMTP; 6 May 2005 10:41:25 -0000 From: info(a)sivaonline.pt To: Recipient(a)free.fr Date: Fri, 06 May 2005 09:52:45 UTC Subject: [avast! - INFECTED] Your email was blocked Importance: Normal X-Priority: 3 (Normal) Message-ID: <56cd.70f8e0dab9d7ee0(a)sivaonline.pt> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===79bce1635598.2ceab3bf964" Content-Transfer-Encoding: 7bit This is a multi-part message in MIME format. X-Antivirus: avast! (VPS 0518-4, 06/05/2005), Inbound message X-Antivirus-Status: Infected Attachment: \error-mail_info.zip#1997431942 Virus: Win32:Sober-N [Wrm] Deleted ------------------------------------------------------------------------------------------------- 82.64.236.212 X-x: TimeOut+OK 73580 octets Return-Path: <hostmaster(a)yahoo.fr> Delivered-To: online.fr-freeram(a)free.fr Received: (qmail 12725 invoked from network); 5 May 2005 06:17:15 -0000 Received: from lns-th2-15-poi-82-64-236-212.adsl.proxad.net (HELO butqay.fr) (82.64.236.212) by mrelay3-2.free.fr with SMTP; 5 May 2005 06:17:15 -0000 From: hostmaster(a)yahoo.fr To: mailhost(a)free.fr Date: Thu, 05 May 2005 06:09:40 UTC Subject: [avast! - INFECTED] mailing error Importance: Normal X-Priority: 3 (Normal) Message-ID: <74d8c001e683ef48(a)yahoo.fr> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="6653bc9b707531bc.8" Content-Transfer-Encoding: 7bit This is a multi-part message in MIME format. X-Antivirus: avast! (VPS 0518-3, 04/05/2005), Inbound message X-Antivirus-Status: Infected Attachment: \mail_info.zip#1997431942 Virus: Win32:Sober-N [Wrm] Deleted --------------------------------------------------------------------------------------------------- 82-64-238-162 Return-Path: <Admin(a)ac-corse.fr> Delivered-To: online.fr-freeram(a)free.fr Received: (qmail 17762 invoked from network); 4 May 2005 05:53:29 -0000 Received: from lns-th2-15-poi-82-64-238-162.adsl.proxad.net (HELO hnmuwxt.fr) (82.64.238.162) by mrelay1-2.free.fr with SMTP; 4 May 2005 05:53:29 -0000 From: Admin(a)ac-corse.fr To: fe2e2ec0(a)free.fr Date: Wed, 04 May 2005 05:45:09 GMT Subject: [avast! - INFECTED] mailing error Importance: Normal X-Priority: 3 (Normal) X-MSMail-Priority: Normal Message-ID: <db2da62ab.587e8a2c9(a)ac-corse.fr> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=====8389c8.dea2bff67" Content-Transfer-Encoding: 7bit This is a multi-part message in MIME format. X-Antivirus: avast! (VPS 0518-2, 04/05/2005), Inbound message X-Antivirus-Status: Infected Attachment: \error-mail_info.zip#1997431942 Virus: Win32:Sober-N [Wrm] Deleted ---------------------------------------------------------------------------------------------------- 82.64.226.163 Return-Path: <service(a)ac-reims.fr> Delivered-To: online.fr-freeram(a)free.fr Received: (qmail 7819 invoked from network); 4 May 2005 23:00:38 -0000 Received: from lns-th2-15-poi-82-64-226-163.adsl.proxad.net (HELO osymwmxh.fr) (82.64.226.163) by mrelay2-1.free.fr with SMTP; 4 May 2005 23:00:38 -0000 From: service(a)ac-reims.fr To: oel(a)free.fr Date: Wed, 04 May 2005 23:00:06 GMT Subject: FwD: Registration Confirmation Importance: Normal X-Priority: 3 (Normal) X-MSMail-Priority: Normal Message-ID: <f24f8b.dc6bb7cddd(a)ac-reims.fr> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="==eb445d.b2cfb65" Content-Transfer-Encoding: 7bit This is a multi-part message in MIME format.

1 0

Revised Agenda v2 for Address Policy WG @ RIPE 50 Thursday 5th May
by Hans Petter Holen 05 May '05

05 May '05

Time: 1400- 15:30 Date: Tursday May 5th Place: Main room, RIPE 50 A. Administrative Matters - Welcome - Select a scribe - Distribute participants list - Finalise agenda - Approve minutes from RIPE 49: http://www.ripe.net/ripe/wg/address-policy/r49-minutes.html B. Policy overview - Regional policy overview -- presentation of the status of the current regional proposals under the "beta test of the PDP" -- status of the PDP and transition to the PDP --- PDP last call posted to ripe-list with closing date May 10th. C. Policy proposal: #alpha: TLD Anycast Allocation Policy Discussion phase until: May 6th D. Policy proposal: #beta: IPv4-HD-Ratio Discussion phase until: April 4th E. Policy proposal: #gamma: IPv6 remove 200 customer requirement Discussion phase until May: 9th F. Policy Proposal: #epsilon: Removal of Africa Special Policy Discussion phase until May: 1st G. Policy Proposal: #zeta: Adding Regional Boundaries to Policy Documents Discussion phase until May: 1st H. Discussion: (IPv6) HD ratio consequences (Geoff Huston: http://www.ripe.net/ripe/meetings/ripe-50/presentations/ripe50-plenary-wed-… There is also a related agenda item in the IPv6 WG on friday: http://www.ripe.net/ripe/maillists/archives/ipv6-wg/2005/msg00042.html " D. Revisiting the /48 recommendation (Thomas Narten) Discussion, read rfc3177 as preparation ftp://ftp.rfc-editor.org/in-notes/rfc3177.txt" J. Report from the Address Council - Hans Petter Holen K. Any other Business

1 1