- NANOG - lists.nanog.org

[NANOG-announce] Mailman Maintenance
by Valerie Wittkop 18 Jun '17

18 Jun '17

Hello NANOGers, The mailman servers will be undergoing maintenance tonight between 8:00 and 8:30pm Eastern. Mail sent to lists hosted on the NANOG mailman servers will be held during the maintenance window. Regular operations will resume once the maintenance is complete. Sincerely, NANOG Staff _______________________________________________ NANOG-announce mailing list NANOG-announce(a)mailman.nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-announce

1 0

Internet connectivity in Nigeria
by Sina Owolabi 18 Jun '17

18 Jun '17

Hi All Currently having a terrible situation in Nigeria where the GLO1 and MainOne cables appear to be both down. Can anyone suggest a good Nigerian ISP with redundancies enough to overcome at least two of the following dying out? SAT-3 WACS GLO1 ACE MainOne Please dont say MTN or any of the Nigerian telcos, except there are no other options, customer service will leave you trying to commit bodily harm.

3 4

Net neutrality filing
by Stephen Satchell 18 Jun '17

18 Jun '17

> https://ecfsapi.fcc.gov/file/10616167661646/satchell.answers2questions.NPRM… Warning: this is 63 pages long, and dull as dishwater. It does have a few color pictures, though. And one comic strip. Summary: fix the statutes (thank you Sen. Stevens, for the junk!) and apply Title II only to monopoly Internet access service providers. I had sent this notice to a listserve (of which I'm a subscriber) of telecomm policy people, and I'm getting a whole lot of pushback. So I thought, why should NANOG lose out on the fun? So, instead of you hearing about this in the sweet bye and bye, I'll get the firestorm over with now, rather than stretching this out for three months. (I'm on this listserve, too.) And if you think my ideas are bad, perhaps you will propose a better suggestion to the FCC about the subject.

2 2

Incapsula AS19551
by Vireak Ouk 17 Jun '17

17 Jun '17

Hello all If anyone from Incapsula can contact me off-list, I would highly appreciate. We are not able to access several sites hosted in Incapsula from source AS59318 and from our downstream. The issues only happened from yesterday. Many thanks vireak

1 0

Re: Vendors spamming NANOG attendees
by Alexander Maassen 16 Jun '17

16 Jun '17

the discussion about the external spam kinda exceeds the volume of the spam itself. just my 2 cents. just block, delete, continue life Kind regards, Alexander Maassen - Technical Maintenance Engineer Parkstad Support BV- Maintainer DroneBL- Peplink Certified Engineer -------- Oorspronkelijk bericht --------Van: bzs(a)theworld.com Datum: 15-06-17 20:09 (GMT+01:00) Aan: Dan Hollis <goemon(a)sasami.anime.net> Cc: Niels Bakker <niels=nanog(a)bakker.net>, nanog(a)nanog.org, bzs(a)theworld.com Onderwerp: Re: Vendors spamming NANOG attendees On June 14, 2017 at 14:22 goemon(a)sasami.anime.net (Dan Hollis) wrote: > On Wed, 14 Jun 2017, bzs(a)theworld.com wrote: > > Merely deciding not to patronize them may not be sufficient and that's > > why we make that sort of thing just outright illegal rather than hope > > market forces will suffice. > > Most spam is sent from compromised machines anyway, so there are already > criminal violations involved in sending spam. FWIW I believe the context was a vendor spamming NANOG attendees (see the Subject:) so not likely being done from compromised machines. That said, yes, a lot of spam is sent from compromised machines as you say. But criminal violations can be additive, even rising to things like RICO charges (a pattern of organized criminal behavior etc.) which can be both criminal and civil and added onto charges like the criminality of specific mechanisms (compromised systems etc.) It really depends on how interested one can get the legal machinery in the problem. Thus far that's hit or miss. I can't find any instance where RICO charges were used against a spam gang tho, at least on a quick search. -- -Barry Shein Software Tool & Die | bzs(a)TheWorld.com | http://www.TheWorld.com Purveyors to the Trade | Voice: +1 617-STD-WRLD | 800-THE-WRLD The World: Since 1989 | A Public Information Utility | *oo*

2 1

