July 2020 - NANOG - lists.nanog.org

Comcast DNS Assistance?
by Dave Dechellis 06 Jul '20

06 Jul '20

Hello, Last night we made some changes to our DNS-SEC environment at Tufts University and all changes seem to have propagated - but we're having issues resolving against Comcast's DNS servers. All DNS-SEC checking seems to be looking good post changes and other ISPs are resolving fine. Is there anyone from Comcast who might be able to validate behavior? I'm assuming it might take up to 1 day for TTL propagation. Thanks Dave David.DeChellis(a)tufts.edu

3 2

Anyone from Airtel or Tata on list? DNS block issue on search engine
by John Von Essen 03 Jul '20

03 Jul '20

Starting yesterday, we’ve noticed the search engine DuckDuckGo being blocked via DNS in India. Specifically, users using Airtel or Tata DNS servers. Other search engines are fine (Bing, etc.,.). I know alot of blocking is occurring in India recently, but I think the net was incorrectly cast over this one. Its not all ISPs in India, so far just Airtel and Tata. $ dig @122.166.234.70 duckduckgo.com ; <<>> DiG 9.10.6 <<>> @122.166.234.70 duckduckgo.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7316 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: ;duckduckgo.com. IN A ;; AUTHORITY SECTION: rpz.airtelblack.com. 262 IN SOA rpz.airtelblack.com. hostmaster.rpz.airtelblack.com. 2360 3 3 2419200 604800 $ dig @59.163.126.38 duckduckgo.com ; <<>> DiG 9.10.6 <<>> @59.163.126.38 duckduckgo.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36722 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: ;duckduckgo.com. IN A ;; ANSWER SECTION: duckduckgo.com. 10800 IN A 127.0.0.1

2 1

Weekly Routing Table Report
by cscora＠apnic.net 03 Jul '20

