May 2011 - NANOG - lists.nanog.org

Huawei Symantec Anti-DDOS
by Andrew Cruse 20 May '11

20 May '11

Anyone demoed or worked with this in production? http://bit.ly/lq6eTY Thoughts on how it stacks up with the usual suspects -- Arbor, etc? Worth looking into? Thanks, Andrew

1 0

Weekly Routing Table Report
by Routing Analysis Role Account 20 May '11

20 May '11

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, 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 <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 21 May, 2011 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 357743 Prefixes after maximum aggregation: 161995 Deaggregation factor: 2.21 Unique aggregates announced to Internet: 176757 Total ASes present in the Internet Routing Table: 37632 Prefixes per ASN: 9.51 Origin-only ASes present in the Internet Routing Table: 31443 Origin ASes announcing only one prefix: 15107 Transit ASes present in the Internet Routing Table: 5101 Transit-only ASes present in the Internet Routing Table: 135 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 36 Max AS path prepend of ASN (48687) 24 Prefixes from unregistered ASNs in the Routing Table: 647 Unregistered ASNs in the Routing Table: 338 Number of 32-bit ASNs allocated by the RIRs: 1366 Number of 32-bit ASNs visible in the Routing Table: 1088 Prefixes from 32-bit ASNs in the Routing Table: 2459 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 166 Number of addresses announced to Internet: 2432900032 Equivalent to 145 /8s, 3 /16s and 27 /24s Percentage of available address space announced: 65.6 Percentage of allocated address space announced: 65.6 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 90.9 Total number of prefixes smaller than registry allocations: 148733 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 89422 Total APNIC prefixes after maximum aggregation: 30028 APNIC Deaggregation factor: 2.98 Prefixes being announced from the APNIC address blocks: 85798 Unique aggregates announced from the APNIC address blocks: 36687 APNIC Region origin ASes present in the Internet Routing Table: 4453 APNIC Prefixes per ASN: 19.27 APNIC Region origin ASes announcing only one prefix: 1236 APNIC Region transit ASes present in the Internet Routing Table: 707 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 21 Number of APNIC region 32-bit ASNs visible in the Routing Table: 46 Number of APNIC addresses announced to Internet: 615312672 Equivalent to 36 /8s, 172 /16s and 237 /24s Percentage of available APNIC address space announced: 78.0 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079 55296-56319, 131072-132095 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, 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: 140448 Total ARIN prefixes after maximum aggregation: 71554 ARIN Deaggregation factor: 1.96 Prefixes being announced from the ARIN address blocks: 112638 Unique aggregates announced from the ARIN address blocks: 45620 ARIN Region origin ASes present in the Internet Routing Table: 14381 ARIN Prefixes per ASN: 7.83 ARIN Region origin ASes announcing only one prefix: 5494 ARIN Region transit ASes present in the Internet Routing Table: 1498 Average ARIN Region AS path length visible: 4.0 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 12 Number of ARIN addresses announced to Internet: 801671424 Equivalent to 47 /8s, 200 /16s and 137 /24s Percentage of available ARIN address space announced: 63.7 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, 173/8, 174/8, 184/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: 84534 Total RIPE prefixes after maximum aggregation: 48247 RIPE Deaggregation factor: 1.75 Prefixes being announced from the RIPE address blocks: 78018 Unique aggregates announced from the RIPE address blocks: 51632 RIPE Region origin ASes present in the Internet Routing Table: 15619 RIPE Prefixes per ASN: 5.00 RIPE Region origin ASes announcing only one prefix: 7813 RIPE Region transit ASes present in the Internet Routing Table: 2464 Average RIPE Region AS path length visible: 4.6 Max RIPE Region AS path length visible: 36 Number of RIPE region 32-bit ASNs visible in the Routing Table: 805 Number of RIPE addresses announced to Internet: 472636160 Equivalent to 28 /8s, 43 /16s and 219 /24s Percentage of available RIPE address space announced: 76.1 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 196608-198655 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, 176/8, 178/8, 185/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 32829 Total LACNIC prefixes after maximum aggregation: 7512 LACNIC Deaggregation factor: 4.37 Prefixes being announced from the LACNIC address blocks: 31866 Unique aggregates announced from the LACNIC address blocks: 16758 LACNIC Region origin ASes present in the Internet Routing Table: 1456 LACNIC Prefixes per ASN: 21.89 LACNIC Region origin ASes announcing only one prefix: 431 LACNIC Region transit ASes present in the Internet Routing Table: 266 Average LACNIC Region AS path length visible: 4.4 Max LACNIC Region AS path length visible: 19 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 220 Number of LACNIC addresses announced to Internet: 83532288 Equivalent to 4 /8s, 250 /16s and 154 /24s Percentage of available LACNIC address space announced: 55.3 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, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 7836 Total AfriNIC prefixes after maximum aggregation: 1877 AfriNIC Deaggregation factor: 4.17 Prefixes being announced from the AfriNIC address blocks: 6175 Unique aggregates announced from the AfriNIC address blocks: 1909 AfriNIC Region origin ASes present in the Internet Routing Table: 448 AfriNIC Prefixes per ASN: 13.78 AfriNIC Region origin ASes announcing only one prefix: 133 AfriNIC Region transit ASes present in the Internet Routing Table: 100 Average AfriNIC Region AS path length visible: 4.8 Max AfriNIC Region AS path length visible: 24 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 5 Number of AfriNIC addresses announced to Internet: 23174656 Equivalent to 1 /8s, 97 /16s and 158 /24s Percentage of available AfriNIC address space announced: 34.5 AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4766 2457 9494 918 Korea Telecom (KIX) 17974 1832 516 32 PT TELEKOMUNIKASI INDONESIA 7545 1556 301 87 TPG Internet Pty Ltd 4755 1472 635 169 TATA Communications formerly 24560 1153 336 184 Bharti Airtel Ltd., Telemedia 7552 1123 1064 7 Vietel Corporation 9583 1082 81 511 Sify Limited 4808 1080 2141 298 CNCGROUP IP network: China169 9829 1039 874 51 BSNL National Internet Backbo 18101 935 116 142 Reliance Infocom Ltd Internet 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 3645 3822 255 bellsouth.net, inc. 4323 1976 1081 397 Time Warner Telecom 18566 1860 354 267 Covad Communications 1785 1786 681 123 PaeTec Communications, Inc. 6478 1693 315 55 AT&T Worldnet Services 20115 1538 1540 635 Charter Communications 19262 1496 4943 300 Verizon Global Networks 7018 1365 7069 890 AT&T WorldNet Services 22773 1330 2897 88 Cox Communications, Inc. 11492 1279 240 15 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 6830 520 1780 321 UPC Distribution Services 34984 514 106 182 BILISIM TELEKOM 3292 460 2062 395 TDC Tele Danmark 20940 457 134 351 Akamai Technologies European 29049 453 33 44 AzerSat LLC. 8866 444 134 26 Bulgarian Telecommunication C 12479 432 577 6 Uni2 Autonomous System 3320 426 8153 371 Deutsche Telekom AG 8551 406 355 45 Bezeq International 702 395 1802 309 UUNET - Commercial IP service 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 1481 273 154 TVCABLE BOGOTA 8151 1375 2702 362 UniNet S.A. de C.V. 28573 1314 991 86 NET Servicos de Comunicao S.A 7303 925 470 151 Telecom Argentina Stet-France 6503 731 354 73 AVANTEL, S.A. 14420 670 54 91 CORPORACION NACIONAL DE TELEC 22047 563 310 15 VTR PUNTO NET S.A. 3816 522 227 101 Empresa Nacional de Telecomun 13489 511 254 124 Orbitel S.A. E.S.P. 11172 493 84 83 Servicios Alestra S.A de C.V 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 894 445 11 TEDATA 24863 787 147 37 LINKdotNET AS number 15475 415 90 8 Nile Online 36992 287 331 17 Etisalat MISR 3741 268 985 228 The Internet Solution 6713 241 215 13 Itissalat Al-MAGHRIB 33776 217 12 11 Starcomms Nigeria Limited 24835 208 78 10 RAYA Telecom - Egypt 29571 163 19 12 Ci Telecom Autonomous system 16637 150 441 86 MTN Network Solutions 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 3645 3822 255 bellsouth.net, inc. 23456 2459 631 1341 32-bit ASN transition 4766 2457 9494 918 Korea Telecom (KIX) 4323 1976 1081 397 Time Warner Telecom 18566 1860 354 267 Covad Communications 17974 1832 516 32 PT TELEKOMUNIKASI INDONESIA 1785 1786 681 123 PaeTec Communications, Inc. 6478 1693 315 55 AT&T Worldnet Services 7545 1556 301 87 TPG Internet Pty Ltd 20115 1538 1540 635 Charter Communications Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 17974 1832 1800 PT TELEKOMUNIKASI INDONESIA 1785 1786 1663 PaeTec Communications, Inc. 6478 1693 1638 AT&T Worldnet Services 18566 1860 1593 Covad Communications 4323 1976 1579 Time Warner Telecom 4766 2457 1539 Korea Telecom (KIX) 7545 1556 1469 TPG Internet Pty Ltd 10620 1481 1327 TVCABLE BOGOTA 4755 1472 1303 TATA Communications formerly 11492 1279 1264 Cable One 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 32567 UNALLOCATED 12.14.170.0/24 4323 Time Warner Telecom 32567 UNALLOCATED 12.25.107.0/24 4323 Time Warner Telecom 26973 UNALLOCATED 12.39.152.0/24 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.154.0/23 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.155.0/24 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.159.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 Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 24.225.128.0/18 36377 Comcast Telecommunications, I 24.225.192.0/23 36377 Comcast Telecommunications, I 24.225.192.0/18 36377 Comcast Telecommunications, I 24.225.224.0/21 36377 Comcast Telecommunications, I 24.225.237.0/24 36377 Comcast Telecommunications, I 24.225.248.0/21 36377 Comcast Telecommunications, I 27.0.128.0/17 7514 Media Exchange, Inc. 41.190.32.0/23 31856 CABSAS 41.190.34.0/23 31856 CABSAS 41.190.36.0/23 31856 CABSAS 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:20 /9:12 /10:28 /11:79 /12:226 /13:461 /14:793 /15:1393 /16:11769 /17:5810 /18:9731 /19:19329 /20:25643 /21:25885 /22:34217 /23:32989 /24:186103 /25:1087 /26:1274 /27:713 /28:165 /29:8 /30:2 /31:0 /32:6 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6389 2245 3645 bellsouth.net, inc. 18566 1824 1860 Covad Communications 6478 1647 1693 AT&T Worldnet Services 10620 1371 1481 TVCABLE BOGOTA 11492 1225 1279 Cable One 23456 1204 2459 32-bit ASN transition 7011 1060 1159 Citizens Utilities 1785 1051 1786 PaeTec Communications, Inc. 4323 886 1976 Time Warner Telecom 22773 846 1330 Cox Communications, Inc. Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:279 2:39 4:14 5:1 6:3 8:352 12:1985 13:1 14:457 15:15 16:3 17:8 20:10 23:7 24:1633 27:753 31:345 32:60 33:4 34:2 37:1 38:738 40:101 41:2537 42:5 44:3 46:920 47:4 49:194 50:415 52:13 55:3 56:2 57:30 58:844 59:481 60:387 61:1235 62:960 63:1935 64:3941 65:2292 66:4158 67:1846 68:1092 69:2985 70:704 71:352 72:1883 73:1 74:2351 75:303 76:340 77:870 78:709 79:464 80:1094 81:821 82:490 83:447 84:629 85:1069 86:594 87:749 88:328 89:1556 90:204 91:3771 92:516 93:1053 94:1279 95:817 96:504 97:249 98:835 99:35 101:60 103:12 106:1 107:7 108:85 109:950 110:601 111:715 112:302 113:401 114:534 115:667 116:956 117:691 118:821 119:1145 120:308 121:677 122:1627 123:1001 124:1265 125:1228 128:262 129:176 130:164 131:573 132:109 133:19 134:218 135:48 136:215 137:143 138:305 139:112 140:487 141:239 142:402 143:402 144:481 145:54 146:444 147:209 148:589 149:243 150:172 151:186 152:306 153:178 154:3 155:396 156:194 157:352 158:135 159:387 160:317 161:207 162:279 163:163 164:501 165:354 166:516 167:433 168:729 169:152 170:794 171:77 172:1 173:1566 174:551 175:374 177:128 178:918 180:844 181:17 182:446 183:207 184:272 185:1 186:1164 187:735 188:842 189:897 190:4805 192:5790 193:4854 194:3482 195:2982 196:1210 197:19 198:3584 199:3908 200:5540 201:1486 202:8357 203:8427 204:4158 205:2326 206:2730 207:2913 208:3964 209:3462 210:2736 211:1392 212:1972 213:1734 214:735 215:71 216:4899 217:1623 218:563 219:362 220:1200 221:483 222:336 223:148 End of report

