March 2018 - Test - lists.nanog.org

Re: Yet another Quadruple DNS?
by Scott Weeks 30 Mar '18

30 Mar '18

> Public DNS resolvers still help against "ordinary" > adversaries. (If your ennemy is the NSA, you have > other problems, anyway.) : I think there's ample evidence that everyone's enemy : is 'the nsa' (or other nation-state-actors) isn't : there? --- nanog(a)ics-il.net wrote: ------------- From: Mike Hammett <nanog(a)ics-il.net> :: I doubt most people could care less. ------------------------------------------- You have to wait, it's not april 1st yet! >8-\ scott

1 0

Weekly Routing Table Report
by cscora＠apnic.net 30 Mar '18

30 Mar '18

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG, IRNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 31 Mar, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 692170 Prefixes after maximum aggregation (per Origin AS): 267487 Deaggregation factor: 2.59 Unique aggregates announced (without unneeded subnets): 333579 Total ASes present in the Internet Routing Table: 60264 Prefixes per ASN: 11.49 Origin-only ASes present in the Internet Routing Table: 52065 Origin ASes announcing only one prefix: 22789 Transit ASes present in the Internet Routing Table: 8199 Transit-only ASes present in the Internet Routing Table: 262 Average AS path length visible in the Internet Routing Table: 4.2 Max AS path length visible: 40 Max AS path prepend of ASN ( 22394) 37 Prefixes from unregistered ASNs in the Routing Table: 44 Number of instances of unregistered ASNs: 44 Number of 32-bit ASNs allocated by the RIRs: 22003 Number of 32-bit ASNs visible in the Routing Table: 17722 Prefixes from 32-bit ASNs in the Routing Table: 73797 Number of bogon 32-bit ASNs visible in the Routing Table: 13 Special use prefixes present in the Routing Table: 3 Prefixes being announced from unallocated address space: 295 Number of addresses announced to Internet: 2857155394 Equivalent to 170 /8s, 76 /16s and 187 /24s Percentage of available address space announced: 77.2 Percentage of allocated address space announced: 77.2 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.9 Total number of prefixes smaller than registry allocations: 230623 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 189779 Total APNIC prefixes after maximum aggregation: 53876 APNIC Deaggregation factor: 3.52 Prefixes being announced from the APNIC address blocks: 188701 Unique aggregates announced from the APNIC address blocks: 77097 APNIC Region origin ASes present in the Internet Routing Table: 8739 APNIC Prefixes per ASN: 21.59 APNIC Region origin ASes announcing only one prefix: 2464 APNIC Region transit ASes present in the Internet Routing Table: 1287 Average APNIC Region AS path length visible: 4.3 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3665 Number of APNIC addresses announced to Internet: 767373154 Equivalent to 45 /8s, 189 /16s and 47 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-137529 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 206257 Total ARIN prefixes after maximum aggregation: 98744 ARIN Deaggregation factor: 2.09 Prefixes being announced from the ARIN address blocks: 206949 Unique aggregates announced from the ARIN address blocks: 97769 ARIN Region origin ASes present in the Internet Routing Table: 18130 ARIN Prefixes per ASN: 11.41 ARIN Region origin ASes announcing only one prefix: 6709 ARIN Region transit ASes present in the Internet Routing Table: 1807 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 40 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2334 Number of ARIN addresses announced to Internet: 1104557184 Equivalent to 65 /8s, 214 /16s and 52 /24s ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-397212 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 188296 Total RIPE prefixes after maximum aggregation: 91199 RIPE Deaggregation factor: 2.06 Prefixes being announced from the RIPE address blocks: 184577 Unique aggregates announced from the RIPE address blocks: 110233 RIPE Region origin ASes present in the Internet Routing Table: 25023 RIPE Prefixes per ASN: 7.38 RIPE Region origin ASes announcing only one prefix: 11348 RIPE Region transit ASes present in the Internet Routing Table: 3489 Average RIPE Region AS path length visible: 4.2 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6824 Number of RIPE addresses announced to Internet: 715842688 Equivalent to 42 /8s, 170 /16s and 228 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-207259 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 89312 Total LACNIC prefixes after maximum aggregation: 19652 LACNIC Deaggregation factor: 4.54 Prefixes being announced from the LACNIC address blocks: 90700 Unique aggregates announced from the LACNIC address blocks: 40695 LACNIC Region origin ASes present in the Internet Routing Table: 6968 LACNIC Prefixes per ASN: 13.02 LACNIC Region origin ASes announcing only one prefix: 1898 LACNIC Region transit ASes present in the Internet Routing Table: 1294 Average LACNIC Region AS path length visible: 4.7 Max LACNIC Region AS path length visible: 32 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4499 Number of LACNIC addresses announced to Internet: 172487904 Equivalent to 10 /8s, 71 /16s and 244 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 18480 Total AfriNIC prefixes after maximum aggregation: 3976 AfriNIC Deaggregation factor: 4.65 Prefixes being announced from the AfriNIC address blocks: 20948 Unique aggregates announced from the AfriNIC address blocks: 7549 AfriNIC Region origin ASes present in the Internet Routing Table: 1117 AfriNIC Prefixes per ASN: 18.75 AfriNIC Region origin ASes announcing only one prefix: 369 AfriNIC Region transit ASes present in the Internet Routing Table: 228 Average AfriNIC Region AS path length visible: 4.6 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 400 Number of AfriNIC addresses announced to Internet: 96509184 Equivalent to 5 /8s, 192 /16s and 157 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5416 4192 74 ERX-CERNET-BKB China Education and Rese 7545 3709 410 426 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2849 11131 780 KIXS-AS-KR Korea Telecom, KR 9829 2808 1499 542 BSNL-NIB National Internet Backbone, IN 7552 2674 1158 62 VIETEL-AS-AP Viettel Group, VN 9394 2638 4923 29 CTTNET China TieTong Telecommunications 45899 2546 1569 165 VNPT-AS-VN VNPT Corp, VN 17974 2315 930 80 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9808 2164 8699 32 CMNET-GD Guangdong Mobile Communication 4755 2086 417 216 TATACOMM-AS TATA Communications formerl Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 6327 3375 1323 86 SHAW - Shaw Communications Inc., CA 22773 3290 2988 150 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2167 405 108 MEGAPATH5-US - MegaPath Corporation, US 20115 2092 2484 447 CHARTER-NET-HKY-NC - Charter Communicat 16509 2019 4372 670 AMAZON-02 - Amazon.com, Inc., US 30036 1947 341 181 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 1920 5070 606 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 11492 1778 228 556 CABLEONE - CABLE ONE, INC., US 7018 1701 20189 1254 ATT-INTERNET4 - AT&T Services, Inc., US 16625 1695 825 1213 AKAMAI-AS - Akamai Technologies, Inc., 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 3974 1504 540 UNI2-AS, ES 39891 3522 203 20 ALJAWWALSTC-AS, SA 20940 2751 778 2008 AKAMAI-ASN1, US 8551 2093 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2039 1859 706 ROSTELECOM-AS, RU 34984 2020 334 481 TELLCOM-AS, TR 9121 1953 1692 19 TTNET, TR 13188 1606 100 46 TRIOLAN, UA 6849 1241 355 21 UKRTELNET, UA 8402 1228 544 14 CORBINA-AS OJSC "Vimpelcom", RU Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 4325 3385 575 Uninet S.A. de C.V., MX 10620 3599 540 261 Telmex Colombia S.A., CO 11830 2639 369 85 Instituto Costarricense de Electricidad 6503 1629 437 53 Axtel, S.A.B. de C.V., MX 7303 1508 1022 191 Telecom Argentina S.A., AR 28573 1033 2253 175 CLARO S.A., BR 6147 1010 377 27 Telefonica del Peru S.A.A., PE 3816 1006 506 120 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 928 126 84 Alestra, S. de R.L. de C.V., MX 18881 908 1074 29 TELEFÔNICA BRASIL S.A, BR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1150 397 49 LINKdotNET-AS, EG 37611 821 107 9 Afrihost, ZA 36903 741 372 137 MT-MPLS, MA 36992 707 1396 40 ETISALAT-MISR, EG 24835 637 850 15 RAYA-AS, EG 8452 625 1730 18 TE-AS TE-AS, EG 29571 466 68 12 ORANGE-COTE-IVOIRE, CI 37492 450 376 81 ORANGE-, TN 15399 362 35 7 WANANCHI-, KE 37342 361 32 1 MOVITEL, MZ Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5416 4192 74 ERX-CERNET-BKB China Education and Rese 8151 4325 3385 575 Uninet S.A. de C.V., MX 12479 3974 1504 540 UNI2-AS, ES 7545 3709 410 426 TPG-INTERNET-AP TPG Telecom Limited, AU 10620 3599 540 261 Telmex Colombia S.A., CO 39891 3522 203 20 ALJAWWALSTC-AS, SA 6327 3375 1323 86 SHAW - Shaw Communications Inc., CA 22773 3290 2988 150 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 4766 2849 11131 780 KIXS-AS-KR Korea Telecom, KR 9829 2808 1499 542 BSNL-NIB National Internet Backbone, IN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 8151 4325 3750 Uninet S.A. de C.V., MX 39891 3522 3502 ALJAWWALSTC-AS, SA 12479 3974 3434 UNI2-AS, ES 10620 3599 3338 Telmex Colombia S.A., CO 6327 3375 3289 SHAW - Shaw Communications Inc., CA 7545 3709 3283 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3290 3140 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 2674 2612 VIETEL-AS-AP Viettel Group, VN 9394 2638 2609 CTTNET China TieTong Telecommunications Corpora 11830 2639 2554 Instituto Costarricense de Electricidad y Telec Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 230105 UNALLOCATED 38.110.79.0/24 23015 CMC180-TOR-AS - Cambridge Merc 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW 65537 DOCUMENT 62.162.120.0/24 6821 MT-AS-OWN bul. Orce Nikolov bb 419333 UNALLOCATED 84.17.91.0/24 41933 IPRAGAZ-AS Istanbul/ TURKEY, T 65024 PRIVATE 87.103.234.0/24 39407 CHITATELECOM-AS, RU 65024 PRIVATE 95.189.78.0/24 39407 CHITATELECOM-AS, RU 65024 PRIVATE 95.189.80.0/22 39407 CHITATELECOM-AS, RU 64111 UNALLOCATED 98.159.5.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64111 UNALLOCATED 98.159.7.0/24 19555 KMI-NETWORK - Kinder Morgan, I Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 100.66.224.0/19 209 CENTURYLINK-US-LEGACY-QWEST - Qwest Communicati 100.127.16.0/23 28885 OMANTEL-NAP-AS OmanTel NAP, OM 100.127.18.0/23 28885 OMANTEL-NAP-AS OmanTel NAP, OM Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 27.100.7.0/24 56096 UNKNOWN 41.76.136.0/22 37500 -Reserved AS-, ZZ 41.76.136.0/24 37500 -Reserved AS-, ZZ 41.76.138.0/24 37500 -Reserved AS-, ZZ 41.76.139.0/24 37500 -Reserved AS-, ZZ 41.76.140.0/22 37500 -Reserved AS-, ZZ 41.76.140.0/24 37500 -Reserved AS-, ZZ 41.76.141.0/24 37500 -Reserved AS-, ZZ 41.76.142.0/24 37500 -Reserved AS-, ZZ 41.76.143.0/24 37500 -Reserved AS-, ZZ Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:14 /9:11 /10:37 /11:100 /12:288 /13:563 /14:1096 /15:1903 /16:13368 /17:7800 /18:13616 /19:25164 /20:39207 /21:45113 /22:85887 /23:69263 /24:386496 /25:844 /26:604 /27:664 /28:35 /29:20 /30:17 /31:4 /32:56 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3166 3375 SHAW - Shaw Communications Inc., CA 39891 2946 3522 ALJAWWALSTC-AS, SA 12479 2721 3974 UNI2-AS, ES 22773 2543 3290 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2061 2167 MEGAPATH5-US - MegaPath Corporation, US 11830 1987 2639 Instituto Costarricense de Electricidad y Telec 30036 1698 1947 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1603 3599 Telmex Colombia S.A., CO 8551 1556 2093 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11492 1549 1778 CABLEONE - CABLE ONE, INC., US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1579 2:823 4:19 5:2817 6:59 7:1 8:1118 9:1 12:1880 13:182 14:1733 15:29 16:3 17:197 18:68 20:47 21:4 23:2588 24:2153 25:2 27:2260 31:1970 32:89 35:26 36:501 37:2748 38:1446 39:251 40:119 41:3018 42:602 43:1958 44:100 45:4030 46:3049 47:203 49:1345 50:1052 51:49 52:998 54:370 55:5 56:12 57:42 58:1536 59:1008 60:428 61:2133 62:1812 63:1802 64:4736 65:2218 66:4584 67:2354 68:1148 69:3200 70:1144 71:559 72:2112 74:2717 75:411 76:425 77:1550 78:1693 79:1883 80:1485 81:1424 82:1080 83:783 84:1023 85:2079 86:589 87:1310 88:928 89:2324 90:201 91:6309 92:1176 93:2379 94:2400 95:2749 96:657 97:356 98:932 99:133 100:80 101:1430 102:40 103:17431 104:3306 105:225 106:644 107:1792 108:708 109:2701 110:1580 111:1780 112:1314 113:1340 114:1119 115:1635 116:1648 117:1713 118:2163 119:1672 120:958 121:1053 122:2463 123:1800 124:1450 125:1900 128:986 129:637 130:448 131:1592 132:670 133:196 134:1005 135:227 136:451 137:499 138:1950 139:578 140:424 141:688 142:795 143:963 144:798 145:456 146:1168 147:756 148:1566 149:720 150:722 151:1057 152:760 153:311 154:1012 155:764 156:855 157:786 158:625 159:1652 160:929 161:732 162:2581 163:528 164:1035 165:1402 166:419 167:1402 168:3043 169:815 170:3716 171:428 172:1074 173:1960 174:883 175:767 176:1870 177:3969 178:2421 179:1198 180:2244 181:2197 182:2454 183:1139 184:918 185:13114 186:3587 187:2354 188:2767 189:2009 190:8136 191:1443 192:9830 193:5865 194:4787 195:3934 196:2476 197:1405 198:5505 199:5895 200:7439 201:5007 202:10424 203:10124 204:4520 205:2843 206:3073 207:3196 208:3977 209:3934 210:4031 211:2112 212:3018 213:2739 214:907 215:60 216:5851 217:2117 218:899 219:621 220:1722 221:999 222:1041 223:1233 End of report

