February 2015 - Test - lists.nanog.org

DNS Admin at Comcast
by Mark Stevens 20 Feb '15

20 Feb '15

If a DNS Admin at Comcast could contact me offline it would be great. This is concerning your IPV6 configured mail servers. Thanks, Mark

2 1

Weekly Routing Table Report
by Routing Analysis Role Account 20 Feb '15

20 Feb '15

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, CaribNOG and the RIPE Routing Working Group. 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 21 Feb, 2015 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 533255 Prefixes after maximum aggregation (per Origin AS): 204025 Deaggregation factor: 2.61 Unique aggregates announced (without unneeded subnets): 259930 Total ASes present in the Internet Routing Table: 49437 Prefixes per ASN: 10.79 Origin-only ASes present in the Internet Routing Table: 36458 Origin ASes announcing only one prefix: 16285 Transit ASes present in the Internet Routing Table: 6273 Transit-only ASes present in the Internet Routing Table: 171 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 107 Max AS path prepend of ASN ( 55644) 100 Prefixes from unregistered ASNs in the Routing Table: 1334 Unregistered ASNs in the Routing Table: 436 Number of 32-bit ASNs allocated by the RIRs: 8646 Number of 32-bit ASNs visible in the Routing Table: 6706 Prefixes from 32-bit ASNs in the Routing Table: 24396 Number of bogon 32-bit ASNs visible in the Routing Table: 5 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 400 Number of addresses announced to Internet: 2732253284 Equivalent to 162 /8s, 218 /16s and 224 /24s Percentage of available address space announced: 73.8 Percentage of allocated address space announced: 73.8 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 97.2 Total number of prefixes smaller than registry allocations: 180436 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 131658 Total APNIC prefixes after maximum aggregation: 38372 APNIC Deaggregation factor: 3.43 Prefixes being announced from the APNIC address blocks: 137114 Unique aggregates announced from the APNIC address blocks: 55712 APNIC Region origin ASes present in the Internet Routing Table: 5024 APNIC Prefixes per ASN: 27.29 APNIC Region origin ASes announcing only one prefix: 1220 APNIC Region transit ASes present in the Internet Routing Table: 872 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 107 Number of APNIC region 32-bit ASNs visible in the Routing Table: 1310 Number of APNIC addresses announced to Internet: 747396800 Equivalent to 44 /8s, 140 /16s and 94 /24s Percentage of available APNIC address space announced: 87.3 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: 176104 Total ARIN prefixes after maximum aggregation: 87045 ARIN Deaggregation factor: 2.02 Prefixes being announced from the ARIN address blocks: 178169 Unique aggregates announced from the ARIN address blocks: 83527 ARIN Region origin ASes present in the Internet Routing Table: 16498 ARIN Prefixes per ASN: 10.80 ARIN Region origin ASes announcing only one prefix: 6087 ARIN Region transit ASes present in the Internet Routing Table: 1714 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 22 Number of ARIN region 32-bit ASNs visible in the Routing Table: 352 Number of ARIN addresses announced to Internet: 1061271072 Equivalent to 63 /8s, 65 /16s and 182 /24s Percentage of available ARIN address space announced: 56.1 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, 393216-394239 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: 129524 Total RIPE prefixes after maximum aggregation: 64588 RIPE Deaggregation factor: 2.01 Prefixes being announced from the RIPE address blocks: 135852 Unique aggregates announced from the RIPE address blocks: 83507 RIPE Region origin ASes present in the Internet Routing Table: 17873 RIPE Prefixes per ASN: 7.60 RIPE Region origin ASes announcing only one prefix: 8145 RIPE Region transit ASes present in the Internet Routing Table: 2965 Average RIPE Region AS path length visible: 4.9 Max RIPE Region AS path length visible: 32 Number of RIPE region 32-bit ASNs visible in the Routing Table: 3456 Number of RIPE addresses announced to Internet: 693406084 Equivalent to 41 /8s, 84 /16s and 137 /24s Percentage of available RIPE address space announced: 100.8 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-202239 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: 58761 Total LACNIC prefixes after maximum aggregation: 10997 LACNIC Deaggregation factor: 5.34 Prefixes being announced from the LACNIC address blocks: 68139 Unique aggregates announced from the LACNIC address blocks: 31758 LACNIC Region origin ASes present in the Internet Routing Table: 2400 LACNIC Prefixes per ASN: 28.39 LACNIC Region origin ASes announcing only one prefix: 630 LACNIC Region transit ASes present in the Internet Routing Table: 490 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 26 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 1499 Number of LACNIC addresses announced to Internet: 167785728 Equivalent to 10 /8s, 0 /16s and 53 /24s Percentage of available LACNIC address space announced: 100.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: 12620 Total AfriNIC prefixes after maximum aggregation: 2979 AfriNIC Deaggregation factor: 4.24 Prefixes being announced from the AfriNIC address blocks: 13581 Unique aggregates announced from the AfriNIC address blocks: 5066 AfriNIC Region origin ASes present in the Internet Routing Table: 735 AfriNIC Prefixes per ASN: 18.48 AfriNIC Region origin ASes announcing only one prefix: 203 AfriNIC Region transit ASes present in the Internet Routing Table: 156 Average AfriNIC Region AS path length visible: 4.5 Max AfriNIC Region AS path length visible: 28 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 89 Number of AfriNIC addresses announced to Internet: 61893888 Equivalent to 3 /8s, 176 /16s and 109 /24s Percentage of available AfriNIC address space announced: 61.5 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 4766 2891 11553 911 Korea Telecom 17974 2826 904 77 PT Telekomunikasi Indonesia 7545 2580 336 128 TPG Telecom Limited 4755 1977 421 205 TATA Communications formerly 4538 1758 4190 71 China Education and Research 9829 1660 1325 36 National Internet Backbone 9808 1547 8717 29 Guangdong Mobile Communicatio 4808 1451 2218 436 CNCGROUP IP network China169 9583 1395 132 556 Sify Limited 9498 1299 336 97 BHARTI Airtel Ltd. 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 2985 2955 141 Cox Communications Inc. 6389 2891 3688 51 BellSouth.net Inc. 3356 2566 10684 480 Level 3 Communications, Inc. 18566 2041 379 183 MegaPath Corporation 20115 1849 1829 443 Charter Communications 4323 1623 1037 407 tw telecom holdings, inc. 6983 1623 850 242 EarthLink, Inc. 30036 1520 312 511 Mediacom Communications Corp 701 1391 11268 678 MCI Communications Services, 22561 1329 412 241 CenturyTel Internet Holdings, 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 2472 128 6 SaudiNet, Saudi Telecom Compa 34984 1965 300 352 TELLCOM ILETISIM HIZMETLERI A 20940 1619 632 1202 Akamai International B.V. 8402 1344 544 15 OJSC "Vimpelcom" 6849 1199 356 25 JSC "Ukrtelecom" 31148 1045 45 21 Freenet Ltd. 13188 1044 97 61 TOV "Bank-Inform" 8551 903 373 48 Bezeq International-Ltd 12479 862 793 87 France Telecom Espana SA 9198 850 349 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 3117 506 213 Telmex Colombia S.A. 28573 2307 2141 111 NET Serviços de Comunicação S 7303 1788 1190 229 Telecom Argentina S.A. 6147 1589 374 30 Telefonica del Peru S.A.A. 8151 1543 3111 451 Uninet S.A. de C.V. 6503 1196 421 58 Axtel, S.A.B. de C.V. 7738 1001 1882 42 Telemar Norte Leste S.A. 26615 920 2325 35 Tim Celular S.A. 3816 910 395 151 COLOMBIA TELECOMUNICACIONES S 18881 858 1036 22 Global Village Telecom 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 8452 1556 958 13 TE-AS 24863 965 284 26 Link Egypt (Link.NET) 36903 479 241 90 Office National des Postes et 36992 390 973 31 ETISALAT MISR 37492 319 155 71 Orange Tunisie 24835 299 144 9 Vodafone Data 3741 250 921 209 Internet Solutions 29571 234 21 12 Cote d'Ivoire Telecom 36947 195 712 14 Telecom Algeria 37054 188 19 6 Data Telecom Service 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 10620 3117 506 213 Telmex Colombia S.A. 22773 2985 2955 141 Cox Communications Inc. 4766 2891 11553 911 Korea Telecom 6389 2891 3688 51 BellSouth.net Inc. 17974 2826 904 77 PT Telekomunikasi Indonesia 7545 2580 336 128 TPG Telecom Limited 3356 2566 10684 480 Level 3 Communications, Inc. 39891 2472 128 6 SaudiNet, Saudi Telecom Compa 28573 2307 2141 111 NET Serviços de Comunicação S 18566 2041 379 183 MegaPath Corporation Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 22773 2985 2844 Cox Communications Inc. 6389 2891 2840 BellSouth.net Inc. 17974 2826 2749 PT Telekomunikasi Indonesia 39891 2472 2466 SaudiNet, Saudi Telecom Compa 7545 2580 2452 TPG Telecom Limited 28573 2307 2196 NET Serviços de Comunicação S 3356 2566 2086 Level 3 Communications, Inc. 4766 2891 1980 Korea Telecom 18566 2041 1858 MegaPath Corporation 4755 1977 1772 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 30662 UNALLOCATED 8.2.129.0/24 3356 Level 3 Communicatio 47092 UNALLOCATED 8.8.204.0/24 16410 The Reynolds and Rey 53506 UNALLOCATED 8.17.102.0/23 3356 Level 3 Communicatio 46467 UNALLOCATED 8.19.192.0/24 46887 Lightower Fiber Netw 18985 UNALLOCATED 8.21.68.0/22 3356 Level 3 Communicatio 46473 UNALLOCATED 8.27.122.0/24 12180 Internap Network Ser 46473 UNALLOCATED 8.27.124.0/24 12180 Internap Network Ser 27205 UNALLOCATED 8.38.16.0/21 6461 Abovenet Communicati 15347 UNALLOCATED 8.224.147.0/24 12064 Cox Communications I 33628 UNALLOCATED 12.0.239.0/24 1239 Sprint Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 5.100.241.0/24 23456 32bit Transition AS 23.92.160.0/24 14013 EPSON America (Factory Automa 23.92.161.0/24 14013 EPSON America (Factory Automa 23.226.112.0/20 62788 Bitfinite LLC 23.252.224.0/20 62502 >>UNKNOWN<< 23.252.224.0/21 62502 >>UNKNOWN<< 23.252.232.0/21 62502 >>UNKNOWN<< 24.231.96.0/24 21548 MTO Telecom Inc. 27.100.7.0/24 56096 >>UNKNOWN<< 31.217.248.0/21 44902 COVAGE NETWORKS SASU 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:12 /10:34 /11:92 /12:264 /13:504 /14:997 /15:1723 /16:12974 /17:7130 /18:12142 /19:24903 /20:35716 /21:38479 /22:57743 /23:50414 /24:287236 /25:1069 /26:1084 /27:670 /28:17 /29:14 /30:9 /31:0 /32:13 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 39891 2432 2472 SaudiNet, Saudi Telecom Compa 22773 2201 2985 Cox Communications Inc. 18566 1996 2041 MegaPath Corporation 6389 1671 2891 BellSouth.net Inc. 30036 1366 1520 Mediacom Communications Corp 6983 1314 1623 EarthLink, Inc. 34984 1274 1965 TELLCOM ILETISIM HIZMETLERI A 11492 1133 1191 CABLE ONE, INC. 6147 1132 1589 Telefonica del Peru S.A.A. 10620 1105 3117 Telmex Colombia S.A. Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1474 2:670 3:1 4:97 5:1716 6:21 8:1409 12:1842 13:4 14:1300 15:16 16:2 17:42 18:21 20:49 23:1163 24:1681 27:1851 31:1484 32:39 33:2 34:5 35:3 36:119 37:1862 38:1011 39:9 40:233 41:3046 42:259 43:1091 44:25 45:198 46:2116 47:34 49:795 50:783 52:12 54:66 55:4 56:8 57:33 58:1203 59:680 60:460 61:1765 62:1306 63:1914 64:4427 65:2263 66:4082 67:2023 68:1042 69:3284 70:965 71:435 72:1959 74:2620 75:314 76:404 77:1471 78:1255 79:778 80:1326 81:1332 82:813 83:680 84:682 85:1335 86:387 87:1082 88:501 89:1753 90:148 91:5915 92:808 93:2182 94:1958 95:2090 96:431 97:340 98:1054 99:45 100:73 101:800 103:6796 104:1266 105:61 106:217 107:886 108:611 109:2023 110:1078 111:1474 112:772 113:1030 114:853 115:1258 116:1332 117:1022 118:1688 119:1429 120:438 121:1044 122:2177 123:1718 124:1489 125:1564 128:628 129:373 130:380 131:1098 132:475 133:166 134:405 135:88 136:311 137:302 138:472 139:173 140:229 141:418 142:629 143:471 144:518 145:111 146:688 147:560 148:1104 149:458 150:563 151:748 152:485 153:239 154:325 155:725 156:403 157:331 158:264 159:991 160:372 161:633 162:1904 163:387 164:654 165:670 166:324 167:704 168:1003 169:149 170:1442 171:223 172:41 173:1580 174:688 175:622 176:1444 177:3757 178:2077 179:863 180:1918 181:1581 182:1705 183:603 184:743 185:2943 186:2669 187:1830 188:2012 189:1556 190:7744 191:877 192:8098 193:5562 194:4055 195:3632 196:1683 197:946 198:5501 199:5529 200:6537 201:2991 202:9552 203:9069 204:4655 205:2719 206:2978 207:2995 208:3953 209:3894 210:3492 211:1830 212:2467 213:2277 214:846 215:70 216:5544 217:1808 218:665 219:468 220:1457 221:790 222:463 223:654 End of report