1 0

Re: corporations using BGP for advertising prefixes in mid-1990s
by Roy 20 May '11

20 May '11

On 5/12/2011 4:03 PM, George Herbert wrote: > .... > Large end-user companies generally multihomed by that time, and you > generally did that by BGP4 at the time (post-1994), and before that > BGP3, and before that EGP, and before that... well, there was little > "commercial ISPness" other than NSFNet connectivity and the regional > networks back then so multihoming was somewhat of a moot point. > > Thank you again, UUNet/Alternet and PSI! > The management of the large end-user company I worked for could barely spell Internet at the beginning of 1995. A few connections to the Internet existed and the lab where I worked was experimenting with a socks-server. There was a large intranet allocated from the company's class A space.

2 1

Re: Had an idea - looking for a math buff to tell me if it's possible with today's technology.
by Landon Stewart 20 May '11

20 May '11

On Thu, May 19, 2011 at 5:05 AM, Vitkovsky, Adam <avitkovsky(a)emea.att.com>wrote: > >"inverse problem" > This is what I believe Landon meant in his original post > > Everybody started talking about compression -but that is I believe sending > the result of the function -where both nodes know the function > > But how hard if at all possible is to figure out a function(or set of > functions) and variables that describe the given data > > And than just send those functions and variables to the other node > And let it to recompute the original file > > Complex function can be represented by simple numbers to shrink down the > amount of data to be sent over the wire > > If the file is: 1048576 > > -than that coule be represneted via: > 1*1 > X=2 > Y=10 > Where both nodes would know that 1 = x^y > Just wanted to say yes, this is entirely what I meant. Of course the smaller the file the more pointless it gets but still... If the file was 1GB instead of just 7 bytes I'm wondering if a regular old workstation could put it back together in any reasonable amount of time with the equation. -- Landon Stewart <LStewart(a)SUPERB.NET> SuperbHosting.Net by Superb Internet Corp. Toll Free (US/Canada): 888-354-6128 x 4199 Direct: 206-438-5879 Web hosting and more "Ahead of the Rest": http://www.superbhosting.net

