- Test - lists.nanog.org

SRv6
by aaron1＠gvtc.com 22 Sep '20

22 Sep '20

I have what seems to be a good SRv6 test in my lab running XRv9k 7.0.2 But I'm wondering why the sniffer doesn't show the much-spoken-of SRH (Segment Routing Header).. But rather, shows my L3VPN v4 traffic riding v6 and that's it. Let me know if I'm seeing an SRH and just don't know it, LOL. Ethernet - Type 0x86dd Ipv6 - Next Header IPIP (4) Ipv4 - icmp echo (my tests ce to ce end to end) Those layers is all it shows. I've read a lot about SRv6 with SID's inside extension headers or segment routing header, but I'm not seeing it. Any idea what this is that I'm seeing ? I've configured the PE's IAW https://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k-r6-6/se gment-routing/configuration/guide/b-segment-routing-cg-asr9000-66x/b-segment -routing-cg-asr9000-66x_chapter_011.html#id_95420 I can give you more info if you wish. Aaron aaron1(a)gvtc.com

19 61

Just got this apparently fake NANOG invoice - Looks phishy
by Chris Boyd 22 Sep '20

22 Sep '20

Apparent MS-Word doc attached. Be careful out there. Return-Path: <cb2004097(a)bristol.lu> Received: from cross6.lu-visp.net (cross6.lu-visp.net [62.182.179.184]) by lenny.gizmopartners.com (8.14.7/8.14.7) with ESMTP id 08LJIMld018071 for <cboyd(a)gizmopartners.com>; Mon, 21 Sep 2020 19:18:25 GMT Message-Id: <202009211918.08LJIMld018071(a)lenny.gizmopartners.com> Received: from [161.132.101.74] (unknown [161.132.101.74]) by cross4.lu-visp.net (Postfix) with ESMTPSA id 54FDC8808 for <cboyd(a)gizmopartners.com>; Mon, 21 Sep 2020 21:13:53 +0200 (CEST) Date: Mon, 21 Sep 2020 14:15:49 -0500 From: "NANOG" <cb2004097(a)bristol.lu> To: "Chris Boyd" <cboyd(a)gizmopartners.com> Subject: Chris Boyd MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="--308522813199332622918802174927344" X-unconfigured-debian-site-MailScanner-ID: 54FDC8808.AF049 X-unconfigured-debian-site-MailScanner: Found to be clean X-unconfigured-debian-site-MailScanner-From: cb2004097(a)bristol.lu X-Spam-Status: No ----308522813199332622918802174927344 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =0DPlease let me know WHAT ADDRESS TO SEND TO. NANOG =0D----Original Message-----=0DOn Mon, Sep 21, 2020 at 15:17 Chris Boyd <cb= oyd(a)gizmopartners.com> wrote:=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ----308522813199332622918802174927344 Content-Type: application/msword; name="INV #7565831.doc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="INV #7565831.doc" 0M8R4KGxGuEAAAAAAAAA

4 3

ARIN 46 Registration Now Open
by John Curran 22 Sep '20

22 Sep '20