1 0

xtube.com/ultradns/dynect zone issues
by Feldman, Mark 30 Mar '18

30 Mar '18

If folks from xtube.com/ultradns/dynect are on the list, it appears that there’s a discrepancy in the xtube.com zone being served by the some auths. At least one of the CNAMEs required for resolution is missing from the zone being served by at least some ultra instances. No idea where the breakdown is, but we’ve got customers telling the world that we’re blocking access to porn. I’ll also note that the SOA ttl and ncache are on the large side, so we’re caching those NXDOMAINs for quite a while. Flushing is just playing whack-a-mole at the moment. Also, if folks from any large auths want to provide me with contact info, we’ll happily reach out to you privately/directly should something similar occur in the future . Mark Comcast TPX Core Network Services

1 0

Network Services Forms/methods for tracking
by Craig 30 Mar '18

30 Mar '18

Could anyone that operates in a ISP or large enterprise that deals with many different customers/clients discuss some methods you handle network service requests. - Do you have/use an online form? - How is it tracked, IE a service request #, circuit ID, etc? - Can the customer look up the info to see if their request is completed? - Can engineers reference this info when issues arrise, and customers call in for support? - Pros/cons about the method you are using now? once the information is gathered how is it verified? (sometimes clients/customers don't know what they need....) and finally what information does the engineer receive to complete the build of the network service? does the engineer update the information when the network service is build out so its tracked? I am looking to get some feedback on some better ways to handle network requests, service providers would probably have good feedback on this that can facilitate collecting all the info needed, adding to the info once the build is completed and then having something that can be accessed when any t-shooting is required, and also if the service is to be decommissioned. Any feedback is appreciated; craig

