- NANOG - lists.nanog.org

ISC DHCPD
by Butch Evans 16 Jul '10

16 Jul '10

I have a cisco cmts that forwards dhcp requests to an ISC dhcp server. I have a working configuration for this. I am trying to set up ISC DHCPD so that it can handle multiple shared-networks. I cannot seem to get this working correctly. If there is an expert "in the house" who can offer me a few minutes of your time to look over a configuration for me, please send me a phone number/email offlist and I'll discuss specifics. -- ******************************************************************** * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/ * Network Engineering * * http://store.wispgear.net/ * Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * ********************************************************************

1 1

Weekly Routing Table Report
by Routing Analysis Role Account 16 Jul '10

16 Jul '10

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 NANOG, AfNOG, AusNOG, SANOG, PacNOG, LacNOG and the RIPE Routing Working Group. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.apnic.net. If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 17 Jul, 2010 Report Website: http://thyme.apnic.net Detailed Analysis: http://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 325312 Prefixes after maximum aggregation: 149926 Deaggregation factor: 2.17 Unique aggregates announced to Internet: 159012 Total ASes present in the Internet Routing Table: 34366 Prefixes per ASN: 9.47 Origin-only ASes present in the Internet Routing Table: 29833 Origin ASes announcing only one prefix: 14455 Transit ASes present in the Internet Routing Table: 4533 Transit-only ASes present in the Internet Routing Table: 100 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 25 Max AS path prepend of ASN (41664) 21 Prefixes from unregistered ASNs in the Routing Table: 308 Unregistered ASNs in the Routing Table: 118 Number of 32-bit ASNs allocated by the RIRs: 686 Prefixes from 32-bit ASNs in the Routing Table: 825 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 166 Number of addresses announced to Internet: 2276042112 Equivalent to 135 /8s, 169 /16s and 165 /24s Percentage of available address space announced: 61.4 Percentage of allocated address space announced: 66.2 Percentage of available address space allocated: 92.8 Percentage of address space in use by end-sites: 83.8 Total number of prefixes smaller than registry allocations: 154768 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 78953 Total APNIC prefixes after maximum aggregation: 27110 APNIC Deaggregation factor: 2.91 Prefixes being announced from the APNIC address blocks: 75847 Unique aggregates announced from the APNIC address blocks: 33498 APNIC Region origin ASes present in the Internet Routing Table: 4111 APNIC Prefixes per ASN: 18.45 APNIC Region origin ASes announcing only one prefix: 1138 APNIC Region transit ASes present in the Internet Routing Table: 633 Average APNIC Region AS path length visible: 3.6 Max APNIC Region AS path length visible: 15 Number of APNIC addresses announced to Internet: 531282208 Equivalent to 31 /8s, 170 /16s and 185 /24s Percentage of available APNIC address space announced: 79.2 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, 43/8, 58/8, 59/8, 60/8, 61/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: 134218 Total ARIN prefixes after maximum aggregation: 69466 ARIN Deaggregation factor: 1.93 Prefixes being announced from the ARIN address blocks: 107063 Unique aggregates announced from the ARIN address blocks: 41911 ARIN Region origin ASes present in the Internet Routing Table: 13792 ARIN Prefixes per ASN: 7.76 ARIN Region origin ASes announcing only one prefix: 5279 ARIN Region transit ASes present in the Internet Routing Table: 1357 Average ARIN Region AS path length visible: 3.4 Max ARIN Region AS path length visible: 22 Number of ARIN addresses announced to Internet: 729625120 Equivalent to 43 /8s, 125 /16s and 50 /24s Percentage of available ARIN address space announced: 62.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, 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, 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, 54/8, 55/8, 56/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, 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: 74811 Total RIPE prefixes after maximum aggregation: 43408 RIPE Deaggregation factor: 1.72 Prefixes being announced from the RIPE address blocks: 67993 Unique aggregates announced from the RIPE address blocks: 44455 RIPE Region origin ASes present in the Internet Routing Table: 14604 RIPE Prefixes per ASN: 4.66 RIPE Region origin ASes announcing only one prefix: 7511 RIPE Region transit ASes present in the Internet Routing Table: 2179 Average RIPE Region AS path length visible: 3.9 Max RIPE Region AS path length visible: 24 Number of RIPE addresses announced to Internet: 434075776 Equivalent to 25 /8s, 223 /16s and 120 /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, 196608-197631 RIPE Address Blocks 2/8, 25/8, 31/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, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 28966 Total LACNIC prefixes after maximum aggregation: 6957 LACNIC Deaggregation factor: 4.16 Prefixes being announced from the LACNIC address blocks: 27578 Unique aggregates announced from the LACNIC address blocks: 14516 LACNIC Region origin ASes present in the Internet Routing Table: 1307 LACNIC Prefixes per ASN: 21.10 LACNIC Region origin ASes announcing only one prefix: 410 LACNIC Region transit ASes present in the Internet Routing Table: 232 Average LACNIC Region AS path length visible: 3.9 Max LACNIC Region AS path length visible: 25 Number of LACNIC addresses announced to Internet: 75606464 Equivalent to 4 /8s, 129 /16s and 169 /24s Percentage of available LACNIC address space announced: 56.3 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 262144-263167 plus ERX transfers LACNIC Address Blocks 177/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: 7287 Total AfriNIC prefixes after maximum aggregation: 1866 AfriNIC Deaggregation factor: 3.91 Prefixes being announced from the AfriNIC address blocks: 5592 Unique aggregates announced from the AfriNIC address blocks: 1599 AfriNIC Region origin ASes present in the Internet Routing Table: 380 AfriNIC Prefixes per ASN: 14.72 AfriNIC Region origin ASes announcing only one prefix: 117 AfriNIC Region transit ASes present in the Internet Routing Table: 85 Average AfriNIC Region AS path length visible: 3.7 Max AfriNIC Region AS path length visible: 14 Number of AfriNIC addresses announced to Internet: 19625216 Equivalent to 1 /8s, 43 /16s and 117 /24s Percentage of available AfriNIC address space announced: 58.5 AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4766 1859 8425 493 Korea Telecom (KIX) 7545 1379 232 105 TPG Internet Pty Ltd 4755 1375 297 162 TATA Communications formerly 17488 1333 145 127 Hathway IP Over Cable Interne 17974 1166 285 51 PT TELEKOMUNIKASI INDONESIA 9583 1001 74 485 Sify Limited 24560 957 305 178 Bharti Airtel Ltd., Telemedia 4134 879 21740 411 CHINANET-BACKBONE 4808 824 1572 215 CNCGROUP IP network: China169 9829 813 685 32 BSNL National Internet Backbo Complete listing at http://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 6389 3891 3718 287 bellsouth.net, inc. 4323 2717 1112 393 Time Warner Telecom 19262 1827 4562 274 Verizon Global Networks 1785 1780 698 129 PaeTec Communications, Inc. 20115 1548 1524 653 Charter Communications 7018 1484 5736 963 AT&T WorldNet Services 2386 1284 568 905 AT&T Data Communications Serv 6478 1257 253 197 AT&T Worldnet Services 22773 1173 2859 65 Cox Communications, Inc. 3356 1162 10879 405 Level 3 Communications, LLC Complete listing at http://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 35805 652 56 6 United Telecom of Georgia 9198 497 202 13 Kazakhtelecom Data Network Ad 3292 452 2027 393 TDC Tele Danmark 30890 440 111 206 Evolva Telecom 702 413 1869 325 UUNET - Commercial IP service 8866 402 117 18 Bulgarian Telecommunication C 8551 400 353 46 Bezeq International 3320 373 7329 324 Deutsche Telekom AG 3301 372 1414 327 TeliaNet Sweden 34984 362 89 183 BILISIM TELEKOM Complete listing at http://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 1529 3033 248 UniNet S.A. de C.V. 10620 1072 240 149 TVCABLE BOGOTA 28573 1042 812 99 NET Servicos de Comunicao S.A 7303 736 390 93 Telecom Argentina Stet-France 6503 700 177 219 AVANTEL, S.A. 22047 551 310 15 VTR PUNTO NET S.A. 3816 503 218 88 Empresa Nacional de Telecomun 14420 498 32 72 CORPORACION NACIONAL DE TELEC 7738 477 922 30 Telecomunicacoes da Bahia S.A 11172 449 99 76 Servicios Alestra S.A de C.V Complete listing at http://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 8452 1101 445 10 TEDATA 24863 727 147 39 LINKdotNET AS number 36992 650 279 185 Etisalat MISR 3741 267 834 229 The Internet Solution 33776 220 12 12 Starcomms Nigeria Limited 2018 209 244 61 Tertiary Education Network 6713 195 186 16 Itissalat Al-MAGHRIB 24835 189 78 9 RAYA Telecom - Egypt 29571 177 19 10 Ci Telecom Autonomous system 16637 166 440 95 MTN Network Solutions Complete listing at http://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 6389 3891 3718 287 bellsouth.net, inc. 4323 2717 1112 393 Time Warner Telecom 4766 1859 8425 493 Korea Telecom (KIX) 19262 1827 4562 274 Verizon Global Networks 1785 1780 698 129 PaeTec Communications, Inc. 20115 1548 1524 653 Charter Communications 8151 1529 3033 248 UniNet S.A. de C.V. 7018 1484 5736 963 AT&T WorldNet Services 7545 1379 232 105 TPG Internet Pty Ltd 4755 1375 297 162 TATA Communications formerly Complete listing at http://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 4323 2717 2324 Time Warner Telecom 1785 1780 1651 PaeTec Communications, Inc. 19262 1827 1553 Verizon Global Networks 4766 1859 1366 Korea Telecom (KIX) 8151 1529 1281 UniNet S.A. de C.V. 7545 1379 1274 TPG Internet Pty Ltd 4755 1375 1213 TATA Communications formerly 17488 1333 1206 Hathway IP Over Cable Interne 17974 1166 1115 PT TELEKOMUNIKASI INDONESIA 22773 1173 1108 Cox Communications, Inc. Complete listing at http://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 16927 UNALLOCATED 12.0.252.0/23 7018 AT&T WorldNet Servic 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.14.170.0/24 7018 AT&T WorldNet Servic 13746 UNALLOCATED 12.24.56.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.25.107.0/24 7018 AT&T WorldNet Servic 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 Complete listing at http://thyme.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 31.0.0.0/16 12654 RIPE NCC RIS Project 31.1.0.0/21 12654 RIPE NCC RIS Project 31.1.24.0/24 12654 RIPE NCC RIS Project 41.222.79.0/24 36938 >>UNKNOWN<< 41.223.92.0/22 36936 >>UNKNOWN<< 41.223.188.0/24 22351 Intelsat 41.223.189.0/24 6453 Teleglobe Inc. 41.223.196.0/24 36990 Alkan Telecom Ltd 41.223.197.0/24 36990 Alkan Telecom Ltd 41.223.198.0/24 36990 Alkan Telecom Ltd Complete listing at http://thyme.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:21 /9:10 /10:25 /11:68 /12:197 /13:408 /14:713 /15:1289 /16:11185 /17:5357 /18:9179 /19:18475 /20:23046 /21:23004 /22:29925 /23:29564 /24:169691 /25:1006 /26:1277 /27:702 /28:110 /29:47 /30:6 /31:0 /32:7 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6389 2491 3891 bellsouth.net, inc. 4766 1487 1859 Korea Telecom (KIX) 4323 1392 2717 Time Warner Telecom 1785 1241 1780 PaeTec Communications, Inc. 17488 1078 1333 Hathway IP Over Cable Interne 11492 1068 1160 Cable One 18566 1068 1087 Covad Communications 8452 993 1101 TEDATA 10620 988 1072 TVCABLE BOGOTA 7018 885 1484 AT&T WorldNet Services Complete listing at http://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:10 2:2 4:13 8:287 12:2018 13:7 14:1 15:22 16:3 17:8 20:6 24:1464 27:251 31:1 32:49 33:12 38:688 40:98 41:2399 44:3 46:2 47:17 52:9 55:5 56:2 57:28 58:755 59:503 60:461 61:1088 62:1042 63:1970 64:3678 65:2347 66:4045 67:1828 68:1109 69:2690 70:723 71:385 72:1947 73:2 74:2262 75:248 76:316 77:897 78:619 79:430 80:974 81:765 82:492 83:444 84:680 85:1050 86:458 87:682 88:340 89:1563 90:94 91:2875 92:503 93:987 94:1401 95:645 96:356 97:212 98:610 99:31 108:100 109:567 110:384 111:547 112:286 113:319 114:431 115:568 116:1088 117:654 118:483 119:880 120:131 121:728 122:1483 123:944 124:1116 125:1322 128:226 129:199 130:196 131:553 132:247 133:17 134:195 135:45 136:241 137:145 138:265 139:104 140:483 141:197 142:337 143:370 144:470 145:50 146:449 147:167 148:663 149:301 150:153 151:229 152:298 153:169 154:2 155:359 156:160 157:296 158:109 159:356 160:316 161:183 162:249 163:177 164:405 165:365 166:458 167:414 168:649 169:157 170:708 171:59 172:2 173:942 174:480 175:146 176:1 178:301 180:522 182:149 183:235 184:111 186:499 187:391 188:1008 189:768 190:3813 192:5737 193:4719 194:3396 195:2800 196:1192 198:3577 199:3456 200:5336 201:1565 202:7972 203:8285 204:4074 205:2319 206:2486 207:3104 208:3864 209:3453 210:2532 211:1272 212:1711 213:1663 214:639 215:69 216:4699 217:1525 218:498 219:378 220:1149 221:402 222:316 223:1 End of report

