- NANOG - lists.nanog.org

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

17 Jan '20

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 18 Jan, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 791374 Prefixes after maximum aggregation (per Origin AS): 301457 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 387840 Total ASes present in the Internet Routing Table: 66740 Prefixes per ASN: 11.86 Origin-only ASes present in the Internet Routing Table: 57361 Origin ASes announcing only one prefix: 24165 Transit ASes present in the Internet Routing Table: 9379 Transit-only ASes present in the Internet Routing Table: 288 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 35 Max AS path prepend of ASN ( 53176) 31 Prefixes from unregistered ASNs in the Routing Table: 1313 Number of instances of unregistered ASNs: 1313 Number of 32-bit ASNs allocated by the RIRs: 30192 Number of 32-bit ASNs visible in the Routing Table: 24830 Prefixes from 32-bit ASNs in the Routing Table: 113996 Number of bogon 32-bit ASNs visible in the Routing Table: 31 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 443 Number of addresses announced to Internet: 2852676736 Equivalent to 170 /8s, 8 /16s and 100 /24s Percentage of available address space announced: 77.1 Percentage of allocated address space announced: 77.1 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.4 Total number of prefixes smaller than registry allocations: 264746 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 210449 Total APNIC prefixes after maximum aggregation: 61270 APNIC Deaggregation factor: 3.43 Prefixes being announced from the APNIC address blocks: 203980 Unique aggregates announced from the APNIC address blocks: 84945 APNIC Region origin ASes present in the Internet Routing Table: 10291 APNIC Prefixes per ASN: 19.82 APNIC Region origin ASes announcing only one prefix: 2850 APNIC Region transit ASes present in the Internet Routing Table: 1543 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 25 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5344 Number of APNIC addresses announced to Internet: 768001280 Equivalent to 45 /8s, 198 /16s and 197 /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: 232092 Total ARIN prefixes after maximum aggregation: 107372 ARIN Deaggregation factor: 2.16 Prefixes being announced from the ARIN address blocks: 230025 Unique aggregates announced from the ARIN address blocks: 116598 ARIN Region origin ASes present in the Internet Routing Table: 18372 ARIN Prefixes per ASN: 12.52 ARIN Region origin ASes announcing only one prefix: 6763 ARIN Region transit ASes present in the Internet Routing Table: 1905 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: 3119 Number of ARIN addresses announced to Internet: 1079028480 Equivalent to 64 /8s, 80 /16s and 171 /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: 223723 Total RIPE prefixes after maximum aggregation: 103953 RIPE Deaggregation factor: 2.15 Prefixes being announced from the RIPE address blocks: 220449 Unique aggregates announced from the RIPE address blocks: 130028 RIPE Region origin ASes present in the Internet Routing Table: 26743 RIPE Prefixes per ASN: 8.24 RIPE Region origin ASes announcing only one prefix: 11696 RIPE Region transit ASes present in the Internet Routing Table: 3776 Average RIPE Region AS path length visible: 4.6 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 8838 Number of RIPE addresses announced to Internet: 723697536 Equivalent to 43 /8s, 34 /16s and 191 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-210331 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 102509 Total LACNIC prefixes after maximum aggregation: 23648 LACNIC Deaggregation factor: 4.33 Prefixes being announced from the LACNIC address blocks: 103661 Unique aggregates announced from the LACNIC address blocks: 45327 LACNIC Region origin ASes present in the Internet Routing Table: 9321 LACNIC Prefixes per ASN: 11.12 LACNIC Region origin ASes announcing only one prefix: 2380 LACNIC Region transit ASes present in the Internet Routing Table: 1759 Average LACNIC Region AS path length visible: 5.3 Max LACNIC Region AS path length visible: 35 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 6890 Number of LACNIC addresses announced to Internet: 174034688 Equivalent to 10 /8s, 95 /16s and 143 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-270748 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 21287 Total AfriNIC prefixes after maximum aggregation: 4434 AfriNIC Deaggregation factor: 4.80 Prefixes being announced from the AfriNIC address blocks: 32816 Unique aggregates announced from the AfriNIC address blocks: 10593 AfriNIC Region origin ASes present in the Internet Routing Table: 1340 AfriNIC Prefixes per ASN: 24.49 AfriNIC Region origin ASes announcing only one prefix: 476 AfriNIC Region transit ASes present in the Internet Routing Table: 258 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 639 Number of AfriNIC addresses announced to Internet: 107533056 Equivalent to 6 /8s, 104 /16s and 211 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 45/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7545 5245 645 603 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4621 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3318 1331 24 VIETEL-AS-AP Viettel Group, VN 45899 3120 1785 107 VNPT-AS-VN VNPT Corp, VN 7713 2697 814 495 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2600 9043 62 CMNET-GD Guangdong Mobile Communication 4766 2264 11102 566 KIXS-AS-KR Korea Telecom, KR 9498 2218 433 212 BBIL-AP BHARTI Airtel Ltd., IN 9829 2160 1377 249 BSNL-NIB National Internet Backbone, IN 4755 2138 441 190 TATACOMM-AS TATA Communications formerl Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7155 4047 280 27 VIASAT-SP-BACKBONE, US 11492 3894 258 653 CABLEONE, US 16509 3805 7736 1687 AMAZON-02, US 22773 3516 2971 152 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3373 1324 93 SHAW, CA 16625 2956 1550 2122 AKAMAI-AS, US 30036 2284 358 92 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2250 5075 534 CENTURYLINK-US-LEGACY-QWEST, US 20115 2136 2774 519 CHARTER-20115, US 18566 2059 405 103 MEGAPATH5-, US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 5848 1631 135 UNI2-AS, ES 39891 4034 219 19 ALJAWWALSTC-AS, SA 31334 3388 484 13 KABELDEUTSCHLAND-AS, DE 8551 3110 379 46 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2819 469 1955 AKAMAI-ASN1, US 12389 2421 2239 702 ROSTELECOM-AS, RU 9009 2063 223 1111 M247, GB 34984 2048 348 556 TELLCOM-AS, TR 9121 1932 1691 18 TTNET, TR 13188 1605 100 46 TRIOLAN, UA Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 6190 3297 610 Uninet S.A. de C.V., MX 10620 3361 533 469 Telmex Colombia S.A., CO 11830 2680 369 63 Instituto Costarricense de Electricidad 6503 1682 323 389 Axtel, S.A.B. de C.V., MX 7303 1478 1026 265 Telecom Argentina S.A., AR 28573 1267 2235 200 CLARO S.A., BR 13999 1157 501 273 Mega Cable, S.A. de C.V., MX 3816 1119 561 133 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1097 379 39 Telefonica del Peru S.A.A., PE 11172 942 111 65 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 1243 393 23 LINKdotNET-AS, EG 24835 1097 566 24 RAYA-AS, EG 36992 1036 1535 73 ETISALAT-MISR, EG 36903 876 452 97 MT-MPLS, MA 6713 623 1863 34 IAM-AS, MA 29571 561 68 12 ORANGE-COTE-IVOIRE, CI 37342 477 32 1 MOVITEL, MZ 36935 383 522 40 Vodafone-, EG 23889 352 231 15 MauritiusTelecom, MU 15399 351 45 10 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 8151 6190 3297 610 Uninet S.A. de C.V., MX 12479 5848 1631 135 UNI2-AS, ES 7545 5245 645 603 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4621 4192 73 ERX-CERNET-BKB China Education and Rese 7155 4047 280 27 VIASAT-SP-BACKBONE, US 39891 4034 219 19 ALJAWWALSTC-AS, SA 11492 3894 258 653 CABLEONE, US 16509 3805 7736 1687 AMAZON-02, US 22773 3516 2971 152 ASN-CXA-ALL-CCI-22773-RDC, US 31334 3388 484 13 KABELDEUTSCHLAND-AS, DE Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 12479 5848 5713 UNI2-AS, ES 7545 5245 4642 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4621 4548 ERX-CERNET-BKB China Education and Research Net 7155 4047 4020 VIASAT-SP-BACKBONE, US 39891 4034 4015 ALJAWWALSTC-AS, SA 31334 3388 3375 KABELDEUTSCHLAND-AS, DE 22773 3516 3364 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3318 3294 VIETEL-AS-AP Viettel Group, VN 6327 3373 3280 SHAW, CA 11492 3894 3241 CABLEONE, US Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 17076 UNALLOCATED 8.12.244.0/24 3356 LEVEL3, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 174 COGENT-174, US 62485 UNALLOCATED 8.23.229.0/24 3356 LEVEL3, US 32985 UNALLOCATED 8.28.31.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 23071 UNALLOCATED 8.33.235.0/24 3356 LEVEL3, US 27205 UNALLOCATED 8.38.16.0/21 6461 ZAYO-6461, US 27205 UNALLOCATED 8.38.16.0/22 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 27205 UNALLOCATED 8.38.20.0/22 32787 PROLEXIC-TECHNOLOGIES-DDOS-M Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.136.224.0/24 Origin: 15206 UNASSIGNED Transit: 174 COGENT-174, US 23.137.192.0/24 Origin: 31798 CANAD-86-31798, CA Transit: 6939 HURRICANE, US 27.100.7.0/24 Origin: 56096 UNASSIGNED Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 27.126.156.0/22 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY 27.126.156.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:10 /9:11 /10:38 /11:98 /12:287 /13:580 /14:1159 /15:1920 /16:13391 /17:8115 /18:13879 /19:25777 /20:40474 /21:47497 /22:98432 /23:80749 /24:457619 /25:1338 /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 4810 5848 UNI2-AS, ES 31334 3233 3388 KABELDEUTSCHLAND-AS, DE 6327 3161 3373 SHAW, CA 7155 3139 4047 VIASAT-SP-BACKBONE, US 11492 3037 3894 CABLEONE, US 39891 2946 4034 ALJAWWALSTC-AS, SA 22773 2736 3516 ASN-CXA-ALL-CCI-22773-RDC, US 8551 2569 3110 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2033 2284 MEDIACOM-ENTERPRISE-BUSINESS, US 11830 2028 2680 Instituto Costarricense de Electricidad y Telec Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1525 2:1155 3:12 4:19 5:3217 6:47 8:1366 9:1 12:1786 13:495 14:2216 15:59 16:9 17:284 18:78 20:58 23:3224 24:2619 25:4 27:2524 31:2848 32:101 35:43 36:941 37:3176 38:1821 39:314 40:132 41:3272 42:880 43:2127 44:185 45:12907 46:3616 47:274 49:1432 50:1199 51:344 52:1112 54:274 55:649 56:6 57:48 58:1747 59:1117 60:687 61:2223 62:2125 63:1907 64:5033 65:2327 66:4826 67:2830 68:1234 69:3808 70:1409 71:666 72:2776 74:2622 75:1435 76:661 77:2552 78:1989 79:2380 80:1852 81:1549 82:1202 83:1118 84:1231 85:2574 86:579 87:1677 88:1070 89:2669 90:278 91:7480 92:1451 93:2430 94:2592 95:3707 96:1006 97:337 98:961 99:965 100:85 101:1082 102:769 103:22947 104:3619 105:364 106:828 107:1872 108:688 109:3617 110:1773 111:1920 112:1535 113:1377 114:1483 115:1838 116:1798 117:2016 118:2110 119:1687 120:835 121:1030 122:2369 123:1888 124:1549 125:2018 128:1370 129:912 130:600 131:1849 132:772 133:301 134:1255 135:273 136:604 137:876 138:2193 139:991 140:594 141:881 142:857 143:1155 144:936 145:293 146:1468 147:999 148:1895 149:1106 150:811 151:1260 152:1473 153:370 154:4648 155:905 156:3094 157:1089 158:703 159:1946 160:1712 161:986 162:3023 163:776 164:1501 165:1221 166:536 167:1462 168:3570 169:487 170:4195 171:742 172:1846 173:2350 174:1036 175:1009 176:2581 177:4152 178:2849 179:1409 180:2183 181:2383 182:2835 183:1121 184:2385 185:15882 186:3729 187:2585 188:3492 189:2077 190:8222 191:1439 192:10203 193:7307 194:5953 195:4276 196:3366 197:1839 198:6097 199:5945 200:7177 201:5117 202:10447 203:10148 204:4538 205:3074 206:3251 207:3253 208:4010 209:4340 210:3997 211:1990 212:3217 213:2982 214:1134 215:53 216:5923 217:2326 218:895 219:607 220:1983 221:934 222:1012 223:1392 End of report

