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

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

Re: [address-policy-wg] New Draft Document: De-boganising New Address Blocks
by Michael.Dillon＠radianz.com 25 Feb '04

25 Feb '04

>The RIPE NCC has prepared a draft document titled "De-Bogonising New >Address Blocks": That is a misleading title. The problem is that ISPs cannot react quickly enough to open filters when new ranges are allocated. The proposed solution is to provide advance notification. I suppose this could allow ISPs to open filters before the new addresses are actually in use officially. However, it will also allow spammers to announce this space and get it through bogon filters. The real solution to this problem is to make it possible for ISPs to closely track RIR allocations in their filters in a semi-automated way. There may still be a few days of delay before a new allocation is fully routable but ISPs can compensate for that with internal processes. Why can't ISPs subscribe to a feed of all new RIPE allocations in near real-time? --Michael Dillon

14 23

New Draft Document: De-boganising New Address Blocks
by RIPE NCC WebMaster 25 Feb '04

25 Feb '04

(Apologies for duplicate mails) Dear Colleagues, The RIPE NCC has prepared a draft document titled "De-Bogonising New Address Blocks": <http://www.ripe.net/ripe/draft-documents/deboganising-draft.html> Abstract "This document describes an improvement in the notification process about new blocks of address space being distributed by the RIRs. It is a draft at this stage and your comments are solicited. However to gain experience before finalising the procedures, the RIPE NCC will shortly start announcing the routes from 84/8 described in the document under "pilot"." This document is published as a draft document in order to give RIPE NCC members time to read it and provide feedback. This draft document can be discussed on the RIPE NCC Services Working Group mailing list at <ncc-services-wg(a)ripe.net>. Regards, Webmaster RIPE NCC

2 1

REMINDER: ARIN to allocate from 70.0.0.0/8
by Leslie Nobile 24 Feb '04

24 Feb '04

Hello- This is a reminder that ARIN will begin allocating IP address space from 70.0.0.0/8 in the immediate future. This will include allocations of /20 and shorter prefixes, according to ARIN's minimum allocation policy. You may wish to adjust any filters you have in place accordingly. For informational purposes, a list of ARIN's currently administered IP blocks can be found under "CIDR Blocks" at: http://www.arin.net/statistics/index.html Regards, Leslie Nobile Director, Registration Services American Registry for Internet Numbers (ARIN)

1 0

RIPE 47 Meeting Report
by Nick Hyrka 23 Feb '04

23 Feb '04

