- Test - lists.nanog.org

Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues
by Rich Kulawiec 12 Jan '19

12 Jan '19

The "dumpsterfire" mailing list is for the discussion of security and privacy issues related to the IoT (Internet of Things). Arguably, the entire IoT *is* a security and privacy issue, but we'll get to that in good time. If you want to join, you can either use the list's web page: http://www.firemountain.net/mailman/listinfo/dumpsterfire or the list's subscription/unsubscription address: dumpsterfire-request(a)firemountain.net The list is public and so is its archive. ---rsk

14 18

Weekly Routing Table Report
by cscora＠apnic.net 11 Jan '19

11 Jan '19

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 12 Jan, 2019 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 733674 Prefixes after maximum aggregation (per Origin AS): 282062 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 353352 Total ASes present in the Internet Routing Table: 62885 Prefixes per ASN: 11.67 Origin-only ASes present in the Internet Routing Table: 54196 Origin ASes announcing only one prefix: 23519 Transit ASes present in the Internet Routing Table: 8689 Transit-only ASes present in the Internet Routing Table: 266 Average AS path length visible in the Internet Routing Table: 4.2 Max AS path length visible: 31 Max AS path prepend of ASN ( 16327) 25 Prefixes from unregistered ASNs in the Routing Table: 23 Number of instances of unregistered ASNs: 25 Number of 32-bit ASNs allocated by the RIRs: 25439 Number of 32-bit ASNs visible in the Routing Table: 20634 Prefixes from 32-bit ASNs in the Routing Table: 89143 Number of bogon 32-bit ASNs visible in the Routing Table: 18 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 288 Number of addresses announced to Internet: 2841162851 Equivalent to 169 /8s, 88 /16s and 180 /24s Percentage of available address space announced: 76.7 Percentage of allocated address space announced: 76.7 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.1 Total number of prefixes smaller than registry allocations: 245674 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 199728 Total APNIC prefixes after maximum aggregation: 57048 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 196822 Unique aggregates announced from the APNIC address blocks: 81412 APNIC Region origin ASes present in the Internet Routing Table: 9352 APNIC Prefixes per ASN: 21.05 APNIC Region origin ASes announcing only one prefix: 2635 APNIC Region transit ASes present in the Internet Routing Table: 1395 Average APNIC Region AS path length visible: 4.1 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 4356 Number of APNIC addresses announced to Internet: 769082882 Equivalent to 45 /8s, 215 /16s and 70 /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-139577 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: 217169 Total ARIN prefixes after maximum aggregation: 103060 ARIN Deaggregation factor: 2.11 Prefixes being announced from the ARIN address blocks: 216418 Unique aggregates announced from the ARIN address blocks: 103683 ARIN Region origin ASes present in the Internet Routing Table: 18314 ARIN Prefixes per ASN: 11.82 ARIN Region origin ASes announcing only one prefix: 6811 ARIN Region transit ASes present in the Internet Routing Table: 1845 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2538 Number of ARIN addresses announced to Internet: 1079462304 Equivalent to 64 /8s, 87 /16s and 73 /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, 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: 201112 Total RIPE prefixes after maximum aggregation: 95726 RIPE Deaggregation factor: 2.10 Prefixes being announced from the RIPE address blocks: 197454 Unique aggregates announced from the RIPE address blocks: 116555 RIPE Region origin ASes present in the Internet Routing Table: 25737 RIPE Prefixes per ASN: 7.67 RIPE Region origin ASes announcing only one prefix: 11482 RIPE Region transit ASes present in the Internet Routing Table: 3615 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 28 Number of RIPE region 32-bit ASNs visible in the Routing Table: 7720 Number of RIPE addresses announced to Internet: 716067520 Equivalent to 42 /8s, 174 /16s and 82 /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: 95416 Total LACNIC prefixes after maximum aggregation: 22002 LACNIC Deaggregation factor: 4.34 Prefixes being announced from the LACNIC address blocks: 96820 Unique aggregates announced from the LACNIC address blocks: 42306 LACNIC Region origin ASes present in the Internet Routing Table: 7964 LACNIC Prefixes per ASN: 12.16 LACNIC Region origin ASes announcing only one prefix: 2166 LACNIC Region transit ASes present in the Internet Routing Table: 1486 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 31 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 5513 Number of LACNIC addresses announced to Internet: 173145344 Equivalent to 10 /8s, 81 /16s and 253 /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: 20225 Total AfriNIC prefixes after maximum aggregation: 4208 AfriNIC Deaggregation factor: 4.81 Prefixes being announced from the AfriNIC address blocks: 25872 Unique aggregates announced from the AfriNIC address blocks: 9135 AfriNIC Region origin ASes present in the Internet Routing Table: 1236 AfriNIC Prefixes per ASN: 20.93 AfriNIC Region origin ASes announcing only one prefix: 425 AfriNIC Region transit ASes present in the Internet Routing Table: 245 Average AfriNIC Region AS path length visible: 4.4 Max AfriNIC Region AS path length visible: 20 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 507 Number of AfriNIC addresses announced to Internet: 102989312 Equivalent to 6 /8s, 35 /16s and 126 /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 4645 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4622 519 520 TPG-INTERNET-AP TPG Telecom Limited, AU 7552 3044 1160 91 VIETEL-AS-AP Viettel Group, VN 45899 2990 1721 112 VNPT-AS-VN VNPT Corp, VN 4766 2810 11129 767 KIXS-AS-KR Korea Telecom, KR 9829 2749 1496 551 BSNL-NIB National Internet Backbone, IN 9808 2465 8699 26 CMNET-GD Guangdong Mobile Communication 9394 2405 4906 29 CTTNET China TieTong Telecommunications 4755 2143 437 181 TATACOMM-AS TATA Communications formerl 17974 2088 968 50 TELKOMNET-AS2-AP PT Telekomunikasi Indo 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 3511 1326 92 SHAW - Shaw Communications Inc., CA 11492 3486 225 599 CABLEONE - CABLE ONE, INC., US 22773 3310 2979 174 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 16509 2608 5389 982 AMAZON-02 - Amazon.com, Inc., US 16625 2210 1233 1699 AKAMAI-AS - Akamai Technologies, Inc., 20115 2150 2754 533 CHARTER-20115 - Charter Communications, 18566 2136 405 108 MEGAPATH5-US - MegaPath Corporation, US 30036 2101 350 134 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 5650 2087 3074 1462 FRONTIER-FRTR - Frontier Communications 209 2074 5077 589 CENTURYLINK-US-LEGACY-QWEST - CenturyLi 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 5277 1628 138 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 8551 3290 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2635 575 1936 AKAMAI-ASN1, US 12389 2228 2221 626 ROSTELECOM-AS, RU 34984 2055 338 523 TELLCOM-AS, TR 9121 1736 1691 17 TTNET, TR 13188 1604 100 46 TRIOLAN, UA 8402 1301 545 15 CORBINA-AS OJSC "Vimpelcom", RU 9009 1242 135 695 M247, 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 5494 3319 592 Uninet S.A. de C.V., MX 10620 3150 475 905 Telmex Colombia S.A., CO 11830 2679 371 71 Instituto Costarricense de Electricidad 6503 1631 449 54 Axtel, S.A.B. de C.V., MX 7303 1441 961 226 Telecom Argentina S.A., AR 28573 1184 2239 183 CLARO S.A., BR 6147 1084 377 29 Telefonica del Peru S.A.A., PE 3816 1026 511 112 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 935 143 66 Alestra, S. de R.L. de C.V., MX 13999 928 535 250 Mega Cable, S.A. 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 1162 393 22 LINKdotNET-AS, EG 37611 902 107 9 Afrihost, ZA 36903 797 401 139 MT-MPLS, MA 36992 780 1411 44 ETISALAT-MISR, EG 24835 683 634 21 RAYA-AS, EG 8452 635 1731 19 TE-AS TE-AS, EG 29571 481 70 12 ORANGE-COTE-IVOIRE, CI 37492 459 470 57 ORANGE-, TN 15399 417 45 11 WANANCHI-, KE 37342 410 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 8151 5494 3319 592 Uninet S.A. de C.V., MX 12479 5277 1628 138 UNI2-AS, ES 4538 4645 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4622 519 520 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 203 20 ALJAWWALSTC-AS, SA 6327 3511 1326 92 SHAW - Shaw Communications Inc., CA 11492 3486 225 599 CABLEONE - CABLE ONE, INC., US 22773 3310 2979 174 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 8551 3290 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 10620 3150 475 905 Telmex Colombia S.A., CO Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 12479 5277 5139 UNI2-AS, ES 4538 4645 4571 ERX-CERNET-BKB China Education and Research Net 7545 4622 4102 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 3758 ALJAWWALSTC-AS, SA 6327 3511 3419 SHAW - Shaw Communications Inc., CA 8551 3290 3247 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 3310 3136 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 3044 2953 VIETEL-AS-AP Viettel Group, VN 11492 3486 2887 CABLEONE - CABLE ONE, INC., US 45899 2990 2878 VNPT-AS-VN VNPT Corp, VN 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 266842 UNALLOCATED 45.238.156.0/22 265680 HNTELCO S.A, HN 4200058511 PRIVATE 103.111.177.0/24 137522 OERL-AS-AP Origin Energy Retai 4200058511 PRIVATE 103.111.178.0/24 137522 OERL-AS-AP Origin Energy Retai 64339 UNALLOCATED 143.0.108.0/22 18747 IFX18747 - IFX Corporation, US 64355 UNALLOCATED 156.40.196.0/24 30387 NIH-NET-NCCS - National Instit 64011 UNALLOCATED 166.133.128.0/18 20057 ATT-MOBILITY-LLC-AS20057 - AT& 64011 UNALLOCATED 166.133.192.0/18 20057 ATT-MOBILITY-LLC-AS20057 - AT& 64011 UNALLOCATED 166.184.9.0/24 20057 ATT-MOBILITY-LLC-AS20057 - AT& 64011 UNALLOCATED 166.220.64.0/19 20057 ATT-MOBILITY-LLC-AS20057 - AT& Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 198.18.1.19/32 7497 CSTNET-AS-AP Computer Network Information Cente 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.140.0/22 37500 -Reserved AS-, ZZ 41.78.92.0/22 14988 BTC-GATE1, BW 41.78.180.0/23 37265 -Reserved AS-, ZZ 43.255.80.0/24 36351 SOFTLAYER - SoftLayer Technologies Inc., US 43.255.82.0/24 36351 SOFTLAYER - SoftLayer Technologies Inc., US 43.255.83.0/24 36351 SOFTLAYER - SoftLayer Technologies Inc., US 45.121.32.0/22 134356 UNKNOWN 45.124.164.0/22 38803 GTELECOM-AUSTRALIA Gtelecom-AUSTRALIA, AU 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:12 /9:10 /10:36 /11:99 /12:292 /13:568 /14:1129 /15:1916 /16:13354 /17:7872 /18:13845 /19:25525 /20:39678 /21:46133 /22:91220 /23:74692 /24:414403 /25:924 /26:822 /27:883 /28:32 /29:18 /30:9 /31:2 /32:200 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 4127 5277 UNI2-AS, ES 6327 3274 3511 SHAW - Shaw Communications Inc., CA 39891 2946 3778 ALJAWWALSTC-AS, SA 11492 2764 3486 CABLEONE - CABLE ONE, INC., US 8551 2746 3290 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2550 3310 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2031 2136 MEGAPATH5-US - MegaPath Corporation, US 11830 2024 2679 Instituto Costarricense de Electricidad y Telec 30036 1849 2101 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 5650 1761 2087 FRONTIER-FRTR - Frontier Communications of Amer Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1613 2:894 3:1 4:23 5:2776 6:43 7:1 8:1176 12:1874 13:306 14:1876 15:37 16:2 17:215 18:59 20:48 23:2566 24:2415 25:2 27:2551 31:2014 32:92 35:31 36:822 37:3006 38:1606 39:283 40:122 41:3153 42:726 43:2006 44:140 45:6525 46:3150 47:244 49:1332 50:1083 51:319 52:1081 54:363 55:1 56:6 57:41 58:1714 59:1071 60:456 61:2079 62:2206 63:1813 64:5101 65:2193 66:4817 67:2684 68:1170 69:3455 70:1145 71:601 72:2281 74:2750 75:415 76:543 77:1718 78:1747 79:2323 80:1647 81:1432 82:1068 83:878 84:1080 85:2139 86:562 87:1536 88:994 89:2398 90:213 91:6540 92:1224 93:2381 94:2401 95:3190 96:908 97:349 98:939 99:169 100:87 101:1157 102:339 103:19758 104:3573 105:243 106:895 107:1826 108:697 109:3634 110:1637 111:1867 112:1398 113:1379 114:1154 115:1709 116:1622 117:1915 118:2199 119:1684 120:1056 121:1030 122:2368 123:1640 124:1446 125:1953 128:1196 129:691 130:525 131:1622 132:716 133:213 134:1043 135:230 136:541 137:676 138:1977 139:796 140:566 141:762 142:802 143:1010 144:896 145:504 146:1246 147:774 148:1704 149:805 150:782 151:1000 152:975 153:325 154:2435 155:969 156:1640 157:859 158:656 159:1903 160:1492 161:898 162:2663 163:774 164:1118 165:1581 166:462 167:1364 168:3234 169:872 170:4039 171:497 172:1059 173:2146 174:1003 175:878 176:2290 177:4052 178:2567 179:1295 180:2089 181:2355 182:2678 183:1057 184:1136 185:14558 186:3714 187:2515 188:2976 189:2104 190:8270 191:1438 192:10038 193:6500 194:5334 195:4033 196:2913 197:1724 198:5696 199:5963 200:7395 201:5028 202:10188 203:10176 204:4635 205:3017 206:3301 207:3283 208:3945 209:4225 210:3917 211:1994 212:3081 213:2805 214:1067 215:52 216:5973 217:2188 218:889 219:575 220:1835 221:995 222:978 223:1427 End of report

