May 2018 - Test - lists.nanog.org

BGP Hijack/Sickness with AS4637
by Alain Hebert 29 May '18

29 May '18

Hi, We're looking for a contact, *that works*, to get in touch with AS4637 (Telstra/HK) about some hijacking or router sickness. BGPmon has been reporting an hijack of AS3's subnet 18.29.238.0/23. After being contacted by AS3, we went over the advertisement with AS29909 and AS16532 to be sure. Then we tried getting in touch with AS4637 (Telstra/HK) but it went nowhere at this point. PS: If anyone has better observations that would be greatly appreciated. ----- Context: A few times this month, BGPmon reported an hijack of 18.29.238.0/23 (AS3). For this hijack I see AS4637 (Telstra/HK), AS3257( GTT) AS29909 (MOO) and AS16532 ( (which are peers I know and I'm in contact with). And I'm pretty sure AS3257 (GTT ) is in the same boat as us, as they're not the one advertising those routes to AS4637 AS16532 found it to come from AS4637 as you can see from this ColoAU LG output below ----- https://lg.coloau.com.au/ vrf-international.inet.0: 696533 destinations, 2248101 routes (696249 active, 0 holddown, 103835 hidden) + = Active Route, - = Last Active, * = Both 18.29.238.0/23 *[BGP/170] 1d 19:57:28, localpref 90, from 103.97.52.2 AS path: 4637 3257 29909 16532 16532 16532 16532 I, validation-state: unverified -- ----- Alain Hebert ahebert(a)pubnix.net PubNIX Inc. 50 boul. St-Charles P.O. Box 26770 Beaconsfield, Quebec H9W 6G7 Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443

5 4

Opinions on intent-based networking
by LF OD 29 May '18

29 May '18

Been following the articles on "intent-based" networking from Cisco and other vendors for a couple years now, and I have a basic grasp of the concept of "define your goals/outcomes and automation will make it so", but I do not know the practical applications of it or how you are supposed to convey your "intent". However, $dayjob is a medium-sized enterprise and looking at a potential refresh in the upcoming budget. So... do any of you at ISPs, Cloud Providers, or Enterprises have any hands-on experience with "intent-based" networking products? If so, could you please provide some info on what caused you to look at it, who did you look at, why did you choose whoever you chose, and is it working out for you? If you looked at it very closely and decided not to bother with it, I'd also be interested on your take. At $dayjob we have been adopting automation at the application and workload level, but there hasn't been much need for it at the infrastructure level. However, if we can improve the services we offer while refreshing that infrastructure, it wouldn't hurt - depending on cost of course. Thanks in advance. LF0D

4 3

Re: Impacts of Encryption Everywhere (any solution?)
by Scott Weeks 29 May '18

29 May '18

I believe you were responding to me, but it was really hard to tell. If so, here's the conversation... > Also, please don't just look at continental countries > when researching. Look at the small PICs (Pacific > Island Countries). For example, search the posts from > Christian on Kiribati on the PICISOC list. The cost is > extraordinary and all the ego-flattering bloat rsk > speaks (relevant part of the post id below) of in very > expensive to download and is nearly impossible to stop. --- ben(a)6by7.net wrote: From: Ben Cannon <ben(a)6by7.net> Then Africa in particular is specifically disadvantaged - I spent a good deal of time in Haiti and 4G connectivity was abundant at good speeds, as were terrestrial fiber connections. Mirrors my experience in half a dozen other 3rd world countries. Unless there’s something particularly oppressive about Africa? -------------------------------------- I guess I was more meaning in the Pacific, since I'm from there. And more particularly places like Kiribati, Cook Islands, Marquesas and other far flung Pacific Island Countries. My apologies for the confusion. Hati and other countries close to a rich mainland country do not suffer the same issues due to geography. scott ps. lately the SW Pacific countries (Vanuatu, Solomons, etc) are getting it together on circuits to main islands in the group from help by NZ, AUS and the Asian Development Bank.

2 1

Whois vs GDPR, latest news
by Brian Kantor 28 May '18

28 May '18

A draft of the new ICANN Whois policy was published a few days ago. https://www.icann.org/en/system/files/files/proposed-gtld-registration-data… >From that document: "This Temporary Specification for gTLD Registration Data (Temporary Specification) establishes temporary requirements to allow ICANN and gTLD registry operators and registrars to continue to comply with existing ICANN contractual requirements and community-developed policies in light of the GDPR. Consistent with ICANN’s stated objective to comply with the GDPR, while maintaining the existing WHOIS system to the greatest extent possible, the Temporary Specification maintains robust collection of Registration Data (including Registrant, Administrative, and Technical contact information), but restricts most Personal Data to layered/tiered access. Users with a legitimate and proportionate purpose for accessing the non-public Personal Data will be able to request such access through Registrars and Registry Operators. Users will also maintain the ability to contact the Registrant or Administrative and Technical contacts through an anonymized email or web form. The Temporary Specification shall be implemented where required by the GDPR, while providing flexibility to Registry Operators and Registrars to choose to apply the requirements on a global basis based on implementation, commercial reasonableness and fairness considerations. The Temporary Specification applies to all registrations, without requiring Registrars to differentiate between registrations of legal and natural persons. It also covers data processing arrangements between and among ICANN, Registry Operators, Registrars, and Data Escrow Agents as necessary for compliance with the GDPR."

30 56

Re: Whois vs GDPR, latest news
by Anne P. Mitchell Esq. 26 May '18

26 May '18

> On May 23, 2018, at 7:18 PM, K. Scott Helms <kscott.helms(a)gmail.com> wrote: > > Anything that can tie back to an individual data subject is PII, that means email addresses, names in combination with addresses or phone numbers, finger prints, or even insufficiently abstracted internal ID numbers/codes. Don't forget IP addresses, as part of the wonderfully vague "online identifiers". > Notice I didn't say EU citizen there, that's because the law and regulations (GDPR consists of both) intentionally cover any natural person in any of the 28 EU nations including the citizens of non-EU nations. > I don't go as far as I think Anne was suggesting, in that someone in EU airspace who sent an email or made a purchase is now suddenly an EU data subject. You may accuse me of being a lawyer here (and rightly so :-) ), but "in", as in "in the Union" (which is the actual language) is very much open to interpretation. In a judicial system where lawsuits have turned on - I kid you not - the interpretation of what a comma meant, I can almost guarantee you that "in the Union" is going to get interpreted through lawsuits, and it is absolutely not outside the realm of possibility that a U.S. citizen visiting in the EU will bring a lawsuit based on something happening with their PII while they were "in the Union". > Any company that is covered by the GDPR must be extremely careful that any company they do business with is also compliant if that company will have access or act as a data processor. That means that if you are a US company that has US only customers, but some of your customers have employees that are US citizens but who live in an EU nation then they are bound to only use providers that are GDPR compliant. Now, this will result in contractual disputes and/or loss of business rather than having EU regulators fine your company directly. The end result is that many many many companies that don't sell or market to the EU are finding themselves needing to comply in the same way that companies that sell services to medical companies often have to follow HIPAA (and be audited) even though they provide medical services themselves. > Actually, GDPR specifically requires processors to include statements of compliance right in their contracts; we also strongly recommend that controllers insist on indemnification clauses in their contracts with processors, because if the processor screws up and there is a breach, the _controller_ can also be held liable, and the financial penalties in GDPR are very stiff. Anne Anne P. Mitchell, Attorney at Law CEO/President, SuretyMail Email Reputation Certification and Inbox Delivery Assistance GDPR Compliance Consultant GDPR Compliance Certification http://www.SuretyMail.com/ http://www.SuretyMail.eu/ Attorney at Law / Legislative Consultant Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal anti-spam law) Author: The Email Deliverability Handbook Legal Counsel: The CyberGreen Institute Legal Counsel: The Earth Law Center Member, California Bar Cyberspace Law Committee Member, Colorado Cybersecurity Consortium Member, Board of Directors, Asilomar Microcomputer Workshop Member, Advisory Board, Cause for Awareness Member, Elevations Credit Union Member Council Former Chair, Asilomar Microcomputer Workshop Ret. Professor of Law, Lincoln Law School of San Jose Available for consultations by special arrangement. amitchell(a)isipp.com | @AnnePMitchell Facebook/AnnePMitchell | LinkedIn/in/annemitchell

14 28

IP Reputation
by Mike Hammett 25 May '18

25 May '18

I would like to call on organizations that provide IP reputation information to have methods available for network operators to determine if they are on their lists, what their reputation is, what it means, optionally evidence, and a means of removal of negative information. Near real-time notice of changes in your status would be recommended as well. If those wants sound ridiculous, nearly that same list of wants is provided by e-mail SPAM DNSRBL maintainers so it isn't exactly unprecedented. I recently interacted with an organization that provides IP reputation information as a component in a larger security offering. A particular eyeball network couldn't get to a number of large web destinations. After some prodding of the company providing the security offering, it was determined that the prefix in question was because on a scale of 0 to 10 with 0 being the best and 10 being the worst, that prefix had a score of 1. They claimed they could do nothing about it as their client (the web site being visited) had that in their control. That's a half-truth. The company providing that IP reputation put them on the list (for whatever reason), while the web site chose whatever metrics to block. Their proposed solution was to contact every web site there were issues with and request that they fix it. Okay, so an eyeball is supposed to reach out to dozens of major brands and get someone that understands the situation and can resolve it in a reasonable time frame? Most of these brands take days to address core things dealing with their core product or service, much less getting someone in IT to whitelist a prefix. I'm sorry, that's not a realistic solution. If not a proactive alert (like a SPAM feedback loop), they need an easy form to fill out and after some automated means of verification (ASN or IP whois contact lookup), spill the beans on who, what, where, why, and how to get it fixed. I'm not saying there was no valid reason to put them on the list. There's no easy way to determine that they're on the list, why, and any means of getting removed from the list when the problem is fixed. ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP

3 2

Weekly Routing Table Report
by cscora＠apnic.net 25 May '18

25 May '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 26 May, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 701902 Prefixes after maximum aggregation (per Origin AS): 269651 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 337566 Total ASes present in the Internet Routing Table: 60835 Prefixes per ASN: 11.54 Origin-only ASes present in the Internet Routing Table: 52547 Origin ASes announcing only one prefix: 22946 Transit ASes present in the Internet Routing Table: 8288 Transit-only ASes present in the Internet Routing Table: 271 Average AS path length visible in the Internet Routing Table: 4.0 Max AS path length visible: 30 Max AS path prepend of ASN ( 30873) 28 Prefixes from unregistered ASNs in the Routing Table: 48 Number of instances of unregistered ASNs: 48 Number of 32-bit ASNs allocated by the RIRs: 22716 Number of 32-bit ASNs visible in the Routing Table: 18310 Prefixes from 32-bit ASNs in the Routing Table: 76393 Number of bogon 32-bit ASNs visible in the Routing Table: 15 Special use prefixes present in the Routing Table: 2 Prefixes being announced from unallocated address space: 276 Number of addresses announced to Internet: 2860355907 Equivalent to 170 /8s, 125 /16s and 145 /24s Percentage of available address space announced: 77.3 Percentage of allocated address space announced: 77.3 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.9 Total number of prefixes smaller than registry allocations: 234647 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 191524 Total APNIC prefixes after maximum aggregation: 54361 APNIC Deaggregation factor: 3.52 Prefixes being announced from the APNIC address blocks: 190353 Unique aggregates announced from the APNIC address blocks: 77978 APNIC Region origin ASes present in the Internet Routing Table: 8831 APNIC Prefixes per ASN: 21.56 APNIC Region origin ASes announcing only one prefix: 2475 APNIC Region transit ASes present in the Internet Routing Table: 1317 Average APNIC Region AS path length visible: 4.0 Max APNIC Region AS path length visible: 22 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3802 Number of APNIC addresses announced to Internet: 766494466 Equivalent to 45 /8s, 175 /16s and 199 /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: 208837 Total ARIN prefixes after maximum aggregation: 99153 ARIN Deaggregation factor: 2.11 Prefixes being announced from the ARIN address blocks: 209554 Unique aggregates announced from the ARIN address blocks: 99034 ARIN Region origin ASes present in the Internet Routing Table: 18185 ARIN Prefixes per ASN: 11.52 ARIN Region origin ASes announcing only one prefix: 6713 ARIN Region transit ASes present in the Internet Routing Table: 1798 Average ARIN Region AS path length visible: 3.6 Max ARIN Region AS path length visible: 20 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2353 Number of ARIN addresses announced to Internet: 1106418720 Equivalent to 65 /8s, 242 /16s and 156 /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: 191947 Total RIPE prefixes after maximum aggregation: 92215 RIPE Deaggregation factor: 2.08 Prefixes being announced from the RIPE address blocks: 187983 Unique aggregates announced from the RIPE address blocks: 111588 RIPE Region origin ASes present in the Internet Routing Table: 25207 RIPE Prefixes per ASN: 7.46 RIPE Region origin ASes announcing only one prefix: 11384 RIPE Region transit ASes present in the Internet Routing Table: 3515 Average RIPE Region AS path length visible: 4.1 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 7023 Number of RIPE addresses announced to Internet: 715946112 Equivalent to 42 /8s, 172 /16s and 120 /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: 90883 Total LACNIC prefixes after maximum aggregation: 19907 LACNIC Deaggregation factor: 4.57 Prefixes being announced from the LACNIC address blocks: 92294 Unique aggregates announced from the LACNIC address blocks: 41069 LACNIC Region origin ASes present in the Internet Routing Table: 7170 LACNIC Prefixes per ASN: 12.87 LACNIC Region origin ASes announcing only one prefix: 1993 LACNIC Region transit ASes present in the Internet Routing Table: 1324 Average LACNIC Region AS path length visible: 4.7 Max LACNIC Region AS path length visible: 26 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4711 Number of LACNIC addresses announced to Internet: 172631712 Equivalent to 10 /8s, 74 /16s and 38 /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: 18661 Total AfriNIC prefixes after maximum aggregation: 3971 AfriNIC Deaggregation factor: 4.70 Prefixes being announced from the AfriNIC address blocks: 21442 Unique aggregates announced from the AfriNIC address blocks: 7656 AfriNIC Region origin ASes present in the Internet Routing Table: 1143 AfriNIC Prefixes per ASN: 18.76 AfriNIC Region origin ASes announcing only one prefix: 380 AfriNIC Region transit ASes present in the Internet Routing Table: 233 Average AfriNIC Region AS path length visible: 4.4 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 421 Number of AfriNIC addresses announced to Internet: 98415872 Equivalent to 5 /8s, 221 /16s and 181 /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 5404 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4406 419 433 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2908 11137 790 KIXS-AS-KR Korea Telecom, KR 7552 2871 1154 73 VIETEL-AS-AP Viettel Group, VN 9829 2812 1498 543 BSNL-NIB National Internet Backbone, IN 9394 2544 4923 26 CTTNET China TieTong Telecommunications 45899 2491 1574 160 VNPT-AS-VN VNPT Corp, VN 17974 2219 928 79 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9808 2203 8699 26 CMNET-GD Guangdong Mobile Communication 4755 2104 417 206 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 3431 1324 85 SHAW - Shaw Communications Inc., CA 22773 3299 2968 147 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 11492 2183 245 410 CABLEONE - CABLE ONE, INC., US 18566 2172 405 109 MEGAPATH5-US - MegaPath Corporation, US 16509 2124 4705 668 AMAZON-02 - Amazon.com, Inc., US 20115 2106 2530 456 CHARTER-NET-HKY-NC - Charter Communicat 30036 1989 342 157 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 1986 5070 607 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 16625 1838 908 1313 AKAMAI-AS - Akamai Technologies, Inc., 7018 1723 20216 1264 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 4206 1518 532 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 8551 2869 377 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2626 687 1925 AKAMAI-ASN1, US 12389 2068 1877 707 ROSTELECOM-AS, RU 34984 2010 334 491 TELLCOM-AS, TR 9121 1889 1692 19 TTNET, TR 13188 1609 100 43 TRIOLAN, UA 6849 1241 355 21 UKRTELNET, UA 8402 1240 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 4895 3350 592 Uninet S.A. de C.V., MX 10620 3602 542 236 Telmex Colombia S.A., CO 11830 2649 369 77 Instituto Costarricense de Electricidad 6503 1616 438 58 Axtel, S.A.B. de C.V., MX 7303 1517 1026 191 Telecom Argentina S.A., AR 28573 1031 2253 173 CLARO S.A., BR 3816 1009 505 124 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 989 377 31 Telefonica del Peru S.A.A., PE 11172 926 126 85 Alestra, S. de R.L. de C.V., MX 18881 911 1078 30 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 1069 396 45 LINKdotNET-AS, EG 37611 854 107 9 Afrihost, ZA 36903 739 371 140 MT-MPLS, MA 36992 705 1412 43 ETISALAT-MISR, EG 8452 688 1730 17 TE-AS TE-AS, EG 24835 566 786 17 RAYA-AS, EG 37492 465 470 57 ORANGE-, TN 29571 441 68 10 ORANGE-COTE-IVOIRE, CI 37342 378 32 1 MOVITEL, MZ 15399 367 35 7 WANANCHI-, KE 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 5404 4192 74 ERX-CERNET-BKB China Education and Rese 8151 4895 3350 592 Uninet S.A. de C.V., MX 7545 4406 419 433 TPG-INTERNET-AP TPG Telecom Limited, AU 12479 4206 1518 532 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 10620 3602 542 236 Telmex Colombia S.A., CO 6327 3431 1324 85 SHAW - Shaw Communications Inc., CA 22773 3299 2968 147 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 4766 2908 11137 790 KIXS-AS-KR Korea Telecom, KR 7552 2871 1154 73 VIETEL-AS-AP Viettel Group, VN 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 4895 4303 Uninet S.A. de C.V., MX 7545 4406 3973 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 3758 ALJAWWALSTC-AS, SA 12479 4206 3674 UNI2-AS, ES 10620 3602 3366 Telmex Colombia S.A., CO 6327 3431 3346 SHAW - Shaw Communications Inc., CA 22773 3299 3152 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8551 2869 2826 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 7552 2871 2798 VIETEL-AS-AP Viettel Group, VN 11830 2649 2572 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 64514 PRIVATE 5.42.231.0/24 35753 ITC ITC AS number, SA 230105 UNALLOCATED 38.110.79.0/24 23015 CMC180-TOR-AS - Cambridge Merc 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 64111 UNALLOCATED 98.159.5.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64111 UNALLOCATED 98.159.7.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64121 UNALLOCATED 98.159.9.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64121 UNALLOCATED 98.159.12.0/24 19555 KMI-NETWORK - Kinder Morgan, I 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 198.18.1.19/32 7497 CSTNET-AS-AP Computer Network Information Cente 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 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 41.76.143.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:290 /13:566 /14:1093 /15:1904 /16:13375 /17:7900 /18:13645 /19:25191 /20:39380 /21:45456 /22:87378 /23:70654 /24:392642 /25:847 /26:644 /27:644 /28:36 /29:20 /30:18 /31:4 /32:53 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3218 3431 SHAW - Shaw Communications Inc., CA 12479 2990 4206 UNI2-AS, ES 39891 2946 3778 ALJAWWALSTC-AS, SA 22773 2554 3299 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8551 2331 2869 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 18566 2065 2172 MEGAPATH5-US - MegaPath Corporation, US 11830 1997 2649 Instituto Costarricense de Electricidad y Telec 11492 1926 2183 CABLEONE - CABLE ONE, INC., US 30036 1740 1989 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1613 3602 Telmex Colombia S.A., CO Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1588 2:849 4:19 5:2810 6:65 7:1 8:1126 12:1861 13:189 14:1743 15:28 16:3 17:206 18:66 20:49 21:6 23:2658 24:2227 25:2 27:2349 31:1982 32:90 35:27 36:509 37:2752 38:1466 39:262 40:121 41:3187 42:588 43:1923 44:119 45:4613 46:3049 47:199 49:1322 50:1055 51:314 52:1041 54:369 55:3 56:12 57:41 58:1603 59:994 60:432 61:2162 62:1831 63:1800 64:5036 65:2220 66:4707 67:2439 68:1162 69:3199 70:1143 71:566 72:2112 74:2734 75:414 76:453 77:1542 78:1704 79:1837 80:1505 81:1394 82:1073 83:783 84:1043 85:2048 86:578 87:1333 88:930 89:2356 90:212 91:6367 92:1200 93:2365 94:2393 95:2818 96:721 97:357 98:947 99:133 100:81 101:1282 102:60 103:17764 104:3632 105:246 106:618 107:1891 108:699 109:3481 110:1628 111:1778 112:1266 113:1258 114:1120 115:1643 116:1649 117:1730 118:2156 119:1647 120:980 121:1051 122:2440 123:1801 124:1433 125:1902 128:1021 129:649 130:453 131:1587 132:660 133:195 134:1025 135:224 136:474 137:547 138:1969 139:597 140:407 141:706 142:818 143:993 144:802 145:465 146:1190 147:717 148:1635 149:733 150:728 151:1059 152:781 153:312 154:1100 155:760 156:963 157:790 158:650 159:1741 160:945 161:764 162:2586 163:564 164:1052 165:1603 166:455 167:1406 168:3078 169:805 170:3711 171:436 172:1065 173:1985 174:906 175:774 176:1891 177:4043 178:2454 179:1209 180:2213 181:2232 182:2361 183:1166 184:1029 185:13559 186:3559 187:2376 188:2832 189:2047 190:8120 191:1437 192:9842 193:5958 194:4789 195:3974 196:2555 197:1493 198:5522 199:5920 200:7377 201:5017 202:10456 203:10217 204:4571 205:2902 206:3106 207:3197 208:4006 209:3952 210:4042 211:2112 212:3043 213:2735 214:970 215:61 216:5960 217:2127 218:908 219:613 220:1760 221:986 222:1027 223:1259 End of report

1 0

Re: SD-WAN Solutions
by Sabina M. 25 May '18

25 May '18

Thanks everyone for replying! As for why I'm asking, working today together with a $customer in order to figure out integration with other VXLAN environments, and extending the control plane past just the nuage solution. There's plenty of customers that use either basic VXLAN (think Cisco N9k with barebone VXLAN EVPN, not ACI), Juniper Contrail and others. The "rumors" that I heard regarding the nuage solution is that so far, Nokia/Alcatel hasn't implemented the RFC for EVPN to the letter and that there there's quite a bit of custom stuff in there (from sym/asym routing methods) to signaling and all. My question boils down to when/how will nuage implement interoperability with other vendors at VXLAN level? In the SP market we've had it for years where you can have MPLS on a variety of boxes and the network wouldn't suffer from this. It seems with VXLAN it's less cooperative (and I understand there's more to it now than just the protocol and it's more a fabric approach) Also, can you maybe tell me/us more about these extensions? ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On May 24, 2018 11:40 PM, Alastair Johnson <aj(a)sneep.net> wrote: > > > On 5/24/18 5:43 AM, Sabina M. wrote: > > > Has anyone worked with Nuage from around here? Additionally, is anyone familiar with what RFC Alcatel/Nokia is implementing for the VXLAN part of the solution? It looks a bit non-standard but I can't find any clear documentation regarding this anywhere > > > > Cheers, > > > > S. > > Hi Sabina, > > I work for Nuage Networks. What can I help you with? Happy to discuss > > our architecture, but may I know why you are asking? > > VxLAN is just the datapath. Control plane is based on EVPN and is > > standards-based for our DC overlay platform, but the SD-WAN product uses > > a number of extensions. > > Regards, > > AJ > > aj(a)nuagenetworks.net

1 0

Re: Whois vs GDPR, latest news
by John Levine 25 May '18

25 May '18

> No, but in the absence of a law that specifically bars the courts from > doing so the will under current reciprocal treaty arrangements. No, really, what treaties? I understand treaties about domesticating a tort judgement but this isn't a tort, this is a regulation. R's, John PS: >> can treaties supercede US law? That question has a very complicated answer. tl;dr: sometimes

3 3

VPP-based router
by Ross Tajvar 25 May '18

25 May '18

Hi all, Has anyone had any luck building their own routers on common compute (x86) with VPP? I'm considering it as I'm looking for a cheap, fast peering router. I haven't seen much written about that type of solution so I was wondering if anyone here has experience to share. Thanks, Ross

1 0