June 2012 - Test - lists.nanog.org

Weekly Routing Table Report
by Routing Analysis Role Account 22 Jun '12

22 Jun '12

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, LacNOG, TRNOG, 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 23 Jun, 2012 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 414975 Prefixes after maximum aggregation: 175345 Deaggregation factor: 2.37 Unique aggregates announced to Internet: 202288 Total ASes present in the Internet Routing Table: 41358 Prefixes per ASN: 10.03 Origin-only ASes present in the Internet Routing Table: 33312 Origin ASes announcing only one prefix: 15660 Transit ASes present in the Internet Routing Table: 5532 Transit-only ASes present in the Internet Routing Table: 141 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 28 Max AS path prepend of ASN ( 36992) 22 Prefixes from unregistered ASNs in the Routing Table: 392 Unregistered ASNs in the Routing Table: 123 Number of 32-bit ASNs allocated by the RIRs: 2879 Number of 32-bit ASNs visible in the Routing Table: 2514 Prefixes from 32-bit ASNs in the Routing Table: 6440 Special use prefixes present in the Routing Table: 2 Prefixes being announced from unallocated address space: 260 Number of addresses announced to Internet: 2568129068 Equivalent to 153 /8s, 18 /16s and 138 /24s Percentage of available address space announced: 69.3 Percentage of allocated address space announced: 69.4 Percentage of available address space allocated: 99.9 Percentage of address space in use by end-sites: 93.0 Total number of prefixes smaller than registry allocations: 144378 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 101060 Total APNIC prefixes after maximum aggregation: 32679 APNIC Deaggregation factor: 3.09 Prefixes being announced from the APNIC address blocks: 101493 Unique aggregates announced from the APNIC address blocks: 41912 APNIC Region origin ASes present in the Internet Routing Table: 4708 APNIC Prefixes per ASN: 21.56 APNIC Region origin ASes announcing only one prefix: 1240 APNIC Region transit ASes present in the Internet Routing Table: 743 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 24 Number of APNIC region 32-bit ASNs visible in the Routing Table: 238 Number of APNIC addresses announced to Internet: 703274368 Equivalent to 41 /8s, 235 /16s and 29 /24s Percentage of available APNIC address space announced: 82.2 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 131072-133119 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: 152044 Total ARIN prefixes after maximum aggregation: 77265 ARIN Deaggregation factor: 1.97 Prefixes being announced from the ARIN address blocks: 152987 Unique aggregates announced from the ARIN address blocks: 68132 ARIN Region origin ASes present in the Internet Routing Table: 15172 ARIN Prefixes per ASN: 10.08 ARIN Region origin ASes announcing only one prefix: 5752 ARIN Region transit ASes present in the Internet Routing Table: 1601 Average ARIN Region AS path length visible: 4.0 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 16 Number of ARIN addresses announced to Internet: 1080985216 Equivalent to 64 /8s, 110 /16s and 134 /24s Percentage of available ARIN address space announced: 57.2 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, 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: 103551 Total RIPE prefixes after maximum aggregation: 54846 RIPE Deaggregation factor: 1.89 Prefixes being announced from the RIPE address blocks: 105587 Unique aggregates announced from the RIPE address blocks: 66781 RIPE Region origin ASes present in the Internet Routing Table: 16640 RIPE Prefixes per ASN: 6.35 RIPE Region origin ASes announcing only one prefix: 8070 RIPE Region transit ASes present in the Internet Routing Table: 2666 Average RIPE Region AS path length visible: 5.0 Max RIPE Region AS path length visible: 28 Number of RIPE region 32-bit ASNs visible in the Routing Table: 1654 Number of RIPE addresses announced to Internet: 631874948 Equivalent to 37 /8s, 169 /16s and 165 /24s Percentage of available RIPE address space announced: 91.9 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, 196608-199679 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: 42327 Total LACNIC prefixes after maximum aggregation: 8320 LACNIC Deaggregation factor: 5.09 Prefixes being announced from the LACNIC address blocks: 44845 Unique aggregates announced from the LACNIC address blocks: 21926 LACNIC Region origin ASes present in the Internet Routing Table: 1600 LACNIC Prefixes per ASN: 28.03 LACNIC Region origin ASes announcing only one prefix: 431 LACNIC Region transit ASes present in the Internet Routing Table: 308 Average LACNIC Region AS path length visible: 4.4 Max LACNIC Region AS path length visible: 21 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 600 Number of LACNIC addresses announced to Internet: 111077288 Equivalent to 6 /8s, 158 /16s and 231 /24s Percentage of available LACNIC address space announced: 66.2 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 262144-263167 plus 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: 9352 Total AfriNIC prefixes after maximum aggregation: 2173 AfriNIC Deaggregation factor: 4.30 Prefixes being announced from the AfriNIC address blocks: 9803 Unique aggregates announced from the AfriNIC address blocks: 3304 AfriNIC Region origin ASes present in the Internet Routing Table: 548 AfriNIC Prefixes per ASN: 17.89 AfriNIC Region origin ASes announcing only one prefix: 167 AfriNIC Region transit ASes present in the Internet Routing Table: 125 Average AfriNIC Region AS path length visible: 4.6 Max AfriNIC Region AS path length visible: 25 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 6 Number of AfriNIC addresses announced to Internet: 40527872 Equivalent to 2 /8s, 106 /16s and 104 /24s Percentage of available AfriNIC address space announced: 40.3 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 2704 11117 1196 Korea Telecom (KIX) 17974 1945 533 80 PT TELEKOMUNIKASI INDONESIA 7545 1689 301 87 TPG Internet Pty Ltd 4755 1594 385 154 TATA Communications formerly 9829 1300 1085 28 BSNL National Internet Backbo 9583 1173 89 511 Sify Limited 4808 1107 2054 313 CNCGROUP IP network: China169 7552 1100 1062 11 Vietel Corporation 24560 1034 385 165 Bharti Airtel Ltd., Telemedia 9498 966 291 63 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 6389 3401 3791 190 bellsouth.net, inc. 7029 3238 986 157 Windstream Communications Inc 18566 2091 382 181 Covad Communications 1785 1925 681 132 PaeTec Communications, Inc. 22773 1650 2911 121 Cox Communications, Inc. 20115 1645 1570 613 Charter Communications 4323 1571 1043 385 Time Warner Telecom 30036 1439 269 763 Mediacom Communications Corp 7018 1225 10013 823 AT&T WorldNet Services 11492 1189 216 356 Cable One 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 8402 1690 544 16 Corbina telecom 2118 1255 97 14 EUnet/RELCOM Autonomous Syste 12479 757 721 93 Uni2 Autonomous System 34984 710 188 173 BILISIM TELEKOM 31148 686 37 9 FreeNet ISP 6830 685 2234 437 UPC Distribution Services 20940 664 215 520 Akamai Technologies European 8551 577 364 61 Bezeq International 3320 490 8442 403 Deutsche Telekom AG 13188 476 100 10 Educational Network 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 1967 342 205 TVCABLE BOGOTA 28573 1942 1211 54 NET Servicos de Comunicao S.A 6503 1530 418 65 AVANTEL, S.A. 8151 1491 3068 336 UniNet S.A. de C.V. 7303 1440 901 195 Telecom Argentina Stet-France 26615 903 728 33 Tim Brasil S.A. 27947 705 73 93 Telconet S.A 11172 646 91 74 Servicios Alestra S.A de C.V 3816 586 247 89 Empresa Nacional de Telecomun 22047 583 326 15 VTR PUNTO NET S.A. 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 1275 958 13 TEDATA 24863 860 274 35 LINKdotNET AS number 6713 499 649 18 Itissalat Al-MAGHRIB 24835 321 80 8 RAYA Telecom - Egypt 3741 262 905 223 The Internet Solution 33776 209 12 21 Starcomms Nigeria Limited 12258 197 28 62 Vodacom Internet Company 16637 172 664 87 MTN Network Solutions 29975 167 571 19 Vodacom 29571 157 15 16 Ci Telecom Autonomous system 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 6389 3401 3791 190 bellsouth.net, inc. 7029 3238 986 157 Windstream Communications Inc 4766 2704 11117 1196 Korea Telecom (KIX) 18566 2091 382 181 Covad Communications 10620 1967 342 205 TVCABLE BOGOTA 17974 1945 533 80 PT TELEKOMUNIKASI INDONESIA 28573 1942 1211 54 NET Servicos de Comunicao S.A 1785 1925 681 132 PaeTec Communications, Inc. 8402 1690 544 16 Corbina telecom 7545 1689 301 87 TPG Internet Pty Ltd Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 7029 3238 3081 Windstream Communications Inc 18566 2091 1910 Covad Communications 28573 1942 1888 NET Servicos de Comunicao S.A 17974 1945 1865 PT TELEKOMUNIKASI INDONESIA 1785 1925 1793 PaeTec Communications, Inc. 10620 1967 1762 TVCABLE BOGOTA 8402 1690 1674 Corbina telecom 7545 1689 1602 TPG Internet Pty Ltd 22773 1650 1529 Cox Communications, Inc. 4766 2704 1508 Korea Telecom (KIX) Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet Servic 25639 UNALLOCATED 12.41.169.0/24 7018 AT&T WorldNet Servic 13317 UNALLOCATED 12.44.10.0/24 7018 AT&T WorldNet Servic 23502 UNALLOCATED 12.44.44.0/24 7018 AT&T WorldNet Servic 17300 UNALLOCATED 12.45.103.0/24 7018 AT&T WorldNet Servic 17300 UNALLOCATED 12.45.110.0/24 701 UUNET Technologies, 16476 UNALLOCATED 12.46.27.0/24 7018 AT&T WorldNet Servic 32873 UNALLOCATED 12.46.100.0/23 10912 InterNAP Network Ser 32873 UNALLOCATED 12.46.102.0/24 10912 InterNAP Network Ser 14764 UNALLOCATED 12.108.237.0/24 7018 AT&T WorldNet Servic Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 128.0.0.0/21 12654 RIPE NCC RIS Project 128.0.24.0/24 12654 RIPE NCC RIS Project Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 14.192.0.0/22 45464 Room 201, TGU Bldg 14.192.4.0/22 45464 Room 201, TGU Bldg 14.192.8.0/22 45464 Room 201, TGU Bldg 14.192.12.0/22 45464 Room 201, TGU Bldg 14.192.16.0/22 45464 Room 201, TGU Bldg 14.192.20.0/22 45464 Room 201, TGU Bldg 14.192.24.0/22 45464 Room 201, TGU Bldg 14.192.28.0/22 45464 Room 201, TGU Bldg 27.112.114.0/24 23884 Proimage Engineering and Comm 46.96.0.0/22 31733 Link Telecom PJSC 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:19 /9:13 /10:28 /11:83 /12:236 /13:462 /14:832 /15:1508 /16:12291 /17:6333 /18:10725 /19:20814 /20:29569 /21:31283 /22:40922 /23:38788 /24:217227 /25:1238 /26:1460 /27:866 /28:171 /29:66 /30:18 /31:0 /32:23 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 7029 2636 3238 Windstream Communications Inc 18566 2040 2091 Covad Communications 6389 1874 3401 bellsouth.net, inc. 8402 1389 1690 Corbina telecom 30036 1378 1439 Mediacom Communications Corp 11492 1152 1189 Cable One 22773 1082 1650 Cox Communications, Inc. 6503 1061 1530 AVANTEL, S.A. 8452 1040 1275 TEDATA 1785 1036 1925 PaeTec Communications, Inc. Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:563 2:712 3:1 4:13 5:62 6:3 8:429 12:2014 13:1 14:630 15:12 16:3 17:5 20:24 23:185 24:1784 27:1311 31:984 32:56 33:2 34:2 36:9 37:582 38:814 39:1 40:127 41:3147 42:139 44:3 46:1448 47:2 49:415 50:559 52:13 54:12 55:7 56:1 57:34 58:976 59:504 60:259 61:1227 62:997 63:2040 64:4251 65:2254 66:4460 67:2022 68:1155 69:3194 70:982 71:503 72:1829 74:2601 75:477 76:330 77:951 78:968 79:493 80:1216 81:943 82:653 83:526 84:498 85:1191 86:420 87:936 88:331 89:1721 90:298 91:4956 92:573 93:1402 94:1595 95:1230 96:371 97:316 98:893 99:38 100:17 101:251 103:1200 106:103 107:186 108:340 109:1411 110:785 111:925 112:419 113:623 114:642 115:822 116:949 117:730 118:899 119:1233 120:348 121:694 122:1673 123:1097 124:1400 125:1255 128:560 129:198 130:254 131:633 132:289 133:22 134:244 135:61 136:215 137:239 138:334 139:185 140:491 141:253 142:437 143:372 144:516 145:76 146:510 147:292 148:775 149:314 150:163 151:182 152:473 153:175 154:17 155:420 156:225 157:381 158:190 159:619 160:342 161:269 162:352 163:192 164:643 165:413 166:587 167:475 168:912 169:127 170:885 171:137 172:5 173:1779 174:615 175:436 176:545 177:842 178:1517 180:1264 181:97 182:1020 183:232 184:517 185:1 186:2375 187:1133 188:1349 189:1852 190:5635 192:6005 193:5539 194:4542 195:3430 196:1220 197:161 198:3666 199:4796 200:5897 201:1967 202:8667 203:8580 204:4337 205:2542 206:2805 207:2798 208:4042 209:3608 210:2786 211:1552 212:2032 213:1925 214:874 215:83 216:5102 217:1566 218:555 219:312 220:1241 221:574 222:315 223:354 End of report