1 0

Re: [j-nsp] draft-ietf-mpls-ldp-ipv6-16
by Tim Durack 20 Feb '15

20 Feb '15

On Fri, Feb 20, 2015 at 11:33 AM, Adam Vitkovsky <Adam.Vitkovsky(a)gamma.co.uk > wrote: > > Of Tim Durack > > Sent: 20 February 2015 14:00 > > IPv6 control plane this decade may yet be optimistic. > > > > And most importantly it's not actually needed it's just a whim of network > operators. > > adam > > > ------------------------------ > This email has been scanned for email related threats and delivered safely > by Mimecast. > For more information please visit http://www.mimecast.com > ------------------------------ > I don't consider unique addressing of infrastructure a whim. -- Tim:>

1 0

NYC Metro Ethernet Providers
by Bryn Sadler 20 Feb '15

20 Feb '15

Hi all, We're currently a UK based managed service provider looking to open up in the New York area. Part of our service model involves buying quite a lot of L2 ethernet tails from customer prems back to our DCs, usually 100Mb and 1Gb, but sometimes smaller 10-50Mb services for backups. I was wondering if anyone on the list would be able to recommend reliable providers in that region, we'd essentially just want pure Layer 2 so we can run our own VLANs etc across them, with a number of circuits aggregated and handed off in a DC as a trunk, each circuit as an SPVLAN that we can then strip. Thanks in advance for any feedback, Bryn Sadler