Weekly Routing Table Report
by cscora＠apnic.net 16 Jun '17

16 Jun '17

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, MENOG, 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 17 Jun, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 651216 Prefixes after maximum aggregation (per Origin AS): 253596 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 313678 Total ASes present in the Internet Routing Table: 57522 Prefixes per ASN: 11.32 Origin-only ASes present in the Internet Routing Table: 49794 Origin ASes announcing only one prefix: 21982 Transit ASes present in the Internet Routing Table: 7728 Transit-only ASes present in the Internet Routing Table: 221 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 42 Max AS path prepend of ASN ( 55644) 36 Prefixes from unregistered ASNs in the Routing Table: 50 Numnber of instances of unregistered ASNs: 54 Number of 32-bit ASNs allocated by the RIRs: 19084 Number of 32-bit ASNs visible in the Routing Table: 14816 Prefixes from 32-bit ASNs in the Routing Table: 60261 Number of bogon 32-bit ASNs visible in the Routing Table: 65 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 395 Number of addresses announced to Internet: 2848765156 Equivalent to 169 /8s, 204 /16s and 180 /24s Percentage of available address space announced: 76.9 Percentage of allocated address space announced: 76.9 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.6 Total number of prefixes smaller than registry allocations: 216985 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 178613 Total APNIC prefixes after maximum aggregation: 51337 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 177820 Unique aggregates announced from the APNIC address blocks: 73451 APNIC Region origin ASes present in the Internet Routing Table: 8177 APNIC Prefixes per ASN: 21.75 APNIC Region origin ASes announcing only one prefix: 2284 APNIC Region transit ASes present in the Internet Routing Table: 1158 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 42 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3010 Number of APNIC addresses announced to Internet: 763804388 Equivalent to 45 /8s, 134 /16s and 186 /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: 198323 Total ARIN prefixes after maximum aggregation: 94647 ARIN Deaggregation factor: 2.10 Prefixes being announced from the ARIN address blocks: 200232 Unique aggregates announced from the ARIN address blocks: 92051 ARIN Region origin ASes present in the Internet Routing Table: 17902 ARIN Prefixes per ASN: 11.18 ARIN Region origin ASes announcing only one prefix: 6620 ARIN Region transit ASes present in the Internet Routing Table: 1776 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: 2033 Number of ARIN addresses announced to Internet: 1110205088 Equivalent to 66 /8s, 44 /16s and 98 /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: 175032 Total RIPE prefixes after maximum aggregation: 85556 RIPE Deaggregation factor: 2.05 Prefixes being announced from the RIPE address blocks: 170672 Unique aggregates announced from the RIPE address blocks: 102495 RIPE Region origin ASes present in the Internet Routing Table: 24125 RIPE Prefixes per ASN: 7.07 RIPE Region origin ASes announcing only one prefix: 11106 RIPE Region transit ASes present in the Internet Routing Table: 3388 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 33 Number of RIPE region 32-bit ASNs visible in the Routing Table: 5917 Number of RIPE addresses announced to Internet: 711738752 Equivalent to 42 /8s, 108 /16s and 69 /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: 82046 Total LACNIC prefixes after maximum aggregation: 18272 LACNIC Deaggregation factor: 4.49 Prefixes being announced from the LACNIC address blocks: 83317 Unique aggregates announced from the LACNIC address blocks: 38421 LACNIC Region origin ASes present in the Internet Routing Table: 6022 LACNIC Prefixes per ASN: 13.84 LACNIC Region origin ASes announcing only one prefix: 1645 LACNIC Region transit ASes present in the Internet Routing Table: 1113 Average LACNIC Region AS path length visible: 5.4 Max LACNIC Region AS path length visible: 32 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 3537 Number of LACNIC addresses announced to Internet: 170651872 Equivalent to 10 /8s, 43 /16s and 240 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-266652 + 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: 17102 Total AfriNIC prefixes after maximum aggregation: 3739 AfriNIC Deaggregation factor: 4.57 Prefixes being announced from the AfriNIC address blocks: 18780 Unique aggregates announced from the AfriNIC address blocks: 6926 AfriNIC Region origin ASes present in the Internet Routing Table: 1047 AfriNIC Prefixes per ASN: 17.94 AfriNIC Region origin ASes announcing only one prefix: 326 AfriNIC Region transit ASes present in the Internet Routing Table: 204 Average AfriNIC Region AS path length visible: 4.8 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 319 Number of AfriNIC addresses announced to Internet: 91917056 Equivalent to 5 /8s, 122 /16s and 139 /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 5543 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3929 403 356 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2977 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4766 2787 11137 759 KIXS-AS-KR Korea Telecom, KR 9829 2752 1499 540 BSNL-NIB National Internet Backbone, IN 9808 2205 8699 34 CMNET-GD Guangdong Mobile Communication 4755 2086 422 221 TATACOMM-AS TATA Communications formerl 45899 1989 1396 108 VNPT-AS-VN VNPT Corp, VN 7552 1630 1105 70 VIETEL-AS-AP Viettel Corporation, VN 9498 1591 361 139 BBIL-AP BHARTI Airtel Ltd., IN 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 3809 2969 154 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 6327 3419 1333 82 SHAW - Shaw Communications Inc., CA 18566 2127 405 109 MEGAPATH5-US - MegaPath Corporation, US 6389 2066 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 20115 2009 2171 419 CHARTER-NET-HKY-NC - Charter Communicat 209 1816 5068 639 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 16509 1814 3441 585 AMAZON-02 - Amazon.com, Inc., US 30036 1786 325 307 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 6983 1696 854 232 ITCDELTA - Earthlink, Inc., US 701 1561 10578 635 UUNET - MCI Communications Services, In 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 3338 187 22 ALJAWWALSTC-AS, SA 8551 3184 377 40 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2893 969 2083 AKAMAI-ASN1, US 34984 2023 329 391 TELLCOM-AS, TR 9121 1971 1691 17 TTNET, TR 13188 1614 100 55 TRIOLAN, UA 12479 1603 1044 53 UNI2-AS, ES 12389 1525 1408 627 ROSTELECOM-AS, RU 6849 1226 355 21 UKRTELNET, UA 8402 1125 544 15 CORBINA-AS OJSC "Vimpelcom", 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 3549 546 148 Telmex Colombia S.A., CO 8151 2542 3404 574 Uninet S.A. de C.V., MX 11830 2085 369 57 Instituto Costarricense de Electricidad 7303 1547 989 275 Telecom Argentina S.A., AR 6503 1540 437 53 Axtel, S.A.B. de C.V., MX 6147 1298 377 27 Telefonica del Peru S.A.A., PE 3816 1026 501 94 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 28573 979 2299 177 CLARO S.A., BR 11172 910 126 82 Alestra, S. de R.L. de C.V., MX 18881 896 1052 23 TELEFÔNICA BRASIL 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 1261 398 48 LINKdotNET-AS, EG 37611 720 83 7 Afrihost, ZA 36903 713 358 123 MT-MPLS, MA 36992 638 1375 26 ETISALAT-MISR, EG 24835 495 850 15 RAYA-AS, EG 29571 421 36 10 CITelecom-AS, CI 37492 407 320 75 ORANGE-, TN 8452 361 1730 17 TE-AS TE-AS, EG 15399 353 35 7 WANANCHI-, KE 2018 300 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 5543 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3929 403 356 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3809 2969 154 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3549 546 148 Telmex Colombia S.A., CO 6327 3419 1333 82 SHAW - Shaw Communications Inc., CA 39891 3338 187 22 ALJAWWALSTC-AS, SA 8551 3184 377 40 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 17974 2977 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 20940 2893 969 2083 AKAMAI-ASN1, US 4766 2787 11137 759 KIXS-AS-KR Korea Telecom, KR 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 3809 3655 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7545 3929 3573 TPG-INTERNET-AP TPG Telecom Limited, AU 10620 3549 3401 Telmex Colombia S.A., CO 6327 3419 3337 SHAW - Shaw Communications Inc., CA 39891 3338 3316 ALJAWWALSTC-AS, SA 8551 3184 3144 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 17974 2977 2904 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 9829 2752 2212 BSNL-NIB National Internet Backbone, IN 9808 2205 2171 CMNET-GD Guangdong Mobile Communication Co.Ltd. 4766 2787 2028 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 65602 UNALLOCATED 8.225.192.0/24 30372 SUNESYS2 - Sunesys, LLC, US 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 65010 PRIVATE 46.56.192.0/21 42772 VELCOM-AS, BY 65010 PRIVATE 46.56.224.0/21 42772 VELCOM-AS, BY 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 65538 DOCUMENT 64.27.253.0/24 1273 CW Vodafone Group PLC, GB 65346 PRIVATE 94.50.36.0/22 31094 TTKNET Tyumen, Russia, RU 64111 UNALLOCATED 98.159.5.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64111 UNALLOCATED 98.159.7.0/24 19555 KMI-NETWORK - Kinder Morgan, I Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 14.192.48.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.49.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.50.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 14.192.51.0/24 134833 LIHGL-HK LANLIAN INTERNATIONAL HOLDING GROUP LIMITE 27.100.7.0/24 56096 UNKNOWN 36.255.250.0/24 64091 UNKNOWN 41.76.232.0/21 62878 XLITT - Xlitt, US 41.77.248.0/21 62878 XLITT - Xlitt, US 41.78.12.0/23 62878 XLITT - Xlitt, US 41.78.180.0/23 37265 -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:15 /9:13 /10:36 /11:104 /12:280 /13:546 /14:1046 /15:1847 /16:13485 /17:7630 /18:13432 /19:24628 /20:38586 /21:41176 /22:77437 /23:64125 /24:364605 /25:841 /26:608 /27:644 /28:43 /29:32 /30:25 /31:3 /32:29 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3210 3419 SHAW - Shaw Communications Inc., CA 22773 2972 3809 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 39891 2898 3338 ALJAWWALSTC-AS, SA 8551 2649 3184 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 18566 2020 2127 MEGAPATH5-US - MegaPath Corporation, US 30036 1579 1786 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 11830 1475 2085 Instituto Costarricense de Electricidad y Telec 10620 1474 3549 Telmex Colombia S.A., CO 6389 1373 2066 BELLSOUTH-NET-BLK - BellSouth.net Inc., US 9121 1363 1971 TTNET, TR Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1605 2:824 4:18 5:2431 6:34 8:1031 12:1830 13:122 14:1762 15:26 16:2 17:124 18:91 20:57 23:2366 24:1838 25:2 27:2434 31:1910 32:86 33:9 35:20 36:411 37:2329 38:1320 39:45 40:97 41:3019 42:463 43:1940 44:72 45:2777 46:2790 47:140 49:1225 50:984 51:18 52:825 54:363 55:6 56:4 57:42 58:1591 59:1048 60:391 61:1954 62:1602 63:1915 64:4558 65:2219 66:4519 67:2253 68:1241 69:3385 70:1147 71:585 72:2180 74:2691 75:386 76:431 77:1487 78:1450 79:2439 80:1399 81:1398 82:996 83:709 84:898 85:1747 86:481 87:1146 88:766 89:2071 90:176 91:6166 92:975 93:2379 94:2377 95:2681 96:624 97:353 98:1052 99:86 100:154 101:1272 103:15041 104:2923 105:194 106:489 107:1662 108:819 109:3013 110:1432 111:1724 112:1194 113:1233 114:1029 115:1716 116:1799 117:1719 118:2145 119:1592 120:1037 121:1111 122:2255 123:1819 124:1503 125:1897 128:776 129:646 130:431 131:1401 132:531 133:199 134:653 135:225 136:455 137:436 138:1930 139:489 140:395 141:571 142:760 143:928 144:793 145:181 146:1018 147:690 148:1432 149:581 150:706 151:974 152:707 153:302 154:816 155:750 156:600 157:647 158:449 159:1478 160:678 161:744 162:2525 163:533 164:794 165:1221 166:386 167:1252 168:2684 169:785 170:3383 171:319 172:1016 173:1913 174:811 175:748 176:1880 177:4079 178:2477 179:1176 180:2215 181:1897 182:2366 183:998 184:859 185:9851 186:3134 187:2223 188:2688 189:1814 190:8203 191:1353 192:9441 193:5787 194:4652 195:3909 196:2114 197:1313 198:5501 199:5894 200:7439 201:4334 202:10349 203:9956 204:4489 205:2816 206:3036 207:3167 208:3990 209:4025 210:3970 211:2148 212:2857 213:2491 214:889 215:66 216:5735 217:2102 218:855 219:600 220:1658 221:913 222:762 223:1176 End of report

