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

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

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