November 2018 - Test - lists.nanog.org

at&t abuse
by Erik Montemer 20 Nov '18

20 Nov '18

Hello,Can some from at&t rbl abuse please contact me off list? Having difficulty with RBL delisting through the appropriate and recommended channels.Thank you,Erik

1 0

Amazon now controls 3.0.0.0/8
by Eric Kuhnke 20 Nov '18

20 Nov '18

https://news.ycombinator.com/item?id=18407173 Quoting from the post: " Apparently bought in two chunks: 3.0.0.0/9 and 3.128.0.0/9. Previous owner was GE. Anecdotal reports across the Internet that AWS EIPs are now being assigned in that range. https://whois.arin.net/rest/net/NET-3-0-0-0-1.html https://whois.arin.net/rest/net/NET-3-128-0-0-1.html "

16 18

IGP protocol
by im 19 Nov '18

19 Nov '18

goodmorning nanog, I heard that OSPF is only famous in asia region... So that, please could you explain me 1. what is your backbone's IGP protocol? 2. why you choose it? thanks,

24 39

DAZN Geolocation issue
by Sam Roche 17 Nov '18

17 Nov '18

Are there any DAZN contacts on-list? We are having geolocation issues with a few IP blocks we purchased last summer. Please contact me off list. Thanks, Sam. Sam Roche | Supervisor of Network Operations | Lakeland Networks Support: support(a)lakelandnetworks.com 705-646-1846 | Direct: sroche(a)lakelandnetworks.com 705-640-0086 | www.lakelandnetworks.com<http://www.lakelandnetworks.com>

1 0

Weekly Routing Table Report
by cscora＠apnic.net 16 Nov '18

