- Test - lists.nanog.org

RE: Routed optical networks
by Vasilenko Eduard 05 May '23

05 May '23

> Yeah, you sound like an equipment vendor whose main customers are incumbent telco's in a few rich markets :-). You are right. My message was pretty much geared toward incumbents. But the majority of the access/aggregation is in their possessions, isn’t it? They typically have ducts that were huge for copper that is already extracted. One more fiber cable would be easy. Agree that for competitive carriers DWDM would be more often needed. Even for competitive carriers, it makes sense to evaluate the cost to put fiber into the duct of incumbents. Especially because in some countries the price would be regulated. It would solve the problem forever – no need for the DWDM speed upgrade. I am calling to just not forget to evaluate this option too. Reminder: dark fiber is the best technical solution, for sure. Ed/ From: Mark Tinka [mailto:mark@tinka.africa] Sent: Wednesday, May 3, 2023 11:39 AM To: Vasilenko Eduard <vasilenko.eduard(a)huawei.com>; nanog(a)nanog.org Subject: Re: Routed optical networks On 5/3/23 08:20, Vasilenko Eduard wrote: I would risk to say a little more on this. Indeed, maybe the situation (in many countries) when the Carrier sells a lot of TDM services. But in general, packet services are enough these days for many carriers/regions. There aren't enough TDM services to warrant DWDM, nowadays. The reason for DWDM is mainly being driven by Ethernet, and IP. At any reasonable scale, it's actually pretty hard to buy a TDM service, in most markets. Additionally, I am sure that in many countries/Metro it is cheaper to lay down a new fiber than to provision DWDM, even if it is a pizza box. I disagree. Existing fibre may be cheap because it was laid down a decade or more ago, en masse, by several operators. So the market would be experiencing a glut, not because it is cheap to open up the roads and plant more fibre, but because there is so much of it to begin with. At worst, there is still enough duct space that the operator can blow more fibre. But when that duct gets full, and there are no more free ducts available, or another route needs to get built for whatever reason, it is a rather costly affair to open up the roads and trunk some fibre, in any market. So no, DWDM is not more expensive, if you are delivering services at scale. It is actually cheaper. It is only more expensive if you are small scale, because in some markets, the fibre glut means you can buy dark fibre for cheaper than you can light it with DWDM. But this is a situation unique to small operators, not large ones. The colored interface is still very expensive. This only matters for the line side. For client-facing, it's not a drama. And you typically buy more optics for the client side than you do the line side. Of course, there are some Cities (not “towns”) where it is very expensive or maybe even impossible to lay down a new fiber. Yes, in the majority of cases, it is cheaper to lay down fiber. I think what you mean to say is that in the majority of cases where there is fibre glut, and dark fibre is a market option, buying fibre is cheaper than lighting it with DWDM. This is true. But I think that on a global scale, this is the exception, not the rule. In general, you are not likely to be able to buy dark fibre, cheaply or otherwise, if you look at all markets in the world. Hence, the importance of DWDM for the Metro is overestimated. Again, only if you are small scale. If you are a large scale operator with as many IP/Ethernet customers as you have Transport, DWDM is essential. Use only routers. Provision enough fiber. Have always 1 router hop to the aggregation (hub-spoke topology), no routers chaining in the ring. If fiber is not enough – then use normal DWDM with an external transponder. Routers would be still in hub-spoke topology. Yeah, you sound like an equipment vendor whose main customers are incumbent telco's in a few rich markets :-). The life of the average operator, around the world, is far less glamorous. Mark.

3 4

RE: Routed optical networks
by Vasilenko Eduard 05 May '23

05 May '23

