- NANOG - lists.nanog.org

Anyone here from Netflix? | VPN Detection Problem
by Jason Canady 12 Sep '17

12 Sep '17

Hello, We have IP addresses being blocked due to proxy servers that were once on the IP address space. They have now been reclaimed and will be used for ISP services to end-users. We need to ensure that customers can watch Netflix without any issues. Would someone please reach out to me to resolve this? Thank you! Best Regards, Jason Canady Unlimited Net, LLC

2 1

Internet access for security consultants - pen tests, attack traffic, bulk e-mail, etc.
by Sean Pedersen 12 Sep '17

12 Sep '17

We were recently approached by a company that does security consulting. Some of the functions they perform include discovery scans, penetration testing, bulk e-mail generation (phishing, malware, etc.), hosting fake botnets - basically, they'd be generating a lot of bad network traffic. Targeted at specific clients/customers, but still bad. As an ISP, this is new territory for us and there are some concerns about potential impact, abuse reports, reputation, authorization to perform such tests, etc. Does anyone have experience in this area that would be willing to offer advice?

4 4

IPv6 Loopback/Point-to-Point address allocation
by Kody Vicknair 12 Sep '17

12 Sep '17

All, I’ve been doing some reading in preparation of IPv6 deployment and figuring out how we will break up our /32. I think I’m on the right track in thinking that each customer will be allocated a /48 to do whatever they wish with it. I’ve read recent BCOP drafts that have been approved by the IETF: https://www.ripe.net/publications/docs/ripe-554 It looks like the smallest subnet that should ever be assigned is a /64 on a particular link. Some questions that come to mind with IPv6: In regards to Point to point links my thinking is this: Assign a unique /64 to each point to point link with these addresses being Globally routable. This seems to be what our IX providers do when assigning us an IPv6 address. Am I correct in this train of thought? Why/Why not? In regards to core loopback addressing my initial thoughts are as follows: Assign a single /64 encompassing all /128’s planned for loopback addressing schemes. Should I be using Unique Local addressing for loopbacks instead of going with a Globally routeable addressing scheme? Should each interface IP configuration have a /64 or a /128? Also when talking about CPE mgmt addresses what do you think is a practical way of going about assigning “Private” addressing schemes for cpe management purposes. I’m sure some of these questions will be answered when I dive deeper into how OSPFv6 works as well as BGP in regards to IPv6. Are any of you currently running IPv6 and wished you had done something differently during the planning phase that may have prevented headaches down the road? Kody Vicknair Network Engineer [cid:imagebf3343.JPG@c9d2fbd2.4db10e0d] <http://www.rtconline.com> Tel: 985.536.1214 Fax: 985.536.0300 Email: kvicknair(a)reservetele.com Web: www.rtconline.com Reserve Telecommunications 100 RTC Dr Reserve, LA 70084 Disclaimer: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material which should not disseminate, distribute or be copied. Please notify Kody Vicknair immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Kody Vicknair therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

12 16

Any validity to this claim? Fiber cable cut to St. John USVI.
by Javier J 11 Sep '17

11 Sep '17

https://www.reddit.com/r/TropicalWeather/comments/6zcr3y/this_is_a_message_…

1 0

Re: 2017 NANOG Elections General Information
by Scott Weeks 11 Sep '17

11 Sep '17

--- bryan(a)shout.net wrote: From: Bryan Holloway <bryan(a)shout.net> Had I been a first-time attendee, I would've felt like a high-school freshman being told who all the "cool seniors" were. Frankly, it was awkward and off-putting. --------------------------------------------------- Not only first time attendees, but also long time list participants are made to feel that way; me included for making comments about vendor spam or top posting. I note that not only randy is doing what he says, but other old schoolers are now gone (such as vixie, li and others) who are folks that a person could learn a lot from. scott ps. I always shot peas at the "cool kids" table in the lunch room in high school. From time-to-time I want virtual peas to shoot now days... >;-)