1 0

Vyatta as a BRAS
by Sharef Mustafa 16 Jul '10

16 Jul '10

Have anyone tried Vyatta router instead of a Cisco 7200 as BRAS for adsl customers? If so, what model? do you recommend it? BR Sharef

33 71

Re: [c-nsp] L2VPN with IP address
by Kornelijus Survila 16 Jul '10

16 Jul '10

The multihop BGP solution might be the best one with least overhead; however you should be able to use a GRE tunnel if you still want to do this: interface Tunnel1 ip address 10.10.10.1 255.255.255.252 tunnel source FastEthernet0/0 tunnel destination small.router.ip interface Tunnel1 ip address 10.10.10.2 255.255.255.252 tunnel source FastEthernet0/0 tunnel destination big.router.ip -k On Thu, Jul 15, 2010 at 7:40 PM, Pshem Kowalczyk <pshem.k(a)gmail.com> wrote: > Hi, > > I have a situation, where a customer wants a full BGP table > (persuasion failed already), but is connected to small router (2821), > with not enough memory to get anywhere near full table. I have few > other routers (ASR1K, 7600) that would normally be used for that, but > are in far-away locations. Of course I can set up a local BGP session > and then add a multihop one for the full feed, but that doesn't seem > like an elegant solution any more. All the routers run MPLS, so if I > could get a xconnect going between one of the bigger boxes and the > small PE, without actually wasting port on the bigger router (by > having some sort of logical interface) then I could run the BGP > session directly. I had a look on Cisco website, but either it's not > possible or that kind of bridging has a special name that I can't pin > down. If you've heard of such feature - please let me know. > > kind regards > Pshem > _______________________________________________ > cisco-nsp mailing list cisco-nsp(a)puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ >

