- NANOG - lists.nanog.org

Weekly Routing Table Report
by Routing Analysis Role Account 11 Mar '16

11 Mar '16

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, AusNOG, SANOG, PacNOG, SAFNOG, PaNOG, SdNOG, BJNOG, CaribNOG 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 Mar, 2016 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 586718 Prefixes after maximum aggregation (per Origin AS): 215597 Deaggregation factor: 2.72 Unique aggregates announced (without unneeded subnets): 285921 Total ASes present in the Internet Routing Table: 53056 Prefixes per ASN: 11.06 Origin-only ASes present in the Internet Routing Table: 36592 Origin ASes announcing only one prefix: 15789 Transit ASes present in the Internet Routing Table: 6412 Transit-only ASes present in the Internet Routing Table: 167 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 39 Max AS path prepend of ASN ( 40285) 34 Prefixes from unregistered ASNs in the Routing Table: 1062 Unregistered ASNs in the Routing Table: 367 Number of 32-bit ASNs allocated by the RIRs: 13030 Number of 32-bit ASNs visible in the Routing Table: 10052 Prefixes from 32-bit ASNs in the Routing Table: 39223 Number of bogon 32-bit ASNs visible in the Routing Table: 15 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 345 Number of addresses announced to Internet: 2808944324 Equivalent to 167 /8s, 109 /16s and 22 /24s Percentage of available address space announced: 75.9 Percentage of allocated address space announced: 75.9 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.0 Total number of prefixes smaller than registry allocations: 192220 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 150355 Total APNIC prefixes after maximum aggregation: 41706 APNIC Deaggregation factor: 3.61 Prefixes being announced from the APNIC address blocks: 160207 Unique aggregates announced from the APNIC address blocks: 64684 APNIC Region origin ASes present in the Internet Routing Table: 5153 APNIC Prefixes per ASN: 31.09 APNIC Region origin ASes announcing only one prefix: 1192 APNIC Region transit ASes present in the Internet Routing Table: 905 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 39 Number of APNIC region 32-bit ASNs visible in the Routing Table: 1931 Number of APNIC addresses announced to Internet: 753310980 Equivalent to 44 /8s, 230 /16s and 157 /24s Percentage of available APNIC address space announced: 88.0 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, 131072-135580 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: 179827 Total ARIN prefixes after maximum aggregation: 88882 ARIN Deaggregation factor: 2.02 Prefixes being announced from the ARIN address blocks: 184828 Unique aggregates announced from the ARIN address blocks: 87774 ARIN Region origin ASes present in the Internet Routing Table: 16409 ARIN Prefixes per ASN: 11.26 ARIN Region origin ASes announcing only one prefix: 5890 ARIN Region transit ASes present in the Internet Routing Table: 1699 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 37 Number of ARIN region 32-bit ASNs visible in the Routing Table: 1069 Number of ARIN addresses announced to Internet: 1102423104 Equivalent to 65 /8s, 181 /16s and 164 /24s Percentage of available ARIN address space announced: 58.3 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-395164 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: 141090 Total RIPE prefixes after maximum aggregation: 69682 RIPE Deaggregation factor: 2.02 Prefixes being announced from the RIPE address blocks: 149636 Unique aggregates announced from the RIPE address blocks: 92320 RIPE Region origin ASes present in the Internet Routing Table: 18052 RIPE Prefixes per ASN: 8.29 RIPE Region origin ASes announcing only one prefix: 7939 RIPE Region transit ASes present in the Internet Routing Table: 3012 Average RIPE Region AS path length visible: 4.8 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 4538 Number of RIPE addresses announced to Internet: 703641472 Equivalent to 41 /8s, 240 /16s and 183 /24s Percentage of available RIPE address space announced: 102.3 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, 196608-204287 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: 61670 Total LACNIC prefixes after maximum aggregation: 12115 LACNIC Deaggregation factor: 5.09 Prefixes being announced from the LACNIC address blocks: 75505 Unique aggregates announced from the LACNIC address blocks: 35198 LACNIC Region origin ASes present in the Internet Routing Table: 2458 LACNIC Prefixes per ASN: 30.72 LACNIC Region origin ASes announcing only one prefix: 578 LACNIC Region transit ASes present in the Internet Routing Table: 556 Average LACNIC Region AS path length visible: 4.7 Max LACNIC Region AS path length visible: 21 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 2324 Number of LACNIC addresses announced to Internet: 171050752 Equivalent to 10 /8s, 50 /16s and 7 /24s Percentage of available LACNIC address space announced: 102.0 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-265628 + 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: 14441 Total AfriNIC prefixes after maximum aggregation: 3171 AfriNIC Deaggregation factor: 4.55 Prefixes being announced from the AfriNIC address blocks: 16197 Unique aggregates announced from the AfriNIC address blocks: 5641 AfriNIC Region origin ASes present in the Internet Routing Table: 739 AfriNIC Prefixes per ASN: 21.92 AfriNIC Region origin ASes announcing only one prefix: 190 AfriNIC Region transit ASes present in the Internet Routing Table: 167 Average AfriNIC Region AS path length visible: 4.6 Max AfriNIC Region AS path length visible: 18 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 190 Number of AfriNIC addresses announced to Internet: 78155264 Equivalent to 4 /8s, 168 /16s and 142 /24s Percentage of available AfriNIC address space announced: 77.6 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 5590 4192 76 China Education and Research 4766 3144 11142 1115 Korea Telecom 7545 3089 351 184 TPG Telecom Limited 17974 2903 914 96 PT Telekomunikasi Indonesia 9829 2390 1449 427 National Internet Backbone 4755 2096 432 245 TATA Communications formerly 9808 1855 8717 30 Guangdong Mobile Communicatio 45899 1692 1094 170 VNNIC 4808 1641 2287 522 CNCGROUP IP network China169 4788 1520 645 64 TM Net, Internet Service Prov 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 22773 3343 2948 143 Cox Communications Inc. 6389 2394 3687 42 BellSouth.net Inc. 18566 2211 394 276 MegaPath Corporation 20115 1914 1921 401 Charter Communications 30036 1730 342 253 Mediacom Communications Corp 6983 1690 849 232 EarthLink, Inc. 4323 1585 1004 392 tw telecom holdings, inc. 209 1502 4483 1212 Qwest Communications Company, 701 1391 11453 660 MCI Communications Services, 11492 1259 234 594 CABLE ONE, 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 39891 2515 135 9 SaudiNet, Saudi Telecom Compa 20940 2404 925 1729 Akamai International B.V. 34984 1952 322 414 TELLCOM ILETISIM HIZMETLERI A 8551 1230 376 54 Bezeq International-Ltd 6849 1179 355 21 JSC "Ukrtelecom" 12479 1144 980 86 France Telecom Espana SA 8402 1125 544 15 OJSC "Vimpelcom" 13188 1077 98 78 TOV "Bank-Inform" 31148 1041 47 41 Freenet Ltd. 9198 949 352 25 JSC Kazakhtelecom 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 10620 3447 542 122 Telmex Colombia S.A. 8151 2221 3412 551 Uninet S.A. de C.V. 7303 1521 941 238 Telecom Argentina S.A. 11830 1442 366 25 Instituto Costarricense de El 6503 1432 453 56 Axtel, S.A.B. de C.V. 6147 1036 377 27 Telefonica del Peru S.A.A. 3816 994 478 185 COLOMBIA TELECOMUNICACIONES S 7738 994 1882 41 Telemar Norte Leste S.A. 26615 994 2325 34 Tim Celular S.A. 28573 991 2172 159 NET Serviços de Comunicação S 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 1201 402 35 Link Egypt (Link.NET) 8452 1008 1472 15 TE-AS 37611 633 48 2 Afrihost-Brevis Computer Serv 36903 584 294 104 Office National des Postes et 36992 505 1357 25 ETISALAT MISR 37492 377 217 64 Orange Tunisie 24835 338 146 12 Vodafone Data 29571 267 21 12 Cote d'Ivoire Telecom 2018 250 327 74 TENET (The UNINET Project) 36947 231 807 13 Telecom Algeria 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 5590 4192 76 China Education and Research 10620 3447 542 122 Telmex Colombia S.A. 22773 3343 2948 143 Cox Communications Inc. 4766 3144 11142 1115 Korea Telecom 7545 3089 351 184 TPG Telecom Limited 17974 2903 914 96 PT Telekomunikasi Indonesia 39891 2515 135 9 SaudiNet, Saudi Telecom Compa 20940 2404 925 1729 Akamai International B.V. 6389 2394 3687 42 BellSouth.net Inc. 9829 2390 1449 427 National Internet Backbone Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 10620 3447 3325 Telmex Colombia S.A. 22773 3343 3200 Cox Communications Inc. 7545 3089 2905 TPG Telecom Limited 17974 2903 2807 PT Telekomunikasi Indonesia 39891 2515 2506 SaudiNet, Saudi Telecom Compa 6389 2394 2352 BellSouth.net Inc. 4766 3144 2029 Korea Telecom 9829 2390 1963 National Internet Backbone 18566 2211 1935 MegaPath Corporation 4755 2096 1851 TATA Communications formerly Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65001 PRIVATE 5.143.176.0/20 15468 OJSC Rostelecom 30662 UNALLOCATED 8.2.129.0/24 3356 Level 3 Communicatio 53506 UNALLOCATED 8.17.102.0/23 3356 Level 3 Communicatio 46467 UNALLOCATED 8.19.192.0/24 46887 Lightower Fiber Netw 16589 UNALLOCATED 8.20.247.0/24 35838 CCANET Limited 16589 UNALLOCATED 8.26.56.0/24 35838 CCANET Limited 46473 UNALLOCATED 8.27.122.0/24 3356 Level 3 Communicatio 46473 UNALLOCATED 8.27.124.0/24 3356 Level 3 Communicatio 27205 UNALLOCATED 8.38.16.0/21 3356 Level 3 Communicatio 15347 UNALLOCATED 8.224.147.0/24 12064 Cox Communications I Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.226.112.0/20 62788 >>UNKNOWN<< 23.249.144.0/20 40430 colo4jax, LLC 27.100.7.0/24 56096 >>UNKNOWN<< 37.46.10.0/23 36351 SoftLayer Technologies Inc. 37.46.14.0/24 36351 SoftLayer Technologies Inc. 37.46.15.0/24 36351 SoftLayer Technologies Inc. 41.73.1.0/24 37004 >>UNKNOWN<< 41.73.2.0/24 37004 >>UNKNOWN<< 41.73.3.0/24 37004 >>UNKNOWN<< 41.73.4.0/24 37004 >>UNKNOWN<< 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:16 /9:13 /10:36 /11:101 /12:267 /13:517 /14:1030 /15:1763 /16:12978 /17:7575 /18:12702 /19:25792 /20:38135 /21:40194 /22:65126 /23:56317 /24:322554 /25:542 /26:585 /27:404 /28:19 /29:16 /30:13 /31:0 /32:23 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 22773 2527 3343 Cox Communications Inc. 39891 2472 2515 SaudiNet, Saudi Telecom Compa 18566 2113 2211 MegaPath Corporation 30036 1545 1730 Mediacom Communications Corp 6389 1521 2394 BellSouth.net Inc. 6983 1340 1690 EarthLink, Inc. 10620 1332 3447 Telmex Colombia S.A. 34984 1241 1952 TELLCOM ILETISIM HIZMETLERI A 11492 1169 1259 CABLE ONE, INC. 6849 997 1179 JSC "Ukrtelecom" Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1640 2:737 4:20 5:2075 6:26 8:917 12:1774 13:38 14:1617 15:45 16:2 17:72 18:20 20:49 23:1407 24:1742 27:2259 31:1746 32:54 33:2 34:3 35:4 36:240 37:2339 38:1177 39:26 40:88 41:2956 42:385 43:1658 44:40 45:1706 46:2451 47:71 49:1116 50:836 51:8 52:83 54:197 55:3 56:6 57:44 58:1515 59:861 60:562 61:1796 62:1477 63:1927 64:4437 65:2165 66:4011 67:2107 68:1100 69:3263 70:1063 71:468 72:1971 74:2543 75:340 76:439 77:1373 78:1273 79:833 80:1314 81:1363 82:913 83:675 84:800 85:1586 86:466 87:1053 88:570 89:1943 90:167 91:6047 92:857 93:2296 94:2368 95:2307 96:459 97:352 98:959 99:45 100:70 101:1002 103:9873 104:2230 105:178 106:393 107:1146 108:656 109:2116 110:1263 111:1613 112:940 113:1279 114:1058 115:1692 116:1530 117:1383 118:2131 119:1565 120:513 121:1163 122:2224 123:2015 124:1613 125:1741 128:725 129:376 130:430 131:1257 132:605 133:171 134:448 135:122 136:353 137:332 138:1696 139:212 140:338 141:468 142:630 143:874 144:607 145:160 146:851 147:636 148:1467 149:482 150:659 151:827 152:604 153:270 154:555 155:902 156:489 157:444 158:347 159:1098 160:427 161:727 162:2293 163:531 164:727 165:1123 166:311 167:1075 168:1568 169:611 170:1571 171:267 172:493 173:1667 174:721 175:888 176:1515 177:4061 178:2237 179:1089 180:2084 181:1674 182:1953 183:672 184:809 185:5907 186:3018 187:2036 188:2101 189:1761 190:7682 191:1244 192:8906 193:5729 194:4370 195:3765 196:1648 197:1173 198:5497 199:5614 200:6845 201:3706 202:10121 203:9587 204:4627 205:2705 206:2968 207:3103 208:4063 209:3889 210:3945 211:2030 212:2668 213:2192 214:828 215:73 216:5748 217:1902 218:762 219:568 220:1653 221:856 222:675 223:930 End of report

