<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=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)">  <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Address Policy Working Group,<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> I’m working for a company who decided to become a LIR as we have a requirement for Large amounts of IP Space. We are not assigning IP Space to our customers as all the IP Space is used for our own infrastructure.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> We have been provided with a PA Allocation, however we are having issues getting PA Assignments approved by RIPE NCC.<o:p></o:p> <o:p> </o:p> We applied for PA Assignments in /24 blocks so that we could multi-home using BGP from all of our production sites and some of our more critical offices<o:p></o:p> <o:p> </o:p> These sites don’t have a shared Network connecting them (except for the Internet)<o:p></o:p> <o:p> </o:p> We are using the “allowas-in” command so that we don’t need an AS Number from each non-connected site. (As the RIPE NCC wouldn’t approve our application for multiple AS Numbers)<o:p></o:p> <o:p></o:p> <o:p> </o:p> The request of PA Assignments is getting rejected because <o:p></o:p> <o:p> </o:p> <o:p> </o:p> <![if !supportLists]>1. <![endif]>We can’t aggregate the IP Space (RIPE NCC wants us to advertise our entire PA Space and not break it into smaller networks as we require)<o:p></o:p> <![if !supportLists]>2. <![endif]>The IP Space required in some of the sites is less than a /24 (However we need /24 networks as our Transit providers filter IP Space smaller than /24)<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> The suggestion from RIPE NCC was to apply for smaller Assignments from the PA Space and to take each of them from a separate /24 range, and to create a /24 route object for each separate /24 Space, or to apply for PI Space for each location as PI Space was more in-line with what we are trying to achieve.<o:p></o:p> <o:p> </o:p> While this will work, I have an issue with RIPE NCC providing a work around, and I believe the policy should allow for a LIR to use the PA Allocation in the best manner to conserve IP Space and to not have “Available” networks in PA Space which can never be assigned and to not waste PI space by not allowing a LIR use the Allocated PA Space for its own Infrastructure.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Thanks<o:p></o:p> Keith<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=200 style='width:150.0pt'> <tr> <td style='padding:0cm 0cm 0cm 0cm'> Keith Nolan <o:p></o:p> </td> </tr> <tr> <td style='padding:0cm 0cm 0cm 0cm'> Director of Network and IT Operations, EMEA<o:p></o:p> </td> </tr> <tr> <td style='padding:0cm 0cm 0cm 0cm'> <o:p></o:p> </td> </tr> <tr> <td style='padding:0cm 0cm 0cm 0cm'> Premiere Global Services<o:p></o:p> </td> </tr> <tr> <td style='padding:0cm 0cm 0cm 0cm'> Tel: +353 (0) 23 88 32103<o:p></o:p> </td> </tr> <tr> <td style='padding:0cm 0cm 0cm 0cm'> Mob: +353 (0) 86 919 8149 <o:p></o:p> </td> </tr> <tr> <td style='padding:0cm 0cm 0cm 0cm'> Fax: +353 (0) 23 88 36101<o:p></o:p> </td> </tr> <tr> <td style='padding:0cm 0cm 0cm 0cm'> <o:p></o:p> </td> </tr> <tr> <td style='padding:0cm 0cm 0cm 0cm'> <img width=200 height=50 id="Picture_x0020_1" src="cid:image001.jpg@01CA05FD.F1CDEDB0" alt="http://www.premiereglobal.eu/PGS_Signature.jpg"><o:p></o:p> </td> </tr> </table> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html>