1 0

Automatic attack alert to ISPs
by Ganbold Tsagaankhuu 22 Jun '12

22 Jun '12

Hi, Is there any well known free services or scripts that sends automatic attack alerts based on some logs to corresponding ISPs (based on src address)? I have seen dshield.org and mynetwatchman, but I don't know yet how good they are. If somebody has recommendations in this regard please let me know. thanks in advance, Ganbold

5 4

Contact from Global Crossing Kindly contact me off list
by Righa Shake 22 Jun '12

22 Jun '12

Hi, Kindly would someone from Global Crossing contact me offlist. Regards, Righa Shake

1 0

Re: SIXSS not working?
by Hank Nussbacher 21 Jun '12

21 Jun '12

At 19:25 20/06/2012 -0400, Kyle Creyts wrote: Until such time that Sixxs responds as to what happened, it will all be conjecture. -Hank >http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-1820 possibly >related? > >On Wed, Jun 20, 2012 at 11:34 AM, Jeroen Massar <jeroen(a)unfix.org> wrote: > > Good morning (at least on this side of the planet), > > > > On 2012-06-20 02:14, Hank Nussbacher wrote:> On Wed, 20 Jun 2012, Jeroen > > Massar wrote: > >> > >> Ill report it to them but: > > > > NANOG is afaik still not the "contact the people who run things" email > > address... > > > > Nevertheless, if issues, do not hesitate to report to info(a)sixxs.net > > > >> http://www.sixxs.net/tools/grh/tla/ > >> Shows every country as V=0 (prefixes visible per country). > > > > That would mean that every prefix was not updated in the last day, > > sounds odd to me. > > > > On 2012-06-20 04:00, Hank Nussbacher wrote: > >> On Wed, 20 Jun 2012, Hank Nussbacher wrote: > >> > >> It would appear that whatever was broken is now fixed. > > > > The only thing I can think of is that you have noticed some weird glitch > > of the kind there. > > > > As mentioned above the "Visible" is basically the amount of prefixes > > visible in the last 24 hours. For that to become 0 it would have meant > > that no prefix would have been seen for the last 24 hours. > > > > According to http://www.sixxs.net/tools/grh/status/ which just telnets > > into grh.sixxs.net and asks for quagga's status, seems that even peering > > sessions are connected for longer than that, thus I am puzzled to what > > could have caused that then. > > > > Greets, > > Jeroen > > > > > > > >-- >Kyle Creyts > >Information Assurance Professional >BSidesDetroit Organizer