03 Jul '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 04 Jul, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 816292 Prefixes after maximum aggregation (per Origin AS): 310189 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 397059 Total ASes present in the Internet Routing Table: 68553 Prefixes per ASN: 11.91 Origin-only ASes present in the Internet Routing Table: 58924 Origin ASes announcing only one prefix: 24515 Transit ASes present in the Internet Routing Table: 9629 Transit-only ASes present in the Internet Routing Table: 295 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 42 Max AS path prepend of ASN ( 22394) 38 Prefixes from unregistered ASNs in the Routing Table: 818 Number of instances of unregistered ASNs: 819 Number of 32-bit ASNs allocated by the RIRs: 32317 Number of 32-bit ASNs visible in the Routing Table: 26698 Prefixes from 32-bit ASNs in the Routing Table: 123167 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: 539 Number of addresses announced to Internet: 2843427328 Equivalent to 169 /8s, 123 /16s and 66 /24s Percentage of available address space announced: 76.8 Percentage of allocated address space announced: 76.8 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: 275708 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 213635 Total APNIC prefixes after maximum aggregation: 62618 APNIC Deaggregation factor: 3.41 Prefixes being announced from the APNIC address blocks: 207247 Unique aggregates announced from the APNIC address blocks: 86062 APNIC Region origin ASes present in the Internet Routing Table: 10690 APNIC Prefixes per ASN: 19.39 APNIC Region origin ASes announcing only one prefix: 3005 APNIC Region transit ASes present in the Internet Routing Table: 1592 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5768 Number of APNIC addresses announced to Internet: 770136192 Equivalent to 45 /8s, 231 /16s and 88 /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: 238973 Total ARIN prefixes after maximum aggregation: 109556 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 236191 Unique aggregates announced from the ARIN address blocks: 119918 ARIN Region origin ASes present in the Internet Routing Table: 18533 ARIN Prefixes per ASN: 12.74 ARIN Region origin ASes announcing only one prefix: 6775 ARIN Region transit ASes present in the Internet Routing Table: 1901 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 42 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3306 Number of ARIN addresses announced to Internet: 1079399168 Equivalent to 64 /8s, 86 /16s and 83 /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: 231779 Total RIPE prefixes after maximum aggregation: 107648 RIPE Deaggregation factor: 2.15 Prefixes being announced from the RIPE address blocks: 228478 Unique aggregates announced from the RIPE address blocks: 134640 RIPE Region origin ASes present in the Internet Routing Table: 27207 RIPE Prefixes per ASN: 8.40 RIPE Region origin ASes announcing only one prefix: 11753 RIPE Region transit ASes present in the Internet Routing Table: 3835 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 29 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9292 Number of RIPE addresses announced to Internet: 709299328 Equivalent to 42 /8s, 71 /16s and 12 /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: 107765 Total LACNIC prefixes after maximum aggregation: 24953 LACNIC Deaggregation factor: 4.32 Prefixes being announced from the LACNIC address blocks: 108936 Unique aggregates announced from the LACNIC address blocks: 46712 LACNIC Region origin ASes present in the Internet Routing Table: 10049 LACNIC Prefixes per ASN: 10.84 LACNIC Region origin ASes announcing only one prefix: 2486 LACNIC Region transit ASes present in the Internet Routing Table: 1879 Average LACNIC Region AS path length visible: 5.1 Max LACNIC Region AS path length visible: 39 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 7629 Number of LACNIC addresses announced to Internet: 174555136 Equivalent to 10 /8s, 103 /16s and 128 /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: 23321 Total AfriNIC prefixes after maximum aggregation: 4764 AfriNIC Deaggregation factor: 4.90 Prefixes being announced from the AfriNIC address blocks: 34901 Unique aggregates announced from the AfriNIC address blocks: 9272 AfriNIC Region origin ASes present in the Internet Routing Table: 1413 AfriNIC Prefixes per ASN: 24.70 AfriNIC Region origin ASes announcing only one prefix: 496 AfriNIC Region transit ASes present in the Internet Routing Table: 279 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 30 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 703 Number of AfriNIC addresses announced to Internet: 109594880 Equivalent to 6 /8s, 136 /16s and 73 /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 5518 724 655 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4743 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3439 1330 21 VIETEL-AS-AP Viettel Group, VN 45899 3169 1839 101 VNPT-AS-VN VNPT Corp, VN 7713 2700 827 527 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2613 9043 60 CMNET-GD Guangdong Mobile Communication 9498 2281 434 226 BBIL-AP BHARTI Airtel Ltd., IN 4766 2271 11101 552 KIXS-AS-KR Korea Telecom, KR 4755 2133 441 193 TATACOMM-AS TATA Communications formerl 9394 2034 4914 20 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 4460 299 633 CABLEONE, US 7155 4036 264 27 VIASAT-SP-BACKBONE, US 16509 4025 8145 1809 AMAZON-02, US 22773 3572 2968 152 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3351 1324 90 SHAW, CA 16625 3122 1628 2220 AKAMAI-AS, US 209 2424 5075 530 CENTURYLINK-US-LEGACY-QWEST, US 30036 2420 365 161 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2305 2981 1622 FRONTIER-FRTR, US 26484 2267 142 205 IKGUL-26484, 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 5826 1652 135 UNI2-AS, ES 31334 5251 484 13 KABELDEUTSCHLAND-AS, DE 8551 3168 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 3078 451 2071 AKAMAI-ASN1, EU 39891 2879 171 19 ALJAWWALSTC-AS, SA 12389 2550 2263 757 ROSTELECOM-AS, RU 34984 2160 354 566 TELLCOM-AS, TR 9009 2159 226 1183 M247, GB 13188 1609 100 35 TRIOLAN, UA 61317 1365 164 577 ASDETUK http://www.heficed.com, GB 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 6769 3328 597 Uninet S.A. de C.V., MX 10620 3365 530 511 Telmex Colombia S.A., CO 11830 2665 369 63 Instituto Costarricense de Electricidad 6503 1719 326 387 Mega Cable, S.A. de C.V., MX 7303 1519 988 253 Telecom Argentina S.A., AR 13999 1430 513 339 Mega Cable, S.A. de C.V., MX 28573 1406 2245 219 CLARO S.A., BR 6147 1136 379 39 Telefonica del Peru S.A.A., PE 3816 1113 571 149 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 957 112 71 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 1489 393 22 LINKdotNET-AS, EG 36992 1112 1539 76 ETISALAT-MISR, EG 24835 1073 474 23 RAYA-AS, EG 36903 917 480 93 MT-MPLS, MA 29571 625 68 11 ORANGE-COTE-IVOIRE, CI 6713 552 1863 34 IAM-AS, MA 15399 492 45 12 WANANCHI-, KE 37342 481 32 1 MOVITEL, MZ 36935 437 522 40 Vodafone-, EG 23889 344 231 15 MauritiusTelecom, MU Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 6769 3328 597 Uninet S.A. de C.V., MX 12479 5826 1652 135 UNI2-AS, ES 7545 5518 724 655 TPG-INTERNET-AP TPG Telecom Limited, AU 31334 5251 484 13 KABELDEUTSCHLAND-AS, DE 4538 4743 4192 73 ERX-CERNET-BKB China Education and Rese 11492 4460 299 633 CABLEONE, US 7155 4036 264 27 VIASAT-SP-BACKBONE, US 16509 4025 8145 1809 AMAZON-02, US 22773 3572 2968 152 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3439 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 5826 5691 UNI2-AS, ES 31334 5251 5238 KABELDEUTSCHLAND-AS, DE 7545 5518 4863 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4743 4670 ERX-CERNET-BKB China Education and Research Net 7155 4036 4009 VIASAT-SP-BACKBONE, US 11492 4460 3827 CABLEONE, US 22773 3572 3420 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3439 3418 VIETEL-AS-AP Viettel Group, VN 6327 3351 3261 SHAW, CA 8551 3168 3123 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 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 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 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 26584 UNALLOCATED 8.42.62.0/23 209 CENTURYLINK-US-LEGACY-QWEST, 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 46766 UNALLOCATED 8.44.208.0/24 3356 LEVEL3, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 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 27.126.158.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY 41.67.208.0/21 Origin: 15964 CAMNET-AS, CM Transit: 12956 TELEFONICA TELXIUS, ES 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:11 /10:38 /11:100 /12:287 /13:578 /14:1169 /15:1915 /16:13370 /17:8231 /18:13970 /19:25899 /20:40910 /21:48611 /22:101364 /23:83849 /24:474707 /25:1274 /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 31334 5100 5251 KABELDEUTSCHLAND-AS, DE 12479 4849 5826 UNI2-AS, ES 11492 3519 4460 CABLEONE, US 6327 3140 3351 SHAW, CA 7155 3128 4036 VIASAT-SP-BACKBONE, US 22773 2779 3572 ASN-CXA-ALL-CCI-22773-RDC, US 8551 2627 3168 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 8151 2449 6769 Uninet S.A. de C.V., MX 39891 2417 2879 ALJAWWALSTC-AS, SA 30036 2162 2420 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1543 2:1197 3:31 4:19 5:3393 6:52 8:1461 9:1 11:1 12:1778 13:513 14:2299 15:72 16:8 17:291 18:81 20:106 23:3757 24:2302 25:3 27:2560 31:3089 32:129 34:1 35:42 36:961 37:3273 38:1953 39:427 40:127 41:3682 42:617 43:2142 44:209 45:14680 46:3703 47:297 49:1470 50:1548 51:90 52:1103 54:226 55:683 56:6 57:51 58:1757 59:1176 60:762 61:2299 62:2140 63:1982 64:5236 65:2331 66:5011 67:2877 68:1176 69:4003 70:1404 71:680 72:2875 74:2575 75:1451 76:660 77:2910 78:1661 79:2385 80:1945 81:1660 82:1312 83:1257 84:1232 85:2619 86:548 87:1748 88:1167 89:2756 90:339 91:8075 92:1538 93:2508 94:2737 95:3929 96:1226 97:338 98:923 99:978 100:86 101:1002 102:998 103:23938 104:3450 105:401 106:911 107:2042 108:697 109:3643 110:1848 111:2029 112:1642 113:1360 114:1543 115:1827 116:1797 117:2105 118:2075 119:1715 120:833 121:1038 122:2442 123:2081 124:1567 125:2015 128:1383 129:1213 130:662 131:1872 132:771 133:302 134:1345 135:305 136:628 137:859 138:2197 139:1009 140:686 141:1003 142:934 143:1262 144:1034 145:328 146:1492 147:1019 148:2118 149:1183 150:826 151:1074 152:1496 153:414 154:4566 155:1059 156:2998 157:1131 158:854 159:1974 160:1920 161:1065 162:3102 163:829 164:1475 165:1301 166:562 167:1639 168:3535 169:568 170:4253 171:777 172:1941 173:2575 174:987 175:1059 176:2589 177:4211 178:3032 179:1516 180:2272 181:2500 182:3093 183:1155 184:2413 185:16568 186:3764 187:2863 188:4084 189:2445 190:8785 191:1350 192:10398 193:7568 194:6273 195:4434 196:3266 197:2029 198:6133 199:5883 200:7243 201:5254 202:10546 203:10275 204:4562 205:3129 206:3176 207:3283 208:4068 209:4466 210:4013 211:2025 212:3398 213:3140 214:1189 215:62 216:6047 217:2414 218:855 219:616 220:2018 221:950 222:1006 223:1515 End of report

