March 2018 - Test - lists.nanog.org

Last call for presentations and Draft programme for RIPE 76
by Benno Overeinder 20 Mar '18

20 Mar '18

Colleagues, A list of currently accepted RIPE 76 presentations is now published at: https://ripe76.ripe.net/programme/meeting-plan/plenary/ There are still plenary, BoF, tutorial and workshop slots remaining for the final RIPE 76 programme and RIPE Programme Committee will accept new proposals until *8 April 2018*. This is our last call for you to submit your proposals. You can find the CFP for RIPE 76 below, or at https://ripe76.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings, see the "Speakers" paragraph in CFP for more information. Kind regards, Benno Overeinder RIPE PC Chair https://ripe76.ripe.net/ripe-pc -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 76 will take place from 14-18 May in Marseille, France. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 76. See the full descriptions of the different presentation formats, https://ripe76.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *8 April 2018*. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) Speakers Presenters, RIPE Working Group Chairs and the RIPE Programme Committee are required to cover their own costs to attend a RIPE Meeting (meeting ticket, travel and accommodation). We have various ticket options available depending on your needs. In extraordinary circumstances, the RIPE Chair can waive the meeting fee for presenters. These requests are dealt with on a case-by-case basis via pc(a)ripe.net. Also note that, on an individual basis, participants can apply for a RIPE Fellowship to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship Submissions Presenters should be clear on whether they wish to submit a presentation for a plenary or working group (WG) session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe76.ripe.net/plenary-or-wg/ RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour (during evening sessions) - Lightning talks: 10 minutes total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe76.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe76.ripe.net/submit-topic/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. If you have any questions or requests concerning content submissions, please email pc(a)ripe.net. -- Benno J. Overeinder NLnet Labs https://www.nlnetlabs.nl/

1 0

IPv4 smaller than /24 leasing?
by Filip Hruska 18 Mar '18

18 Mar '18

Hi, I have stumbled upon this site [1] which seems to offer /27 IPv4 leasing. They also claim "All of our IPv4 address space can be used on any network in any location." I thought that the smallest prefix size one could get routed globally is /24? So how does this work? [1] http://www.forked.net/ip-address-leasing/ Thanks -- Filip Hruska Linux System Administrator

16 42

any contact at mycheckfree.com
by Randy Bush 18 Mar '18

18 Mar '18

i am using both ffox 59.01 and chrome 65.0.3325.162 on latest macos high sierra. i am trying to connect to mycheckfree.com ffox and chrome are offering sha1 and then puking when the site selects it. clearly ffox and chrome should not do this. but also, mycheckfree should not be selecting sha1. and i can't see their web site to get a support contact. randy

3 2

TWC/Charter/Spectrum contact off-list ? (Reverse DNS issue)
by Brandon Applegate 17 Mar '18

17 Mar '18

Hello, I had success with this issue about 2 years ago when some TWC folks contacted me. I don’t know if those folks are still with TWC/Charter here in the end of 2017 - hence posting on NANOG. The tl;dr is IPv6 reverse DNS issues. It was broken, got fixed, and seems to have broken again recently. Thanks in advance. -- Brandon Applegate - CCIE 10273 PGP Key fingerprint: 0641 D285 A36F 533A 73E5 2541 4920 533C C616 703A "For thousands of years men dreamed of pacts with demons. Only now are such things possible."

2 2

New Jersey Telecom Lawyer
by Rod Beck 16 Mar '18

16 Mar '18

Please contact offline. Best, Roderick. Roderick Beck Director of Global Sales United Cable Company www.unitedcablecompany.com<http://www.unitedcablecompany.com> New York City & Budapest rod.beck(a)unitedcablecompany.com 36-30-859-5144 [1467221477350_image005.png]

1 0

Finding scale in Columbus, OH
by Drew Weaver 16 Mar '18

16 Mar '18

Hello, We've been running into some trouble finding Internet connectivity that will scale (100G) in Central Ohio. So we decided to try and find transport that would scale to other areas that have better Internet infrastructure (CLE, CIN, CHI, ATL, WDC/ASH), our success in this has been surprisngly limited. I know that AWS just put a facility in this area and Facebook is either building one or it is already completed so there must be someone either leasing fiber/transport or they built their own which means that somebody is still doing that kind of construction in this area. Has anyone completed any projects recently with any success at scale in Central Ohio? If so, could you share how you achieved this, either on-list or off-list? Thank you, -Drew

