July 2013 - address-policy-wg

regid: rspn.ir
by Mehdi Sabour 15 Jul '13

15 Jul '13

Dear Colleague, I've faced a problem and I want to address it to you; I hope you can help me. One of my customers called "Sapco" has 193.105.2.0/24 range of IP address, It has already established BGP protocol with us and ITC (You can find its diagram in attachment). Everything with this Range IP is ok but when Sapco's clients want to browse Google's website, google.br (Belgium) opens instead of google.com. I registered its IPs in Google' support (https://support.google.com/websearch/contact/ip), unfortunately the problem hasn't solved yet. I've checked these IPs in all websites, in all of them 193.105.2.0/24 registered Iran country but I and ITC don't know what the problem is. I hope you can help me, if you face this kind of problem. Best Regards. --- Mehdi Sabour NOC Manager Technical Division Respina Networks & Beyond T: +98 21 84 23 00 00 F: +98 21 88 19 10 83 www.respina.net<http://www.respina.net/> ________________________________ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system administrator. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of RESPINA. Finally, the recipient should check this email and any attachments for the presence of viruses. RESPINA accepts no liability for any damage caused by any virus transmitted by this email. ________________________________

2 1

Guidance Requested: Reassigning Referenced ASNs
by Sonderegger Olaf ABRAXAS INFORMATIK AG 01 Jul '13

01 Jul '13

Hi all Based on Randy's proposal: > inform owner of dangling reference. wait a week. inform again. > wait a month. inform again. wait a week. remove dangling reference. > wait a month to see if anything has broken enough to get the attention > of folk who do not respond to email. reassign AS number. In my point of view, it is enough to inform once. Members have to update their information, members have to be contactable by e-mail. So: 1. Inform owner about its wrong objects (only once). 2. If an owner doesn't clean up its objects, RIPE NCC should be able to clean up by itself after a month. 3. Re-assign AS numbers after two month. Best regards, Olaf Sonderegger

11 12

Re: [address-policy-wg] PA/PI unification PI Address Space
by Gert Doering 01 Jul '13

01 Jul '13

Hi, (subject changed and in-reply-to: removed, to make it clear that this is really a different thread) On Wed, Jun 26, 2013 at 11:34:56AM +0000, Sonderegger Olaf ABRAXAS INFORMATIK AG wrote: > It would be nice if Address Policy WG could continue with the > idea about removing status "Provider Aggregatable" (PA) and "Provider > Independent" (PI). Are there any plans? For IPv4, let's wait until Tore's proposal has come to a conclusion, as it's very hard to do two large-scale changes to the same text at the same time. For IPv6, it's still sitting on my lap, and I need to restart the process - thanks for the reminder. Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279

4 6

Guidance Requested: Reassigning Referenced ASNs
by Andrea Cima 01 Jul '13

01 Jul '13

[Apologies for duplicates] Dear colleagues, At the Address Policy WG session during RIPE 66, the RIPE NCC requested guidance from the RIPE community on reassigning referenced 16-bit ASNs. Together with the Address Policy WG Chairs, we have decided to seek additional input from the WG mailing list. Background: the RIPE NCC has around 1,400 returned 16-bit ASNs that are currently referenced in route objects, and "import" and "export" lines in aut-num objects. Problem: there is a need for 16-bit ASNs by operators. However, because these ASNs are referenced, they are not being reassigned. At RIPE 66, the RIPE NCC suggested the following potential solutions: A. Not reassign referenced AS numbers B. Reassign AS numbers even if referenced C. Clean up the RIPE Database from references and then reassign the AS numbers C.1. "Silent" update; or C.2. Informing the object holder of the update Please find the RIPE Meeting slides at the following url: https://ripe66.ripe.net/presentations/176-Address_Policy_WG_RIPE_66.pdf This email has been sent to both the Address Policy WG and RIPE Database WG mailing lists, due to the impact the proposals would have on the RIPE Database. However, we would ask to keep the discussion on the Address Policy WG mailing list to facilitate participation and the channeling of feedback. Thank you in advance for your input and best regards, Andrea Cima RIPE NCC

12 21