January 2020 - Test - lists.nanog.org

RIP: Bill Manning
by Brett Watson 28 Jan '20

28 Jan '20

I was saddened to see this yesterday, that Bill Manning had passed. I was surprised this morning that it hadn’t hit NANOG yet but thought I’d post something because I have a ton of respect for Bill as I’m sure many here do. I met Bill as a very young, thought-I-knew-everything network engineer around ’92 when I was starting my internet life at a small ISP in Houston. Bill was visiting Stan Barber @ Sesquinet, which was my upstream provider at the time via T1, if I remember it all correctly. I was young, fresh out of college with a CS degree, and learning this “internet thing.” I met with Bill on campus at Rice University to discuss networking/routing, and Bill taught me CIDR, which I had no f-ing idea at that time what it was. Bill was always gracious and willing to share/teach. We always chatted and stayed in touch at NANOG and IETF conferences and through his relationship with Los Nettos over the years. Most notable, to me, was 2007 when my youngest daughter was diagnosed with cancer, and I believe Bill’s wife had (or previously battled) cancer as well. I hadn’t seen Bill for a few years, but he immediately reached out, shared his positive thoughts/prayers, and kept in touch during the battle we went through. Bill cared about people, and as noted below, he was smart as hell, and always had a crazy idea for how to solve a problem. Also as noted in Rod’s note below, Bill had a wealth of music knowledge and could always recommend something new and interesting to listen to. I’ll definitely miss Bill, and his passing makes me feel the years, and the mileage, but in a good way. -b >> This morning I talked to Julie Manning, Bill's wife. Bill died early >> Saturday morning, at home in Oregon. Most of you know Bill was >> waiting for a new heart. He would perhaps have gotten one next >> month. I guess the old one just wouldn't hold out long enough. >> >> I first met Bill in about 1995, when I returned to ISI after my first >> stint in Japan. He had taken a position in the Los Nettos project at >> ISI, a regional network project in the days when Internet service and >> operations work was still heavily shared between business and >> academia. Bill brought an operator's eye to the project, often seeing >> things differently from the researchers in the group. >> >> Bill kept the most erratic hours of any non-student I've ever met. He >> might be in the office at 2am or at 2pm, either was equally likely. >> I'd ask, "Bill, what time did you come in?" He'd reply, "10am." "I >> was here before that, and you were already here, it must have been >> earlier." "Greenwich Mean Time." >> >> And in one phase of life, "Bill, where do you live?" "Seat 4A." He >> would speculate about his average altitude and speed over the previous >> month. >> >> And, like any good geek, Bill had a spectacular collection of tie-dye >> t-shirts. He came by the look honestly: growing up in the Bay Area, >> he had actually snuck into Grateful Dead rehearsals held in a barn, >> and had traveled as a deadhead for a while. >> >> At ISI, we called Bill "the bad idea fairy". He always brought a >> slightly-off-kilter view of technical problems, which triggered >> endless discussions of fascinating, if usually implausible, >> alternatives. >> >> He had the most broad-ranging musical tastes of anyone I knew, and >> would eat almost anything (though, like me, he didn't drink alcohol). >> I was often envious of his eating and musical experiences. He >> certainly lived life to its fullest. >> >> On one occasion, I recall, we were eating lunch in a Thai restaurant >> for the first time. Bill called for the food "the way you'd make it >> in Thailand". The waiter went back into the kitchen and came out with >> a few raw Thai chiles. Bill ate one whole, without even breaking a >> sweat. The owner of the restaurant immediately came out to see who >> was eating them. Pam became a friend to our group. >> >> On other occasions, when the waiter asked for his order, Bill would >> point to another person at the table, and say, "I'll have what she's >> having." "Well, what is she having?" "I don't know, I haven't heard >> her say." Once in a while, he would point to someone else in the >> restaurant and say, "I'll have what they are having." It was funny >> and sometimes disconcerting, which was very Bill, and it was also his >> way of making sure he himself was eating (and thinking and doing) as >> broadly as possible, without getting stale. >> >> Bill worked in a bakery before joining Texas Instruments and >> accidentally falling into computer networking. (When we first met, he >> was commuting between Houston and L.A.; Julie and the kids were still >> in Houston.) I believe he attended a series of colleges but never >> finished his bachelor's degree. Just a few years ago, however, Jun >> Murai convinced him to get a Ph.D.; this took clearing administrative >> hoops to demonstrate that Bill's life experience matched that of a >> bachelor's degree, which it certainly did. I was honored to be on his >> Ph.D. committee. I literally created a "trouble ticket" accounting >> scheme to track change requests for his thesis. >> >> Bill was a valued member of the WIDE Project here in Japan. He worked >> with the DNS root operations group here, and participated in as many >> WIDE meetings as he could. He also came to Keio University's Shonan >> Fujisawa Campus when he was in Japan, and one of the best things about >> Bill was how seriously he took the students and their work, treating >> them like adult colleagues. >> >> Bill had friends on all seven continents, and for all I know on the >> International Space Station, as well. He was loved by us all. >> >> Julie does not plan to have a funeral immediately, so there is no need >> for flowers or the like. The family may do a memorial service in Utah >> in the spring. >> >> He was a unique and wonderful human being. And a good friend. >> Rest in peace, Bill. >> >> —Rod >

8 7

Major issues with Cloudflare DNS (specifically DNS-over-HTTPS)
by John Von Essen 28 Jan '20

28 Jan '20

Can someone from Cloudflare contact me off-list? I work for a major search engine (not Google) and starting yesterday, we are getting reports from around the world about a DNS issue. They are either not resolving our site, or they are getting incorrect resolution (i.e. the wrong IP). The issues appears to be centered around Firefox users who have DNS-over-HTTPS enabled, with Cloudflare as the provider. Thanks John

1 0

Call for Presentations: 33rd DNS-OARC Workshop, Paris, France, May 09 - 10th 2020
by Joe Abley 28 Jan '20

28 Jan '20

The 33rd DNS-OARC Workshop will take place at the Marriott Rive Gauche Hotel & Conference Center in Paris, France on May 9th and 10th 2020. It is co-located with and will take place right after the ICANN GDD (May 3rd to 6th), Registrations Operations Workshop (May 6th) and ICANN DNS Symposium (May 7th and 8th). The Workshop's Program Committee is requesting proposals for presentations. All DNS-related subjects are welcome. A time slot will also be available for lightning talks (5-10 minutes each) on day two of the workshop, for which submissions will be accepted just before the start of the workshop and until the start of the morning break on day two. Poster submissions are also welcome. There will be an OARC Business session during the workshop, which will be for OARC Members only. If you are an OARC member and have a sensitive topic that you wish to present during that session those can be accommodated. Workshop Milestones: 10 Jan 2020 - Submissions open via Indico 05 Mar 2020 - Deadline for submission (midnight CEST) 19 Mar 2020 - Initial Contribution list published 02 Apr 2020 - Full agenda published 02 May 2020 - Deadline for slideset submission 09 May 2020 - Workshop begins Details for presentation submission are published here: <https://indico.dns-oarc.net/event/34/call-for-abstracts/> The workshop presentations will be organized by common themes, depending on the topics and the timing of each presentation. There are 30-minute and 15-minute slots, let us know your preference in your submission. To allow the Programme Committee to make objective assessments of submissions, so as to ensure the quality of the workshop, submissions SHOULD include slides. Draft slides are acceptable on submission. If you have questions or concerns you can contact the Programme Committee: https://www.dns-oarc.net/oarc/programme via <submissions(a)dns-oarc.net> Joe Abley, for Dave Knight, for the DNS-OARC Programme Committee OARC depends on sponsorship to fund its workshops and associated social events. Please contact <sponsor(a)dns-oarc.net> if your organization is interested in becoming a sponsor. (Please note that OARC is run on a non-profit basis, and is not in a position to reimburse expenses or time for speakers at its meetings.)

1 0

DHCP Snooping Issue on Cisco N3K SW
by Md. abdullah Al naser 28 Jan '20

28 Jan '20

Hi everyone, I hope all you are fine. I'm very new to this mailing list and looking for a solution if anyone could help me. I am a network operation engineer and working for an ISP in Bangladesh. We are serving internet, data connectivity, IPTSP, IPTV and other services to corporate and retail clients. Retail clients are basically home users and small offices. To connect their CPE devices to our access network we are using DHCP. For example, we are using 192.168.0.1/24 IP in our BRAS interface and rest of all IPs are in DHCP pool to be allocated to the end users. By this time we had some bad experience with rouge DHCP server while clients connect the WAN link to the LAN port of CPE devices. To overcome that we recently deployed DHCP-snooping on our distribution switches which is in between the DHCP server and clients. But we are facing new problem after deploying that. Sometime our switch got stuck and clients don't get any IP via DHCP and all the allocations on valid DHCP server are stuck in "OFFERED" state. If we disable and then again enable the DHCP snooping feature in switch then problem is resolved for temporary. But few hours later the same problem happens repeatedly. For your information we are using Cisco Nexus 3000 switch and around 3k to 4k clients are there under that switch. We have a different location/POP where not more than 500 users are there and we don't have this kind of problem at all. So we assume that our Nexus 3000 switch is not performing well to handle DHCP snooping for large number of customers!!! For better understanding please check the network topology diagram (attached) SW Details: Hardware cisco Nexus3000 C3064PQ Chassis Software BIOS: version 3.8.0 NXOS: version 7.0(3)I4(3) NXOS image file is: bootflash:///nxos.7.0.3.I4.3.bin Just seeking expert opinion on above mention issue. Thanks & Regards, Naser

1 0

Wifi implementators
by Mehmet Akcin 27 Jan '20

27 Jan '20

Hi there I am looking for companies who can implement wifi to a 20,000 sq ft space in Virginia (near Virginia Beach area) and offer services that are turn key including upgrades/expansion/maintenance and such. Please contact me offlist if you can provide enterprise grade turn key wifi solutions Mehmet -- Mehmet +1-424-298-1903

2 1

Rogue objects in routing databases
by Florian Brandstetter 27 Jan '20

27 Jan '20

It appears that there is currently an influx of rogue route objects created within the NTTCOM and RaDB IRR databases, in connection to Quadranet (AS8100) and China Mobile International (CMI). Examples of affected networks are: 193.30.32.0/23 45.129.92.0/23 45.129.94.0/24 Networks, which have seemingly no affiliation with Quadranet, nor China Mobile International (CMI), which merely appears to be an upstream of Quadranet and hence creates the route objects in an automated manner. Another person has already reached out to Quadranet to find out the root cause of the creation of these objects. Their support gave an ETA of 24-72 hours. The route objects are all identical: route: 193.30.32.0/23 descr: CMI (Customer Route) origin: AS8100 mnt-by: MAINT-AS58453 changed: qas_support(a)cmi.chinamobile.com 20200117 source: RADB There appears to be a correlation with the affected networks, a fair share of them is part of AS-SBAG, which in turn is part of AS-VMHAUS, which in turn is part of AS- QUADRANET and could yield the importing of these prefixes. AS-VMHAUS appears to be a customer of Quadranet, listed within AS-QUADRANET-CUSTOMER-ASSET. These networks do however have no direct connection to Quadranet, and are not affiliated with Quadranet, nor are currently connected to Quadranet, which, entirely ignoring that the `origin` points to Quadranet, makes the route object illicit. Basically this has given AS8100, whether that be legitimately Quadranet, or somebody impersonating/spinning up a rogue AS8100, theoretical control over a massive amount of prefixes, as these can be advertised without restrictions and very likely reach a fairly high percentage of global visibility. -- Florian Brandstetter President & Founder SquareFlow Network LTD.

4 5

Comcast DNS Admin
by Childs, Aaron 26 Jan '20

26 Jan '20

Good Afternoon, If theres a Comcast DNS admin on this list, could you respond off list? Thanks, Aaron Sent from my Sprint Samsung Galaxy S10.

1 0

Data on latency and loss-rates during congestion DDoS attacks
by Amir Herzberg 26 Jan '20

26 Jan '20

Dear NANOG, One of my ongoing research works is about a transport protocol that ensures (critical) communication in spite of DDoS congestion attack (which cannot be circumvented), by (careful) use of Forward Error Correction. Yes, obviously, this has to be done and used carefully since the FEC clearly increases traffic rather than the typical congestion-control approach of reducing it, I'm well aware of it; but some applications are critical (and often low-bandwidth) so such tool is important. I am looking for data on loss rate and congestion of DDoS attacks to make sure we use right parameters. Any chance you have such data and can share? Many thanks! -- Amir Herzberg Comcast chair of security innovation, University of Connecticut Foundations of cybersecurity <https://www.researchgate.net/publication/323243320_Introduction_to_Cyber-Se…>, part I (see also part II and presentations): https://www.researchgate.net/publication/323243320_Introduction_to_Cyber-Se… <https://www.researchgate.net/project/Lecture-notes-on-Introduction-to-Cyber…>

4 9

Weekly Routing Table Report
by cscora＠apnic.net 24 Jan '20

24 Jan '20

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 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 25 Jan, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 792806 Prefixes after maximum aggregation (per Origin AS): 301689 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 387892 Total ASes present in the Internet Routing Table: 66795 Prefixes per ASN: 11.87 Origin-only ASes present in the Internet Routing Table: 57383 Origin ASes announcing only one prefix: 24135 Transit ASes present in the Internet Routing Table: 9412 Transit-only ASes present in the Internet Routing Table: 291 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 34 Max AS path prepend of ASN (206156) 26 Prefixes from unregistered ASNs in the Routing Table: 1310 Number of instances of unregistered ASNs: 1310 Number of 32-bit ASNs allocated by the RIRs: 30286 Number of 32-bit ASNs visible in the Routing Table: 24906 Prefixes from 32-bit ASNs in the Routing Table: 114350 Number of bogon 32-bit ASNs visible in the Routing Table: 20 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 895 Number of addresses announced to Internet: 2852684672 Equivalent to 170 /8s, 8 /16s and 131 /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: 99.4 Total number of prefixes smaller than registry allocations: 265507 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 210634 Total APNIC prefixes after maximum aggregation: 61288 APNIC Deaggregation factor: 3.44 Prefixes being announced from the APNIC address blocks: 204262 Unique aggregates announced from the APNIC address blocks: 84939 APNIC Region origin ASes present in the Internet Routing Table: 10299 APNIC Prefixes per ASN: 19.83 APNIC Region origin ASes announcing only one prefix: 2849 APNIC Region transit ASes present in the Internet Routing Table: 1546 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5357 Number of APNIC addresses announced to Internet: 768077056 Equivalent to 45 /8s, 199 /16s and 237 /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-141625 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: 233323 Total ARIN prefixes after maximum aggregation: 107360 ARIN Deaggregation factor: 2.17 Prefixes being announced from the ARIN address blocks: 231005 Unique aggregates announced from the ARIN address blocks: 116626 ARIN Region origin ASes present in the Internet Routing Table: 18389 ARIN Prefixes per ASN: 12.56 ARIN Region origin ASes announcing only one prefix: 6760 ARIN Region transit ASes present in the Internet Routing Table: 1910 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3139 Number of ARIN addresses announced to Internet: 1078903808 Equivalent to 64 /8s, 78 /16s and 196 /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-399260 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, 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: 223883 Total RIPE prefixes after maximum aggregation: 104142 RIPE Deaggregation factor: 2.15 Prefixes being announced from the RIPE address blocks: 220672 Unique aggregates announced from the RIPE address blocks: 130268 RIPE Region origin ASes present in the Internet Routing Table: 26746 RIPE Prefixes per ASN: 8.25 RIPE Region origin ASes announcing only one prefix: 11678 RIPE Region transit ASes present in the Internet Routing Table: 3774 Average RIPE Region AS path length visible: 4.6 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 8849 Number of RIPE addresses announced to Internet: 723569792 Equivalent to 43 /8s, 32 /16s and 204 /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-210331 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: 102646 Total LACNIC prefixes after maximum aggregation: 23681 LACNIC Deaggregation factor: 4.33 Prefixes being announced from the LACNIC address blocks: 103793 Unique aggregates announced from the LACNIC address blocks: 45214 LACNIC Region origin ASes present in the Internet Routing Table: 9347 LACNIC Prefixes per ASN: 11.10 LACNIC Region origin ASes announcing only one prefix: 2376 LACNIC Region transit ASes present in the Internet Routing Table: 1764 Average LACNIC Region AS path length visible: 5.3 Max LACNIC Region AS path length visible: 31 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 6920 Number of LACNIC addresses announced to Internet: 174043648 Equivalent to 10 /8s, 95 /16s and 178 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-270748 + 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: 21009 Total AfriNIC prefixes after maximum aggregation: 4443 AfriNIC Deaggregation factor: 4.73 Prefixes being announced from the AfriNIC address blocks: 32179 Unique aggregates announced from the AfriNIC address blocks: 10047 AfriNIC Region origin ASes present in the Internet Routing Table: 1343 AfriNIC Prefixes per ASN: 23.96 AfriNIC Region origin ASes announcing only one prefix: 472 AfriNIC Region transit ASes present in the Internet Routing Table: 264 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 641 Number of AfriNIC addresses announced to Internet: 107534592 Equivalent to 6 /8s, 104 /16s and 217 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 45/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 7545 5250 642 599 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4622 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3318 1331 24 VIETEL-AS-AP Viettel Group, VN 45899 3122 1786 108 VNPT-AS-VN VNPT Corp, VN 7713 2697 813 498 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2606 9043 62 CMNET-GD Guangdong Mobile Communication 4766 2265 11101 566 KIXS-AS-KR Korea Telecom, KR 9498 2221 433 212 BBIL-AP BHARTI Airtel Ltd., IN 9829 2156 1377 246 BSNL-NIB National Internet Backbone, IN 4755 2137 441 195 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 7155 4047 280 27 VIASAT-SP-BACKBONE, US 11492 3907 259 651 CABLEONE, US 16509 3789 7730 1676 AMAZON-02, US 22773 3521 2971 152 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3364 1324 93 SHAW, CA 16625 2966 1555 2129 AKAMAI-AS, US 30036 2284 358 92 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2247 5075 532 CENTURYLINK-US-LEGACY-QWEST, US 20115 2136 2774 519 CHARTER-20115, US 18566 2059 405 103 MEGAPATH5-, 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 5846 1630 135 UNI2-AS, ES 39891 4034 219 19 ALJAWWALSTC-AS, SA 31334 3423 484 13 KABELDEUTSCHLAND-AS, DE 8551 3104 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2803 460 1942 AKAMAI-ASN1, US 12389 2420 2244 700 ROSTELECOM-AS, RU 9009 2071 223 1118 M247, GB 34984 2066 348 556 TELLCOM-AS, TR 9121 1931 1691 18 TTNET, TR 13188 1605 100 46 TRIOLAN, UA 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 6192 3295 610 Uninet S.A. de C.V., MX 10620 3352 533 470 Telmex Colombia S.A., CO 11830 2680 369 63 Instituto Costarricense de Electricidad 6503 1683 323 390 Axtel, S.A.B. de C.V., MX 7303 1480 1026 265 Telecom Argentina S.A., AR 28573 1249 2235 194 CLARO S.A., BR 13999 1168 504 285 Mega Cable, S.A. de C.V., MX 3816 1123 561 133 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1092 379 39 Telefonica del Peru S.A.A., PE 11172 953 112 68 Alestra, S. de R.L. de C.V., MX 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 24835 1059 558 23 RAYA-AS, EG 24863 1042 393 23 LINKdotNET-AS, EG 36992 1034 1535 73 ETISALAT-MISR, EG 36903 876 452 97 MT-MPLS, MA 6713 619 1863 34 IAM-AS, MA 29571 560 68 12 ORANGE-COTE-IVOIRE, CI 37342 402 32 1 MOVITEL, MZ 36935 371 522 42 Vodafone-, EG 15399 352 45 10 WANANCHI-, KE 23889 351 231 15 MauritiusTelecom, MU 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 8151 6192 3295 610 Uninet S.A. de C.V., MX 12479 5846 1630 135 UNI2-AS, ES 7545 5250 642 599 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4622 4192 73 ERX-CERNET-BKB China Education and Rese 7155 4047 280 27 VIASAT-SP-BACKBONE, US 39891 4034 219 19 ALJAWWALSTC-AS, SA 11492 3907 259 651 CABLEONE, US 16509 3789 7730 1676 AMAZON-02, US 22773 3521 2971 152 ASN-CXA-ALL-CCI-22773-RDC, US 31334 3423 484 13 KABELDEUTSCHLAND-AS, DE Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 12479 5846 5711 UNI2-AS, ES 7545 5250 4651 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4622 4549 ERX-CERNET-BKB China Education and Research Net 7155 4047 4020 VIASAT-SP-BACKBONE, US 39891 4034 4015 ALJAWWALSTC-AS, SA 31334 3423 3410 KABELDEUTSCHLAND-AS, DE 22773 3521 3369 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3318 3294 VIETEL-AS-AP Viettel Group, VN 6327 3364 3271 SHAW, CA 11492 3907 3256 CABLEONE, US Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 17076 UNALLOCATED 8.12.244.0/24 3356 LEVEL3, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 174 COGENT-174, US 62485 UNALLOCATED 8.23.229.0/24 3356 LEVEL3, US 32985 UNALLOCATED 8.28.31.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 27205 UNALLOCATED 8.38.16.0/21 6461 ZAYO-6461, US 27205 UNALLOCATED 8.38.16.0/22 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 27205 UNALLOCATED 8.38.20.0/22 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 14109 UNALLOCATED 8.38.252.0/24 3356 LEVEL3, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.136.224.0/24 Origin: 15206 UNASSIGNED Transit: 174 COGENT-174, US 23.137.192.0/24 Origin: 31798 CANAD-86-31798, CA Transit: 174 COGENT-174, US 27.100.7.0/24 Origin: 56096 UNASSIGNED Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 27.126.156.0/22 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY 27.126.156.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY 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:10 /9:11 /10:38 /11:98 /12:287 /13:580 /14:1158 /15:1919 /16:13371 /17:8171 /18:13880 /19:25797 /20:40454 /21:47564 /22:98314 /23:80812 /24:459006 /25:1336 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 4818 5846 UNI2-AS, ES 31334 3268 3423 KABELDEUTSCHLAND-AS, DE 6327 3152 3364 SHAW, CA 7155 3139 4047 VIASAT-SP-BACKBONE, US 11492 3050 3907 CABLEONE, US 39891 2946 4034 ALJAWWALSTC-AS, SA 22773 2740 3521 ASN-CXA-ALL-CCI-22773-RDC, US 8551 2564 3104 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2034 2284 MEDIACOM-ENTERPRISE-BUSINESS, US 11830 2028 2680 Instituto Costarricense de Electricidad y Telec Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1523 2:1155 3:24 4:19 5:3232 6:48 8:1375 9:1 12:1788 13:492 14:2221 15:63 16:9 17:283 18:79 20:58 23:3231 24:2621 25:4 27:2519 31:2860 32:101 35:44 36:931 37:3187 38:1827 39:314 40:134 41:3288 42:872 43:2126 44:189 45:12985 46:3624 47:275 49:1432 50:1562 51:344 52:1109 54:272 55:646 56:6 57:48 58:1887 59:1118 60:687 61:2220 62:2146 63:1911 64:5036 65:2327 66:4854 67:2844 68:1230 69:3821 70:1412 71:670 72:2779 74:2619 75:1436 76:667 77:2556 78:1987 79:2377 80:1836 81:1554 82:1203 83:1112 84:1231 85:2586 86:587 87:1692 88:1074 89:2682 90:286 91:7497 92:1452 93:2434 94:2571 95:3709 96:1011 97:337 98:961 99:965 100:84 101:1083 102:794 103:22994 104:3610 105:371 106:826 107:1869 108:698 109:3612 110:1779 111:1920 112:1545 113:1373 114:1502 115:1841 116:1796 117:2028 118:2112 119:1691 120:836 121:1032 122:2372 123:1885 124:1558 125:2019 128:1379 129:912 130:602 131:1846 132:779 133:301 134:1261 135:273 136:604 137:888 138:2193 139:993 140:596 141:878 142:860 143:1157 144:948 145:293 146:1470 147:1016 148:1901 149:1099 150:809 151:1269 152:1474 153:370 154:4661 155:926 156:3280 157:1090 158:712 159:1947 160:1717 161:992 162:3012 163:772 164:1429 165:1229 166:539 167:1469 168:3533 169:487 170:4216 171:751 172:1856 173:2365 174:1036 175:1009 176:2610 177:4127 178:2879 179:1412 180:2180 181:2348 182:2833 183:1120 184:2384 185:15962 186:3730 187:2576 188:3536 189:2075 190:8203 191:1470 192:10234 193:7304 194:5972 195:4286 196:3362 197:1768 198:6103 199:5941 200:7141 201:5100 202:10442 203:10221 204:4544 205:3075 206:3251 207:3271 208:4013 209:4367 210:4003 211:1992 212:3228 213:2966 214:1157 215:53 216:5926 217:2329 218:893 219:604 220:1981 221:920 222:1013 223:1387 End of report

1 0

Looking for topology validation
by Kévin Vermeulen 24 Jan '20

24 Jan '20

Hi NANOG, Sorry for multiple sendings. First of all, thanks to the operators that have contributed to our survey, we will acknowledge you publicly. I just resend the message one last time, hoping to get some more feedback. Our teams at Sorbonne Université and Naval Postgraduate School have developed a new Internet topology mapping tool, Diamond-Miner. Diamond-Miner[3] combines Paris Traceroute Multipath Detection Algorithm[1] and high probing rate Yarrp[2] techniques to trace the load balanced paths at Internet Scale. We are seeking now some validation of our inferences, in particular the traceroutes links that we have found. We have developed a small website for operators to provide validation: http://heartbeat.planet-lab.eu:8000 You can either publicly submit the validation on the website or send us an email to kevin.vermeulen(a)sorbonne-universite.fr . You will find all the details on the website, do not hesitate to ask if you have further questions. Thanks in advance, Kevin [1]: https://arxiv.org/pdf/1809.10070 [2]: http://rbeverly.net/research/papers/yarrp-imc16.pdf [3]: https://www.usenix.org/conference/nsdi20/accepted-papers

1 0