1 0

IPv6 operations discussions
by Lee Howard 16 Jun '17

16 Jun '17

The IETF v6ops working group is chartered to improve the operation of IPv6. We have several active documents right now that would benefit from broader operator feedback. For instance, there is current active discussion on: Requirements for IPv6 Routers <https://tools.ietf.org/html/draft-ietf-v6ops-ipv6rtr-reqs> This document provides a list of requirements for operators’ routers. Is it clear and exhaustive? Basic Requirements for IPv6 Customer Edge Routers <https://tools.ietf.org/html/draft-ietf-v6ops-rfc7084-bis> What transition technologies should all CPE vendors put in their devices? The current version proposes all of: 464xlat, DS-Lite, lw4o6, MAP-E, MAP-T, 6in4, and 6rd, as well as IPv4 multicast over IPv6. There are related documents that split out some requirements for further discussion. Happy Eyeballs Version 2: Better Connectivity Using Concurrency <https://tools.ietf.org/html/draft-ietf-v6ops-rfc6555bis> Is this a useful update to the existing Happy Eyeballs specification (rfc6555)? Should we update Happy Eyeballs? Considerations For Using Unique Local Addresses <https://tools.ietf.org/html/draft-ietf-v6ops-ula-usage-considerations> Are ULAs useful, or are they a natural and risky predecessor to IPv6 NAT? It would help future IPv6 operations if current operators would read these documents and comment on them on the mailing list: https://www.ietf.org/mailman/listinfo/v6ops Note Well that comments become part of the IETF record, and thank you for them. Lee v6ops co-chair