(Apologies for any duplicate mails.) RIPE 47 Meeting Report Dear Colleagues, The <http://www.ripe.net/ripe/meetings/ripe-47/index.html>RIPE 47 Meeting was held from 26 - 30 January 2004 at the Grand Hotel Krasnapolsky, Amsterdam, the Netherlands. There were a total of 253 attendees comprised of the RIPE NCC membership, the RIPE community and government representatives. Attendees also included representatives from APNIC, ARIN, AfriNIC, LACNIC, ICANN and IANA. HIGHLIGHTS ========== - Highlights of RIPE 47 included the open discussion on the services of the RIPE NCC during the RIPE NCC Services Working Group; updates on the World Summit on the Information Society from Mirjam Khne, ISOC, and Axel Pawlik, Managing Director, RIPE NCC; an AfriNIC update; the proposal by the RIPE community to make RIPE 152 ( 'Charging by Local Internet Registries') a historical document. - As announced by Rob Blokzijl, RIPE Chair, two RIPE Meetings will be held in 2005. Based on the feedback from the community, this schedule will continue in 2006. The RIPE NCC will offer additional support to RIPE Working Groups to facilitate discussion and progress between RIPE Meetings. - Robin Tasker (CCLRC) gave a presentation on the European Commission-sponsored DataTAG project. - The European Operators Forum (EOF) featured an NSP Security BoF, a presentation on which types of SMTP flows should be blocked to prevent spam, a case study on the migration of AOL's backbone network from OSPF to IS-IS and discussion on the use of XML in network configuration. EOF presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/index.html#eof>http://www.ripe.net/ripe/meetings/ripe-47/presentations/index.html#eof - The RIPE NCC, Afilias, Cisco, NIKHEF, NOKIA, Riverhead and SURFnet are thanked for the support they provided to the meeting. Global Voice Networks are thanked for the provision of excellent Internet connectivity. SUMMARY ======== ADDRESS POLICY - It was proposed that RIPE 152 ('Charging by Local Internet Registries') should be made a historical document and that the RIPE NCC should make a clear statement on <http://www.ripe.net/>www.ripe.net that it does not charge for IP addresses. - Hans Petter Holen, Chair, will form a task force to write a policy development process proposal. - Consensus is needed on the mailing list on the AfriNIC proposal regarding /22 minimum allocation size. - Hans Petter Holen, Chair, will start a discussion on the mailing list on changing the 80% rule for IPv4 allocations. Address Policy Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ap>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ap DATABASE - The issue of CRISP versus joint Whois was discussed. - The proposal to introduce new attribute "abuse-c" in the inet(6)num objects was discussed. - A detailed proposal about "abuse-c" will be sent to Database Working Group mailing list. Database Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#db>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#db TEST TRAFFIC MEASUREMENT (TTM) - It was noted that as of 1/1/2004 changes were made to the TTM service contract: Fees were lowered (from 3000 EUR per year to 1000 EUR per year) and all data has been made public as specified in RIPE 300 ('Test Traffic Measurement Service Data Disclosure Policy'). - Two presentations made use of TTM delay data: a presentation on delay tomography used traceroute data from the TTM project; a presentation on the reordering of IP packets used delay data. TTM Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#tt>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#tt ANTI-SPAM - A proposal has been sent to the Database Working Group mailing list regarding the inclusion of an abuse-c attribute/object in the RIPE Database to help solve the problem of misdirected/multiple spam complaints. - It was noted that the European Commission Directive is now widely implemented and that in the United States CAN-SPAM is the first federal legislation. IPv6 - The anycast policy discussion was sent to the Address Policy Working Group. - There was discussion on how 6 to 4 is being used to spoof IPv4 origin addresses to make Distributed Denial of Service (DDoS) attacks anonymous. - There was a presentation on the security implications of IPv6 on IPv4 networks. IPv6 Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ipv6>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ipv6 EIX - An editorial group will be set up to revise the exchange point operator wish list for switches. - Operator-member charters for exchange points were discussed. - DE-CIX presented their experience migrating to new hardware and adding new premises. EIX Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#eix>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#eix DN* - The DNR Forum and the DNS Working Group were combined under the DNS Working Group heading. - It was noted that the ENUM RFC 2916bis has been approved by the IETF Working Group and is in the queue of the RFC editor. - It was noted that Internationalized Domain Names (IDN) are being deployed in more new regions. DN* Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#dn>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#dn ROUTING - There was a presentation on RISwhois, a tool that allows IP address to origin ASN mapping. - Case studies about convergence of IGP protocols were presented and discussed. Routing Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#routing>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#routing RIPE NCC SERVICES - Bijal Sanghani, FLAG Telecom, was appointed as the co-chair of the Working Group. - The RIPE NCC will explore the possibility of providing a service giving test statistics on the routability of new blocks. - The RIPE NCC will give a status update on the Activity Plan 2004 and request input for the Activity Plan 2005 during the RIPE NCC Services Working Group at RIPE 48. RIPE NCC Services Working Group presentations can be viewed at: <http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ncc-services>http://www.ripe.net/ripe/meetings/ripe-47/presentations/#ncc-services 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-47/tutorials/ip-request/>http://www.ripe.net/ripe/meetings/ripe-47/tutorials/ip-request/ RIPE 47 WEBCASTING AND ARCHIVES ============================== During RIPE 47, 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 47 are available at: <http://www.ripe.net/ripe/meetings/ripe-47/sessions-archive.html>http://www.ripe.net/ripe/meetings/ripe-47/sessions-archive.html HOSTMASTER CONSULTATION CENTRE (HCC) ==================================== The RIPE NCC Hostmaster Consultation Centre was open at RIPE 47, allowing RIPE NCC Members to discuss issues relating to their business directly with RIPE NCC Hostmasters. RIPE 47 REFERENCE PAGE ====================== A complete list of RIPE 47 sessions, tutorials and presentations can be found at: <http://www.ripe.net/ripe/meetings/ripe-47/index.html>http://www.ripe.net/ripe/meetings/ripe-47/index.html "MEET & GREET" ============= The RIPE NCC's "Meet & Greet" was available for first-time RIPE Meeting attendees at RIPE 47. "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 48 ====== RIPE 48 will be held in Amsterdam, the Netherlands, from 3 - 7 May 2004. Information on RIPE 48 will soon be made available at: <http://www.ripe.net/ripe/meetings/ripe-48/>http://www.ripe.net/ripe/meetings/ripe-48/ 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>http://www.ripe.net/ripe/meetings/new-lir.html For more information, contact <meeting(a)ripe.net>. -- end --

1 0