3 2

PIM survey for operators
by Mike McBride 21 Jun '12

21 Jun '12

The IETF pim working group is conducting a survey in order to advance the PIM Sparse Mode spec on the IETF Standards Track, and would like input from operators. The survey ends July 20th. Please see below for more information. thank you, pim chairs Mike & Stig Introduction: PIM-SM was first published as RFC 2117 in 1997 and then again as RFC 2362 in 1998. The protocol was classified as Experimental in both of these documents. The PIM-SM protocol specification was then rewritten in whole and advanced to Proposed Standard as RFC 4601 in 2006. Considering the multiple independent implementations developed and the successful operational experience gained, the IETF has decided to advance the PIM-SM routing protocol to Draft Standard. This survey intends to provide supporting documentation to advance the Protocol Independent Multicast - Sparse Mode (PIM-SM) routing protocol from IETF Proposed Standard to Draft Standard. (Due to RFC 6410, now the intention is to progress it to Internet Standard. Draft Standard is no longer used.) This survey is issued on behalf of the IETF PIM Working Group. The responses will be collected by a neutral third-party and kept strictly confidential; only the final combined results will be published. Marshall Eubanks has agreed to anonymize the response to this Questionnaire. Marshall has a long experience with Multicast but has no direct financial interest in this matter, nor ties to any of the vendors involved. He is also a member of the IAOC, Chair of the IETF Trust and co-chair of the IETF Layer 3 VPN Working Group. Please send Questionnaire responses to his email address, marshall.eubanks(a)gmail.com. He requests that such responses include the string "RFC 4601 bis Questionnaire" in the subject field. Before answering the questions, please comple the following background information. Name of the Respondent: Affliation/Organization: Contact Email: Provide description of PIM deployment: Do you wish to keep the information provided confidential: Questions: 1 Have you deployed PIM-SM in your network? 2 How long have you had PIM-SM deployed in your network? Do you know if your deployment is based on the most recent RFC4601? 3 Have you deployed PIM-SM for IPv6 in your network? 4 Are you using equipment with different (multi-vendor) PIM-SM implementations for your deployment? 5 Have you encountered any inter-operability or backward- compatibility issues amongst differing implementations? If yes, what are your concerns about these issues? 6 Have you deployed both dense mode and sparse mode in your network? If yes, do you route between these modes using features such as *,*,RP or PMBR? 7 To what extent have you deployed PIM functionality, like BSR, SSM, and Explicit Tracking? 8 Which RP mapping mechanism do you use: Static, AutoRP, or BSR? 9 How many RPs have you deployed in your network? 10 If you use Anycast-RP, is it Anycast-RP using MSDP (RFC 3446) or Anycast-RP using PIM (RFC 4610)? 11 Do you have any other comments on PIM-SM deployment in your network?

