September 2016 - Test - lists.nanog.org

Root and ARPA DNSSEC operational message -- signature validity period
by Wessels, Duane 06 Sep '16

06 Sep '16

DNSSEC signatures in the Root and ARPA zones are currently given a validity period of 10 days. The validity period is being increased to 13 days, per the recommendations of RSSAC's Report on Root Zone TTLs [1] (aka RSSAC003). Note that we are not aware of any cases where the 10-day signature validity period has caused problems for DNSSEC validators. This is a precautionary measure designed to accommodate a worst-case scenario. This change will be implemented on September 6, 2016. Please feel free to contact us at RZM(a)verisign.com with concerns or questions, and to forward this notice to others who may not have already received it. [1] https://www.icann.org/en/system/files/files/rssac-003-root-zone-ttls-21aug1… DW

1 1

HUAWEI S6700 - VLANIF MAC ADDRESS
by Josivan Barbosa 06 Sep '16

06 Sep '16

Hi all I have a Huawei S6700 and each vlanif has a different mac. Is there any way so that all vlanifs have the same mac address? In brocades switches, for example, all ports have the same mac. Thanks. Josivan Barbosa

1 0

Last call for presentations and Draft programme for RIPE 73
by Benno Overeinder 06 Sep '16

06 Sep '16

Colleagues, A list of currently accepted RIPE 73 presentations is now published at: https://ripe73.ripe.net/programme/meeting-plan/draft-programme/ There are still few slots remaining for a final RIPE 73 programme and RIPE Programme Committee will accept new proposals until 25 September 2016. This is our last call for you to submit your proposals. You can find the CFP for RIPE 73 below, or at https://ripe73.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. 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 RIPE PC Chair https://www.ripe.net/participate/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 73 will take place from 24-28 October 2016 in Madrid, Spain. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 73. See the full descriptions of the different presentation formats, https://ripe73.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 25 September 2016. Proposals submitted after this date will be considered depending on the remaining available space in the programme. 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 - Internet of Things (IoT) 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. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe73.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe73.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice---in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals 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, presenters/panellists should 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/

1 0

measuring web similarity from dual-stacked hosts
by Bajpai, Vaibhav 05 Sep '16

05 Sep '16

Dear NANOG, Measuring Web Similarity from Dual-stacked Hosts ------------------------------------------------ How similar are the webpages accessed over IPv6 to their IPv4 counterparts? – In situations where the content is dissimilar over IPv4 and IPv6, what factors contribute to the dissimilarity? To answer ^ we developed a tool (simweb) and deployed it on 80 geographically distributed dual-stacked SamKnows probes. A paper presenting results from the collected dataset got accepted recently. We just released the tool and the paper [a]. Thought to share it along. [a] http://goo.gl/sAsDcG Feedback most welcome! You may recall a presentation of this work at RIPE 72 [b]. [b] https://ripe72.ripe.net/archives/video/126 Abstract -------- We compare the similarity of webpages delivered over IPv4 and IPv6. Using the SamKnows web performance (webget) test, we implemented an extension (simweb) that allows us to measure the similarity of webpages. The simweb test measures against ALEXA top 100 dual-stacked websites from 80 SamKnows probes connected to dual-stacked networks representing 58 different ASes. Using a two months-long dataset we show that 14% of these dual-stacked websites exhibit a dissimilarity in the number of fetched webpage elements, with 94% of them exhibiting a dissimilarity in their size. We show that 6% of these websites announce AAAA entries in the DNS but no content is delivered over IPv6 when an HTTP request is made. We also noticed several cases where not all webpage elements (such as images, javascript and CSS) of a dual-stacked website are available over IPv6. We show that 27% of the dual-stacked websites have some fraction of webpage elements that fail over IPv6, with 9% of the websites having more than 50% webpage elements that fail over IPv6. We perform a causality analysis and also identify sources for these failing elements. We show that 12% of these websites have more than 50% webpage elements that belong to the same origin source and fail over IPv6. Failure rates are largely affected by DNS resolution error on images, javascript and CSS content delivered from both same-origin and cross-origin sources. These failures tend to cripple experience for users behind an IPv6-only network and a quantification of failure cases may help improve IPv6 adoption on the Internet. -- Vaibhav =================================== Vaibhav Bajpai www.vaibhavbajpai.com Postdoctoral Researcher Jacobs University Bremen, Germany ===================================

1 0

Weekly Routing Table Report
by cscora＠apnic.net 02 Sep '16