4 3

High throughput switches...
by Jamie Bowden 19 May '11

19 May '11

I'm looking for people's experiences with Voltaire switches in general and the Vantage 6048 in particular. We'd like to use a central switch and use 16 10g ports trunked via LACP to two other switches and a SAN (to clarify, the central switch would have three data channels, each one consisting of 16 trunked 10g ports, the two downstream switches would have 10gb clients hanging off of them and I'm not sure how the SAN is supposed to use 16 10g ports; they haven't felt the need to give me specs on it, but for now I'm assuming it either has a built in switch fabric that supports LACP or will have another switch dedicated to it can handle different L1 media). Assuming we can bond that many channels (which I'm not sure about, but none of the docs I've read on the IEEE protocol involved indicate a limit on the number ports that can be aggregated, and the manufacturer docs don't mention it either), how realistic is the expectation of getting a full 160gb throughput? Are the switches in question up to the task? This is a research project we're building for a customer, so I'm trying to manage expectations, but this isn't the sort of thing I've personally ever built before and I'm hoping someone here has done something close enough and is willing to share experiences. Thanks, Jamie

2 1

Experience with Open Source load balancers?
by Welch, Bryan 19 May '11

19 May '11

Greetings all. I've been tasked with comparing the use of open source load balancing software against commercially available off the shelf hardware such as F5, which is what we currently use. We use the load balancers for traditional load balancing, full proxy for http/ssl traffic, ssl termination and certificate management, ssl and http header manipulation, nat, high availability of the physical hardware and stateful failover of the tcp sessions. These units will be placed at the customer prem supporting our applications and services and we'll need to support them accordingly. Now my "knee jerk" reaction to this is that it's a really bad idea. It is the heart and soul of our data center network after all. However, once I started to think about it I realized that I hadn't had any real experience with this solution beyond tinkering with it at home and reading about it in years past. Can anyone offer any operational insight and real world experiences with these solutions? TIA, replies off list are welcomed. Regards, Bryan

14 16

IPv6 Conventions
by Todd Snyder 19 May '11

19 May '11

As I start working more and more with IPv6 and find myself having to address services, I am wondering if there are any sort of written or unwritten 'conventions'/best practices that are being adopted about how to address devices/servers/services. Specifically: 1) Is there a general convention about addresses for DNS servers? NTP servers? dhcp servers? 2) Are we tending to use different IPs for each service on a device? 3) Any common addresses/schemes for other common services? (smtp/snmp/http/ldap/etc)? Similarly, I've been referring to http://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xml for a list of the 'reserved' space - are there any other blocks/conventions around addressing that exist? Finally, what tools do people find themselves using to manage IPv6 and addressing? It seems to me that IPAM is almost required to manage IPv6 in any sane way, even for very small deployments (My home ISP gave me a /56 and a /64). I figured this was a fairly operational question/set of questions, so I hope this is the right venue. Cheers, Todd.