1 0

AAA design document pointers
by Jay Ashworth 20 Jun '12

20 Jun '12

My takeaway from the conversations we're having as the second and third-order resultants of the LinkedIn password break is that, if there *is* an accepted definition of the problem, in slices small enough for implementers to understand, a lot of people haven't read it. Including me. *Is* there a good defnition of the current shape of the authentication/ authorization problem as it presently exists in the Wide Area with the General Public as audience, which someone can point to? One that identifies, as it goes along, all the points we batted around today, like "person or PC", "multiple accounts", "non/repudiation", and whatever you call "multiple services not being able to tell you're the same person as an account holder, unless you *want* them to"? Not even the solutions, you understand, just the definition of the problem? Seems to me we're on different pages in the hymnal... Off-list, please; I'll summarize. Cheers, -- jra -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274

1 0

SIXSS not working?
by Hank Nussbacher 20 Jun '12

20 Jun '12

I am seeing all IPv6 prefixes that are monitored by Sixxs as being down and unavailable. Anyone know why? Thanks, Hank

3 5

Cisco Smartnet for 6509E Line Cards
by david peahi 20 Jun '12

20 Jun '12

Can anyone comment on Cisco 6509E Smartnet "chassis" coverage? In the past, "chassis" has always meant, not just the passive chassis itself, but all of the components including supervisor cards, line cards, power supplies, fan trays, etc. Now it appears that Cisco is requiring Smartnet coverage on line cards in addition to the chassis. My understanding is that Smartnet functioned much like insurance policies, where Cisco collected maintenance contract fees year after year, but the devices were generally so reliable that the collected Smartnet fees always far exceeded the dollar amount required to replace failed components. Regards, David

