<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style></style></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1>Hi Alexey, <o:p></o:p><o:p> </o:p>Let’s assume that you provided this ‘customer’ a part of a PA allocation. <o:p></o:p><o:p> </o:p>So you have a /21 and provided this specific customer with a /24 and they are announcing that with their own AS to their providers. <o:p></o:p><o:p> </o:p>What you did wrong here is: <o:p></o:p>The customer should not have been provided a /24 which they would be allowed to route under another AS but yours. It is you PA space, not theirs. <o:p></o:p><o:p> </o:p>There are good alternatives for this. PI space is one and the customer could always sign up for their own LIR member status and get their own PA space. <o:p></o:p><o:p> </o:p>In the RIPE DB there is an option to limit another maintainer to their own specific assignment. You can do that in the larger PA allocation (in this example for the /21 above the customers /24) using the following syntax:<o:p></o:p><o:p> </o:p>Inetnum : your /21<o:p></o:p>mnt-routes: Your-MNT<o:p></o:p>mnt-routes: ISP-A-MNT { x.y.56.0/22, x.y.60.0/24 }<o:p></o:p>mnt-routes: MNT-ISP-B { x.y.63.0/24 }<o:p></o:p><o:p> </o:p>That will allow the named maintainers to create a route object with their maintainer authentication that matches only that specific part of your allocation. <o:p></o:p><o:p> </o:p>On the part of how to remove that specific route-object. Typically only the maintainer that is named can do that. <o:p></o:p><o:p> </o:p>And normally they will do that as soon as the customer is no longer using the IP’s or if there is a request to remove it. <o:p></o:p>If the maintainer is of the customer itself and they refuse to remove the route object. That might be tricky to get it removed, as they need to do it. <o:p></o:p><o:p> </o:p>Regards,<o:p></o:p>Erik Bais<o:p></o:p>A2B Internet <o:p></o:p><o:p> </o:p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>From: members-discuss-bounces@ripe.net [mailto:members-discuss-bounces@ripe.net] On Behalf Of LeaderTelecom Ltd. Sent: dinsdag 19 juni 2012 12:22 To: members-discuss@ripe.net Subject: Re: [members-discuss] [Ticket#2012061901001911] Need help. Can't remove routes for ex Assigned PA.<o:p></o:p></div></div><o:p> </o:p>Dear Members, Please help what better to do in this case. We have allocated PA. From this space we Assigned PA to customer. Customer has own AS and he created routes. Route objects doesn't have our mnt-by. He has another carrier. The customer to which we have assiged PA space sending a lot of mails to Hotmail. We are receiving thousands complains per day from Hotmail. We suggested to block this IPs for Hotmail. They tell that it can be done only in automatic mode when hotmail will receive many complains for this IPs. We already found IPs in some black lists. RIPE position in this case. While routes doesn't have RIPE mnt record - they can't do anything. Routes should be removed by our ex customer. Ex customer position. He won't remove routes until we will return money back. And tell us that he doesn't send any e-mails - all was made by his customers. In our agreement written that we don't return money back in this case. And if we will return money back - anyway we don't have any warranty of removing routes. Questions: 1. How can we restrict using this routes right now? 2. How can we remove wrong routes (see an example bellow)? Additional information: ------------------------------ Example of route:<o:p></o:p><div>route: xx.xx.xx.0/24<o:p></o:p></div><div>descr: route for xxxxxxxxxxx<o:p></o:p></div><div>origin: asYYYY<o:p></o:p></div><div>mnt-by: zzzzz-mnt<o:p></o:p></div><div>source: RIPE # Filtered<o:p></o:p></div> Where: - xx.xx.xx.0/24 - IPs from our allocation (Assigned PA). - ASyyyy - AS our ex customer. - zzzzz-mnt - MNT of our ex customer.<o:p></o:p><div>-- Alexey Ivanov General Director LeaderTelecom Ltd.<o:p></o:p></div></div></body></html>