NANOGers - ARIN 46 Registration is now open! Note that we will have the Public Policy consultations on 14-15 October (before NANOG) and the ARIN Member Meeting afterwards on 23 October. Please register asap for the ARIN meeting if you will be participating! Thanks! /John John Curran President and CEO American Registry for Internet Numbers Begin forwarded message: From: ARIN <info(a)arin.net<mailto:info@arin.net>> Subject: [arin-announce] ARIN 46 Registration Now Open Date: 9 September 2020 at 4:10:25 PM EDT To: <arin-announce(a)arin.net<mailto:arin-announce@arin.net>> Registration is now open for the ARIN 46 Public Policy and Members Meeting, which will be held entirely online this October. ARIN is holding this Public Policy and Members Meeting so that attendees may gather virtually to discuss draft Internet number resource policies and learn more about ARIN services and operations. Register today by visiting: https://www.arin.net/ARIN46 The ARIN 46 Public Policy and Members Meeting will be spread out over two sets of dates: 14-15 October and 23 October. Note that you only have to register once to attend any and all meeting dates! On 14-15 October, we will be conducting policy discussions and providing ARIN operational reports during the meeting sessions. Attendees will have the opportunity to join topic-based breakout sessions on a range of topics for informal conversation and networking. These breakout sessions will take place immediately following the conclusion of the meeting on 14 October. On 23 October, we will reconvene for the Members Meeting, which is open to all interested individuals. In addition to updates from the Board and Advisory Council, this session will focus on the 2020 ARIN Elections. Attendees will hear from the candidates as they answer community-sourced questions in our moderated candidate forums. Don’t forget to save the date for the ARIN 46 Newcomer Orientation and Policy Preview! All registrants will be invited to participate in an optional Newcomer Orientation and Policy Preview on 7 October. We welcome all first-time ARIN meeting attendees to come learn about ARIN and find out how to make the most of your meeting experience. Just like our last virtual meeting, ARIN 46 will be held via Zoom. We will provide the same remote participation options for ARIN 46 that we usually do for our in-person Public Policy and Members Meetings, utilizing features inside the Zoom webinar platform. The meeting will also be webcast with a live transcript for unregistered viewing. Registration is free, and all remote registrants will be listed as registered participants on the meeting website and in the archive of the meeting on the ARIN website. You must register for the meeting in order to submit comments and questions and vote in straw polls. The ARIN 46 chat in the Zoom webinar will be monitored to ensure that all participants adhere to the ARIN Participants Expected Standards of Behavior: https://www.arin.net/about/corporate/standards/ Register today at: https://www.arin.net/ARIN46 A link to access the virtual meeting will be emailed to all registered attendees in the days leading up to 14 October. For more details about remote participation and everything you’ll need to know to get ready for ARIN 46, visit: https://www.arin.net/ARIN46_remote If you have any questions, please email us at meetings(a)arin.net. Regards, American Registry for Internet Numbers (ARIN) _______________________________________________ ARIN-Announce You are receiving this message because you are subscribed to the ARIN Announce Mailing List (ARIN-announce(a)arin.net) Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-announce Please contact info(a)arin.net if you experience any issues.

1 0

BFD for routes learned trough Route-servers in IXPs
by Douglas Fischer 22 Sep '20

22 Sep '20

Time-to-time, in some IXP in the world some issue on the forwarding plane occurs. When it occurs, this topic comes back. The failures are not big enough to drop the BGP sessions between IXP participants and route-servers. But are enough to prejudice traffic between participants. And then the problem comes: "How can I check if my communication against the NextHop of the routes that I learn from the route-servers are OK? If it is not OK, how can I remove it from my FIB?" Some other possible causes of this feeling are: - ARP Resolution issues (CPU protection and lunatic Mikrotiks with 30 seconds ARP timeout is a bombastic recipe) - MAC-Address Learning limitations on the transport link of the participants can be a pain in the a..rm. So, I was searching on how to solve that and I found a draft (8th release) with the intention to solve that... https://tools.ietf.org/html/draft-ietf-idr-rs-bfd-08 If understood correctly, the effective implementation of it will depend on new code on any BGP engine that will want to do that check. It is kind of frustrating... At least 10 years after the release of RFC until the refresh os every router involved in IXPs in the world. Some questions come: A) There is anything that we can do to rush this? B) There is any other alternative to that? P.S.1: I gave up of inventing crazy BGP filter polices to test reachability of NextHop. The effectiveness of it can't even be compared to BFD, and almost kill de processing capacity of my router. P.S.2: IMHO, the biggest downside of those problems is the evasion of route-servers from some participants when issues described above occurs.

14 20

SPAM for nanog@ senders
by Łukasz Bromirski 21 Sep '20

21 Sep '20