2 1

RE: IPv6 Loopback/Point-to-Point address allocation
by Kody Vicknair 09 Sep '17

09 Sep '17

Apologies, Wrong link: https://www.sinog.si/docs/draft-IPv6pd-BCOP-v7.pdf Kody Vicknair Network Engineer [cid:image764c5e.JPG@bb882327.44b4b1d7] <http://www.rtconline.com> Tel: 985.536.1214 Fax: 985.536.0300 Email: kvicknair(a)reservetele.com Web: www.rtconline.com Reserve Telecommunications 100 RTC Dr Reserve, LA 70084 Disclaimer: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material which should not disseminate, distribute or be copied. Please notify Kody Vicknair immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Kody Vicknair therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. From: Kody Vicknair Sent: Saturday, September 09, 2017 11:06 AM To: nanog(a)nanog.org Subject: IPv6 Loopback/Point-to-Point address allocation All, I’ve been doing some reading in preparation of IPv6 deployment and figuring out how we will break up our /32. I think I’m on the right track in thinking that each customer will be allocated a /48 to do whatever they wish with it. I’ve read recent BCOP drafts that have been approved by the IETF: https://www.ripe.net/publications/docs/ripe-554 It looks like the smallest subnet that should ever be assigned is a /64 on a particular link. Some questions that come to mind with IPv6: In regards to Point to point links my thinking is this: Assign a unique /64 to each point to point link with these addresses being Globally routable. This seems to be what our IX providers do when assigning us an IPv6 address. Am I correct in this train of thought? Why/Why not? In regards to core loopback addressing my initial thoughts are as follows: Assign a single /64 encompassing all /128’s planned for loopback addressing schemes. Should I be using Unique Local addressing for loopbacks instead of going with a Globally routeable addressing scheme? Should each interface IP configuration have a /64 or a /128? Also when talking about CPE mgmt addresses what do you think is a practical way of going about assigning “Private” addressing schemes for cpe management purposes. I’m sure some of these questions will be answered when I dive deeper into how OSPFv6 works as well as BGP in regards to IPv6. Are any of you currently running IPv6 and wished you had done something differently during the planning phase that may have prevented headaches down the road?

1 0

Weekly Routing Table Report
by cscora＠apnic.net 08 Sep '17