7 9

IPv6 and RDNS
by Rodolfo (kix) 19 May '11

19 May '11

Hi! what is the status of the reverse DNS in IPv6? The draft "http://tools.ietf.org/html/draft-howard-isp-ip6rdns-04" is expired. What are the network operators doing? Regards, kix -- Rodolfo García "kix" http://www.kix.es/ ham: EA4ERH @ IN80ER

3 2

Re: Yahoo and IPv6
by Paul Vixie 19 May '11

19 May '11

Matthew Kaufman <matthew(a)matthew.at> writes: >> My Desktop is not able to make any IPv4 socket connections anymore. I get >> "Protocol not supported". So there are IPv6-only users, already bitten by >> no AAAA. So that's -1 from me. > > Sounds to me like you're not on The Internet any more. in <http://www.merit.edu/mail.archives/nanog/2001-04/msg00294.html> we see: (*2) Q: But what IS the Internet? A: "It's the largest equivalence class in the reflexive, transitive, symmetric, closure of the relationship 'can be reached by an IP packet from'". Seth Breidbart by which definition, matthew's observation would be correct. folks who want to run V6 only and still be "on the internet" will need proxies for a long while. folks who want to run V6 only *today* and not have any proxies *today* are sort of on their own -- the industry will not cater to market non-forces. -- Paul Vixie KI6YSY