Hi Mark, Thanks a lot for many of your valuable comments I almost always agree. 1. I agree that 50GE has not got the same popularity as 100GE. Many vendors did ignore it for some time. Looks like not many ignore it now. 2. Even in your example for 40km, 100GE is about twice more expensive than 50GE. 3. Hence, I have to google for the cheaper proposition in 10km. For obvious reasons, I could not reference my employer (my assumption about the cost is based on this comparison). https://opticswave.com/collections/50g-qsfp28 https://www.compufox.com/50G_QSFP28_Transceivers_s/3036.htm https://www.genuinemodules.com/033030600050 Looks like I have found twice cheaper in public information. 4. Pay attention that bidirectional is available too. 5. The public price is not what you get in the real tender. We are talking about big networks, hence, big tenders. Eduard From: Mark Tinka [mailto:mark@tinka.africa] Sent: Friday, May 5, 2023 1:17 PM To: Vasilenko Eduard <vasilenko.eduard(a)huawei.com>; nanog(a)nanog.org Subject: Re: Routed optical networks On 5/5/23 10:54, Vasilenko Eduard wrote: 50GE is better just because it is half of the cost of 100GE and it is enough now for the great majority of cases. Money is very important these days for this industry. 100GE single mode is more expensive than the best router port itself. Routers have been deprecated 10x for the decade (almost 100x for 2 decades). Pluggable optics is not that much deprecated. Not sure where your pricing is coming from, but if I look at Flexoptix's 50Gbps QSFP28 optics pricing, I am getting: * EUR724 @ 10km. * EUR1,246 @ 40km. They are also selling an SFP56 LR for EUR925. Juxtapose that against 100Gbps pricing: * EUR473 @ 10km. * EUR1,300 @ 25km. * EUR1,500 @ 30km. * EUR2,600 @ 40km. * EUR3,925 @ 80km. Doesn't immediately seem to me that 50Gbps is cheaper than 100Gbps. There also don't seem to be as many deployments of 50Gbps in the metro (same could be said for 25Gbps and 40Gbps), but others on the list can chime in with what they are seeing/doing. I do not think that content provider guys call their DCI “Metro”, not very often. Well, whatever they call it, the concept is the same - move lots of traffic across town between data centres. I agree that 100GE for DCI is the minimum, 400GE is probably already needed in some places. IMHO: it is a different story. Very interested too. Most content providers have no choice but to run DWDM, for even very short spans between data centres. That is because it is just cheaper and simpler to pack Tbps of capacity in DWDM for the price than you can in a router. And besides, most routers don't need to carry Tbps of traffic in a single line card, which would be a waste of a fibre pair over that distance. In such cases, better to use DWDM and drop capacity on individual routers and/or line cards as you see fit. PS: By the way, even if some ISP has 50% of revenue from Enterprise services (it is probably the biggest number, typically 30%-40%), it is still just 5% compare to residential traffic. Traffic to enterprises is still sold 4x-10x (depending on the country). That is why residential Access networks tend to be 2nd class citizens :-). Hence, Enterprise does not make sense to mention in the traffic discussion. It is a “rounding error”. Enterprise business created a huge demand for oversubscribed ports to connect Enterprises. And QoS/QoE. Not traffic. Well, not all operators that offer enterprise services also do consumer broadband, or vice versa. To a network doing only one or the other, whatever traffic they are carrying means the world to them. It's not ours to decide what is high or low traffic... that priviledge always remains with the network operator. Mark.

2 1

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 05 May '23

05 May '23