08 Sep '17

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG MENOG, BJNOG, SDNOG, CMNOG, IRNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 09 Sep, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 662997 Prefixes after maximum aggregation (per Origin AS): 257792 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 320036 Total ASes present in the Internet Routing Table: 58342 Prefixes per ASN: 11.36 Origin-only ASes present in the Internet Routing Table: 50442 Origin ASes announcing only one prefix: 22239 Transit ASes present in the Internet Routing Table: 7900 Transit-only ASes present in the Internet Routing Table: 228 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 56 Max AS path prepend of ASN ( 55644) 51 Prefixes from unregistered ASNs in the Routing Table: 60 Number of instances of unregistered ASNs: 63 Number of 32-bit ASNs allocated by the RIRs: 19920 Number of 32-bit ASNs visible in the Routing Table: 15706 Prefixes from 32-bit ASNs in the Routing Table: 64185 Number of bogon 32-bit ASNs visible in the Routing Table: 25 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 354 Number of addresses announced to Internet: 2854371936 Equivalent to 170 /8s, 34 /16s and 66 /24s Percentage of available address space announced: 77.1 Percentage of allocated address space announced: 77.1 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.7 Total number of prefixes smaller than registry allocations: 219492 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 182793 Total APNIC prefixes after maximum aggregation: 52381 APNIC Deaggregation factor: 3.49 Prefixes being announced from the APNIC address blocks: 181746 Unique aggregates announced from the APNIC address blocks: 75097 APNIC Region origin ASes present in the Internet Routing Table: 8337 APNIC Prefixes per ASN: 21.80 APNIC Region origin ASes announcing only one prefix: 2308 APNIC Region transit ASes present in the Internet Routing Table: 1190 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 56 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3175 Number of APNIC addresses announced to Internet: 765835488 Equivalent to 45 /8s, 165 /16s and 184 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-137529 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 201058 Total ARIN prefixes after maximum aggregation: 95867 ARIN Deaggregation factor: 2.10 Prefixes being announced from the ARIN address blocks: 202840 Unique aggregates announced from the ARIN address blocks: 93729 ARIN Region origin ASes present in the Internet Routing Table: 17966 ARIN Prefixes per ASN: 11.29 ARIN Region origin ASes announcing only one prefix: 6634 ARIN Region transit ASes present in the Internet Routing Table: 1771 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2175 Number of ARIN addresses announced to Internet: 1110263072 Equivalent to 66 /8s, 45 /16s and 69 /24s ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-397212 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 176808 Total RIPE prefixes after maximum aggregation: 86676 RIPE Deaggregation factor: 2.04 Prefixes being announced from the RIPE address blocks: 172692 Unique aggregates announced from the RIPE address blocks: 104276 RIPE Region origin ASes present in the Internet Routing Table: 24360 RIPE Prefixes per ASN: 7.09 RIPE Region origin ASes announcing only one prefix: 11189 RIPE Region transit ASes present in the Internet Routing Table: 3447 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 32 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6153 Number of RIPE addresses announced to Internet: 713023360 Equivalent to 42 /8s, 127 /16s and 223 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-207259 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 84911 Total LACNIC prefixes after maximum aggregation: 18956 LACNIC Deaggregation factor: 4.48 Prefixes being announced from the LACNIC address blocks: 86164 Unique aggregates announced from the LACNIC address blocks: 39587 LACNIC Region origin ASes present in the Internet Routing Table: 6348 LACNIC Prefixes per ASN: 13.57 LACNIC Region origin ASes announcing only one prefix: 1762 LACNIC Region transit ASes present in the Internet Routing Table: 1173 Average LACNIC Region AS path length visible: 5.3 Max LACNIC Region AS path length visible: 36 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 3860 Number of LACNIC addresses announced to Internet: 171057888 Equivalent to 10 /8s, 50 /16s and 34 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 17365 Total AfriNIC prefixes after maximum aggregation: 3859 AfriNIC Deaggregation factor: 4.50 Prefixes being announced from the AfriNIC address blocks: 19201 Unique aggregates announced from the AfriNIC address blocks: 7060 AfriNIC Region origin ASes present in the Internet Routing Table: 1074 AfriNIC Prefixes per ASN: 17.88 AfriNIC Region origin ASes announcing only one prefix: 345 AfriNIC Region transit ASes present in the Internet Routing Table: 210 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 343 Number of AfriNIC addresses announced to Internet: 93713664 Equivalent to 5 /8s, 149 /16s and 245 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5417 4194 88 ERX-CERNET-BKB China Education and Rese 7545 3834 406 382 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2962 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4766 2838 11126 751 KIXS-AS-KR Korea Telecom, KR 9829 2759 1499 541 BSNL-NIB National Internet Backbone, IN 9394 2418 5027 46 CTTNET China TieTong Telecommunications 9808 2363 8699 32 CMNET-GD Guangdong Mobile Communication 45899 2163 1468 115 VNPT-AS-VN VNPT Corp, VN 4755 2102 422 221 TATACOMM-AS TATA Communications formerl 7552 1669 1105 69 VIETEL-AS-AP Viettel Corporation, VN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 22773 3644 2952 158 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 6327 3444 1341 87 SHAW - Shaw Communications Inc., CA 18566 2204 405 109 MEGAPATH5-US - MegaPath Corporation, US 6389 2045 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 20115 2032 2237 434 CHARTER-NET-HKY-NC - Charter Communicat 209 1892 5065 640 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 30036 1830 329 279 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 16509 1829 3960 544 AMAZON-02 - Amazon.com, Inc., US 6983 1685 854 229 ITCDELTA - Earthlink, Inc., US 701 1673 10557 629 UUNET - MCI Communications Services, In Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 39891 3387 186 23 ALJAWWALSTC-AS, SA 20940 2952 936 2115 AKAMAI-ASN1, US 8551 2478 377 41 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 34984 2059 333 425 TELLCOM-AS, TR 9121 1830 1691 17 TTNET, TR 12389 1706 1629 668 ROSTELECOM-AS, RU 12479 1682 1052 60 UNI2-AS, ES 13188 1603 100 52 TRIOLAN, UA 6849 1225 355 21 UKRTELNET, UA 8402 1195 544 15 CORBINA-AS OJSC "Vimpelcom", RU Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 10620 3568 543 209 Telmex Colombia S.A., CO 8151 2981 3418 578 Uninet S.A. de C.V., MX 11830 2097 370 65 Instituto Costarricense de Electricidad 6503 1583 437 53 Axtel, S.A.B. de C.V., MX 7303 1567 1024 248 Telecom Argentina S.A., AR 6147 1257 377 27 Telefonica del Peru S.A.A., PE 3816 1025 504 94 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 28573 962 2284 185 CLARO S.A., BR 11172 917 126 85 Alestra, S. de R.L. de C.V., MX 18881 898 1052 23 TELEFÔNICA BRASIL S.A, BR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1194 398 48 LINKdotNET-AS, EG 37611 763 91 8 Afrihost, ZA 36903 710 357 131 MT-MPLS, MA 36992 655 1383 29 ETISALAT-MISR, EG 24835 515 850 15 RAYA-AS, EG 29571 421 36 10 CITelecom-AS, CI 37492 410 354 77 ORANGE-, TN 15399 357 35 7 WANANCHI-, KE 8452 310 1730 17 TE-AS TE-AS, EG 2018 299 327 74 TENET-1, ZA Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5417 4194 88 ERX-CERNET-BKB China Education and Rese 7545 3834 406 382 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3644 2952 158 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3568 543 209 Telmex Colombia S.A., CO 6327 3444 1341 87 SHAW - Shaw Communications Inc., CA 39891 3387 186 23 ALJAWWALSTC-AS, SA 8151 2981 3418 578 Uninet S.A. de C.V., MX 17974 2962 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 20940 2952 936 2115 AKAMAI-ASN1, US 4766 2838 11126 751 KIXS-AS-KR Korea Telecom, KR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 22773 3644 3486 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7545 3834 3452 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3387 3364 ALJAWWALSTC-AS, SA 10620 3568 3359 Telmex Colombia S.A., CO 6327 3444 3357 SHAW - Shaw Communications Inc., CA 17974 2962 2889 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 8551 2478 2437 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 8151 2981 2403 Uninet S.A. de C.V., MX 9394 2418 2372 CTTNET China TieTong Telecommunications Corpora 9808 2363 2331 CMNET-GD Guangdong Mobile Communication Co.Ltd. Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65602 UNALLOCATED 8.225.192.0/24 30372 SUNESYS2 - Sunesys, LLC, US 64525 PRIVATE 45.119.143.0/24 133275 GIGANTIC-AS Gigantic Infotel P 64525 PRIVATE 45.125.62.0/24 133275 GIGANTIC-AS Gigantic Infotel P 65530 PRIVATE 45.249.40.0/24 133720 SOFTCALLCOC-AS SOFT CALL CUST- 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 65534 PRIVATE 58.68.109.0/24 10201 DWL-AS-IN Dishnet Wireless Lim 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW 290012147 UNALLOCATED 63.65.43.0/24 7046 RFC2270-UUNET-CUSTOMER - MCI C 65538 DOCUMENT 64.27.253.0/24 1273 CW Vodafone Group PLC, GB 65346 PRIVATE 94.50.36.0/22 31094 TTKNET Tyumen, Russia, RU Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 14.192.48.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.49.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.50.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.51.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 23.226.112.0/20 62788 UNKNOWN 27.100.7.0/24 56096 UNKNOWN 41.76.232.0/21 62878 XLITT - Xlitt, US 41.77.248.0/21 62878 XLITT - Xlitt, US 41.78.12.0/23 62878 XLITT - Xlitt, US 41.78.180.0/23 37265 -Reserved AS-, ZZ Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:15 /9:13 /10:36 /11:104 /12:283 /13:550 /14:1046 /15:1872 /16:13443 /17:7744 /18:13757 /19:25219 /20:39220 /21:42490 /22:80052 /23:65206 /24:369524 /25:846 /26:625 /27:648 /28:37 /29:38 /30:200 /31:2 /32:27 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3241 3444 SHAW - Shaw Communications Inc., CA 39891 2946 3387 ALJAWWALSTC-AS, SA 22773 2842 3644 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2088 2204 MEGAPATH5-US - MegaPath Corporation, US 8551 1943 2478 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 1610 1830 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1516 3568 Telmex Colombia S.A., CO 11830 1487 2097 Instituto Costarricense de Electricidad y Telec 11492 1419 1597 CABLEONE - CABLE ONE, INC., US 6389 1356 2045 BELLSOUTH-NET-BLK - BellSouth.net Inc., US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1561 2:832 4:18 5:2447 6:31 7:1 8:1058 12:1854 13:150 14:1670 15:28 16:2 17:168 18:90 20:59 23:2455 24:1942 25:2 27:2365 29:1 31:1923 32:90 33:20 35:21 36:439 37:2354 38:1384 39:69 40:98 41:2978 42:462 43:1956 44:80 45:3037 46:2794 47:165 49:1240 50:1002 51:19 52:816 54:366 55:2 56:4 57:43 58:1573 59:997 60:312 61:2027 62:1711 63:1909 64:4687 65:2206 66:4553 67:2283 68:1227 69:3377 70:1170 71:603 72:2138 74:2712 75:400 76:423 77:1498 78:1481 79:1891 80:1397 81:1392 82:1009 83:726 84:964 85:1831 86:468 87:1194 88:780 89:2180 90:171 91:6199 92:1004 93:2389 94:2351 95:2674 96:644 97:351 98:997 99:98 100:153 101:1443 102:1 103:15737 104:3049 105:189 106:563 107:1756 108:825 109:2915 110:1471 111:1745 112:1250 113:1342 114:1069 115:1586 116:1645 117:1764 118:2160 119:1642 120:730 121:1060 122:2382 123:1858 124:1483 125:1786 128:876 129:673 130:432 131:1482 132:584 133:194 134:685 135:226 136:402 137:489 138:1943 139:514 140:380 141:644 142:734 143:891 144:795 145:183 146:1105 147:706 148:1501 149:585 150:710 151:983 152:735 153:296 154:881 155:755 156:675 157:689 158:481 159:1552 160:760 161:748 162:2508 163:509 164:964 165:1453 166:380 167:1284 168:3024 169:843 170:3538 171:367 172:1018 173:2007 174:782 175:768 176:1885 177:3924 178:2560 179:1112 180:2203 181:1999 182:2403 183:768 184:864 185:10659 186:3282 187:2143 188:2575 189:1843 190:8332 191:1351 192:9620 193:5802 194:4723 195:3934 196:2114 197:1329 198:5520 199:5879 200:7592 201:4364 202:10334 203:9936 204:4532 205:2845 206:3072 207:3162 208:3962 209:4028 210:3951 211:2137 212:2863 213:2533 214:835 215:66 216:5885 217:2118 218:911 219:600 220:1677 221:919 222:740 223:1207 End of report