1 0

Verizon Voice Engineering Contact?
by chris 11 Mar '16

11 Mar '16

Anyone from Verizon on the voice side on the list or if anyone has any good contacts they can share? We have customers in LATA 224 who cannot complete calls to a common carrier and are hearing an audible verizon message "we're sorry all circuits are busy now" Please contact offlist Thanks chris

1 0

Re: AW: Cogent - Google - HE Fun
by Mark Tinka 11 Mar '16

11 Mar '16

On 10/Mar/16 17:25, Jon Lewis wrote: > My guess is that GOOG is playing peering chicken with Cogent on "the > IPv6 Internet" because doing so is low impact. Doing this with v4 > routing would be far more painful to both GOOG and single-homed Cogent > customers (probably make the news and make one or both look bad). > Doing this with v6 keeps it off in the shadows...both parties know its > an issue, but its likely not seriously impacting anyone yet. GOOG > likely thinks they're big enough and their content desirable enough, > that Cogent should peer with them. Cogent clearly disagrees. I'm > sure GOOG would prefer SFI with Cogent for v4 and v6...but they're > working on getting v6 first. Assuming the IPv6 traffic is traversing the same physical ports as IPv4 between both networks, it is actually unnecessary pain to not pass IPv6 traffic across their interconnect relationship, unless removal of IPv6 peering lowers traffic utilization significantly to negate the need for Google to pay a higher rate to Cogent, and/or delay physical port speed upgrades. Mark.