This is an automated weekly mailing describing the state of the Global IPv4 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 https://thyme.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. IPv4 Routing Table Report 04:00 +10GMT Sat 06 May, 2023 BGP Table (Global) as seen in Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 921175 Prefixes after maximum aggregation (per Origin AS): 349130 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 448298 Total ASes present in the Internet Routing Table: 74403 Prefixes per ASN: 12.38 Origin-only ASes present in the Internet Routing Table: 63835 Origin ASes announcing only one prefix: 26244 Transit ASes present in the Internet Routing Table: 10568 Transit-only ASes present in the Internet Routing Table: 439 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 127 Max AS path prepend of ASN (150261) 120 Prefixes from unregistered ASNs in the Routing Table: 1077 Number of instances of unregistered ASNs: 1077 Number of 32-bit ASNs allocated by the RIRs: 41797 Number of 32-bit ASNs visible in the Routing Table: 34561 Prefixes from 32-bit ASNs in the Routing Table: 170988 Number of bogon 32-bit ASNs visible in the Routing Table: 13 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 621 Number of addresses announced to Internet: 3059771008 Equivalent to 182 /8s, 96 /16s and 102 /24s Percentage of available address space announced: 82.6 Percentage of allocated address space announced: 82.6 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 307475 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 243936 Total APNIC prefixes after maximum aggregation: 69409 APNIC Deaggregation factor: 3.51 Prefixes being announced from the APNIC address blocks: 238075 Unique aggregates announced from the APNIC address blocks: 97934 APNIC Region origin ASes present in the Internet Routing Table: 13424 APNIC Prefixes per ASN: 17.74 APNIC Region origin ASes announcing only one prefix: 3961 APNIC Region transit ASes present in the Internet Routing Table: 1801 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 127 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8728 Number of APNIC addresses announced to Internet: 773529088 Equivalent to 46 /8s, 27 /16s and 30 /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-151865 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: 269600 Total ARIN prefixes after maximum aggregation: 122444 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 272217 Unique aggregates announced from the ARIN address blocks: 130042 ARIN Region origin ASes present in the Internet Routing Table: 19092 ARIN Prefixes per ASN: 14.26 ARIN Region origin ASes announcing only one prefix: 6968 ARIN Region transit ASes present in the Internet Routing Table: 1954 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4794 Number of ARIN addresses announced to Internet: 1283932416 Equivalent to 76 /8s, 135 /16s and 65 /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-401308 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: 259442 Total RIPE prefixes after maximum aggregation: 122186 RIPE Deaggregation factor: 2.12 Prefixes being announced from the RIPE address blocks: 255549 Unique aggregates announced from the RIPE address blocks: 158227 RIPE Region origin ASes present in the Internet Routing Table: 28334 RIPE Prefixes per ASN: 9.02 RIPE Region origin ASes announcing only one prefix: 12072 RIPE Region transit ASes present in the Internet Routing Table: 3964 Average RIPE Region AS path length visible: 4.2 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11174 Number of RIPE addresses announced to Internet: 718147200 Equivalent to 42 /8s, 206 /16s and 14 /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: 117998 Total LACNIC prefixes after maximum aggregation: 28501 LACNIC Deaggregation factor: 4.14 Prefixes being announced from the LACNIC address blocks: 117269 Unique aggregates announced from the LACNIC address blocks: 49386 LACNIC Region origin ASes present in the Internet Routing Table: 10991 LACNIC Prefixes per ASN: 10.67 LACNIC Region origin ASes announcing only one prefix: 2637 LACNIC Region transit ASes present in the Internet Routing Table: 2305 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8784 Number of LACNIC addresses announced to Internet: 176697088 Equivalent to 10 /8s, 136 /16s and 47 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-273820 + 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: 29122 Total AfriNIC prefixes after maximum aggregation: 5811 AfriNIC Deaggregation factor: 5.01 Prefixes being announced from the AfriNIC address blocks: 37444 Unique aggregates announced from the AfriNIC address blocks: 12195 AfriNIC Region origin ASes present in the Internet Routing Table: 1732 AfriNIC Prefixes per ASN: 21.62 AfriNIC Region origin ASes announcing only one prefix: 606 AfriNIC Region transit ASes present in the Internet Routing Table: 335 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 30 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1081 Number of AfriNIC addresses announced to Internet: 107053312 Equivalent to 6 /8s, 97 /16s and 129 /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 9808 9486 8706 40 CHINAMOBILE-CN China Mobile Communicati 7545 5726 787 694 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4863 4192 75 ERX-CERNET-BKB China Education and Rese 45899 4053 1877 47 VNPT-AS-VN VNPT Corp, VN 7713 3548 1043 65 TELKOMNET-AS-AP PT Telekomunikasi Indon 7552 3227 1331 21 VIETEL-AS-AP Viettel Group, VN 9498 2949 490 235 BBIL-AP BHARTI Airtel Ltd., IN 4766 2551 11251 591 KIXS-AS-KR Korea Telecom, KR 24560 2385 836 446 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 45090 2184 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute Complete listing at https://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 8289 10784 2931 AMAZON-02, US 11492 4533 300 610 CABLEONE, US 7155 3975 281 51 VIASAT-SP-BACKBONE, US 22773 3587 3057 283 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3525 1320 64 SHAW, CA 16625 3121 1581 2362 AKAMAI-AS, US 749 3101 54980 2353 DNIC-AS-00749, US 396982 2637 3591 368 GOOGLE-CLOUD-PLATFORM, US 7018 2515 24151 1580 ATT-INTERNET4, US 30036 2504 360 437 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at https://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 7282 1707 141 UNI2-AS, ES 39891 4833 286 59 ALJAWWALSTC-AS, SA 20940 4090 3399 164 AKAMAI-ASN1, NL 8551 3882 370 37 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2952 2292 909 ROSTELECOM-AS, RU 9009 2699 250 1394 M247, RO 34984 2273 359 611 TELLCOM-AS, TR 6849 2018 307 18 UKRTELNET, UA 58224 1853 950 535 TCI, IR 13188 1607 100 18 TRIOLAN, UA Complete listing at https://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 11260 3328 593 Uninet S.A. de C.V., MX 10620 3509 507 854 Telmex Colombia S.A., CO 13999 2343 360 621 Mega Cable, S.A. de C.V., MX 11830 2270 369 64 Instituto Costarricense de Electricidad 28573 1331 2324 240 Claro NXT Telecomunicacoes Ltda, BR 6503 1299 339 514 Axtel, S.A.B. de C.V., MX 3816 1293 760 170 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1132 370 22 Telefonica del Peru S.A.A., PE 11664 1099 180 448 Techtel LMDS Comunicaciones Interactiva 26615 1035 2498 45 TIM SA, BR Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1591 393 19 LINKdotNET-AS, EG 24835 1553 533 30 RAYA-AS, EG 36992 1338 1518 275 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 1021 67 46 ORANGE-COTE-IVOIRE, CI 36935 875 520 42 Vodafone-, EG 6713 550 1861 34 IAM-AS, MA 15399 533 54 48 WANANCHI-, KE 37342 489 32 1 MOVITEL, MZ 24757 485 73 5 EthioNet-AS, ET Complete listing at https://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 11260 3328 593 Uninet S.A. de C.V., MX 9808 9486 8706 40 CHINAMOBILE-CN China Mobile Communicati 16509 8289 10784 2931 AMAZON-02, US 12479 7282 1707 141 UNI2-AS, ES 7545 5726 787 694 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4863 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4833 286 59 ALJAWWALSTC-AS, SA 11492 4533 300 610 CABLEONE, US 20940 4090 3399 164 AKAMAI-ASN1, NL 45899 4053 1877 47 VNPT-AS-VN VNPT Corp, VN Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9486 9446 CHINAMOBILE-CN China Mobile Communications Grou 12479 7282 7141 UNI2-AS, ES 16509 8289 5358 AMAZON-02, US 7545 5726 5032 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4863 4788 ERX-CERNET-BKB China Education and Research Net 39891 4833 4774 ALJAWWALSTC-AS, SA 45899 4053 4006 VNPT-AS-VN VNPT Corp, VN 20940 4090 3926 AKAMAI-ASN1, NL 7155 3975 3924 VIASAT-SP-BACKBONE, US 11492 4533 3923 CABLEONE, US Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 3507 UNALLOCATED 5.105.69.0/24 213035 AS-SERVERION Serverion B.V., 3507 UNALLOCATED 5.105.206.0/24 213035 AS-SERVERION Serverion B.V., 33492 UNALLOCATED 8.6.184.0/23 33650 COMCAST-33650, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, US 396894 UNALLOCATED 8.28.201.0/24 46887 LIGHTOWER, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.139.232.0/24 Origin: 211619 MAXKO, HR 23.139.232.0/24 Transit: 42864 GIGANET-HU GigaNet Internet Service Prov 23.140.216.0/24 Origin: 27176 DATAWAGON, US 23.140.216.0/24 Transit: 20278 NEXEON, US 23.141.0.0/24 Origin: 395350 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 27.100.7.0/24 Origin: 56096 UNASSIGNED 27.100.7.0/24 Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 41.57.124.0/22 Origin: 37442 UNASSIGNED 41.57.124.0/22 Transit: 37204 TELONE, ZW Complete listing at https://thyme.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:16 /9:14 /10:39 /11:105 /12:301 /13:579 /14:1196 /15:2049 /16:13466 /17:8231 /18:14285 /19:25195 /20:44250 /21:51262 /22:109695 /23:97776 /24:551973 /25:743 /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 6342 7282 UNI2-AS, ES 8151 5216 11260 Uninet S.A. de C.V., MX 39891 3632 4833 ALJAWWALSTC-AS, SA 11492 3441 4533 CABLEONE, US 8551 3354 3882 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3334 3525 SHAW, CA 7155 3042 3975 VIASAT-SP-BACKBONE, US 22773 2651 3587 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2161 2504 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2064 3509 Telmex Colombia S.A., CO Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1821 2:1302 3:175 4:5 5:4524 6:127 7:6 8:1553 9:1 11:172 12:1535 13:388 14:2332 15:303 16:184 17:374 18:421 20:256 21:4 22:188 23:6227 24:2609 25:6 27:2459 29:19 31:2497 32:77 34:11 35:109 36:1942 37:4700 38:4558 39:827 40:150 41:3908 42:1247 43:2359 44:310 45:16536 46:4286 47:363 49:1757 50:1836 51:573 52:1592 54:389 55:765 56:8 57:114 58:1779 59:1155 60:988 61:2453 62:2650 63:1927 64:5648 65:2330 66:4999 67:3003 68:1353 69:4085 70:1235 71:671 72:2990 74:2620 75:1482 76:613 77:2452 78:1817 79:3170 80:2120 81:1780 82:1500 83:1280 84:1521 85:2959 86:768 87:2021 88:1173 89:3689 90:610 91:7756 92:2069 93:2622 94:3620 95:4010 96:1311 97:335 98:1153 99:745 100:73 101:1073 102:2660 103:31279 104:4655 105:488 106:945 107:2523 108:1031 109:4418 110:2104 111:3145 112:2037 113:1647 114:1651 115:2019 116:1920 117:2535 118:2377 119:2018 120:1824 121:1128 122:2612 123:2218 124:1616 125:2497 128:1378 129:1090 130:1018 131:2002 132:811 133:422 134:1901 135:304 136:880 137:950 138:2556 139:1572 140:1244 141:1457 142:1441 143:1501 144:1170 145:347 146:1943 147:1584 148:2569 149:2228 150:881 151:1160 152:1814 153:489 154:4469 155:1449 156:1779 157:1310 158:1051 159:2316 160:2547 161:1533 162:3512 163:1524 164:1620 165:1717 166:1033 167:1724 168:3867 169:939 170:4580 171:875 172:3549 173:2934 174:1070 175:1178 176:3702 177:4576 178:3593 179:2171 180:2571 181:3471 182:3387 183:1979 184:2340 185:20216 186:4773 187:3968 188:4118 189:3575 190:9156 191:1433 192:10945 193:8870 194:7322 195:5171 196:3099 197:2387 198:5957 199:6104 200:8040 201:5868 202:10672 203:10269 204:4585 205:3688 206:4322 207:3450 208:4085 209:4864 210:4437 211:2497 212:4152 213:3599 214:1088 215:59 216:6646 217:2682 218:1299 219:577 220:2021 221:976 222:885 223:2180 End of report