16 Nov '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 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 17 Nov, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 726297 Prefixes after maximum aggregation (per Origin AS): 279323 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 348399 Total ASes present in the Internet Routing Table: 62474 Prefixes per ASN: 11.63 Origin-only ASes present in the Internet Routing Table: 53901 Origin ASes announcing only one prefix: 23425 Transit ASes present in the Internet Routing Table: 8573 Transit-only ASes present in the Internet Routing Table: 254 Average AS path length visible in the Internet Routing Table: 4.0 Max AS path length visible: 40 Max AS path prepend of ASN ( 22394) 37 Prefixes from unregistered ASNs in the Routing Table: 34 Number of instances of unregistered ASNs: 34 Number of 32-bit ASNs allocated by the RIRs: 24905 Number of 32-bit ASNs visible in the Routing Table: 20153 Prefixes from 32-bit ASNs in the Routing Table: 86126 Number of bogon 32-bit ASNs visible in the Routing Table: 17 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 263 Number of addresses announced to Internet: 2862740641 Equivalent to 170 /8s, 161 /16s and 244 /24s Percentage of available address space announced: 77.3 Percentage of allocated address space announced: 77.3 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: 242331 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 198594 Total APNIC prefixes after maximum aggregation: 56383 APNIC Deaggregation factor: 3.52 Prefixes being announced from the APNIC address blocks: 196021 Unique aggregates announced from the APNIC address blocks: 80441 APNIC Region origin ASes present in the Internet Routing Table: 9236 APNIC Prefixes per ASN: 21.22 APNIC Region origin ASes announcing only one prefix: 2584 APNIC Region transit ASes present in the Internet Routing Table: 1369 Average APNIC Region AS path length visible: 4.0 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 4219 Number of APNIC addresses announced to Internet: 768640640 Equivalent to 45 /8s, 208 /16s and 134 /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: 215480 Total ARIN prefixes after maximum aggregation: 102201 ARIN Deaggregation factor: 2.11 Prefixes being announced from the ARIN address blocks: 214804 Unique aggregates announced from the ARIN address blocks: 102213 ARIN Region origin ASes present in the Internet Routing Table: 18304 ARIN Prefixes per ASN: 11.74 ARIN Region origin ASes announcing only one prefix: 6806 ARIN Region transit ASes present in the Internet Routing Table: 1835 Average ARIN Region AS path length visible: 3.6 Max ARIN Region AS path length visible: 40 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2505 Number of ARIN addresses announced to Internet: 1103190176 Equivalent to 65 /8s, 193 /16s and 88 /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: 198202 Total RIPE prefixes after maximum aggregation: 94737 RIPE Deaggregation factor: 2.09 Prefixes being announced from the RIPE address blocks: 194634 Unique aggregates announced from the RIPE address blocks: 115231 RIPE Region origin ASes present in the Internet Routing Table: 25636 RIPE Prefixes per ASN: 7.59 RIPE Region origin ASes announcing only one prefix: 11479 RIPE Region transit ASes present in the Internet Routing Table: 3546 Average RIPE Region AS path length visible: 4.1 Max RIPE Region AS path length visible: 36 Number of RIPE region 32-bit ASNs visible in the Routing Table: 7587 Number of RIPE addresses announced to Internet: 715506304 Equivalent to 42 /8s, 165 /16s and 194 /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: 93976 Total LACNIC prefixes after maximum aggregation: 21764 LACNIC Deaggregation factor: 4.32 Prefixes being announced from the LACNIC address blocks: 95375 Unique aggregates announced from the LACNIC address blocks: 41696 LACNIC Region origin ASes present in the Internet Routing Table: 7804 LACNIC Prefixes per ASN: 12.22 LACNIC Region origin ASes announcing only one prefix: 2147 LACNIC Region transit ASes present in the Internet Routing Table: 1481 Average LACNIC Region AS path length visible: 4.8 Max LACNIC Region AS path length visible: 32 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 5349 Number of LACNIC addresses announced to Internet: 172593664 Equivalent to 10 /8s, 73 /16s and 146 /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: 20010 Total AfriNIC prefixes after maximum aggregation: 4210 AfriNIC Deaggregation factor: 4.75 Prefixes being announced from the AfriNIC address blocks: 25200 Unique aggregates announced from the AfriNIC address blocks: 8571 AfriNIC Region origin ASes present in the Internet Routing Table: 1219 AfriNIC Prefixes per ASN: 20.67 AfriNIC Region origin ASes announcing only one prefix: 409 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: 26 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 493 Number of AfriNIC addresses announced to Internet: 102417408 Equivalent to 6 /8s, 26 /16s and 196 /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 4639 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4610 518 515 TPG-INTERNET-AP TPG Telecom Limited, AU 7552 3012 1154 94 VIETEL-AS-AP Viettel Group, VN 45899 2947 1689 111 VNPT-AS-VN VNPT Corp, VN 4766 2799 11130 764 KIXS-AS-KR Korea Telecom, KR 9829 2747 1496 551 BSNL-NIB National Internet Backbone, IN 9808 2428 8699 26 CMNET-GD Guangdong Mobile Communication 9394 2407 4907 31 CTTNET China TieTong Telecommunications 17974 2247 968 51 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4755 2123 421 172 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 3486 1324 84 SHAW - Shaw Communications Inc., CA 11492 3466 224 627 CABLEONE - CABLE ONE, INC., US 22773 3277 2973 166 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 16509 2503 5215 930 AMAZON-02 - Amazon.com, Inc., US 18566 2154 405 109 MEGAPATH5-US - MegaPath Corporation, US 20115 2145 2739 544 CHARTER-NET-HKY-NC - Charter Communicat 16625 2121 1146 1574 AKAMAI-AS - Akamai Technologies, Inc., 5650 2086 3074 1461 FRONTIER-FRTR - Frontier Communications 30036 2066 347 135 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 2044 5079 594 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 5092 1613 133 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 8551 3038 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2579 569 1918 AKAMAI-ASN1, US 12389 2186 2194 617 ROSTELECOM-AS, RU 34984 2042 337 540 TELLCOM-AS, TR 9121 1845 1691 17 TTNET, TR 13188 1605 100 42 TRIOLAN, UA 8402 1285 544 14 CORBINA-AS OJSC "Vimpelcom", RU 6849 1218 355 21 UKRTELNET, 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 5462 3313 605 Uninet S.A. de C.V., MX 10620 3120 475 885 Telmex Colombia S.A., CO 11830 2668 370 75 Instituto Costarricense de Electricidad 6503 1660 449 54 Axtel, S.A.B. de C.V., MX 7303 1441 963 208 Telecom Argentina S.A., AR 28573 1192 2237 191 CLARO S.A., BR 6147 1111 377 29 Telefonica del Peru S.A.A., PE 3816 1021 512 118 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 938 145 72 Alestra, S. de R.L. de C.V., MX 13999 922 537 260 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 1167 394 29 LINKdotNET-AS, EG 37611 905 107 9 Afrihost, ZA 36903 796 400 142 MT-MPLS, MA 36992 763 1411 43 ETISALAT-MISR, EG 8452 649 1728 15 TE-AS TE-AS, EG 24835 641 680 21 RAYA-AS, EG 37492 467 470 57 ORANGE-, TN 29571 464 70 12 ORANGE-COTE-IVOIRE, CI 23889 401 231 15 MauritiusTelecom, MU 15399 396 45 11 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 5462 3313 605 Uninet S.A. de C.V., MX 12479 5092 1613 133 UNI2-AS, ES 4538 4639 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4610 518 515 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 203 20 ALJAWWALSTC-AS, SA 6327 3486 1324 84 SHAW - Shaw Communications Inc., CA 11492 3466 224 627 CABLEONE - CABLE ONE, INC., US 22773 3277 2973 166 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3120 475 885 Telmex Colombia S.A., CO 8551 3038 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 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 5092 4959 UNI2-AS, ES 4538 4639 4565 ERX-CERNET-BKB China Education and Research Net 7545 4610 4095 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 3758 ALJAWWALSTC-AS, SA 6327 3486 3402 SHAW - Shaw Communications Inc., CA 22773 3277 3111 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8551 3038 2995 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 7552 3012 2918 VIETEL-AS-AP Viettel Group, VN 11492 3466 2839 CABLEONE - CABLE ONE, INC., US 45899 2947 2836 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 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 64121 UNALLOCATED 98.159.9.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64121 UNALLOCATED 98.159.12.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64140 UNALLOCATED 98.159.14.0/24 64121 UNKNOWN 65001 PRIVATE 109.161.56.0/24 13118 ASN-YARTELECOM PJSC Rostelecom 92937 UNALLOCATED 110.49.72.0/24 45458 SBN-AWN-AS-02-AP SBN-ISP/AWN-I 4230060012 PRIVATE 132.190.106.0/24 64673 -Private Use AS-, ZZ 4230060012 PRIVATE 132.190.232.0/24 64673 -Private Use AS-, ZZ 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.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 45.252.236.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:14 /9:11 /10:36 /11:99 /12:290 /13:567 /14:1118 /15:1896 /16:13312 /17:7873 /18:13825 /19:25455 /20:39503 /21:46131 /22:90381 /23:74057 /24:409466 /25:828 /26:646 /27:653 /28:37 /29:20 /30:21 /31:4 /32:54 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 3916 5092 UNI2-AS, ES 6327 3258 3486 SHAW - Shaw Communications Inc., CA 39891 2946 3778 ALJAWWALSTC-AS, SA 11492 2754 3466 CABLEONE - CABLE ONE, INC., US 22773 2529 3277 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8551 2494 3038 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 18566 2048 2154 MEGAPATH5-US - MegaPath Corporation, US 11830 2012 2668 Instituto Costarricense de Electricidad y Telec 30036 1815 2066 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 5650 1761 2086 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:1626 2:891 4:18 5:2721 6:43 7:1 8:1143 12:1872 13:254 14:1877 15:34 16:3 17:196 18:58 20:48 23:2547 24:2420 25:2 27:2528 31:2007 32:85 35:31 36:535 37:2937 38:1567 39:272 40:120 41:3189 42:726 43:1987 44:133 45:6061 46:3057 47:237 49:1314 50:1071 51:318 52:1109 54:362 55:1 56:6 57:41 58:1701 59:1032 60:463 61:2093 62:1879 63:1799 64:5069 65:2199 66:4813 67:2643 68:1157 69:3372 70:1179 71:602 72:2236 74:2724 75:411 76:495 77:1691 78:1747 79:2219 80:1590 81:1416 82:1058 83:813 84:1067 85:2113 86:569 87:1497 88:938 89:2388 90:210 91:6481 92:1285 93:2389 94:2391 95:3078 96:913 97:348 98:940 99:161 100:87 101:1167 102:277 103:19218 104:3605 105:241 106:876 107:1828 108:705 109:3425 110:1635 111:1827 112:1407 113:1328 114:1146 115:1698 116:1662 117:1879 118:2207 119:1675 120:1118 121:1036 122:2344 123:1686 124:1454 125:1952 128:1211 129:667 130:513 131:1630 132:718 133:191 134:1039 135:229 136:532 137:668 138:1959 139:742 140:564 141:755 142:805 143:1011 144:842 145:498 146:1250 147:767 148:1686 149:781 150:769 151:996 152:890 153:325 154:2055 155:955 156:1581 157:844 158:653 159:1865 160:1467 161:884 162:2639 163:757 164:1113 165:1595 166:460 167:1340 168:3158 169:865 170:3997 171:499 172:1051 173:2103 174:988 175:832 176:2197 177:3999 178:2513 179:1310 180:2171 181:2379 182:2598 183:1481 184:1139 185:14352 186:3608 187:2483 188:2923 189:2027 190:8322 191:1387 192:9910 193:6422 194:5247 195:4034 196:2992 197:1790 198:5665 199:5997 200:7314 201:5003 202:10246 203:10195 204:4613 205:2996 206:3260 207:3220 208:3970 209:4176 210:3857 211:2017 212:3021 213:2819 214:1047 215:55 216:6036 217:2188 218:877 219:575 220:1827 221:998 222:969 223:1402 End of report