1 0

LiveAction?
by Adam Greene 20 Feb '15

20 Feb '15

Hi all, Has anyone used this product? http://www.liveaction.com/ Cisco seems to tout it: http://www.cisco.com/c/en/us/solutions/enterprise-networks/intelligent-wan/i ndex.html (scroll down) We're evaluating it as a way to manage customer bandwidth utilization on our service provider network. To me, it looks like an affordable alternative to deploying extremely expensive bandwidth management appliances. It's centrally managed on a VM, and I like that it does not impose scalability limitations like some bandwidth management vendors who charge every time you want to push more bandwidth through their devices. Interested in whether anyone has rolled it out and how their experience has been. Thanks, Adam

1 0

FYI: An Easy way to build a server cluster without top of rack switches (MEMO)
by NAOTO MATSUMOTO 20 Feb '15

20 Feb '15

Hi all! We wrote up TIPS memo "an easy way to build a server cluster without top of rack switches" concept. This model have a reduce switches and cables costs and high network durability by lightweight and simple configuration. if you interest in, please try to do yourself this concept ;-) An Easy way to build a server cluster without top of rack switches (MEMO) http://slidesha.re/1EduYXM Best regards, -- Naoto MATSUMOTO

3 4

Re: v6 deagg
by Brandon Butterworth 20 Feb '15