1 0

Reliable neutral global networks for connectivity testing
by Dmitriy A. 05 May '23

05 May '23

Hey all, I have a niche problem and wanted to get some feedback and ideas. I am trying to find some global networks that accept ICMP requests that I can use to ping and based on the packet loss try to understand if the client is having connectivity issues or uses an unreliable internet connection. The exact testing logic is here https://github.com/jsdelivr/globalping-probe/blob/master/src/lib/status-man… It basically requires 2/3 endpoints to have 0 packet loss when sending 6 packets to each. Some requirements: - Must be a global anycasted network since the client devices can be anywhere - Must be neutral. Meaning no government or ISP having a reason to block it. This eliminates Google, Microsoft, Akamai, Cloudflare... (blocked in China and elsewhere) - Must be reliable to avoid false-positives as much as possible. - Must be public and open. The network must be ok with random devices sending packets to them - Must be safe and controlled by a trusted entity I am currently trying to use DNS root servers https://root-servers.org/ but turns out many of them are unreliable for this use-case, I have noticed bad routing resulting in high latency and lots of packet loss at random. Same goes for pool.ntp.org where some Chinese users hit Amsterdam for some reason. This results in high packet loss marking the test as false-positive. Popular public DNS resolvers are also controlled by companies that are mostly likely to be banned in certain countries. Am I missing any other networks that fit the requirements? Any ideas on how to go about this would be appreciated, Thanks