1 0

NANOG 75 Call For Presentations Update
by BRAD RAYMO 16 Nov '18

16 Nov '18

NANOG Community, The NANOG Program Committee (PC would like to remind you that we are now accepting proposals for all sessions at NANOG 75 in San Francisco, California, February 18-20, 2019. Below is a summary of key details and dates from the Call For Presentations on the NANOG website, which can be found at http://www.cvent.com/d/1bqspy/6K. *Due to the holidays, we have extended the deadline for slides to be submitted to December 17th.* The NANOG PC seeks proposals for presentations, panels, tutorials, and track sessions for the NANOG 75 program. We welcome suggestions of speakers or topic ideas. Presentations may cover current technologies already deployed or soon-to-be deployed in the Internet. Vendors are welcome to submit talks which cover relevant technologies and capabilities, but presentations must not be promotional or discuss proprietary solutions. NANOG 75 submissions can be entered on the NANOG Program Committee Tool (PC Tool) at: https://pc.nanog.org The primary speaker, moderator, or author should submit a presentation proposal and an abstract in the PC Tool. -- Select “Propose Talk” from the Talks menu -- Select NANOG 75 from the Meeting menu -- Select the appropriate *Session* the talk will be presented in = General Session (30-45 minutes) = Tutorial (90-120 minutes) = Track (90-120 minutes) Timeline for submission and proposal review: -- Submitter enters abstract (and draft slides if possible) in PC Tool prior to deadline for slide submission -- PC performs initial review and assigns a “shepherd” to help develop the submission - within 2 weeks -- Submitter develops draft slides of talk if not already submitted with initial proposal. Please submit initial draft slides early -- Panel and Track submissions should provide topic list and intended/confirmed participants in the abstract -- PC reviews slides and continues to work with Submitter as needed to develop topic -- Draft presentation slides should be submitted prior to published deadline for slides -- PC accepts or declines submission -- Agenda assembled and posted -- Submitters notified If you think you have an interesting topic but want feedback or suggestions for developing an idea into a presentation, please email the Program Committee, and a representative will respond. Otherwise, submit your talk, keynote, track, or panel proposal to the PC Tool without delay! We look forward to reviewing your submission. Key Dates for NANOG 75: Oct. 29, 2018: CFP Opens & Agenda Outline Posted *Dec. 17, 2018: CFP Deadline: Presentation Slides Due* Jan. 14, 2019: CFP Topic List & NANOG Meeting Highlights Page Jan. 22, 2019: NANOG 75 Agenda Published Feb. 11, 2019: Speaker FINAL presentations to PC tool or speaker-support Feb. 17, 2019: Lightning Talk Submissions Open (Abstracts Only) Feb. 17, 2019: Onsite Registration Final slides MUST be submitted by Monday, February 11, 2018, and no changes will be accepted between that date and the conference. Materials received after that date will be updated on the web site after the completion of the conference. We look forward to seeing you in February in San Francisco! Sincerely, Brad Raymo NANOG PC

1 0

Community-driven FAQ for RPKI
by Alex Band 16 Nov '18

16 Nov '18

We put together a Frequently Asked Questions document for the Resource Public Key Infrastructure (RPKI). The aim is to provide a comprehensive overview of common questions that network operators and interested parties ask about the technology itself and the deployment of it, along with peer reviewed answers. To make this truly inclusive, it is available as an open source project on Github, allowing you to fork, do a pull request with an edit or addition, or open an issue in case you have suggestion. The original content was written by David Monosov, Melchior Aelmans, Job Snijders and myself, along with contributions from network operators around the world. The Github project is available here: https://github.com/NLnetLabs/rpki-faq The contents are automatically published on the NLnet Labs website: https://nlnetlabs.nl/projects/rpki/faq/ Many thanks to the NLNOG community for getting this off the ground. Cheers, Alex

1 0

Tata Scenic routing in LAX area?
by Marcus Josephson 15 Nov '18

15 Nov '18

Anyone else seeing an odd Scenic routing in the LAX/SJE area for tata. traceroute to 23.92.178.22 (23.92.178.22), 30 hops max, 52 byte packets 1 if-ae-13-2.tcore2.lvw-los-angeles.as6453.net (64.86.252.34) 180.698 ms 180.610 ms 181.712 ms MPLS Label=344269 CoS=0 TTL=1 S=1 2 if-ae-7-2.tcore2.svw-singapore.as6453.net (180.87.15.25) 189.327 ms if-ae-7-2.tcore2.svw-singapore.as6453.net (64.86.252.37) 176.800 ms if-ae-7-2.tcore2.svw-singapore.as6453.net (64.86.252.39) 174.631 ms MPLS Label=609315 CoS=0 TTL=1 S=1 3 if-ae-20-2.tcore1.svq-singapore.as6453.net (180.87.96.21) 174.287 ms 173.370 ms 173.804 ms 4 120.29.215.202 (120.29.215.202) 179.104 ms 179.367 ms 179.324 ms 5 182.79.152.247 (182.79.152.247) 180.164 ms 182.79.152.253 (182.79.152.253) 184.816 ms 182.79.152.247 (182.79.152.247) 250.928 ms 6 unknown.telstraglobal.net (202.127.73.101) [AS 4637] 173.974 ms 173.986 ms 173.484 ms 7 i-93.sgpl-core02.telstraglobal.net (202.84.224.189) [AS 4637] 175.094 ms 175.699 ms 174.343 ms 8 i-10850.eqnx-core02.telstraglobal.net (202.84.140.46) [AS 4637] 280.686 ms 288.703 ms 280.836 ms 9 i-92.eqnx03.telstraglobal.net (202.84.247.17) [AS 4637] 278.021 ms 276.637 ms 302.249 ms 10 equinix-ix.sjc1.us.voxel.net (206.223.116.4) 174.139 ms 174.163 ms 174.067 ms [cid:image002.jpg@01D47CE9.3122B790] Marcus Josephson IP Operations mjosephson(a)inap.com This message is intended for the use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

9 10

Cisco IOS BGP Graceful-Restart Implementation query
by Florin Vlad Olariu 15 Nov '18

15 Nov '18

Hey there! In our environment we generally have ASR-1000X-2s everywhere peering via iBGP/eBGP. These routers have no redundant RPs, hence cannot keep forwarding traffic while the router reboots or crashes. As such, this is a clear example of a router that's only NSF-aware (or graceful-restart-aware) but not capable. The reason I enabled this is because, from RFC 4724: In addition, even if the speaker does not have the ability to preserve its forwarding state for any address family during BGP restart, it is still recommended that the speaker advertise the Graceful Restart Capability to its peer (as mentioned before *this is done by not including any <AFI, SAFI> in the advertised capability*). There are two reasons for doing this. The first is to indicate its intention of generating the End-of-RIB marker upon the completion of its initial routing updates, as doing this would be useful for routing convergence in general. The second is to indicate its support for a peer which wishes to perform a graceful restart. So what I would expect to see in the "show ip bgp neighbor <ip>" command, regarding Graceful Restart, would be something like the following: BGP neighbor is <IP>, remote AS <AS>, internal link [...] Neighbor capabilities: [...] Graceful Restart Capability: advertised and received Remote Restart timer is 120 seconds Address families advertised by peer: *none* Basically, GR is negotiated, but no address family is specified, effectively only using the EOR marker for routing convergence improvements. Instead, here's what the router specifies: BGP neighbor is <IP>, remote AS <AS>, internal link [...] Neighbor capabilities: [...] Graceful Restart Capability: advertised and received Remote Restart timer is 120 seconds Address families advertised by peer: *IPv4 Unicast (was not preserved, VPNv4 Unicast (was not preserved* My assumption is that the 'was not preserved' in the parentesis refers to the most recent restart of the neighbor, and it means that when the neighbor re-established the BGP connection, the GR Capability for IPv4 and VPNv4 AFIs did not set the "Forwarding bit" as specified by the GR-RFC: Once the session is re-established, if the "Forwarding State" bit for a specific address family is not set in the newly received Graceful Restart Capability, or if a specific address family is not included in the newly received Graceful Restart Capability, or if the Graceful Restart Capability is not received in the re-established session at all, then the Receiving Speaker MUST immediately remove all the stale routes from the peer that it is retaining for that address family. Clearly the Forwarding State bit is never going to be set by this type of router, due to hardware limitations. Here's my concern though: What happens when the router reboots, and the neighboring routers keep forwarding packets to this router because the GR-capabily did specify IPv4 and VPNv4 AFI/SAFI? This would clearly cause impact as traffic would be blackholed. I will try to simulate this and see how it behaves, I'll report back, but any info you have it would be greatly appreciated. -- Florin Vlad Olariu

1 0

Re: China ’s Maxim – Leave No Access Point Unexploited: The Hidden Story of China Telecom’ s BGP Hijacking
by Scott Weeks 14 Nov '18

14 Nov '18

--- alfie(a)fdx.services wrote: From: Alfie Pates <alfie(a)fdx.services> Never attribute to malice that which can be adequately explained by apathy. ------------------------------------------- Especially when they can do it without being seen as was discussed here years ago. I believe this was one of the discussions? https://www.nanog.org/meetings/nanog44/presentations/Tuesday/Kapela_steal_i… scott

1 0