1 0

Oracle Certification Exams...
by Michael Bullut 02 Jul '20

02 Jul '20

Greetings Team, Are there any Oracle Certified Professionals in the group? Currently, I am undertaking several Oracle certifications during this month and would to inquire which materials did you use to prepare for the aforementioned? Warm regards, Michael Bullut. --- *Cell:* *+254 723 393 114.**Skype Name:* *Michael Bullut.* *Blog: http://www.kipsang.com/ <http://www.kipsang.com/>* *E-mail:* *main(a)kipsang.com <main(a)kipsang.com>* *---*

2 1

Re: Microsoft SNDS contact with a clue?
by Brian Rak 01 Jul '20

01 Jul '20

Unfortunately, that's the generic SNDS support email I have been talking to. They don't appear to be able to actually fix anything. On 6/25/2020 3:03 PM, Udeme Ukutt wrote: > Brian, try msn-snds(a)microsoft.com <mailto:msn-snds@microsoft.com>. > It's been awhile I've had to use it, but it's worth a shot. > > Udeme > Postmaster at LinkedIn > > On Thu, Jun 25, 2020 at 12:00 PM Brian Rak via NANOG <nanog(a)nanog.org > <mailto:nanog@nanog.org>> wrote: > > Is there anyone around from Microsoft that can help me with a SNDS > verification issue? > > I'm having problems where the verification system is trying to use > the > wrong WHOIS server, and the responses I'm getting from support don't > really indicate they understand the issue. > > I also have a different problem where I have a /17 and support keeps > telling me I need to go and verify all the /23's within it... > which is > going to take quite awhile. > >