2 1

Registration is Open for Hackathon 88 + DNS 1-Day Course + More
by Nanog News 04 May '23

04 May '23

*Registration is Open for Hackathon 88* *Hackathon 88 will Kick-Off 07, Jun * The NANOG Hackathons are hands-on and educational at their core — directly supporting the most critical aspects of our mission, so all levels are welcome to participate and registration is free. *REGISTER NOW * <https://nanog.org/events/nanog-88/> *Registration Open for DNS 1-Day Course * *Presented by Eddy Winstead * *Can you Dig It?* All skill levels are welcome. Date: 11 June — In-person class will take place during NANOG 88. *MORE INFO <https://nanog.org/events/nanog-88-dns-fundamentals/> * *Did You Know About our LGBTQ+ Group at NANOG?* *Find Community in our Online Discussion Threads* The NANOG Affinity Groups are part of the Community Forum and allow our members to connect over shared interests. *We need your voice! *Connect with others in the tech industry and find mentorship and support while sharing your experiences. *MORE INFO * <https://community.nanog.org/c/lgbtq/39>

1 0

Re: Best Linux (or BSD) hosted BGP?
by Jakob Heitz (jheitz) 03 May '23

03 May '23

I just checked the Cisco IOS-XR code. It's not vulnerable to any of the 3 flaws listed in the below linked hackernews article. Kind Regards, Jakob Date: Wed, 3 May 2023 12:52:46 +0300 From: Hank Nussbacher <hank(a)efes.iucc.ac.il> On 02/05/2023 17:56, Warren Kumari wrote: For those that like FRR: https://thehackernews.com/2023/05/researchers-uncover-new-bgp-flaws-in.html Regards, Hank