2 1

Weekly Routing Table Report
by cscora＠apnic.net 16 Mar '18

16 Mar '18

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 TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG, 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 17 Mar, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 690673 Prefixes after maximum aggregation (per Origin AS): 267882 Deaggregation factor: 2.58 Unique aggregates announced (without unneeded subnets): 332450 Total ASes present in the Internet Routing Table: 60129 Prefixes per ASN: 11.49 Origin-only ASes present in the Internet Routing Table: 51933 Origin ASes announcing only one prefix: 22773 Transit ASes present in the Internet Routing Table: 8196 Transit-only ASes present in the Internet Routing Table: 255 Average AS path length visible in the Internet Routing Table: 4.2 Max AS path length visible: 31 Max AS path prepend of ASN (262865) 25 Prefixes from unregistered ASNs in the Routing Table: 63 Number of instances of unregistered ASNs: 63 Number of 32-bit ASNs allocated by the RIRs: 21837 Number of 32-bit ASNs visible in the Routing Table: 17567 Prefixes from 32-bit ASNs in the Routing Table: 73049 Number of bogon 32-bit ASNs visible in the Routing Table: 13 Special use prefixes present in the Routing Table: 3 Prefixes being announced from unallocated address space: 338 Number of addresses announced to Internet: 2855059586 Equivalent to 170 /8s, 44 /16s and 192 /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.8 Total number of prefixes smaller than registry allocations: 229892 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 189758 Total APNIC prefixes after maximum aggregation: 54251 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 188659 Unique aggregates announced from the APNIC address blocks: 76998 APNIC Region origin ASes present in the Internet Routing Table: 8708 APNIC Prefixes per ASN: 21.67 APNIC Region origin ASes announcing only one prefix: 2470 APNIC Region transit ASes present in the Internet Routing Table: 1294 Average APNIC Region AS path length visible: 4.3 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3623 Number of APNIC addresses announced to Internet: 767297698 Equivalent to 45 /8s, 188 /16s and 8 /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: 205948 Total ARIN prefixes after maximum aggregation: 98707 ARIN Deaggregation factor: 2.09 Prefixes being announced from the ARIN address blocks: 206695 Unique aggregates announced from the ARIN address blocks: 97753 ARIN Region origin ASes present in the Internet Routing Table: 18110 ARIN Prefixes per ASN: 11.41 ARIN Region origin ASes announcing only one prefix: 6707 ARIN Region transit ASes present in the Internet Routing Table: 1800 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: 2323 Number of ARIN addresses announced to Internet: 1104486016 Equivalent to 65 /8s, 213 /16s and 30 /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: 187538 Total RIPE prefixes after maximum aggregation: 91246 RIPE Deaggregation factor: 2.06 Prefixes being announced from the RIPE address blocks: 183828 Unique aggregates announced from the RIPE address blocks: 109868 RIPE Region origin ASes present in the Internet Routing Table: 24989 RIPE Prefixes per ASN: 7.36 RIPE Region origin ASes announcing only one prefix: 11341 RIPE Region transit ASes present in the Internet Routing Table: 3485 Average RIPE Region AS path length visible: 4.2 Max RIPE Region AS path length visible: 28 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6776 Number of RIPE addresses announced to Internet: 714742144 Equivalent to 42 /8s, 154 /16s and 25 /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: 88911 Total LACNIC prefixes after maximum aggregation: 19649 LACNIC Deaggregation factor: 4.52 Prefixes being announced from the LACNIC address blocks: 90277 Unique aggregates announced from the LACNIC address blocks: 40074 LACNIC Region origin ASes present in the Internet Routing Table: 6915 LACNIC Prefixes per ASN: 13.06 LACNIC Region origin ASes announcing only one prefix: 1885 LACNIC Region transit ASes present in the Internet Routing Table: 1290 Average LACNIC Region AS path length visible: 4.7 Max LACNIC Region AS path length visible: 31 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4448 Number of LACNIC addresses announced to Internet: 172058848 Equivalent to 10 /8s, 65 /16s and 104 /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: 18453 Total AfriNIC prefixes after maximum aggregation: 3980 AfriNIC Deaggregation factor: 4.64 Prefixes being announced from the AfriNIC address blocks: 20876 Unique aggregates announced from the AfriNIC address blocks: 7506 AfriNIC Region origin ASes present in the Internet Routing Table: 1124 AfriNIC Prefixes per ASN: 18.57 AfriNIC Region origin ASes announcing only one prefix: 369 AfriNIC Region transit ASes present in the Internet Routing Table: 229 Average AfriNIC Region AS path length visible: 4.6 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 397 Number of AfriNIC addresses announced to Internet: 96067584 Equivalent to 5 /8s, 185 /16s and 224 /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 5421 4192 74 ERX-CERNET-BKB China Education and Rese 7545 3919 406 402 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2865 11132 778 KIXS-AS-KR Korea Telecom, KR 9829 2803 1499 541 BSNL-NIB National Internet Backbone, IN 7552 2698 1161 58 VIETEL-AS-AP Viettel Group, VN 9394 2637 4923 29 CTTNET China TieTong Telecommunications 45899 2580 1561 162 VNPT-AS-VN VNPT Corp, VN 17974 2318 930 80 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9808 2179 8699 32 CMNET-GD Guangdong Mobile Communication 4755 2086 417 215 TATACOMM-AS TATA Communications formerl 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 6327 3369 1323 86 SHAW - Shaw Communications Inc., CA 22773 3283 2988 149 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2167 405 108 MEGAPATH5-US - MegaPath Corporation, US 20115 2096 2484 436 CHARTER-NET-HKY-NC - Charter Communicat 16509 2052 4374 611 AMAZON-02 - Amazon.com, Inc., US 30036 1939 339 186 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 1938 5071 622 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 6389 1776 3671 36 BELLSOUTH-NET-BLK - BellSouth.net Inc., 11492 1760 228 558 CABLEONE - CABLE ONE, INC., US 7018 1689 20188 1251 ATT-INTERNET4 - AT&T Services, Inc., US 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 12479 3696 1447 771 UNI2-AS, ES 39891 3520 187 21 ALJAWWALSTC-AS, SA 20940 2793 805 2043 AKAMAI-ASN1, US 8551 2104 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2036 1864 704 ROSTELECOM-AS, RU 34984 2026 334 478 TELLCOM-AS, TR 9121 1930 1692 19 TTNET, TR 13188 1606 100 46 TRIOLAN, UA 6849 1241 355 21 UKRTELNET, UA 8402 1223 544 14 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 8151 4318 3384 583 Uninet S.A. de C.V., MX 10620 3597 540 259 Telmex Colombia S.A., CO 11830 2642 370 66 Instituto Costarricense de Electricidad 6503 1631 437 53 Axtel, S.A.B. de C.V., MX 7303 1507 1026 191 Telecom Argentina S.A., AR 28573 1024 2247 195 CLARO S.A., BR 6147 1016 377 27 Telefonica del Peru S.A.A., PE 3816 1006 506 120 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 927 126 83 Alestra, S. de R.L. de C.V., MX 18881 907 1072 29 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 1162 398 50 LINKdotNET-AS, EG 37611 815 91 8 Afrihost, ZA 36903 741 372 137 MT-MPLS, MA 36992 678 1380 39 ETISALAT-MISR, EG 8452 625 1730 18 TE-AS TE-AS, EG 24835 602 850 15 RAYA-AS, EG 29571 466 68 12 ORANGE-COTE-IVOIRE, CI 37492 450 376 81 ORANGE-, TN 15399 362 35 7 WANANCHI-, KE 37342 361 32 1 MOVITEL, MZ 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 5421 4192 74 ERX-CERNET-BKB China Education and Rese 8151 4318 3384 583 Uninet S.A. de C.V., MX 7545 3919 406 402 TPG-INTERNET-AP TPG Telecom Limited, AU 12479 3696 1447 771 UNI2-AS, ES 10620 3597 540 259 Telmex Colombia S.A., CO 39891 3520 187 21 ALJAWWALSTC-AS, SA 6327 3369 1323 86 SHAW - Shaw Communications Inc., CA 22773 3283 2988 149 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 4766 2865 11132 778 KIXS-AS-KR Korea Telecom, KR 9829 2803 1499 541 BSNL-NIB National Internet Backbone, IN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 8151 4318 3735 Uninet S.A. de C.V., MX 7545 3919 3517 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3520 3499 ALJAWWALSTC-AS, SA 10620 3597 3338 Telmex Colombia S.A., CO 6327 3369 3283 SHAW - Shaw Communications Inc., CA 22773 3283 3134 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 12479 3696 2925 UNI2-AS, ES 7552 2698 2640 VIETEL-AS-AP Viettel Group, VN 9394 2637 2608 CTTNET China TieTong Telecommunications Corpora 11830 2642 2576 Instituto Costarricense de Electricidad y Telec Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65456 PRIVATE 31.171.126.0/23 199311 AZRT-LX Local Internet Exchang 267285 UNALLOCATED 45.232.244.0/22 53087 TELY Ltda., BR 267285 UNALLOCATED 45.232.244.0/23 53087 TELY Ltda., BR 267285 UNALLOCATED 45.232.246.0/23 53087 TELY Ltda., BR 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW 65537 DOCUMENT 62.162.120.0/24 6821 MT-AS-OWN bul. Orce Nikolov bb 419333 UNALLOCATED 84.17.91.0/24 41933 IPRAGAZ-AS Istanbul/ TURKEY, T 65024 PRIVATE 87.103.234.0/24 39407 CHITATELECOM-AS, RU 65000 PRIVATE 95.179.2.0/24 65001 -Private Use AS-, ZZ Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 100.66.224.0/19 209 CENTURYLINK-US-LEGACY-QWEST - Qwest Communicati 100.127.16.0/23 28885 OMANTEL-NAP-AS OmanTel NAP, OM 100.127.18.0/23 28885 OMANTEL-NAP-AS OmanTel NAP, OM Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 27.100.7.0/24 56096 UNKNOWN 37.44.224.0/20 48666 AS-MAROSNET Moscow, Russia, RU 41.76.136.0/22 37500 -Reserved AS-, ZZ 41.76.136.0/24 37500 -Reserved AS-, ZZ 41.76.138.0/24 37500 -Reserved AS-, ZZ 41.76.139.0/24 37500 -Reserved AS-, ZZ 41.76.140.0/22 37500 -Reserved AS-, ZZ 41.76.140.0/24 37500 -Reserved AS-, ZZ 41.76.141.0/24 37500 -Reserved AS-, ZZ 41.76.142.0/24 37500 -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:14 /9:11 /10:37 /11:100 /12:289 /13:563 /14:1094 /15:1899 /16:13328 /17:7842 /18:13622 /19:25082 /20:39220 /21:45173 /22:85549 /23:69207 /24:385416 /25:837 /26:601 /27:656 /28:35 /29:20 /30:17 /31:4 /32:57 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3160 3369 SHAW - Shaw Communications Inc., CA 39891 2946 3520 ALJAWWALSTC-AS, SA 22773 2538 3283 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 12479 2482 3696 UNI2-AS, ES 18566 2061 2167 MEGAPATH5-US - MegaPath Corporation, US 11830 1989 2642 Instituto Costarricense de Electricidad y Telec 30036 1693 1939 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1601 3597 Telmex Colombia S.A., CO 8551 1567 2104 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11492 1538 1760 CABLEONE - CABLE ONE, INC., US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1567 2:832 4:19 5:2806 6:59 7:1 8:1118 9:1 12:1880 13:207 14:1749 15:27 16:3 17:191 18:68 20:47 21:3 23:2559 24:2157 25:2 27:2285 31:1958 32:89 35:27 36:504 37:2736 38:1462 39:247 40:103 41:3028 42:592 43:1949 44:98 45:3919 46:3035 47:199 49:1353 50:1050 51:48 52:989 54:357 55:5 56:10 57:42 58:1563 59:1020 60:428 61:2144 62:1804 63:1802 64:4722 65:2223 66:4594 67:2366 68:1173 69:3206 70:1181 71:558 72:2105 74:2718 75:410 76:426 77:1553 78:1698 79:1868 80:1484 81:1444 82:1078 83:779 84:1022 85:2069 86:578 87:1283 88:928 89:2316 90:200 91:6301 92:1172 93:2362 94:2393 95:2727 96:658 97:356 98:928 99:128 100:79 101:1378 102:31 103:17312 104:3298 105:223 106:588 107:1791 108:709 109:2714 110:1571 111:1756 112:1325 113:1367 114:1117 115:1650 116:1639 117:1717 118:2170 119:1677 120:969 121:1060 122:2450 123:1823 124:1451 125:1885 128:983 129:624 130:444 131:1601 132:656 133:195 134:1002 135:226 136:451 137:495 138:1951 139:573 140:419 141:696 142:790 143:943 144:801 145:452 146:1153 147:742 148:1545 149:697 150:738 151:1046 152:759 153:308 154:1021 155:754 156:847 157:779 158:627 159:1643 160:922 161:718 162:2579 163:526 164:1024 165:1399 166:408 167:1394 168:3062 169:810 170:3665 171:422 172:1052 173:1951 174:879 175:750 176:1876 177:3916 178:2424 179:1194 180:2238 181:2179 182:2466 183:1132 184:915 185:12926 186:3559 187:2326 188:2738 189:1989 190:8120 191:1425 192:9776 193:5893 194:4794 195:3981 196:2435 197:1443 198:5532 199:5908 200:7396 201:4999 202:10390 203:10129 204:4545 205:2848 206:3085 207:3194 208:3994 209:3938 210:4033 211:2118 212:3016 213:2693 214:901 215:61 216:5825 217:2130 218:898 219:621 220:1722 221:996 222:1044 223:1234 End of report