1 0

Switch.com AS23005
by John Von Essen 10 Jan '19

10 Jan '19

Can someone from Switch.com / AS23005 contact me off-list? I have an IRR route object conflict issue that’s attention. John

1 0

Google Fiber v6 PD only giving /64
by Chris Adams 10 Jan '19

10 Jan '19

Anybody here from Google Fiber? When I first got it last year, my IPv6 setup got a /56 prefix delegated. I now see that no matter what size I request, I only get a /64. Is this intentional? -- Chris Adams <cma(a)cmadams.net>

3 2

Proofpoint Mail Delivery Issues
by Tim Donahue 10 Jan '19

10 Jan '19

Hi all, Sorry for the noise, but one of my clients is getting the standard "it's the other guy's fault" with some email delivery issues to/from Proofpoint "Enterprise" customers. If there is anyone from Proofpoint support monitoring this list, some assistance troubleshooting email delivery issues would be greatly appreciated. Thank you, Tim Donahue

7 6

Call for presentations RIPE 78
by Benno Overeinder 10 Jan '19

10 Jan '19

Dear colleagues, Please find the CFP for RIPE 78 below or at: https://ripe78.ripe.net/submit-topic/cfp/. The deadline for submissions is *3 March 2019*. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. However, on an individual basis, participants can apply for a RIPE Fellowship or RACI, see the "Speakers" paragraph in CFP for more information. Kind regards, Benno Overeinder RIPE PC Chair https://ripe78.ripe.net/ripe-pc/ -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. *RIPE 78 will take place from 20-24 May in Reykjavik, Iceland* The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 78. See the full descriptions of the different presentation formats: https://ripe78.ripe.net/submit-topic/presentation-formats/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *3 March 2019*. Proposals submitted after this date will be considered depending on the slots still available in the programme. The PC is looking for presentations covering the topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) ---- Speakers ---- Presenters, RIPE Working Group Chairs and the RIPE Programme Committee are required to cover their own costs to attend a RIPE Meeting (meeting ticket, travel and accommodation). We have various ticket options available depending on your needs. Please note that participants can apply for a RIPE Fellowship or RACI, on an individual basis, to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship https://www.ripe.net/participate/ripe/raci In extraordinary circumstances, the RIPE Chair can waive the meeting fee for presenters. These requests are dealt with on a case-by-case basis via pc(a)ripe.net. ---- Submissions ---- Presenters should be clear on whether they wish to submit a presentation for a plenary or working group (WG) session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe78.ripe.net/plenary-or-wg/ RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and should not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour (during evening sessions) - Lightning talks: 10 minutes in total for both the presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe78.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe78.ripe.net/submit-topic/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. ---- Diversity and Inclusion - On-Site Childcare and the RIPE Meeting Code of Conduct ---- Did you know that RIPE Meetings now have on-site childcare? You can reserve a spot for your child (age 6 months - 10 years) during the registration process for the meeting. Childcare places are limited, so please be quick to reserve a spot for your child while registering for the meeting. More information at: https://ripe78.ripe.net/on-site/on-site-childcare/ Ensuring that RIPE Meeting values are upheld and that attendees experience a professional, respectful and safe meeting is a priority. Please do read the RIPE Meeting Code of Conduct: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… --- If you have any questions or requests concerning content submissions, please email pc(a)ripe.net.