1 0

Cisco Nexus VXLAN w/vlan-aware-bundle ?
by Adam Thompson 03 May '23

03 May '23

Does anyone here use VXLAN on Cisco Nexus gear in the "vlan-aware-bundle" mode (RFC7432 §6.3), not the "vlan-based" mode (§6.1)? If so, could you please contact me directly to explain how you did so? Much appreciated, -Adam Adam Thompson Consultant, Infrastructure Services [cid:image004.png@01D97DB7.68236EA0] 100 - 135 Innovation Drive Winnipeg, MB R3T 6A8 (204) 977-6824 or 1-800-430-6404 (MB only) https://www.merlin.mb.ca<https://www.merlin.mb.ca/> [cid:image003.png@01D97DB7.67506730]Chat with me on Teams<https://teams.microsoft.com/l/chat/0/0?users=athompson@merlin.mb.ca>

1 0

Spectrum networks IPv6 access issue
by Tom Rini 03 May '23

03 May '23

Hey all, I'm posting this here in hopes of getting the attention of someone that can get this issue resolved, or at least an internal ticket filed. I've tried the customer-facing tech support and not been able to get such a thing done. In short, from within Spectrum's US IPv6 network (verified in both North Carolina and Ohio), dfw.source.kernel.org (2604:1380:4641:c500::1) is unreachable and connections time out. This site is otherwise fine and globally accessible via IPv6, tested on both Qwest and T-Mobile hosted systems. This is a regression from some time in early April this year. -- Tom

12 13

100G-LR1 (DR/FR)
by Jared Mauch 03 May '23

03 May '23

The common tech is 100G-LR4 these days - I'm wondering how many operators are supporting the LR1 to allow its use on 400G and future 800G optics as those use breakout to support 100G ports. Would you rather do a 400G port on a router vs 100LR1? Curious what others think. Sent via RFC1925 compliant device

8 12

Re: Best Linux (or BSD) hosted BGP?
by Tomas Jonsson 01 May '23

01 May '23

VyOS uses FRR, but they used to run quagga. And most bsd(?)/linux package managers has frr in their repository so maybe that could be something to look at? On 23/05/01 13:27, Josh Luthman wrote: >Doesn't VyOS simply use Quagga? > >On Mon, May 1, 2023 at 12:09 PM Jean Franco <jfranco(a)maila.inf.br> wrote: > >> Hi, >> >> VyOS >> >> Best regards, >> >> On Mon, May 1, 2023 at 1:03 PM Bryan Fields <Bryan(a)bryanfields.net> wrote: >> >>> I know best subjective, but I'm looking at a project to announce some IP >>> space >>> that's between uses now and see what's there. I'm planing to run a flow >>> logger and ntop on the VM and see what is coming in if anything. I'm >>> looking >>> at the options for BGP out there, and there's quite a few (other than >>> running >>> a VM with a router doing BGP), but most data I've seen is focused on >>> scale and >>> filtering use, or RPKI. My use case is a bit different, and I can't find >>> any >>> best practices for this use case from what I've found. >>> >>> That said, is there a better solution other than linux/ntop/ipt-netflow? >>> -- >>> Bryan Fields >>> >>> 727-409-1194 - Voice >>> http://bryanfields.net >>> >>

5 4