NANOGers, Have you got email from 'dating.support(a)csvwebsupport.xn--com-to0a immediately after you post to nanog@? First time I thought it’s coincidence, but today when I got it, it’s hardly one ;) Topic is '[#WHB-257-41491]: Re: XXXXXX’ where XXXX is subject taken from last e-mail. I understand there’s need to connect people in hard, COVID times, but I doubt automated spam sender has good intentions with that regard ;) So.. somebody is scrapping this list to feed their spamming lists :/ — ./

5 6

See what's in store for NANOG 80 Virtual
by NANOG News 21 Sep '20

21 Sep '20

The NANOG Program Committee is preparing a solid program for NANOG 80, which will take place online October 19-21. Sessions will be held each day of the conference, from 12pm to 5pm EDT Monday through Wednesday, and will feature a variety of presentations, networking sessions, and BoFs on the latest technologies and industry innovation, plus a Virtual Expo, daily games + prizes, and numerous opportunities to connect with our community in real time. Explore the NANOG 80 Highlights page to learn more! View Highlights <https://www.nanog.org/meetings/nanog-80/highlights/>

1 0

Google Android phone earthquake visualization
by Sean Donelan 19 Sep '20

19 Sep '20

The VP Engineering for Android posted a visualization of the 4.5 earthquake in Southern California from data collected by Android phones. https://twitter.com/davey_burke/status/1307395583338885120 USGS ShakeAlert is transmitted via WEA to Android, iPhone and other cellular devices; and shared directly with some public-private partners. Most smart devices (Android, iPhone) collect diagnostic logs and report back to their developers, but generally emergency responders never see data from diagnostic reports. Developers don't include emergency alerts in other "smart" devices like SmartTVs, SmartSpeakers, etc.

2 2

AS16509 Peering Contact
by Paschal Masha 18 Sep '20

18 Sep '20

Hello, Any Techie from AS16509 (Amazon) in here that can help with a peering request for Denver and LA Any2 IXs that was sent to peering@amazon for days now without a response :) *Paschal Masha* Lead Network Engineer 6x7 Networks | 1 (831)325-0544 Time Zone: PST

2 1

Weekly Routing Table Report
by cscora＠apnic.net 18 Sep '20

