January 2003 - lir-wg - mailman.ripe.net

ripe allocation 82.0.0.0/8 and arin allocation 69.0.0.0/8
by Joe Baptista 03 Jan '03

03 Jan '03

ARIN recently released blocks from the 69.0.0.0/8 which are causing numerous problems with routing in this block. Some 200 blocks have been issued from 69.0.0.0/8 and i've spoken with at least 15 operators who have complained. I understand the 82.0.0.0/8 block suffers from the same problem. From what I can see RIPE has not yet issued any netblocks from this pool. If RIPE does issues blocks from this pool will RIPE take back the IP if it enconters the same problems or will RIPE follow the ARIN approach of no returns even though ARIN and RIPE are aware of the frustration it is causing. Some operators I have spoken with in 69/8 have suffered damage to thier business operations. Cheers Joe Baptista -- Planet Communications & Computing Facility a division of The dot.GOD Registry, Limited

8 9

RE: [lir-wg] ripe allocation 82.0.0.0/8 and arin allocation 69.0. 0.0/8
by Sweeting, John 02 Jan '03

02 Jan '03

None of the RIR's are going to tell me what routes I will accept or filter in my network.....as simple as that. If I am filtering out networks that my customers wish to get to then that will be fixed as soon as a ticet is opened by them. Also, what is with the "...you boys..." remarks. -----Original Message----- From: Joe Baptista To: leo vegoda Cc: lir-wg(a)ripe.net Sent: 1/2/03 7:18 AM Subject: Re: [lir-wg] ripe allocation 82.0.0.0/8 and arin allocation 69.0.0.0/8 On Thu, 2 Jan 2003, leo vegoda wrote: > The RIPE NCC can not guarantee whether any particular route will > be accepted by any network operator. Thats a problem. Question - if one of your customers discovers that an allocation does not route can they have it replaced with one that does. I understand you don't guarantee any particular allocation will route. And in the old days when the charges were minimal for IP allocation - well one could reluctantly accept that. However - under the new policies you boys are charging these people hefty bucks and that means liability and I don't think it prudent to hide behind the routing claim. I have documented over 15 cases in which the 69.0.0.0/8 fiasco has cost these people clients and business that went elsewhere. Have also documented situations in which these recent allocation have resulted in the renumbering of networks out of 69.0.0.0/8 allocations into arpa that works. So you see I think it prudent that there be a policy to allow for returns and replacement of arpa. I don't think you boys should be issuing numbers when you are aware that they don't work and are causing people financial problems to their business operations. So if you do get complaints regarding 82.0.0.0/8 - do you intend to make sure your customers get network that work - or will RIPE be following the ARIN lead and just let these people hang. regards joe baptista

1 0

Draft Agenda for RIPE 44 (version 0.3)
by Hans Petter Holen 01 Jan '03

01 Jan '03

Dear Working Group, Please find enclosed a draft agenda for the upcoming working group. As a matter of procedure I suggest that Policy items to be discussed are to be discussed at the mailinglist. We should aslo be careful not to make policy desicions at the upcoming meeting _unless_ there is a concrete proposal circulated to the list in advance of the meeting, we should circulate any policy proposals to this list after te meeting before making any policy desicions. Thanks to leo for preparing the very first draft, looking forward to input from the rest of you. Best Regards, Hans Petter Holen lir-wg chair --- Draft Agenda for RIPE 44 (version 0.2) Wednesday 29 January 2003 09:00 - 12:30 Chair: Hans Petter Holen Co-chair: Denesh Bhabuta A. Admin: Scribe Participant List, Charter, Mailing lists B. Agenda bashing C. RIPE 43 minutes and actions http://www.ripe.net/ripe/wg/lir/r43-minutes.html http://www.ripe.net/ripe/wg/lir/lir-actions.html D. Report from the RIPE NCC Registration Services Presentation by leo vegoda E. Report from the Address Council - Presentation F. Election of new LIR-WG Chairs G. LIR Portal H. Policy issues -- Mailing list AUP ? -- EGLOP Multicast policy discussion ? -- IPv6 policy - experiences ? -- IP addressing for always on (residential broadband) revisited ? X. Any other business Y. Summary of actions arising from this meeting Z. Open microphone

2 1