1 0

De-bogonising 2a10::/12
by Emile Aben 17 Jan '20

17 Jan '20

Dear colleagues, We have now started de-bogonising 2a10::/12! As part of this, we are announcing a couple of prefixes out of 2a10::/12 from AS12654 (RIPE's Routing Information Service, RIS). Pingable targets have been configured in these prefixes, and we invite network operators to test for themselves whether this address space is reachable. The simplest way to do this would be to perform a ping6 to 2a10:4::1 . Using RIPE Atlas and RIS, we will also be carrying out our own tests in order to investigate connectivity and filtering for this address space. We plan to share our results with the RIPE community via RIPE Labs within the next few days. For those who want to do other testing, beyond the basic test described above, we have a total of 8 targets available for this, with 2 different prefix lengths and all variations of having ROUTE objects in the RIPE DB and/or ROAs. 2a10:3:4::1 /48 ROUTE object + ROA 2a10:3:5::1 /48 no ROUTE object + ROA 2a10:3:6::1 /48 ROUTE object + no ROA 2a10:3:7::1 /48 no ROUTE object + no ROA 2a10:4::1 /32 ROUTE object + ROA 2a10:5::1 /32 no ROUTE object + ROA 2a10:6::1 /32 ROUTE object + no ROA 2a10:7::1 /32 no ROUTE object + no ROA Kind regards, Emile Aben RIPE NCC

2 1

GPS may be jammed for several hours per day in the SE US Jan 16-24
by Marshall Eubanks 17 Jan '20

17 Jan '20

I thought this might be relevant to many: GPS reception may be unavailable or unreliable over a large portion of the southeastern states and the Caribbean during offshore military exercises scheduled between January 16 and 24. The FAA has posted a flight advisory for the exercises that will require jamming of GPS signals for periods of several hours each day of the event. Navigation guidance, ADS-B, and other services associated with GPS could be affected for up to 400 nautical miles at Flight Level 400, down to a radius of 180 nm at 50 feet above the ground. https://www.aopa.org/news-and-media/all-news/2020/january/14/gps-jamming-ex… Regards Marshall Eubanks

1 0

IPv6 Prefix Delegation to customers.
by Brandon Price 17 Jan '20

17 Jan '20

Hey Nanog, I am in the process of building out a FTTH proof of concept, and I would really like to offer each of my customers a /48 of IPv6. I've been able to announce my /32 to my upstreams, dual-stack all of my internal infrastructure no-problem, build v6 recursive name servers, etc. This was fairly straight-forward. Where I am struggling is the Prefix Delegation part. How are most folks getting the PD subnets into their IGPs? In my environment I don't run the DHCP server process on the router that is directly connected to the clients. I have seen documentation that cisco and juniper DHCPv6 processes are smart enough to insert that prefix into the routing table when they hand it out, but how is this handled in an environment with a central DHCP server? I do not currently run any PPPOE in my environment and I don't use RADIUS for the subscriber management. I would really just like to stick to DHCP ideally. If anyone has any pointers, I would appreciate it. Brandon Price Senior Network Engineer City of Sherwood, Sherwood Broadband Desk: 503.625.4258 Cell: 971.979.2182 This email may contain confidential information or privileged material and is intended for use solely by the above referenced recipient. Any review, copying, printing, disclosure, distribution, or other use by any other person or entity is strictly prohibited and may be illegal. If you are not the named recipient, or believe you have received this email in error, please immediately notify the City of Sherwood at (503) 625-5522 and delete the copy you received.

8 7

Walmart GEOIP
by Norman Jester 16 Jan '20

16 Jan '20

I’m having an issue with a customer who for some reason is sent to the Mexican walmart site when they load it from USA. If anyone knows which geoip service they use or have a contact in Walmart for geoip issues please advise on or off list. (May be helpful to others) Norman

2 2

China Network Diversity
by Gabe Cole 16 Jan '20

16 Jan '20

We are trying to design a physically diverse network in China and have been challenged. All of the major carriers say that they cannot provide us KMZs or similar detailed route information. Has anyone been able to crack this code? G. Gabriel Cole *RTE Group, Inc.* *Strategic Consulting for Mission Critical Infrastructure* 56 Woodridge Rd Wellesley, MA 02482 US +1-617-303-8707 fax +1-781-209-5577 www.rtegroup.com ( http://www.rtegroup.com ) gabe(a)rtegroup.com skype: ggabrielcole Twitter: @DataCenterGuru Linked In: http://www.linkedin.com/in/gabecole Blog: http://datacenterguru.blogspot.com/ The information contained herein is confidential and proprietary to RTE Group, Inc. It is intended for presentation to and permitted use solely by those person(s) to whom it has been transmitted by RTE Group, Inc. and it is transmitted to such person(s) solely for, conditional upon, and only to the extent necessary for use by such person(s) as part of their business relationship with RTE Group, Inc. or to further their respective evaluation(s) of a potential business relationship with RTE Group, Inc., and no other use, release, or reproduction of this information is permitted. Sent via Superhuman ( https://sprh.mn/?vip=gabe@rtegroup.com )

4 4

AS45102 Alibaba
by Marco Paesani 16 Jan '20

16 Jan '20

Hi, I need contact with AS45102 because there is a lot networks with ROA wrong and invalid. Nobody knows some technical people inside this AS ? Thanks for your help. Kind regards, Marco Paesani Skype: mpaesani Mobile: +39 348 6019349 Success depends on the right choice ! Email: marco(a)paesani.it

3 3

Telco T-Marc 300
by Fawcett, Nick 16 Jan '20

16 Jan '20

Anyone out there willing to share sample config of a Telco Systems T-Mark 300 unit. A config using Q-n-Q would be welcomed. Thanks. ~Nick -- Checked by SOPHOS http://www.sophos.com

1 0

Chicago Conduit
by Rod Beck 16 Jan '20

16 Jan '20

Hi, My client is looking to buy conduit with coverage of the affluent parts of Chicago. Access to manholes, buildings on-net and near-net are important ingredients. Second best solution is to purchase fiber manufactured in the last five years. 144-846 pairs is the likely range. Thanks. Regards, Roderick. Roderick Beck VP of Business Development United Cable Company www.unitedcablecompany.com<http://www.unitedcablecompany.com> New York City & Budapest rod.beck(a)unitedcablecompany.com 36-70-605-5144 [1467221477350_image005.png]

1 0

AWS Network Engineering contact?
by Peter Serwe 14 Jan '20

14 Jan '20

I have a direct connect via Coresite LA1 over to AWS via US West 1, and a customer with VPC's in the east that are getting really bad throughput transferring files via the direct connect. We've isolated it to being an issue behind AWS's PE over a barely utilized 10G XC. Would anyone happen to know what the right starting point to contact someone in AWS Network Engineering? We can replicate the issue at will. Current discussions are to see if we can get anywhere with AWS Network folks, or potentially go rebuild the direct connect / VPC's over in US West 1 to bypass most of the cross-country AWS backbone, but that's a fair amount of work to *maybe* resolve the issue? Peter -- Peter Serwe http://truthlightway.blogspot.com/

3 2