20 Feb '15

> From: Saku Ytti <saku(a)ytti.fi> > Is deaggregation inherently undesirable? I'd say yes when the only limit to deaggregation is /48. Given the opportunity people will do whatever they see fit at everyone elses expense > What is the correct solution here? Deaggregate or allocate space you don't > need? Whichever comes with sensible deagg control. The desired effect is people advertise exactly sufficient prefixes and, I'd say, a simple universal mechanism for everyone else to limit them to that so they don't feel the need to advertise more to prevent hijacks etc. > Or some others solution, should route object creation be limited to LIR > and be controlled by specific policy? It would allow inject information about > the reason for it. There is always a good reason to the person doing it. > Correct solution is not to use some so called 'strict' ipv6 filters, which > break Internet, by not allowing discontinuous pops having connectivity. Yes, strict would be best if based on good data. With no prefix length police there is no good data, RIPE gave up and said /48 everywhere removing the simpler mechanism to do this (I've not noticed what the others are doing) brandon

1 0

RE: OT - Small DNS "appliances" for remote offices.
by Robert Webb 20 Feb '15

20 Feb '15

What I do not like about the Pi is the network port is on the USB bus and thus limited to USB speeds. <div>-------- Original message --------</div><div>From: Maxwell Cole <mcole.mailinglists(a)gmail.com> </div><div>Date:02/18/2015 4:30 PM (GMT-05:00) </div><div>To: "nanog(a)nanog.org >> 'NANOG list'" <nanog(a)nanog.org> </div><div>Subject: Re: OT - Small DNS "appliances" for remote offices. </div><div> </div>

15 22

Call For Presentations RIPE 70, submission deadline 1 March 2015
by Benno Overeinder 20 Feb '15

20 Feb '15

Dear colleagues, Please find the CFP for RIPE 70 below. The deadline for submissions is 1 March 2015. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder for the RIPE Programme Committee http://www.ripe.net/ripe/meetings/ripe-meetings/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 70 will take place from 11-15 May 2015 in Amsterdam, The Netherlands. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary session presentations, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 70. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange Submissions 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 not attempt a product demonstration. The RIPE PC accepts proposals for different presentation formats, including plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. See the full descriptions of these formats at https://ripe70.ripe.net/submit-topic/presentation-formats/ Presenters who are proposing a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. In addition to presentations selected in advance for the plenary, the RIPE PC also offers several time slots for "lightning talks", which are selected immediately before or during the conference. The following general requirements apply: - Proposals for plenary session presentations, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 1 March 2015, using the meeting submission system at https://ripe70.ripe.net/submit-topic/submission-form/. Proposals submitted after this date will be considered on a space-available basis. Important Dates regarding RIPE 70 can be found at: https://ripe70.ripe.net/programme/important-dates/ - Lightning talks should also be submitted using the meeting submission system (https://ripe70.ripe.net/submit-topic/submission-form/) and can be submitted just days before the RIPE Meeting starts or even during the meeting week. The allocation of lightning talk slots will be announced in short notice – in some cases on the same day but often one day prior to the relevant session. - Presenters should indicate how much time they will require. See more information on time slot allocations per presentation format at https://ripe70.ripe.net/submit-topic/presentation-formats/. - Proposals for talks 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. - Due to potential technical issues, it is expected that most, if not all, presenters/panellists will be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

2 1

FW: HTTPv6 access to www.centurylink.com and www.qwest.com are down
by Frank Bulk 19 Feb '15

19 Feb '15

Emails to what I thought were CenturyLink's NOC have gone unanswered, and the other email address resulted in an automated "you're not allowed to send emails to that group". Frank -----Original Message----- From: Frank Bulk Sent: Thursday, February 12, 2015 8:22 AM To: network(a)centurytel.net; 'noc(a)qwest.net' Subject: HTTPv6 access to www.centurylink.com and www.qwest.com are down According to our monitoring system, HTTPv6 access to www.centurylink.com and www.qwest.com have been down since 12:05 am U.S. Central, responding with a "Connection refused". I've tested from two vantage points to confirm that it's not just our prefix. Diagnostic output can be found below. Regards, Frank Bulk Premier Communications root@nagios:~/tmp/ipv6# wget -6 www.centurylink.com --2015-02-12 08:18:22-- http://www.centurylink.com/ Resolving www.centurylink.com... 2001:428:b21:1::20 Connecting to www.centurylink.com|2001:428:b21:1::20|:80... failed: Connection refused. root@nagios:~/tmp/ipv6# root@nagios:~/tmp/ipv6# tcptraceroute6 www.centurylink.com traceroute to www.centurylink.com (2001:428:b21:1::20) from 2607:fe28:0:1000::5, port 80, from port 60661, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.555 ms 19.811 ms 1.632 ms 2 sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197) 0.185 ms 0.196 ms 0.115 ms 3 v6-premier.sxcy-mlx.fbnt.netins.net (2001:5f8:7f0a:2::1) 1.641 ms 1.617 ms 1.585 ms 4 v6-ins-db4-te-0-6-0-4-219.desm.netins.net (2001:5f8:1:1::1) 8.146 ms 8.003 ms 8.051 ms 5 v6-ins-dc1-te-7-4.desm.netins.net (2001:5f8::26:2) 8.035 ms 7.954 ms 7.928 ms 6 2610:18:18b:c000::11 (2610:18:18b:c000::11) 12.925 ms 12.941 ms 12.896 ms 7 mcr1.minneapolis-mn.us.xo.net (2610:18::30b8) 22.254 ms 22.234 ms 22.238 ms 8 2610:18::5802 (2610:18::5802) 32.891 ms 25.156 ms 22.868 ms 9 2610:18::2072 (2610:18::2072) 23.894 ms 22.264 ms 22.759 ms 10 2610:18:16:3000::da (2610:18:16:3000::da) 18.543 ms 18.513 ms 18.569 ms 11 2001:428::205:171:2:52 (2001:428::205:171:2:52) 28.482 ms 28.512 ms 28.549 ms 12 2001:428:1c02:2::2 (2001:428:1c02:2::2) 28.254 ms 28.277 ms 28.238 ms 13 * 2001:428:b21:fc03::2 (2001:428:b21:fc03::2) 28.871 ms 28.608 ms 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * root@nagios:~/tmp/ipv6#

1 1