02 Sep '16

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, AusNOG, SANOG, PacNOG, SAFNOG, SdNOG, BJNOG, CaribNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 03 Sep, 2016 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 608392 Prefixes after maximum aggregation (per Origin AS): 219785 Deaggregation factor: 2.77 Unique aggregates announced (without unneeded subnets): 297057 Total ASes present in the Internet Routing Table: 54732 Prefixes per ASN: 11.12 Origin-only ASes present in the Internet Routing Table: 36408 Origin ASes announcing only one prefix: 15422 Transit ASes present in the Internet Routing Table: 6497 Transit-only ASes present in the Internet Routing Table: 177 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 54 Max AS path prepend of ASN ( 55644) 51 Prefixes from unregistered ASNs in the Routing Table: 60 Unregistered ASNs in the Routing Table: 15 Number of 32-bit ASNs allocated by the RIRs: 15289 Number of 32-bit ASNs visible in the Routing Table: 11827 Prefixes from 32-bit ASNs in the Routing Table: 46954 Number of bogon 32-bit ASNs visible in the Routing Table: 56 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 380 Number of addresses announced to Internet: 2824303844 Equivalent to 168 /8s, 87 /16s and 116 /24s Percentage of available address space announced: 76.3 Percentage of allocated address space announced: 76.3 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.2 Total number of prefixes smaller than registry allocations: 197819 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 156248 Total APNIC prefixes after maximum aggregation: 43060 APNIC Deaggregation factor: 3.63 Prefixes being announced from the APNIC address blocks: 169530 Unique aggregates announced from the APNIC address blocks: 68826 APNIC Region origin ASes present in the Internet Routing Table: 5189 APNIC Prefixes per ASN: 32.67 APNIC Region origin ASes announcing only one prefix: 1158 APNIC Region transit ASes present in the Internet Routing Table: 939 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 54 Number of APNIC region 32-bit ASNs visible in the Routing Table: 2347 Number of APNIC addresses announced to Internet: 759491140 Equivalent to 45 /8s, 68 /16s and 234 /24s 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, 64297-64395, 131072-137529 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: 183404 Total ARIN prefixes after maximum aggregation: 89371 ARIN Deaggregation factor: 2.05 Prefixes being announced from the ARIN address blocks: 189103 Unique aggregates announced from the ARIN address blocks: 88251 ARIN Region origin ASes present in the Internet Routing Table: 16207 ARIN Prefixes per ASN: 11.67 ARIN Region origin ASes announcing only one prefix: 5710 ARIN Region transit ASes present in the Internet Routing Table: 1713 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 1433 Number of ARIN addresses announced to Internet: 1105903584 Equivalent to 65 /8s, 234 /16s and 191 /24s ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-397212 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: 145404 Total RIPE prefixes after maximum aggregation: 71686 RIPE Deaggregation factor: 2.03 Prefixes being announced from the RIPE address blocks: 155575 Unique aggregates announced from the RIPE address blocks: 96261 RIPE Region origin ASes present in the Internet Routing Table: 18117 RIPE Prefixes per ASN: 8.59 RIPE Region origin ASes announcing only one prefix: 7831 RIPE Region transit ASes present in the Internet Routing Table: 3020 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 27 Number of RIPE region 32-bit ASNs visible in the Routing Table: 5030 Number of RIPE addresses announced to Internet: 708253568 Equivalent to 42 /8s, 55 /16s and 23 /24s 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, 64396-64495 196608-207259 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: 61769 Total LACNIC prefixes after maximum aggregation: 12381 LACNIC Deaggregation factor: 4.99 Prefixes being announced from the LACNIC address blocks: 77242 Unique aggregates announced from the LACNIC address blocks: 37237 LACNIC Region origin ASes present in the Internet Routing Table: 2476 LACNIC Prefixes per ASN: 31.20 LACNIC Region origin ASes announcing only one prefix: 551 LACNIC Region transit ASes present in the Internet Routing Table: 582 Average LACNIC Region AS path length visible: 4.8 Max LACNIC Region AS path length visible: 22 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 2764 Number of LACNIC addresses announced to Internet: 170489920 Equivalent to 10 /8s, 41 /16s and 120 /24s 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: 14552 Total AfriNIC prefixes after maximum aggregation: 3277 AfriNIC Deaggregation factor: 4.44 Prefixes being announced from the AfriNIC address blocks: 16562 Unique aggregates announced from the AfriNIC address blocks: 6170 AfriNIC Region origin ASes present in the Internet Routing Table: 732 AfriNIC Prefixes per ASN: 22.63 AfriNIC Region origin ASes announcing only one prefix: 172 AfriNIC Region transit ASes present in the Internet Routing Table: 180 Average AfriNIC Region AS path length visible: 4.6 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 253 Number of AfriNIC addresses announced to Internet: 79780096 Equivalent to 4 /8s, 193 /16s and 89 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5541 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3524 382 250 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 3208 11146 1129 KIXS-AS-KR Korea Telecom, KR 17974 2943 904 78 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9829 2679 1494 527 BSNL-NIB National Internet Backbone, IN 9808 2144 8781 42 CMNET-GD Guangdong Mobile Communication 4755 2057 429 227 TATACOMM-AS TATA Communications formerl 4808 1761 2291 524 CHINA169-BJ China Unicom Beijing Provin 45899 1570 1227 93 VNPT-AS-VN VNPT Corp, VN 24560 1538 508 220 AIRTELBROADBAND-AS-AP 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 3508 2964 146 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 6389 2201 3671 41 BELLSOUTH-NET-BLK - BellSouth.net Inc., 18566 2195 405 110 MEGAPATH5-US - MegaPath Corporation, US 20115 1936 1977 403 CHARTER-NET-HKY-NC - Charter Communicat 30036 1767 343 251 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 1702 5073 655 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 6983 1677 848 227 ITCDELTA - Earthlink, Inc., US 16509 1380 2530 454 AMAZON-02 - Amazon.com, Inc., US 7018 1370 20093 1008 ATT-INTERNET4 - AT&T Services, Inc., US 11492 1284 229 621 CABLEONE - CABLE ONE, INC., US 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 3329 169 15 ALJAWWALSTC-AS , SA 20940 2799 1071 1984 AKAMAI-ASN1 , US 34984 1975 327 356 TELLCOM-AS , TR 12479 1340 1018 46 UNI2-AS , ES 13188 1207 98 71 BANKINFORM-AS , UA 8551 1203 377 46 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 6849 1147 355 21 UKRTELNET , UA 8402 1051 544 15 CORBINA-AS Russia, RU 9198 916 352 25 KAZTELECOM-AS , KZ 12389 898 1087 407 ROSTELECOM-AS , RU 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 3476 540 171 Telmex Colombia S.A., CO 8151 2272 3385 555 Uninet S.A. de C.V., MX 7303 1542 953 243 Telecom Argentina S.A., AR 6503 1396 437 55 Axtel, S.A.B. de C.V., MX 11830 1327 367 57 Instituto Costarricense de Electricidad 6147 1081 377 27 Telefonica del Peru S.A.A., PE 7738 994 1882 40 Telemar Norte Leste S.A., BR 3816 961 463 210 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 907 125 76 Alestra, S. de R.L. de C.V., MX 28573 896 2176 161 CLARO S.A., BR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1182 402 49 LINKdotNET-AS, EG 36903 684 344 115 MT-MPLS, MA 37611 645 48 2 Afrihost, ZA 36992 552 1373 25 ETISALAT-MISR, EG 8452 527 1472 15 TE-AS TE-AS, EG 37492 384 250 69 ORANGE-TN, TN 24835 344 610 16 RAYA-AS, EG 29571 301 37 12 CITelecom-AS, CI 15399 295 35 6 WANANCHI-KE, KE 2018 265 327 74 TENET-1, ZA Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5541 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3524 382 250 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3508 2964 146 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3476 540 171 Telmex Colombia S.A., CO 39891 3329 169 15 ALJAWWALSTC-AS , SA 4766 3208 11146 1129 KIXS-AS-KR Korea Telecom, KR 17974 2943 904 78 TELKOMNET-AS2-AP PT Telekomunikasi Indo 20940 2799 1071 1984 AKAMAI-ASN1 , US 9829 2679 1494 527 BSNL-NIB National Internet Backbone, IN 8151 2272 3385 555 Uninet S.A. de C.V., MX 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 3508 3362 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 39891 3329 3314 ALJAWWALSTC-AS , SA 10620 3476 3305 Telmex Colombia S.A., CO 7545 3524 3274 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2943 2865 TELKOMNET-AS2-AP PT Telekomunikasi Indo 6389 2201 2160 BELLSOUTH-NET-BLK - BellSouth.net Inc., 9829 2679 2152 BSNL-NIB National Internet Backbone, IN 9808 2144 2102 CMNET-GD Guangdong Mobile Communication 18566 2195 2085 MEGAPATH5-US - MegaPath Corporation, US 4766 3208 2079 KIXS-AS-KR Korea Telecom, KR Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65001 PRIVATE 5.143.176.0/20 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.192.0/20 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.192.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.200.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.208.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.216.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65000 PRIVATE 31.219.177.0/25 8966 ETISALAT-AS P.O. Box 1150, Dub 65000 PRIVATE 31.219.177.128/25 8966 ETISALAT-AS P.O. Box 1150, Dub 65512 PRIVATE 45.252.244.0/24 45899 VNPT-AS-VN VNPT Corp, VN 65512 PRIVATE 45.252.245.0/24 45899 VNPT-AS-VN VNPT Corp, VN Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.249.144.0/20 40430 COLO4JAX-AS - colo4jax, LLC, US 27.100.7.0/24 56096 UNKNOWN 41.73.1.0/24 37004 -Reserved AS-, ZZ 41.73.2.0/24 37004 -Reserved AS-, ZZ 41.73.3.0/24 37004 -Reserved AS-, ZZ 41.73.4.0/24 37004 -Reserved AS-, ZZ 41.73.5.0/24 37004 -Reserved AS-, ZZ 41.73.6.0/24 37004 -Reserved AS-, ZZ 41.73.7.0/24 37004 -Reserved AS-, ZZ 41.73.8.0/24 37004 -Reserved AS-, ZZ Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:16 /9:13 /10:36 /11:101 /12:267 /13:516 /14:1052 /15:1768 /16:13136 /17:7811 /18:12992 /19:25305 /20:38539 /21:40208 /22:67597 /23:59424 /24:337949 /25:568 /26:574 /27:386 /28:53 /29:32 /30:14 /31:1 /32:34 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 39891 2896 3329 ALJAWWALSTC-AS , SA 22773 2735 3508 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2087 2195 MEGAPATH5-US - MegaPath Corporation, US 30036 1581 1767 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 6389 1424 2201 BELLSOUTH-NET-BLK - BellSouth.net Inc., 10620 1394 3476 Telmex Colombia S.A., CO 6983 1327 1677 ITCDELTA - Earthlink, Inc., US 34984 1258 1975 TELLCOM-AS , TR 11492 1186 1284 CABLEONE - CABLE ONE, INC., US 13188 993 1207 BANKINFORM-AS , UA Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1619 2:766 4:22 5:2165 6:31 8:983 12:1802 13:42 14:1753 15:45 16:2 17:94 18:126 20:50 22:1 23:1696 24:1793 27:2327 31:1781 32:85 33:4 35:5 36:309 37:2307 38:1251 39:36 40:95 41:2877 42:454 43:1835 44:46 45:2136 46:2570 47:88 49:1207 50:906 51:13 52:540 54:344 55:8 56:7 57:42 58:1641 59:1033 60:381 61:1821 62:1512 63:1909 64:4548 65:2192 66:4230 67:2230 68:1124 69:3258 70:1278 71:517 72:2043 74:2545 75:398 76:411 77:1373 78:1244 79:894 80:1315 81:1402 82:982 83:712 84:854 85:1580 86:485 87:1110 88:550 89:2070 90:215 91:6068 92:953 93:2364 94:2456 95:2478 96:529 97:338 98:944 99:90 100:77 101:1138 103:12145 104:2485 105:126 106:437 107:1342 108:660 109:2261 110:1276 111:1636 112:1049 113:1137 114:1054 115:1683 116:1642 117:1552 118:2043 119:1580 120:926 121:1118 122:2262 123:2016 124:1562 125:1842 128:651 129:455 130:412 131:1381 132:607 133:176 134:484 135:144 136:383 137:402 138:1863 139:419 140:576 141:461 142:662 143:961 144:739 145:163 146:938 147:655 148:1387 149:528 150:659 151:873 152:650 153:295 154:672 155:942 156:524 157:504 158:389 159:1204 160:506 161:732 162:2393 163:562 164:754 165:1101 166:323 167:1160 168:2092 169:664 170:1882 171:252 172:673 173:1697 174:754 175:664 176:1733 177:4027 178:2220 179:1151 180:2144 181:1834 182:2045 183:985 184:826 185:7279 186:3128 187:2115 188:2169 189:1760 190:7679 191:1262 192:9021 193:5713 194:4455 195:3854 196:1732 197:1141 198:5557 199:5752 200:7164 201:3655 202:10107 203:9841 204:4504 205:2737 206:2962 207:3104 208:4015 209:3869 210:3880 211:2051 212:2739 213:2333 214:853 215:71 216:5833 217:1977 218:797 219:613 220:1642 221:884 222:693 223:1286 End of report