1 0

Cogent BCP-38
by Ben Russell 07 Sep '17

07 Sep '17

Could someone from Cogent contact me off-list? We are having an issue with one of our downstream customers who is multi-homed to another carrier. The end customer is advertising their prefix to both us and the other carrier. Both us and the other carrier peer with 174. However, if the prefix is preferred through us and the outbound traffic flows over the other carrier it is dropped. We suspect uRPF-strict on the other carriers Cogent link. We are working together with the other carrier and have a ticket open the help desk seem to be confused. Any help would be appreciated. Thanks Ben Russell Senior Network Engineer Stratus Networks (309)370-3174 [logo]

13 14

WEBCAST TODAY: ION Durban
by Joly MacFie 07 Sep '17

07 Sep '17

This is under way. Unlike many IONs, which are brief afternoon sessions, ION Durban is a full day of technical richness. A good quality webcast too, courtesy of ISOC 's Africa Regional Bureau. ISOC Africa also streamed the SAFNOG-3 Conference the last 2 days, which had many excellent presentations. See https://livestream.com/internetsociety/safnog3 [image: Livestream] <https://livestream.com/internetsociety/iondurban> Today, *Thursday 7 September 2017* the *Internet Society Deploy 360 team <http://www.internetsociety.org/deploy360/>* will present *ION Durban <http://www.internetsociety.org/deploy360/ion/durban2017/>* alongside the South African *iWeek 2017 <https://www.iweek.org.za/>*. ION Conferences bring network engineers and leading industry experts together to discuss emerging technologies and hot technology topics. Early adopters provide valuable insight into their own deployment experiences and bring participants up to speed on new standards emerging from the IETF. There will be a full-day program covering topics including IPv6, DNSSEC, Securing BGP, and TLS for Applications. The event will be webcast live on the *Internet Society Livestream Channel <https://livestream.com/internetsociety/iondurban>*. Durban is 6 hours ahead of NYC (UTC+2). *What: ION Durban <http://www.internetsociety.org/deploy360/ion/durban2017/>Where: Durban, Kwa-Zulu Natal, South AfricaWhen: Thursday 7 September 2017 09:00-16:45 SAST (UTC+2)Agenda: http://www.internetsociety.org/deploy360/ion/durban2017/agenda/ <http://www.internetsociety.org/deploy360/ion/durban2017/agenda/>Webcast: https://livestream.com/internetsociety/iondurban <https://livestream.com/internetsociety/iondurban>Slides: http://www.internetsociety.org/deploy360/ion/durban2017/presentations/ <http://www.internetsociety.org/deploy360/ion/durban2017/presentations/>Twitter: #ionconf https://bit.ly/ionconf <https://bit.ly/ionconf>* Comment <http://isoc-ny.org/p2/9380#respond> See all comments <http://isoc-ny.org/p2/9380#comments> *Permalink* http://isoc-ny.org/p2/9380 -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

1 0

Re: 2017 NANOG Elections General Information
by courtneysmith＠comcast.net 07 Sep '17

07 Sep '17

Have we considered "grooming" folks via the committees? Seems like a better place to allow folks to dip their toes in. But maybe I'm too timid. ------- Date: Tue, 5 Sep 2017 10:59:32 -0700 From: Dave Temkin <dave(a)temk.in> To: members(a)nanog.org, "North American Network Operators' Group" <nanog(a)nanog.org> Subject: Re: 2017 NANOG Elections General Information Message-ID: <CAFJiuFq1OegB5kra0aEiVoiDZfGKVECG=qNWwPS8S9DDh+b+6g(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi NANOG Community, Nominations are rapidly coming to a close - September 8th is the last day to submit nominees. Unfortunately, to follow up on my paragraph about diversity: So far, every single candidate that has completed the nomination process is a white male. Having sat in on sessions such as Women in Technology lunch, I know that this community is passionate about diversity. If you, or a friend, would like to discuss what it takes to be on the NANOG board, I or my colleagues would love to speak about it. If you're ready to enter the nomination process, you can see details below. Best Regards, -Dave Temkin, for the NANOG Board of Directors

2 1