20 32

Re: user-relative names - was:[Re: Yahoo and IPv6]
by Scott Weeks 18 May '11

18 May '11

--- joelja(a)bogus.com wrote: From: Joel Jaeggli <joelja(a)bogus.com> On May 17, 2011, at 4:30 PM, Scott Brim wrote: > On May 17, 2011 6:26 PM, <Valdis.Kletnieks(a)vt.edu> wrote: >> On Tue, 17 May 2011 15:04:19 PDT, Scott Weeks said: >> >>> What about privacy concerns >> >> "Privacy is dead. Get used to it." -- Scott McNeely > > Forget that attitude, Valdis. Just because privacy is blown at one level > doesn't mean you give it away at every other one. We establish the framework > for recovering privacy and make progress step by step, wherever we can. > Someday we'll get it all back under control. if you put something in the dns you do so because you want to discovered. scoping the nameservers such that they only express certain certain resource records to queriers in a particular scope is fairly straight forward. -------------------------------------------------------- The article was not about DNS. It was about "Persistent Personal Names for Globally Connected Mobile Devices" where "Users normally create personal names by introducing devices locally, on a common WiFi network for example. Once created, these names remain persistently bound to their targets as devices move. Personal names are intended to supplement and not replace global DNS names." I see a lot of folks on lists designing future networks where an identifier follows you everywhere and we as operators will have to deal with a public hostile to the idea of being followed. It's happening now. Just read all the articles on privacy lost. It's not going to go away. People like their privacy whether they're doing bad things or not. scott

3 2