1 0

DNS Hijacking? - FiOS Northeast
by Blake Mckeeby 10 Jan '19

10 Jan '19

We are seeing DNS requests for A and AAAA to 8.8.8.8 come back with erroneous replies resolving to 146.112.61.106 when sent via FiOS circuits in the northeast. Anyone else seeing issues with DNS on FiOS in Northeast? Issue started around 12:25 AM ET this morning and seems to be affecting customers in PA, RI, etc.. -- Sincerely, Blake McKeeby

4 3

Centurylink/Level3 WDM?
by James Breeden 09 Jan '19

09 Jan '19

Anyone else having issues with Centurylink IP (Legacy Level3/3356) in/around Houston, or WDM issues between Houston and San Antonio? James W. Breeden Managing Partner [logo_transparent_background] Arenal Group: Arenal Consulting Group | Acilis Telecom | Pines Media PO Box 1063 | Smithville, TX 78957 Email: james(a)arenalgroup.co<mailto:james@arenalgroup.co> | office 512.360.0000 | cell 512.304.0745 | www.arenalgroup.co<http://www.arenalgroup.co/>

1 1

Report on Legal Barriers to RPKI Adoption
by Christopher S. Yoo 09 Jan '19

09 Jan '19

As many of you know, the prospects for widespread RPKI adoption grew more promising in 2018. Cloudflare issued route origin authorizations ("ROAs") to cover 25% of its prefixes, including its 1.1.1.1 resolver and DNS servers. NTT began treating RPKI ROAs as if they were IRR route(6)-objects. Google announced its intention to begin filtering routes in early 2019. The Mutually Agreed Norms for Routing Security now has over 100 network operators signed on. Still, as 2019 begins, many worry that legal issues are hindering RPKI adoption. This is especially true for North American networks, which have a comparatively low percentage of IPv4 space covered by ROAs, and whose ROAs are comparatively underutilized by parties using RPKI-based route origin validation ("ROV") to inform their routing decisions. My coauthor (David Wishnick) and I have spent the past year delving into the legal issues surrounding RPKI. Today, we are publicizing our report on how the network operator community should address these issues. It is available here<https://ssrn.com/abstract=3308619>. If you are interested in the future of routing security, we encourage you to read it (or its Executive Summary). We've tried to keep the legalese to a minimum. RPKI was a major topic of discussion at NANOG 74 and ARIN 42 in Vancouver. Going forward, we expect to continue a fruitful dialogue about how the network operator community can reduce the legal barriers to RPKI adoption. Here is a summary of our recommendations: On the ROV side of the equation, the principal legal hindrances have to do with the terms and conditions governing access to the RPKI repository offered by ARIN in its Relying Party Agreement ("RPA"), and in the manner it has employed to ensure the agreement is binding. Regarding ROV: 1. The goal of widespread ROV counsels in favor of ARIN reviewing its current approach to repository distribution, embodied in the RPA. We conclude that two paths would be reasonable. First, ARIN should consider dropping the RPA altogether. This would remove the most significant legal barriers to widespread utilization of the ARIN RPKI repository. Second, because the legal risks faced by ARIN in an RPA-free world are ultimately uncertain, it would also be reasonable for ARIN to maintain the RPA for the purposes of contractually allocating risks to the parties best positioned to reduce and mitigate them. If ARIN keeps the RPA, ARIN should consider removing the RPA's indemnification clause, instead relying solely on the RPA's disclaimers of warranties and limitations of liability, or at least reducing the indemnification clause's scope to eliminate the problem of moral hazard. 2. Developers of RPKI validation software should consider integrating acceptance of ARIN's RPA into their software workflows. ARIN recently enabled this possibility, and developers should deliberate on whether to capitalize on the opportunity. 3. The network operator community and ARIN should broadly publicize ARIN's policy of revising various RPA clauses for government entities that are prohibited from agreeing to them. 4. In addition to the important step ARIN has already taken to enable third-party software developers to integrate RPA acceptance into their software workflows, ARIN should consider reducing the barriers to third-party service development imposed by the RPA's prohibited conduct clause. Specifically, ARIN should consider methods for allowing approved developers to make use of RPKI information as an input into more sophisticated services. 5. Separately, ARIN should consider revising the prohibited conduct clause to allow broader distribution of information created with RPKI as an input for research and analysis purposes. 6. As a general alternative, the Internet community should consider whether to develop a separate corporate entity that would be responsible for operational aspects of RPKI repository provision. That corporation could conduct such activities for the North American region, or on a worldwide basis. Regarding the ROA-issuance side of the equation, the principal legal obstacles stem from the terms and conditions found in ARIN's Registration Services Agreement ("RSA"), Legacy Registration Services Agreement ("LRSA"), and RPKI Terms of Service. Regarding these, the report recommends the following: 1. ARIN should consider adopting a pathway to provide RPKI services that would explicitly refrain from altering the existing balance of property and transferability rights associated with IP address allocations. 2. The network operator community and ARIN should broadly publicize ARIN's policy of revising certain RSA/LRSA and RPKI Terms of Service clauses for government entities that are prohibited from agreeing to them. ARIN should also begin presenting the RPKI Terms of Service to newly-onboarded members alongside their RSA/LRSA, so that organizations spend less time dealing with legal issues overall. Separately, the report recommends that the network operator community consider whether to encourage companies and the federal government to include RPKI adoption in procurement best practices or requirements. In tandem with recommendations designed to encourage adoption, the report also makes two recommendations concerning operational readiness for widespread RPKI deployment. Specifically: 1. To reduce any legal risks associated with RPKI, the network operator community should focus on adopting operational best practices. No system is 100% reliable across all contingencies; as a result, operators should prepare for outages and other headaches. RPKI implementations should be resilient in the face of such contingencies. 2. The five RIRs should work to ensure readiness for widespread RPKI adoption and strive to publicize deeper details on their service-level intentions to the Internet community. This research is supported by NSF Award No. 1748362. The contents of the report represent our independent views, not those of the NSF. Any mistakes, of course, are also ours alone. Christopher S. Yoo John H. Chestnut Professor of Law, Communication, and Computer & Information Science Founding Director, Center for Technology, Innovation and Competition University of Pennsylvania Law School 3501 Sansom St. Philadelphia, PA 19104-6204 (215) 746-8772 (o) (215) 573-2025 (f) csyoo(a)law.upenn.edu<mailto:csyoo@law.upenn.edu> http://www.law.upenn.edu/faculty/csyoo/ For more information on the Center for Technology, Innovation and Competition, see https://www.law.upenn.edu/institutes/ctic/.