1 0

new diffserv code point LE PHB
by Mikael Abrahamsson 30 Mar '18

30 Mar '18

Hi, I would like to bring attention to the following IETF draft: https://tools.ietf.org/html/draft-ietf-tsvwg-le-phb-04 I believe this is well under way through the IETF process, and if someone has strong opinions on it they should speak up. I am one of the proponents, as I posted to this list back in 2015: https://mailman.nanog.org/pipermail/nanog/2015-July/077040.html I think it's a great idea to have a diffserv code point that is supposed to be treated less than best effort (for backup traffic for instance), but it would be nice if someone would be willing to deploy support for it as well. Thoughts? -- Mikael Abrahamsson email: swmike(a)swm.pp.se

3 2

Fwd: [vicky@isc.org: Planning to stop exporting BIND libraries]
by Rich Kulawiec 29 Mar '18

29 Mar '18

Forwarding here to expose it to a larger, possibly-interested audience. ---rsk ----- Forwarded message from Victoria Risk <vicky(a)isc.org> ----- > From: Victoria Risk <vicky(a)isc.org> > Date: Fri, 23 Mar 2018 12:30:26 +0000 > To: bind-announce(a)lists.isc.org > Subject: Planning to stop exporting BIND libraries > > BIND currently exports number of libraries, including libisc, libisccfg, libirs, libisccc, libdns and libbind9. > > We don???t know of any external projects that use these libraries. Keeping the ABI and API stable is big burden, and we are exploring the possibility of merging all the libraries into a tightly-coupled private library that wouldn't be used outside of BIND (and tools). This change would effectively make those libraries private. > > BIND 9.14 in 2019 would be the first release that would drop the libraries. > > The BIND 9.11 ESV would keep those libraries until 2022, so any external users would have enough time to migrate to other DNS libraries. > > Known external users of libisc and friends: > - ISC DHCP (will continue using BIND 9.11 libraries) > - dnsperf (either use BIND 9.11 libraries, or offer ISC project) > > Please let us know if you see a significant problem with this plan, including which library you are using and how you are using it. > > Thank you > > Vicky > > ------------- > Victoria Risk > Product Manager > Internet Systems Consortium > vicky(a)isc.org > > ----- End forwarded message -----