1 0

Optical Wave Providers
by tim＠29lagrange.com 02 Sep '16

02 Sep '16

I have been looking at optical wave carriers for some long haul 1G/10G across the US. All to major cities and well known POP's. I am finding that there are not a lot of carriers who are offering wave services, usually just ethernet/MPLS. Particularly across the North west. Can someone shed some light on who some of the bigger carriers are and any challenges you have encountered with services like this? Who actually owns the fiber across the US? Thanks Tim

8 7

Software for tracking network related projects and activities
by Manuel Marín 02 Sep '16

02 Sep '16

Dear Nanog community We are currently using RT for tracking tasks related to network operations like BGP configuration change requests, circuit/ports activation, support tickets, etc, but when trying to track multiple activities that involve multiple departments, the RT (Request Tracker) system does not provide all the tools as a project/tasks management system. I was wondering if you can share what you use for tracking network related projects and activities. Thank you in advance Regards

3 2

Re: Don't press the big red buttom on the wall!
by Chris Dunn 01 Sep '16

01 Sep '16

On Mon, Aug 29, 2016 at 4:51 PM, Sean Donelan <sean(a)donelan.com> wrote: > > See that big red button on the wall under the sign "Do Not Push This > Button!".... > > > This is going to date me, well, because it happened in my high school years mid 1970's... but my best power off story was when in senior year we were working on the school Sperry/Univac Solid State Systems 90 mainframe. ( https://en.wikipedia.org/wiki/UNIVAC_Solid_State) Well this thing used a Mil-Spec 4K DRUM as its main memory. Now being mil-spec means the motor to spin the drum is 400 cycle AC. Where do you get 400 cycle AC in a 60 cycle world? Well you install a 60 cycle motor in the base of this monstrosity, and connect it via a fan belt to a 400 cycle AC generator that feeds the drum. We came in to class one day to warm the Univac up (it took about 30 minutes to fully power up) and noticed the machine being very quiet when we applied power. We eventually tracked it down to no power to the drum and it not spinning. And the reason the drum was not spinning? The fan belt had broken on the motor/generator set. :) Lucky, this was a Technical/Vocational high school, and we ran down to the auto repair class and bummed a new belt off them. :) ---- Then there was the time an engineer I worked with pressed the lamp test button on the huge engineering console display for a Burroughs B6700 room sized mainframe (like 3 foot by 3 foot bank of incandescent register and status displays) and the inrush caused the entire machine shut down.... but that's another story. ;) Chris Dunn Data Center Operations ServerCentral