4 3

RE: BGP Experiment
by adamv0025＠netconsultings.com 08 Jan '19

08 Jan '19

> Steve Noble > Sent: Tuesday, January 8, 2019 6:42 PM > > There is no such thing as a fully RFC compliant BGP : > Which RFC do you mean 6286, 6608, 6793, 7606, 7607, 7705 or 8212 when you say fully RFC compliant BGP please? > https://www.juniper.net/documentation/en_US/junos/topics/reference/st > andards/bgp.html does not list 7606 > > Cisco Bug: CSCvf06327 - Error Handling for RFC 7606 not implemented for > NXOS > > This is as of today and a 2 second google search.. anyone running code from > before RFC 7606 (2015) would also not be compliant. > With regards to Revised Error Handling for BGP UPDATE Messages RFC 7606, My recollection is there was a very long discussion with working code preceding the various drafts as well as the final RFC standard. Regarding the Juniper case specifically a bit of googling reveals that: All Junos software releases built on or after 2009-06-29 have been enhanced to be more tolerant of malformed optional, transitive attributes. Releases containing the coding change specifically include: 9.1S2, 9.3R3, 9.6R1 and all subsequent releases (i.e. all releases built after 9.6R1). -so it's not quite black and white, there will be levels of protection available in current releases (albeit not fully compliant with RFC per se). Question is whether folks out there have it actually enabled. Oh and then there are bugs associated with the new feature (like the one in some versions of Junos which ,upon receiving malformed update won't bring the session down but rather the whole rpd if the bgp-error-tolerance feature is enabled ) adam

1 0