1 0

RIPE NCC Global IPv6 Deployment Survey
by Massimiliano Stucchi 29 Mar '18

29 Mar '18

Hi, just a little reminder that there are a few days left to help the RIPE NCC by filling up our Global IPv6 Deployment Survey. We have already received a considerable amount of responses, but would like to hear from more people. The goal of the survey is to get an overview of IPv6 deployment across the world, and to assess how this is seen from the perspective of ISPs and Enterprise users. The 2018 survey is a follow up to similar surveys run between 2008 and 2013, and will serve as a comparison with the data acquired back then. You can find the survey at the following address: https://www.surveymonkey.com/r/GlobalIPv6survey2018 Responses can be submitted until 31 March 2018. We will then collect the data with the aim of presenting the preliminary results during the upcoming RIPE 76 meeting in Marseille. If you have any question about the survey, please feel free to email us at: ipv6survey2018(a)ripe.net. Thank you very much in advance for your participation! -- Massimiliano Stucchi IPv6 Programme Manager RIPE NCC mstucchi(a)ripe.net Follow us on Twitter for the fastest and latest RIPE NCC Training news! @TrainingRIPENCC

1 0

aol login problems - my.screenname.aol.com
by Aaron Gould 29 Mar '18

29 Mar '18

When going to aol.com and click "login/join" in top-right corner, brings you to a login page. when I try to login, I get nothing. just tries and tries to take me to the next page, which seems to be my.screenname.aol.com. but it never gets there. If I try from different subnets in my network, it does work. But from other subnets it does not. Has anyone ever heard/seen this problem ? Anyone from aol here that can assist with this please ? You can contact me directly if you can assist. -Aaron