1 0

Arbor Reports 540Gbps "Sustained" Attack
by Dennis B 01 Sep '16

01 Sep '16

https://www.arbornetworks.com/blog/asert/rio-olympics-take-gold-540gbsec-su… I've used SP Peakflow before and I have my opinions. With all the intelligence out there about DDoS attacks, DDoS attackers, DDoS tools and techniques this article leaves me with ton's of questions. IE: What industry was the attack target? Was it a single customer or multiple customers at the same time? What was the attack vector? Was it multi-vector? What was the duration of the 540Gbps attack? Did you actually block the attack or did you just report on it from your cloud signaling alliance aka cloud offering? Could you help explain if the peak of the attack lasted X minutes, Y hours, Z days? What was the attack targeted protocol? Was it TCP against TCP or UDP against UDP or UDP against TCP? I have to be honest, IDK if Arbor is attempting to claim the largest recorded DDoS attack in the world cup of DDoS attacks but the fact that your a local appliance shop. Selling to the global 100 and T1-3 ISPs - I'd hope for more than a marketing ploy to take the top attack vector. Thought I'd ask Nanog if they heard any whispers about this "white buffalo", which ISPs were Transiting the event, what course of actions were taken. Thanks!

2 1

Don't press the big red buttom on the wall!
by Sean Donelan 01 Sep '16

01 Sep '16

See that big red button on the wall under the sign "Do Not Push This Button!".... DC 911 outage caused by contractor error http://wtop.com/dc/2016/08/dc-911-outage-caused-by-contractor-who-pulled-wr… WASHINGTON — D.C. is now operating two separate 911 centers after a power outage caused by human error left the nation’s capital without any emergency phone service for almost an hour on a busy weekend night. A contractor working Saturday night inadvertently pulled an emergency power shut off switch that cut electricity to the 911 phone system and a call routing system at the District’s Unified Communications Center, said the center’s Director Karima Holmes. “Unfortunately because it was human error we weren’t prepared for it,” Holmes said. [...]

11 16