Hi! 1) RIPE NCC policy requires all routes must be present at the RIPE DB and RIPE IPs could be officially announced outside RIPE Region.
2) Resources owners don't know anything about these routes.. so it means that ranges were announces without permission by third party company. On Thu, Mar 3, 2011 at 9:05 AM, Owen DeLong <[email protected]> wrote: > > On Mar 2, 2011, at 11:55 PM, Alfa Telecom wrote: > >> Hello All! >> >> Maybe somebody could help me with some issue: >> >> Ranges below are announced by Level3 >> >> 79.110.224.0/20 *[BGP/170] 08:23:34, MED 0, localpref 150, from >> 213.248.64.245 >> AS path: 3356 >> 79.110.64.0/20 *[BGP/170] 08:25:07, MED 0, localpref 150, from >> 213.248.64.245 >> AS path: 3356 >> >> Both ranges are from RIPE region and couldn't be announced from ARIN ASN at >> all. We're sponsored LIR for both companies, I sent several emails to Level3 >> noc, made several calls but they still announce these ranges. >> ------------------ >> Andrew > > Why can't they be announced from ARIN ASN? Many network ranges issued by RIPE > are held by companies with operations in north america and are announced in > North America from North American ASNs. > > If you are saying that the announcement from Level 3 is not on behalf of the > companies > for whom you are the sponsoring LIR, then, perhaps the registered customers > (to whom > the addresses are listed in whois) should contact Level 3 directly so that > they can > validate the resource registrants properly before removing the routes. > > If I misunderstand what you are attempting to say, I apologize, but, your > message is > hard to understand. > > Owen > > -- Network Department Alfa Telecom s.r.o. http://www.alfatelecom.cz email: [email protected] phone: +420 226 020 362