1 0

Re: validating reachability via an ISP
by Baldur Norddahl 29 Mar '18

29 Mar '18

Also the only traffic you will be receiving on the other provider will be from parties that did not pick up the more specific prefix. It should therefore be really obvious. You should not receive any traffic at all, not even from the transit provider. Regards, Baldur Den tor. 29. mar. 2018 10.41 skrev Baldur Norddahl < baldur.norddahl(a)gmail.com>: > If your prefix is larger than /24 you can test with a more specific prefix > such as a /24. Announce the test prefix on just one transit provider. Then > check with BGP services such as the looking glass service provided by the > NLNOG RING network. > > There will be no interruption in the traffic as it will follow the less > specific prefix everywhere the test prefix was not picked up. > > If you only have a /24 you will need to test in a service window. > > Regards > > Baldur > > > Den tor. 29. mar. 2018 01.24 skrev Andy Litzinger < > andy.litzinger.lists(a)gmail.com>: > >> Hi all, >> I have an enterprise network and do not provide transit. In one of our >> datacenters we have our own prefixes and rely on two ISPs as BGP neighbors >> to provide global reachability for our prefixes. One is a large regional >> provider and the other is a large global provider. >> >> Recently we took our link to the global provider offline to perform >> maintenance on our router. Nearly immediately we were hit with alerts >> that >> our prefix was unreachable and BGPMon alerted that nearly 80 AS's noted >> our >> route had been withdrawn. We were not unreachable from every AS, but we >> certainly were from some of the largest. >> >> The root cause is that the our prefix is not being adequately >> re-distributed globally by the regional ISP. This is unexpected and we >> are >> working through this with them now. >> >> My question is, how can I monitor global reachability for a prefix via >> this >> or any specific provider I use over time? Are there various route-servers >> I can programmatically query for my prefix and get results that include AS >> paths? Then I could verify that an "acceptable" number of paths exist that >> include the AS of the all the ISPs I rely upon. And what would an >> "acceptable" number of alternate paths be? >> >> >> thanks in advance, >> -andy >> >