1 0

Fwd: [lacnog] Call for Presentations – LACNOG 2017
by Carlos M. Martinez 15 Jun '17

15 Jun '17

FYI, apologies for duplicates. Forwarded message: > From: Tomas Lynch <tomas.lynch(a)gmail.com> > To: lacnog(a)lacnog.org <lacnog(a)lacnog.org> > Subject: [lacnog] Call for Presentations – LACNOG 2017 > Date: Thu, 15 Jun 2017 08:55:17 -0400 > > LACNOG, the Latin American and Caribbean Network Operators Group, will > be > holding its annual conference – LACNOG 2017 – in the city of > Montevideo, > Uruguay, on 18-22 September 2017. This event will be co-located with > the > LACNIC 28 meeting. > > The 2017 LACNOG Program Committee invites the Internet community to > submit > their presentations for the event. > > > > Possible formats are as follows: > > - > > Lightning talk: short, 10-minute presentation with an additional 5 > minutes for questions. > - > > Presentation: 20-minute presentation with an additional 10 minutes > for > questions. > - > > Tutorial: 45-minute presentation with an additional 15 minutes for > questions. > > In the spirit of LACNOG, the topics to be covered by the presentations > should be geared towards regional Internet development. The topics of > interest to LACNOG 2017 include, but are not limited to: > > - > > Network operation and professional experiences, success stories > - > > IP network architecture, sizing, configuration and administration > - > > Routing and switching protocols, including unicast, multicast, > anycast, > and others > - > > End-user applications (e.g. E-mail, HTTP, DNS, etc.) > - > > Value-added services such as VPNs, distributed systems, cloud > computing, > etc. > - > > Peering, regional traffic exchange, IXPs > - > > Transition to IPv6 and IPv6 Deployment > - > > Network security and data management, attack mitigation > - > > Network monitoring, performance, measurements and telemetry > - > > Network automation, evolution and convergence > - > > Infrastructure and physical transport including optical and > wireless > networks > - > > Internet governance issues, legislation and regulations > - > > Research and education > > > > All submissions must meet the following requirements: > > - > > Proposals must be submitted in English, Portuguese or Spanish. > - > > Accepted formats: Microsoft Powerpoint (PPT, PPTX), Apache > OpenOffice > Presentation (ODP), LibreOffice Impress (ODP), or Portable Document > Format > (PDF). > - > > The number of slides must be appropriate for the time assigned for > the > presentation. As a rule of thumb, estimate 1-2 minutes per slide. > - > > We recommend following the Guidelines for Submitting a Presentation > <http://www.lacnog.org/guiapresentaciones/>. > > > > Presentations must be submitted according to the following schedule: > > - > > Reception of drafts and abstracts: 12 June to 17 July > - > > Evaluation by the Program Committee: 17 to 31 July > - > > Submission of the final presentation: 31 July to 28 August > - > > Event date: 18-22 September > > > > Anyone wishing to participate must submit a short biography, picture > and > abstract to > http://www.lacnog.org/en/call-for-presentations-lacnog-2017/ > > > > Presenters at the LACNOG 2017 conference will receive a certificate > attesting their participation. > > > > Program Committee > _______________________________________________ > LACNOG mailing list > LACNOG(a)lacnic.net > https://mail.lacnic.net/mailman/listinfo/lacnog > Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog

1 0

Re: Vendors spamming NANOG attendees
by Anne P. Mitchell Esq. 15 Jun '17

15 Jun '17

> You make a good point. But I wonder how often spammers are so obvious, and I wonder if his "leveraging" falls amiss of CAN-SPAM's specific prohibition: > > > (I) harvesting electronic mail addresses of the users of a website, proprietary service, or other online public forum operated by another person, without the authorization of such person; and > Unfortunately, the actual language of that provision requires that the website from which it was scraped must also include a notice stating that the website will not "give, sell, or otherwise transfer addresses maintained by such website". Here is the actual language: "(i) the electronic mail address of the recipient was obtained using an automated means from an Internet website or proprietary online service operated by another person, and such website or online service included, at the time the address was obtained, a notice stating that the operator of such website or online service will not give, sell, or otherwise transfer addresses maintained by such website or online service to any other party for the purposes of initiating, or enabling others to initiate, electronic mail messages;" It would be interesting* if people had language printed right on their business cards along the lines of: "The presence of my email address on this card does not constitute permission for you to email me absent a prior agreement, or to put my email address on a mailing list." *And by interesting, I mean legally interesting. ;-) Anne* *Dictated due to broken wrist, please forgive top-posting and any weird grammar or typos Anne P. Mitchell, Attorney at Law Legislative Consultant CEO/President, Institute for Social Internet Public Policy Member, Cal. Bar Cyberspace Law Committee Member, Colorado Cyber Committee Member, Elevations Credit Union Member Council Member, Board of Directors, Asilomar Microcomputer Workshop Member, Board of Directors, Greenwood Wildlife Rehabilitation Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal anti-spam law) Ret. Professor of Law, Lincoln Law School of San Jose Ret. Chair, Asilomar Microcomputer Workshop