4 4

Saleslurkers - onnet check in greenville nc
by Chris McDonald 20 Jun '12

20 Jun '12

Anyone have it? 638 Chapman Rd., Greenville, NC 28590 Thanks Chris -- Sent from my mobile device

1 0

Re: TW in ohio
by Brian Henson 20 Jun '12

20 Jun '12

Thank you for the information. I just wish they would get it all working. At this point I would be happy with a GRE tunnel to a router that had IPv6. I use tunnel broker now but with the low lease time of the TW dhcp server i have to run the updater script just about every hour to keep the tunnel up. /beginrant When I called the tech support line trying to get information about their IPv6 plans it was like talking to a brick wall. Eventually I got a supervisor on the phone and he stated that there was no need for IPv6. Everytime I talk to their support I feel dumber and dumber. They don't even know the difference between a software issue and a network issue in most cases. I called about seeing extremly high latency at the border router as seen by traceroute at 2 seperate locations and they refused to do anything until I requested them to talk to their supervisor. They put a ticket in to the advanced tech support but I never heard a word from them. /endrant... So maybe they can't do IPv6 until they get the network issues taken care of. Somedays I miss having qwest, their tech support was great. My account was tagged in someway and they usually asked if I would like to be sent straight to level 2 support once they looked up my account. Maybe someone from TW tech support will eventually see our messages and give the official response. Brian Henson On Tue, Jun 19, 2012 at 10:18 PM, <garya(a)completeweb.net> wrote: > Brian, > When I called Roadrunner about a week before IPV6 day, they had trouble > finding > anyone even in the business tech people that knew if it was even partially > working > for residential or not. I also had signed up over a year ago for testing, > heard nothing. > Our datacenter in Columbus is fully IPV6, and I could route a /64 to me > over an > IPV6->IPV4 tunnel to my D-Link DIR-825 router and it worked great, > contacted any > IPV6 site no problems from within my residential RR network. > But as far as native, they have no idea when, if even by year end. > I couldn't even get a straight answer if they were doing IPV6 over their > business class, > so who knows. They don't even have the IPV6 testing signup page any more. > > Gary Anagnostis > CompleteWeb.Net > > > > Anyone here using timewarrner residential able to use IPv6 natively > during > > world IPv6 day? I have the equipment to support it but never saw any > ipv6 > > address being assigned to my firewall. > > > > Brian Henson > > > > >

1 0