18 Sep '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 19 Sep, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 823713 Prefixes after maximum aggregation (per Origin AS): 313888 Deaggregation factor: 2.62 Unique aggregates announced (without unneeded subnets): 396613 Total ASes present in the Internet Routing Table: 69426 Prefixes per ASN: 11.86 Origin-only ASes present in the Internet Routing Table: 59659 Origin ASes announcing only one prefix: 24758 Transit ASes present in the Internet Routing Table: 9767 Transit-only ASes present in the Internet Routing Table: 303 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 47 Max AS path prepend of ASN ( 37385) 44 Prefixes from unregistered ASNs in the Routing Table: 829 Number of instances of unregistered ASNs: 830 Number of 32-bit ASNs allocated by the RIRs: 33522 Number of 32-bit ASNs visible in the Routing Table: 27683 Prefixes from 32-bit ASNs in the Routing Table: 128618 Number of bogon 32-bit ASNs visible in the Routing Table: 14 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 446 Number of addresses announced to Internet: 2860680832 Equivalent to 170 /8s, 130 /16s and 134 /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: 99.5 Total number of prefixes smaller than registry allocations: 276420 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 216676 Total APNIC prefixes after maximum aggregation: 63566 APNIC Deaggregation factor: 3.41 Prefixes being announced from the APNIC address blocks: 210515 Unique aggregates announced from the APNIC address blocks: 86747 APNIC Region origin ASes present in the Internet Routing Table: 10861 APNIC Prefixes per ASN: 19.38 APNIC Region origin ASes announcing only one prefix: 3045 APNIC Region transit ASes present in the Internet Routing Table: 1590 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 30 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5963 Number of APNIC addresses announced to Internet: 779146752 Equivalent to 46 /8s, 112 /16s and 214 /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: 240915 Total ARIN prefixes after maximum aggregation: 111026 ARIN Deaggregation factor: 2.17 Prefixes being announced from the ARIN address blocks: 238608 Unique aggregates announced from the ARIN address blocks: 116675 ARIN Region origin ASes present in the Internet Routing Table: 18588 ARIN Prefixes per ASN: 12.84 ARIN Region origin ASes announcing only one prefix: 6797 ARIN Region transit ASes present in the Internet Routing Table: 1903 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: 3424 Number of ARIN addresses announced to Internet: 1087758336 Equivalent to 64 /8s, 213 /16s and 224 /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: 230212 Total RIPE prefixes after maximum aggregation: 108152 RIPE Deaggregation factor: 2.13 Prefixes being announced from the RIPE address blocks: 226321 Unique aggregates announced from the RIPE address blocks: 135790 RIPE Region origin ASes present in the Internet Routing Table: 27387 RIPE Prefixes per ASN: 8.26 RIPE Region origin ASes announcing only one prefix: 11818 RIPE Region transit ASes present in the Internet Routing Table: 3864 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 35 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9503 Number of RIPE addresses announced to Internet: 709162624 Equivalent to 42 /8s, 68 /16s and 246 /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-213403 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: 111579 Total LACNIC prefixes after maximum aggregation: 25699 LACNIC Deaggregation factor: 4.34 Prefixes being announced from the LACNIC address blocks: 112706 Unique aggregates announced from the LACNIC address blocks: 47619 LACNIC Region origin ASes present in the Internet Routing Table: 10487 LACNIC Prefixes per ASN: 10.75 LACNIC Region origin ASes announcing only one prefix: 2598 LACNIC Region transit ASes present in the Internet Routing Table: 1964 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 28 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8069 Number of LACNIC addresses announced to Internet: 174514432 Equivalent to 10 /8s, 102 /16s and 225 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-272796 + 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: 23501 Total AfriNIC prefixes after maximum aggregation: 4784 AfriNIC Deaggregation factor: 4.91 Prefixes being announced from the AfriNIC address blocks: 35117 Unique aggregates announced from the AfriNIC address blocks: 9412 AfriNIC Region origin ASes present in the Internet Routing Table: 1425 AfriNIC Prefixes per ASN: 24.64 AfriNIC Region origin ASes announcing only one prefix: 500 AfriNIC Region transit ASes present in the Internet Routing Table: 291 Average AfriNIC Region AS path length visible: 5.0 Max AfriNIC Region AS path length visible: 47 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 724 Number of AfriNIC addresses announced to Internet: 109672704 Equivalent to 6 /8s, 137 /16s and 121 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & 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 5662 766 675 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4762 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3534 1330 21 VIETEL-AS-AP Viettel Group, VN 45899 3228 1896 51 VNPT-AS-VN VNPT Corp, VN 7713 2718 829 613 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2536 9043 60 CMNET-GD Guangdong Mobile Communication 4766 2348 11103 553 KIXS-AS-KR Korea Telecom, KR 9498 2294 450 229 BBIL-AP BHARTI Airtel Ltd., IN 4755 2147 441 193 TATACOMM-AS TATA Communications formerl 9394 2041 4914 18 CTTNET China TieTong Telecommunications 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 11492 4614 309 637 CABLEONE, US 16509 4247 8312 1957 AMAZON-02, US 7155 4034 264 32 VIASAT-SP-BACKBONE, US 22773 3636 2984 173 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3352 1323 82 SHAW, CA 16625 3100 1653 2264 AKAMAI-AS, US 209 2488 5060 526 CENTURYLINK-US-LEGACY-QWEST, US 26484 2448 153 332 IKGUL-26484, US 30036 2435 364 223 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2311 2981 1625 FRONTIER-FRTR, 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 6110 1652 135 UNI2-AS, ES 39891 3652 203 21 ALJAWWALSTC-AS, SA 8551 3428 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 3199 2217 1029 AKAMAI-ASN1, EU 12389 2748 2275 859 ROSTELECOM-AS, RU 34984 2202 355 572 TELLCOM-AS, TR 9009 2180 232 1181 M247, GB 13188 1609 100 35 TRIOLAN, UA 61317 1339 157 595 ASDETUK http://www.heficed.com, GB 58224 1296 838 519 TCI, IR 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 7955 3339 615 Uninet S.A. de C.V., MX 10620 3386 531 509 Telmex Colombia S.A., CO 11830 2565 369 63 Instituto Costarricense de Electricidad 6503 1626 323 414 Axtel, S.A.B. de C.V., MX 7303 1470 949 289 Telecom Argentina S.A., AR 13999 1427 470 386 Mega Cable, S.A. de C.V., MX 28573 1365 2248 215 CLARO S.A., BR 3816 1144 575 155 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1121 379 39 Telefonica del Peru S.A.A., PE 11172 957 111 69 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 24863 1429 393 22 LINKdotNET-AS, EG 36992 1149 1540 75 ETISALAT-MISR, EG 24835 1106 464 28 RAYA-AS, EG 36903 918 480 94 MT-MPLS, MA 29571 695 68 12 ORANGE-COTE-IVOIRE, CI 6713 552 1863 34 IAM-AS, MA 15399 495 46 15 WANANCHI-, KE 37342 481 32 1 MOVITEL, MZ 36935 448 519 37 Vodafone-, EG 23889 345 232 16 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 7955 3339 615 Uninet S.A. de C.V., MX 12479 6110 1652 135 UNI2-AS, ES 7545 5662 766 675 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4762 4192 73 ERX-CERNET-BKB China Education and Rese 11492 4614 309 637 CABLEONE, US 16509 4247 8312 1957 AMAZON-02, US 7155 4034 264 32 VIASAT-SP-BACKBONE, US 39891 3652 203 21 ALJAWWALSTC-AS, SA 22773 3636 2984 173 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3534 1330 21 VIETEL-AS-AP Viettel Group, VN 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 6110 5975 UNI2-AS, ES 7545 5662 4987 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4762 4689 ERX-CERNET-BKB China Education and Research Net 7155 4034 4002 VIASAT-SP-BACKBONE, US 11492 4614 3977 CABLEONE, US 39891 3652 3631 ALJAWWALSTC-AS, SA 7552 3534 3513 VIETEL-AS-AP Viettel Group, VN 22773 3636 3463 ASN-CXA-ALL-CCI-22773-RDC, US 8551 3428 3383 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3352 3270 SHAW, CA 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 22357 UNALLOCATED 8.7.108.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 32985 UNALLOCATED 8.28.31.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 46766 UNALLOCATED 8.44.208.0/24 3356 LEVEL3, US 40544 UNALLOCATED 12.0.33.0/24 6461 ZAYO-6461, US 46505 UNALLOCATED 12.7.131.0/24 7018 ATT-INTERNET4, 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.142.80.0/24 Origin: 10753 LVLT-10753, US Transit: 3356 LEVEL3, US 23.157.0.0/24 Origin: 395101 UNASSIGNED Transit: 33657 CMCS, 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 No. 14, Jala 27.126.156.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala 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:9 /9:12 /10:39 /11:100 /12:286 /13:576 /14:1176 /15:1932 /16:13476 /17:8296 /18:14012 /19:25617 /20:41155 /21:49576 /22:102506 /23:85697 /24:477970 /25:1278 /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 5090 6110 UNI2-AS, ES 11492 3679 4614 CABLEONE, US 6327 3149 3352 SHAW, CA 7155 3122 4034 VIASAT-SP-BACKBONE, US 8551 2887 3428 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2814 3636 ASN-CXA-ALL-CCI-22773-RDC, US 39891 2801 3652 ALJAWWALSTC-AS, SA 8151 2776 7955 Uninet S.A. de C.V., MX 30036 2178 2435 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 1994 2311 FRONTIER-FRTR, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1631 2:1148 3:33 4:19 5:3563 6:54 8:1457 9:1 11:1 12:1771 13:344 14:2331 15:72 16:8 17:294 18:88 20:111 23:3983 24:2339 25:3 27:2337 31:2172 32:123 34:1 35:42 36:982 37:3445 38:1896 39:465 40:143 41:3690 42:638 43:2153 44:217 45:14978 46:3519 47:321 49:1516 50:1639 51:90 52:1110 54:229 55:679 56:6 57:51 58:1629 59:1167 60:785 61:2313 62:2149 63:2015 64:5263 65:2355 66:5073 67:2900 68:1171 69:4078 70:1398 71:677 72:2966 74:2569 75:1456 76:672 77:1953 78:1670 79:2624 80:2067 81:1616 82:1327 83:1258 84:1236 85:2694 86:561 87:1788 88:934 89:2819 90:386 91:7147 92:1569 93:2511 94:2801 95:3385 96:1256 97:340 98:919 99:980 100:87 101:1023 102:1094 103:24369 104:3560 105:397 106:900 107:2102 108:728 109:3761 110:1970 111:2038 112:1673 113:1441 114:1521 115:1839 116:1817 117:2094 118:2168 119:1730 120:834 121:1051 122:2545 123:2060 124:1648 125:2113 128:1384 129:1244 130:716 131:1920 132:755 133:306 134:1370 135:312 136:623 137:839 138:2297 139:1034 140:721 141:1090 142:971 143:1231 144:1158 145:367 146:1397 147:1030 148:2134 149:1184 150:769 151:1332 152:1557 153:423 154:4552 155:1223 156:3020 157:1114 158:880 159:1984 160:1988 161:1075 162:3166 163:868 164:1509 165:1323 166:591 167:1667 168:3498 169:612 170:4383 171:772 172:1988 173:2721 174:975 175:1044 176:2797 177:4832 178:2704 179:1848 180:2281 181:2537 182:3114 183:1189 184:2422 185:16944 186:3895 187:3026 188:3336 189:2684 190:8983 191:1403 192:10454 193:7691 194:6295 195:4534 196:3109 197:2047 198:6098 199:5932 200:7276 201:5247 202:10570 203:10221 204:4634 205:3104 206:3187 207:3266 208:4020 209:4528 210:4179 211:2045 212:3491 213:3250 214:1175 215:60 216:6127 217:2468 218:855 219:612 220:2067 221:911 222:988 223:1684 End of report