2 1

Devil's Advocate - Segment Routing, Why?
by Mark Tinka 01 Jul '20

01 Jul '20

Hi all. When the whole SR concept was being first dreamed up, I was mildly excited about it. But then real life happened and global deployment (be it basic SR-MPLS or SRv6) is what it is, and I became less excited. This was back in 2015. All the talk about LDPv6 this and last week has had me reflecting a great deal on where we are, as an industry, in why we are having to think about SR and all its incarnations. So, let me be the one that stirs up the hornets' nest... Why do we really need SR? Be it SR-MPLS or SRv6 or SRv6+? I've heard a lot about "network programmability", e.t.c., but can anyone point me toward a solution that actually does this in the way that it has been touted for years? A true flow that shows the implementation of "network programming" over any incarnation of SR? Perhaps one a customer can go to the shop and grab off the shelf? A lot of kit does not currently support SR, be it in hardware or software. So are operators expected to dispose of boxes that are happily moving MPLS frames along with no complaints, and replace them with some newfangled creations that will support SR in code and silicon? At whose cost? Not just money, but time, people and working the day-to-day kinks out? I've heard about "end-to-end service chaining" as a use-case for SR. To service-chain what? Classic telco's don't offer complex over-the-top services that operate at a such a scale that "service chaining" in SR would make lives easier. More than half of the traffic we are carrying is coming in over the public Internet, and not some private VPN. And if "service chaining" makes sense to the cloud and content operators who run humongous data centres where the servers significantly outnumber the routing/switching/transport gear, I'd naively posit that they have built a myriad of custom, in-house solutions, systems, tools and controllers to do all the "service chaining" they could ever need, and have been at it for more than 10 years, if not more, all to manage an MPLS/DWDM backbone. So what off-the-shelf "service chaining" controller are they going to walk into the shop and pay money for? If I had to think of the number of network, content and cloud operators who have either said they've deployed some kind of SR, or intend to, you're looking at probably 10% - 15% of a market. What about the other 85% - 90% of the operators whose requirements are so simple, thinking about dumping existing boxes, systems, tools and solutions that work very well in order to join the SR club doesn't seem feasible. What problems are 90% of the operators running MPLS having that SR will truly fix, given that they don't operate large, distributed data centres or have a 5G license? What's even more wild, is that there are equally a number of networks that are stalling IPv6 deployment, for some reason or other, meaning it will probably take us another 1 to 2 decades to see worldwide adoption of IPv6. If SRv6 or SRv6+ is "where the market is dying to go", and a bunch of operators don't have IPv6 in their plans, what gives? To be clear, I'm not against SR; what has to come will come. What I am less enthused about is being forced into an all-or-nothing scenario for the going concern of my network. For those that are keen on SR, give them SR. But for those who would prefer to keep things simple in networks that are not about to fall over and die, let's have LDPv6 and let's implement RFC 7439. Then let the operators choose. On a personal note, it's a pity Juniper gave in to the SRv6 fight, despite all the initial resistance. If they'd gone a different direction and simply implemented RFC 7439 (they have LDPv6 already), not only would that have put Cisco under serious pressure, but it would have solved the problems of many network operators that are desperately looking to go IPv6-only, and still maintain the rich MPLS services they and their customers have grown to like. Mark.

12 38