1 0

Figuring out traceroute
by Reza Motamedi 11 Mar '16

11 Mar '16

2 1

Re: FW: [tld-admin-poc] Fwd: Re: .pro whois registry down?
by Doug Barton 10 Mar '16

10 Mar '16

Joseph, Thanks for the update. However the current state of things is not good ... My Ubuntu host tries to use whois.dotproregistry.net, which has no address records. FreeBSD by default uses pro.whois-servers.net, which resolves to whois.registrypro.pro (which has an A record), but never returns with any data (arguably worse than failing immediately with an obvious error). If it were me, I would have done the following: 1. Reach out to the OS vendors and the folks at whois-servers.net with information that the proper host name for your whois service is changing. Include a drop-dead date of 3 years in the future for the old names to stop working. 2. Place a CNAME at the two (or more?) old host names so that the service will continue to work in the meantime. The CNAME costs you nothing, and while I agree that it should be able to be removed at some point in the future, having things not work at all in the short term is not the right approach. It's also not realistic to expect folks to be able to chase this down on their own ... anyone familiar with using whois on the command line has most assuredly grown accustomed to the convenience of having it "just work," as it has for the last decade or so. While people certainly *can* go back to the "good old days" of having to hunt down each registry's whois server individually, it's hard to think of that as the best approach. Is there some reason that the above can't be/hasn't been done that I'm missing? Doug On 03/09/2016 02:17 PM, Joseph Yee wrote: > Hi Doug, > > Afilias had updated .PRO whois host in Jan 2016, and we filed the record > to ICANN & IANA (http://www.iana.org/domains/root/db/pro.html) > > The new host is 'whois.afilias.net <http://whois.afilias.net>' and not > 'whois.dotproregistry.net <http://whois.dotproregistry.net>' anymore. > > Some operating systems may not update their whois configuration yet. > You may need to check and update the configuration manually for PRO > WHOIS server before official patch were available. > > Best Regards, > Joseph Yee > Afilias > > On Wed, Mar 9, 2016 at 4:56 PM, Michael Flanagan <mflanagan(a)afilias.info > <mailto:mflanagan@afilias.info>> wrote: > > -----Original Message----- > From: Doug Barton [mailto:dougb@dougbarton.us > <mailto:dougb@dougbarton.us>] > Sent: Wednesday, March 09, 2016 4:54 PM > To: tld-admin-poc(a)afilias.info <mailto:tld-admin-poc@afilias.info>; > tld-tech-poc(a)afilias.info <mailto:tld-tech-poc@afilias.info> > Subject: [tld-admin-poc] Fwd: Re: .pro whois registry down? > > FYI > > -------- Forwarded Message -------- > Subject: Re: .pro whois registry down? > Date: Wed, 9 Mar 2016 13:51:28 -0800 > From: Doug Barton <dougb(a)dougbarton.us <mailto:dougb@dougbarton.us>> > To: Bryan Holloway <bholloway(a)pavlovmedia.com > <mailto:bholloway@pavlovmedia.com>>, NANOG list <nanog(a)nanog.org > <mailto:nanog@nanog.org>> > > On 03/09/2016 01:24 PM, Bryan Holloway wrote: > > Anyone else noticing that the .pro TLD is failing for some > things, and > > their WHOIS registry appears to be unavailable? > > The delegation from the root to PRO, and the PRO name servers > themselves, > seem to be working. > > > I appear to be able to resolve, but whois times out, and we're > getting > > reports that mail isn't going through for some folks with this TLD. > > The address records for whois.dotproregistry.net > <http://whois.dotproregistry.net> are missing. > > Doug > >

8 12

anyone from google email / net ops here?
by Josh Reynolds 10 Mar '16

10 Mar '16

It seems like one of your email servers is on SORBS which is causing any email outbound from said server to be blocked by those using SORBS. IP in question is 209.85.214.170 Offlist responses are fine, thanks

1 0

Facebook & Traceroute
by Sam Norris 10 Mar '16

10 Mar '16

Why does Facebook spoof the source IP address of the hop before this server? They spoof the source IP address that is performing the traceroute. 66.220.156.68 --- 7 FACEBOOK-IN.ear1.Atlanta2.Level3.net (4.16.185.58) 51.736 ms 51.678 ms 52.075 ms 8 ae2.bb01.atl1.tfbnw.net (74.119.78.214) 51.636 ms 51.584 ms 51.720 ms 9 be36.bb01.frc3.tfbnw.net (31.13.26.199) 58.669 ms ae4.bb05.frc3.tfbnw.net (31.13.27.129) 61.085 ms ae16.bb06.frc3.tfbnw.net (74.119.76.117) 59.731 ms 10 ae5.bb04.iad3.tfbnw.net (31.13.26.57) 111.338 ms ae7.bb04.iad3.tfbnw.net (31.13.31.245) 110.007 ms 110.015 ms 11 ae9.dr07.ash3.tfbnw.net (31.13.29.29) 68.692 ms ae10.dr08.ash2.tfbnw.net (31.13.28.207) 67.846 ms ae12.dr08.ash3.tfbnw.net (31.13.29.191) 68.629 ms 12 * * * 13 * * * 14 8.25.38.1 (8.25.38.1) 68.571 ms 68.718 ms 68.132 ms 15 edge-star-mini-shv-07-ash4.facebook.com (66.220.156.68) 67.903 ms 67.752 ms 68.071 ms --- Hop 14 is the source ip of the traceroute which is forged. This essentially makes hop 14 reply using the same ip for src and dst. Sam

5 6

.pro whois registry down?
by Bryan Holloway 09 Mar '16

09 Mar '16

Anyone else noticing that the .pro TLD is failing for some things, and their WHOIS registry appears to be unavailable? I appear to be able to resolve, but whois times out, and we're getting reports that mail isn't going through for some folks with this TLD.

3 2

[NANOG-announce] NANOG 67 Chicago, IL - Call for Presentations is Open!
by L Sean Kennedy 09 Mar '16

09 Mar '16

NANOG Community, The NANOG Program Committee is excited to announce that we are accepting proposals for all sessions at NANOG 67 in Chicago, IL on June 13-15, 2016. I have included some key points from the Call for Presentations and the complete text is now available on the NANOG website: https://www.nanog.org/meetings/nanog67/callforpresentations Early bird registration is open for NANOG 67 and hotel reservations in the NANOG block are available for those interested in making advance travel plans. We look forward to seeing all of you in Chicago and are eager to get to work on building a strong program for the upcoming meeting. https://www.nanog.org/meetings/nanog67/home Sincerely, Sean NANOG Program Committee NANOG 67 Call for Presentations The North American Network Operators' Group (NANOG) will hold its 67th conference in Chicago, Illinois on June 13-15, 2016. EdgeConneX will be the Local Host at NANOG 67. The NANOG Program Committee seeks proposals for presentations, panels, tutorials, and tracks sessions for the NANOG 67 program. We welcome suggestions of keynote 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 67 submissions can be entered on the NANOG Program Committee Site <https://pc.nanog.org/>. How To Submit The primary speaker, moderator, or author should submit a presentation proposal and an abstract on the Program Committee Site <https://pc.nanog.org/>. Please upload draft slides as soon as possible so the Program Committee can understand the intended structure and level of detail covered by the talk. Draft slides are not required for a proposal to be initiated, but they are usually expected before the Program Committee can definitively accept a submission. The following information should be included in the proposal: - Author's name(s) - Professional or Educational Affiliation - A preferred contact email address - A preferred phone number for contact - Submission category (General Session, Panel, Tutorial, or Track) - Presentation Title - Abstract - Slides (attachment or URL), in PowerPoint (preferred) or PDF format Timeline for submission and proposal review - Submitter enters Abstract (and draft slides if possible) in Program Committee Site <https://pc.nanog.org/>. - Any time following Call for Presentations and before deadline for Abstracts - PC performs initial review and assigns a “Shepherd” to help develop the submission. - Within 2-3 weeks - Submitter develops draft slides of talk - Please submit initial draft slides early - Panels and Track submissions should provide topic list and intended/confirmed participants - 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 <nanogpc(a)nanog.org>, and a representative of the Program Committee will respond. Otherwise, submit your talk, keynote, track, or panel proposal to the Program Committee Site <https://pc.nanog.org/> without delay! We look forward to reviewing your submission. Key Dates For NANOG 67 Event/Deadline Date Registration for NANOG 67 Opens Monday, 3/7/2016 CFP Opens for NANOG 67 Tuesday, 3/8/2016 CFP Deadline #1: Presentation Abstracts Due Monday, 4/4/2016 CFP Deadline #2: Presentation Slides Due Friday, 4/29/2016 CFP Topic List and NANOG Highlights Page Monday, 5/2/2016 Speaker FINAL presentations to PC Tool <https://pc.nanog.org/> Monday, 5/30/2016 On-site Registration Sunday, 6/12/2016 Lightning Talk Submissions Open (Abstracts Only) Sunday, 6/12/2016 Further Presentation Guidelines can be found under "Present at a NANOG" <https://www.nanog.org/meetings/presentation> and some general advice is available in Tips on Giving a Talk <https://www.nanog.org/meetings/presentation/tips>. The NANOG Program Committee seeks proposals for presentations, panels, tutorial sessions, and tracks in all areas of network operations, such as: - Network Connectivity, Interconnection, and Architecture - Network Management and Configuration including Automation - Network Performance, Measurement, and Telemetry - Data Center and Physical Plant including Cooling and Power Efficiency - Network Research - Internet Governance - Routing and Switching Protocols - Network Data and Control Plane Security - Optical and Transmission Technologies - Wireless Networks - DNS, Transport, and Applications - Network Operations and Engineering Professional Experiences Submissions are welcomed by and for network operators of all sizes. Presentations about difficult problems (and interesting solutions) that you encounter in the course of your job are encouraged. The NANOG registration fee is waived for: - General Session presentations: the conference registration fee will be waived for a maximum of one speaker. - General Session panels: conference registration fees will be waived for one panel moderator and all panelists. - Tracks: conference registration fees will be waived for one moderator. - Tutorials: conference registration fees will be waived for one instructor. _______________________________________________ NANOG-announce mailing list NANOG-announce(a)mailman.nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-announce

1 0

IPV6 planning
by Laurent Dumont 09 Mar '16

09 Mar '16

Hiya, We are currently considering deploying IPv6 for a Lan event in April. We are assigned a /48 which we then split into smaller subnets for each player vlan. That said, what remains to be decided is how we are going to assign the IPv6. Basically, it seems that are two ways, one SLAAC where the endpoints uses RA to generate it's own IP and DHCPv6 which is basically DHCP but for IPv6. Large events like Dreamhack have used SLAAC and the feedback has been mostly positive. Can anyone comment regarding past experiences with IPv6 gotchas and things that you don't really expect when running dual-stack on a large-ish network? Thanks! Laurent

14 21