1 0

Québec Sales tax
by Jean-Francois Mezei 28 Mar '18

28 Mar '18

Not quite networking but probably relevant. The Canadian province of Québec just introduced a new budget with basically the intent to force foreign digital companies who sell services to Québekers to collect the local value added sales tax and remit those to the QC government. The goal is to capture tax from Netflix who has so far escaped taxation in Canada by having no legal/physical presence in Canada, no cache servers of its own etc. Netflix does not currently collect province information from customers (or any address info for that matter). They based many of their arguments on an OECD study (which ironically the Canadian federal government says is not completed yet (as excuse for not proceeding with similar tax). So foreign digital services will be required to require subscibers enter AND VALIDATE their address so that they have an accurate province field (validation remains to be finalized), and IF they sell more than $30,000 to Québec residents, will be required to self register with QC government to collect local sales tax (and remit to QC government). The Québec budget expects that validation of address will be based on IP address geolocation or custoemrs send paper bills to prove place of residence. (Although requiring full address/phone number and sendint this to credit card network for authorization might constitute a better means to validate address). I suspect the big winners will be VPN services in the USA :-) Because many ISPs span multiple provinces, IP geolocation generally points to their HQ address, not necessarily the province of the subscriber. (This is especially true for DSL in bell Canada wholesale where currently a single point of connection between Bell and ISP allows full reach of all of its DSL territory in QC/ON. For Cable, ISPs require different IP pools for Rogers in Ontario and Vidéotron in Ontario (with a couple of exceptions where Vidéotron has service in a couple fo Ontario towns). In Western Canada, things are harder as Shaw serves BC, AB, SASK and MB.

4 7