1 0

Google / GMail Geolocation
by Harry Reeder 15 Mar '18

15 Mar '18

Hi Folks, Wondering if anyone has a contact at Google who can help - I've a customer who's attempted to log in from one of our IPs (which comes from one of Cogent's /16 blocks) however they get an automated email response from Google saying that they're logging in from Hong Kong, and the login was prevented for security reasons (as someone may have their password). For reference, the whois response shows Washington DC, and refers to Cogent's rwhois which places us correctly at Telehouse London. Tools like Maxmind also have our location correct. Is there somewhere I can go to get this corrected for our leased IP ranges? (I am aware that the long term solution is to get our own IP space - I am working on that, I just don't have enough of a business case yet) Off-list replies also welcome. Thanks Harry

2 2

Office365 and a new IP address
by Paul Reichart 14 Mar '18

14 Mar '18

Wondering if anyone on the list has ever set up a mail filtering appliance or server on new IP address and had to deal with 451 messages from Office 365. We're processing a large volume of mail and seem to be throttled by O365. Seeing something like this: 451 4.7.500 Server busy. Please try again later from [x.x.x.x]. (AS77713180) [.....outlook.com ]. We own the IP block and the address itself is not on any block lists. It's been going on for a few days now, pissing off a lot of our customers. As expected O365's front line support is totally useless. Any advice would be appreciated!