1 0

Re: Redhat contact
by Guillaume Tournat 18 Sep '20

18 Sep '20

Hello You may contact distributors instead, such as Arrow or TechData. Best regards >> Le 18 sept. 2020 à 17:51, Eric Litvin <eric(a)lumaoptics.net> a écrit : > > Hi, I need to get in contact with someone in the sales team at Redhat but they are not replying either to my emails or phone calls. Do you know anyone working for Redhat whom we can call? Please dm me. > > Thanks > > Eric Sent from my iPhone > >>> On Sep 18, 2020, at 7:48 AM, Wilco Baan Hofman <wilco(a)baanhofman.nl> wrote: >> >> >>> On 18/09/2020 12:07, Mark Tinka wrote: >>> >>> >>> There was a time when the use-case for MACSec was to move banks away >>> from running their own DWDM/FC networks, and letting operators do it. >> >> Well, the other use case is access networks with 802.1x. With 802.1x as >> long as the port stays up the session cookie (whatever is set as >> authenticated) is the MAC address. So once a port is authenticated, it's >> really easy to spoof a MAC and still be on the network. >> >> With WPA2 enterprise on WiFi, this problem does not exist, because then >> there is a cryptographic session. MACsec fixes that gap on wired. >> >> Not all that relevant for long-distance links though :) >> >> -- Wilco

1 0