1 0

Re: Templating/automating configuration
by Brian Knight 15 Jun '17

15 Jun '17

Because we had different sources of truth which were written in-house, we wound up rolling our own template engine in Python. It took about 3 weeks to write the engine and adapt existing templates. Given a circuit ID, it generates the full config for copy and paste into a terminal session. It also hooks into a configuration parser tool, written in-house, that tracks configured interfaces, so it is easy to see whether the template would overwrite an existing interface. I used the Jinja2 template engine, along with pyodbc/unixODBC/FreeTDS for access to a Microsoft SQL backend. The keys for us are: * extracting information from a source of truth * validating the information for correctness * making sure you don't overwrite existing config * outputting the right templates for the circuit features It made more sense to write a tool than it did to try to adapt something for our environment. If I had a free hand and unlimited budget, I would find a single app that functions as a source of truth for all circuits and products, which includes a templating engine that hooks in easily. -Brian ---- On Tue, 06 Jun 2017 08:22:59 -0500 Graham Johnston <johnstong(a)westmancom.com> wrote ---- Short of complete SDN, for those of you that have some degree of configuration templating and/or automation tools what is it that you run? I'm envisioning some sort of tool that let's me define template snippets of configuration and aids in their deployment to devices. I'm okay doing the heaving lifting in defining everything, I'm just looking for the tool that stitches it together and hopefully makes things a little less error prone for those who aren't as adept. Graham Johnston Network Planner Westman Communications Group 204.717.2829 johnstong@westmancom.com<mailto:johnstong@westmancom.com>

9 10