2 2

Re: Proof of ownership; when someone demands you remove a prefix
by Naslund, Steve 13 Mar '18

13 Mar '18

The fact that it is a newer customer would make me talk to the RIR direct and verify that a dispute is really in progress. I would also look at some looking glasses and see if the prefix is being announced elsewhere, if so that might indicate that your customer is indeed stepping on a legit owner. I would also make it clear to the new customer that they are on thin ice here to light a fire under their process. Let them know that it is up to them to convince you that they are the legit owner. No one wants to lose a customer but they are threatening your business and putting you in legal jeopardy if they are not legit. Steven Naslund Chicago IL >-----Original Message----- >From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Sean Pedersen >Sent: Tuesday, March 13, 2018 12:39 PM >To: nanog(a)nanog.org >Subject: RE: Proof of ownership; when someone demands you remove a prefix > >This is more or less the situation we're in. We contacted the customer and they informed us the matter is in dispute with the RIR and that their >customer (the assignee) is in the process of resolving the issue. We have to allow them time to accomplish this. I've asked for additional information >to help us understand the nature of the dispute. In that time we received another request to stop announcing the prefix(s) in addition to a new set of >prefixes, and a threat to contact our upstream providers as well as ARIN - which is not the RIR the disputed resources are allocated to. > >This is a new(er) customer, so there is some merit to dropping the prefix and letting them sort it out based on the current RIR contact(s). However, >there is obvious concern over customer service and dropping such a large block of IPs. > >I'm definitely leaning toward "let the customer (or customer's customer) and the RIR sort it out" if the POC validates the request weighed responsibly >against customer age. However, from a customer service perspective, I think we owe it to our customers to make sure a request is legitimate before we >knock them offline. With a limited toolset to validate that information, I can't help but feel conflicted. > >I appreciate all the feedback this thread has generated so far!

3 3