2 1

IP Address Management Tool
by D C 16 Jul '10

16 Jul '10

I am looking for a better way to manage IP addresses. I am currently using an excel spreadsheet, but this is becoming cumbersome as more and more addresses are being added. Does anyone have any recommendations? Thanks, Danielle

22 26

First signed root zone published
by Matt Larson 15 Jul '10

15 Jul '10

I am pleased to report that the first fully validatable production signed root zone, with SOA serial number 2010071501, was published and began rolling out to the root servers at 1625 UTC. More details to follow in a formal update. Matt ...on behalf of the root DNSSEC design team

1 2

ARIN's Whois-RWS Directory Service Available 17 July
by Mark Kosters 15 Jul '10

15 Jul '10

<Apologies for the duplicate email but want to keep you informed about changes occurring at ARIN. This particular upgrade may be of interest to those who are not subscribed to arin-announce.> ----- Forwarded message from Member Services <info(a)arin.net> ----- From: Member Services <info(a)arin.net> Date: Thu, 15 Jul 2010 16:03:37 -0400 To: "arin-announce(a)arin.net" <arin-announce(a)arin.net> Subject: [arin-announce] ARIN's Whois-RWS Directory Service Available 17 July ARIN is pleased to announce that it will deploy its Whois-RWS service on 17 July 2010. We have corrected the issues that impacted the first release and are now able to bring you the following services that provide the general public with access to ARIN's registration data: * a RESTful Web Service (RWS) * a NICNAME/WHOIS port 43 service * a user-friendly web site (http://whois.arin.net) When using the Whois-RWS you will notice some differences in behavior for certain queries and corresponding result sets on the NICNAME/WHOIS port 43 service. The detailed documentation on these differences has been updated and is now available at: https://www.arin.net/resources/whoisrws/whois_diff.html ARIN?s Directory Service for registration data has used the NICNAME/WHOIS protocol since its inception. The limitations of the NICNAME/WHOIS protocol are well known and documented in RFC3912. Whois-RWS was created as an alternative to the ARIN Whois and will provide much richer functionality and capability to the community. ARIN continues to welcome community participation on the Whois-RWS mailing list, and we invite you to subscribe and share your experience and feedback about the new service: http://lists.arin.net/mailman/listinfo/arin-whoisrws Regards, Mark Kosters Chief Technical Officer American Registry for Internet Numbers (ARIN) ----- End forwarded message -----

1 0

[Bruce Hoffman] Thank-you for your recent participation.
by Robert E. Seastrom 15 Jul '10

15 Jul '10

Amusingly, this was sent to me *after* I replied to abuse@internap complaining about getting spammed. Anyone else getting spam from this joker? Has he been doing nanog mailing list or arin database harvesting? Anyone know who his boss is? -r

7 9

Root Zone DNSSEC Deployment Technical Status Update
by Joe Abley 14 Jul '10

14 Jul '10

Root Zone DNSSEC Deployment Technical Status Update 2010-07-14 This is the eleventh of a series of technical status updates intended to inform a technical audience on progress in signing the root zone of the DNS. RESOURCES Details of the project, including documentation published to date, can be found at <http://www.root-dnssec.org/>. We'd like to hear from you. If you have feedback for us, please send it to rootsign(a)icann.org. KSK CEREMONY 2 COMPLETE The second KSK ceremony for the root zone was completed this week in El Segundo, CA, USA. The Ceremony Administrator was Mehmet Akcin. The second production Key Signing Request (KSR) generated by VeriSign has now been processed by ICANN using the root zone KSK generated in KSK Ceremony 1, and the resulting Signed Key Response (SKR) has been accepted by VeriSign. This SKR contains signatures for Q4 2010, for use between 2010-10-01 and 2010-12-31. Audit materials relating to both the first and second ceremonies will be published today at <http://www.iana.org/dnssec/>. FULL PRODUCTION SIGNED ROOT ZONE The transition from Deliberately-Unvalidatable Root Zone (DURZ) to production signed root zone is scheduled take place on 2010-07-15 within a maintenance window which begins at 1930 UTC and ends at 2330 UTC. This is the usual window for the generation and distribution of root zones with SOA serials ending in 01. PLANNED DEPLOYMENT SCHEDULE Already completed: 2010-01-27: L starts to serve DURZ 2010-02-10: A starts to serve DURZ 2010-03-03: M, I start to serve DURZ 2010-03-24: D, K, E start to serve DURZ 2010-04-14: B, H, C, G, F start to serve DURZ 2010-05-05: J starts to serve DURZ 2010-06-16: First Key Signing Key (KSK) Ceremony 2010-07-12: Second Key Signing Key (KSK) Ceremony To come: 2010-07-15: Distribution of validatable, production, signed root zone; publication of root zone trust anchor (Please note that this schedule is tentative and subject to change based on testing results or other unforeseen factors.)

1 0

OER/PfR with BGP for inbound load sharing
by Dylan Ebner 14 Jul '10

14 Jul '10

Does anyone have any experience with using OER for inbound load sharing? I am looking to see if people are generaly satisfied with it's abilities or if I should look for other options to balance my inbound traffic. I have two connections (one 50Mb and one 25Mb) with partial BGP routes across two routers that I would like to move from an active/standby model to a more active/active model. Our organization moves very little information out of our forward facing precessence servers so outbound balancing is not as important. Almost 80% of our inbound traffic is VPN as well so using application discovery isn't that important either. Some specific questions I have are: Is OER aware of traffic-shape or bandwidth contstraints that are applied to an interface? Does OER simply add prepending for my advertised routes to my upstreams or does it actually prepend AS from inbound providers to move specific traffic from an AS to one of my underutilized connections? Does OER have to ability to control inbound traffic on a subnet level within the same AS? We receive a ton of data from a few AS numbers, so simply moving a single AS to a different connection may not be extremely effective. Thanks. Dylan Ebner

2 1