- NANOG - lists.nanog.org

Re: USA local SIM card
by DIUA Support 18 Sep '17

18 Sep '17

Sounds like you should go the mvno or twilio route. Twilio is beta testing cloud based since assignments that tie into their data and SIP services. If you go the direct carrier route try mvno. On Sep 17, 2017 2:34 PM, Jean-Francois Mezei <jfmezei_nanog(a)vaxination.ca> wrote: On 2017-09-17 16:40, Max Tulyev wrote: > 1. My phone is not LTE but 3G GSM/UMTS capable (all bands, > 850/900/1700/1900/2100). Will it work? Is 3G coverage good enough in New > York and Orlando for VoIP calls (SIP, Viber, Skype)? 3G coverage is a superset of LTE coverage. (aka: carriers still have some areas that have 3G but not LTE). AT&T has 850 and 1900 in 3G. the AWS (1700/2100) is for LTE only. AT&T has shutdown 2G, but T-Mobile still has it. In Canada, Rogers still has 2G, but Bell/Telus never had 2G. (they went from CDMA to 3G circa 2010). T-Mobile does not have 850. It has AWS (1700/2100) and 1900 in the above list. Originally, it had 1900 only (2G). When it acquired 1700, it deployed 3G on it. But because the big US carriers deemed 1700 to be for LTE once it arrived, very few handset manufacturers provided support for 3G on 1700, especially during the days when handsets coudl only support 3 or 4 frequencies. Many of the hansets custom ordered by T-Mobile and the 3 small new Canadian carriers replaced 1900 support in 3G with 1700 support. (so when Rogers got the Mobilicity customers, many of them had handsets that could not support 3G services in 1900 so Rogers had to get a package to upgrade those customers). T-Mobile has subsequently refarmed 1700 to support LTE, and split its 1900 to support 2G and 3G. It has since acquired some 700 for LTE service, but this is no help to you. However, as a 3G-only user on t-mobile, you are limited to 1900 which has shorter propagation from antennas. So consider that the T-Mobile coverage maps may be built with 700mhz propagation in mind, so you would not get as much coverage on a 1900 only sertvice. There may still be areas where 3G is on 1700, but propagation is similar to 1900. (assuming your handset can support 3G on AWS (1700/2100). Note that AWS (1700/2100) is not used outside North America, even if frequemncies such as 2100 are. Carefully check your handset's specs. > 2. Is there public or private IP address? IPv6? I can't answer this. During my bike trip, I choose AT&T because it is the service which cuases me the least amount of waiting to post a tweet or check emails. Getting the IP address on an iPhone isn't easy so I didn't waste any time doing this.

1 0

Management softwares
by K MEKKAOUI 18 Sep '17

18 Sep '17

Hi We are a medium ISP. We are looking for Management software solutions. We are interested in finding a solution for billing, invoicing, scheduling, ticketing, provisioning and monitoring, Any suggestions or recommendations will be appreciated? We have been using multiple systems which do not communicate. Our objective is to use a single system or at least reduce the number of systems. Thank you KARIM M.

6 5

Re: IOS new versions and network load
by Jean-Francois Mezei 17 Sep '17

17 Sep '17

On 2017-09-17 18:41, Eduardo Schoedler wrote: > https://www.peeringdb.com/net/3554 Peering would reduce an ISP's reliance on transit provider (and thus load on transit providers) hut still present same problem on the ISP's internal network. Also, doesn't Apple use a CDN such as Akamai or L3 to deliver content like that? > "We do have another option to consider - > http://www.apple.com/osx/server/features/#caching-server" Considering Apple has been out of the server business since 2010, Would ISPs really bother installing/configuring (and finding a spot on a rack shelf ) for a Mac Mini only to reduce load once a year ?

2 1

USA local SIM card
by Max Tulyev 17 Sep '17

17 Sep '17

Hi All, sorry for possible off-topic, I really did not know where to ask this. I'm going to visit USA for two weeks. I want to buy a local prepaid SIM card mostly for IP access. Is it possible in USA to buy a prepaid SIM as a visitor, without long term contract? I need a public (can be dynamic) IP address, NOT over NAT, and (or) IPv6, if possible. My phone is GSM UMTS 3G. Expected traffic volume is about 10G. Will use it in New York City and Orlando City, not in rural areas. Good data roaming tariff in Cannada will be a big advantage. What can you advice? Thank you!

14 19

Reliability of looking glass sites / rviews
by Matthew Huff 17 Sep '17

17 Sep '17

This weekend our uninterruptible power supply became interruptible and we lost all circuits. While I was doing initial debugging of the problem while I waited on site power verification, I noticed that there was still paths being shown in rviews for the circuit that were down. This was over an hour after we went hard down and it took hours before we were back up. I worked with our providers last night to verify there weren't any hanging static routes, etc... We shut the upstream circuit down and watched the convergence and saw that eventually all the paths disappeared. Given what we saw on Saturday, what would cause route-views to cache the paths that long? Some looking glass sites only show what they are peered with or at most what their peers are peered with, that's why I've always used route-views. What looking glass sites other than route-views would people recommend?

3 4

Re: FW: Reliability of looking glass sites / rviews
by Tim Evens 16 Sep '17

16 Sep '17

You didn't mention details about which ASN or prefixes you were checking. Are you referring to ASN 14607 that only advertises two prefixes 129.77.0.0/16 and 2620:0:2810::/48? Based what we see over the weekend (using routeviews data), we see: Event Start Time: 2017-09-09 11:29:23 UTC (2017-09-09 07:29:23 EDT) Event End Time: 2017-09-09 13:31:30 UTC (2017-09-09 09:31:30 EDT) Are the above times correct? We see the routes withdraw and then come back. For example: http://demo-rv.snas.io:3000/dashboard/db/prefix-history?orgId=2&var-prefix=… When you checked routeviews, which router and peer were you looking at? When you did a "show ip bgp ..." did you include the prefix length? If not, it would have then shown you 0/0 or 128/5, depending on which router you were on. --Tim On 9/13/17, 8:43 AM, "NANOG on behalf of Matthew Huff" <nanog-bounces(a)nanog.org on behalf of mhuff(a)ox.com> wrote: Both should have been similar. In the first case we lost power to all of our BGP border routers that are peered with the upstream providers In the second case, I did an explicit "shut" on the interface connected to the upstream provider that appeared "stuck" after an hour after the outage. From: <christopher.morrow(a)gmail.com> on behalf of Christopher Morrow <morrowc.lists(a)gmail.com> Date: Wednesday, September 13, 2017 at 10:58 AM To: Matthew Huff <mhuff(a)ox.com> Cc: nanog2 <nanog(a)nanog.org> Subject: Re: Reliability of looking glass sites / rviews On Wed, Sep 13, 2017 at 5:30 AM, Matthew Huff <mhuff(a)ox.com<mailto:mhuff@ox.com>> wrote: This weekend our uninterruptible power supply became interruptible and we lost all circuits. While I was doing initial debugging of the problem while I waited on site power verification, I noticed that there was still paths being shown in rviews for the circuit that were down. This was over an hour after we went hard down and it took hours before we were back up. explicit vs implicit withdrawals causing different handling of the problem routes? I worked with our providers last night to verify there weren't any hanging static routes, etc... We shut the upstream circuit down and watched the convergence and saw that eventually all the paths disappeared. Given what we saw on Saturday, what would cause route-views to cache the paths that long? Some looking glass sites only show what they are peered with or at most what their peers are peered with, that's why I've always used route-views. What looking glass sites other than route-views would people recommend? ripe ris.

2 1

Hurricane Irma: U.S. Virgin Islands and Puerto Rico
by Sean Donelan 15 Sep '17

15 Sep '17

5 fatalities in U.S. Virgin Islands and Puerto Rico FCC doesn't have reliable reporting on Wireline and Cable service providers in either USVI or Puerto Rico. The assumption is large numbers of customers are without cable or wireline service. 870,000 customers (55% of the island) without power in Puerto Rico 22,900 customers without power U.S. Vigin Islands 1 hospital closed, 25 hospitals on backup generators 29.3% of cell sites in Puerto Rico and 60.7% of cell sites in the U.S. Virgin Islands are out of service. 1 radio station and 2 TV stations in USVI are out of service 4 radio stations in Puerto Rico are out of service

5 13

Weekly Routing Table Report
by cscora＠apnic.net 15 Sep '17

15 Sep '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, SANOG, PacNOG, SAFNOG MENOG, BJNOG, SDNOG, CMNOG, LACNOG, IRNOG 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 16 Sep, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 663581 Prefixes after maximum aggregation (per Origin AS): 258067 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 320181 Total ASes present in the Internet Routing Table: 58405 Prefixes per ASN: 11.36 Origin-only ASes present in the Internet Routing Table: 50494 Origin ASes announcing only one prefix: 22241 Transit ASes present in the Internet Routing Table: 7911 Transit-only ASes present in the Internet Routing Table: 231 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 34 Max AS path prepend of ASN ( 55644) 31 Prefixes from unregistered ASNs in the Routing Table: 89 Number of instances of unregistered ASNs: 90 Number of 32-bit ASNs allocated by the RIRs: 19985 Number of 32-bit ASNs visible in the Routing Table: 15788 Prefixes from 32-bit ASNs in the Routing Table: 64697 Number of bogon 32-bit ASNs visible in the Routing Table: 23 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 354 Number of addresses announced to Internet: 2854147424 Equivalent to 170 /8s, 30 /16s and 213 /24s Percentage of available address space announced: 77.1 Percentage of allocated address space announced: 77.1 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.7 Total number of prefixes smaller than registry allocations: 220221 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 182086 Total APNIC prefixes after maximum aggregation: 52304 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 181101 Unique aggregates announced from the APNIC address blocks: 74710 APNIC Region origin ASes present in the Internet Routing Table: 8326 APNIC Prefixes per ASN: 21.75 APNIC Region origin ASes announcing only one prefix: 2305 APNIC Region transit ASes present in the Internet Routing Table: 1192 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 34 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3184 Number of APNIC addresses announced to Internet: 765617376 Equivalent to 45 /8s, 162 /16s and 100 /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: 201350 Total ARIN prefixes after maximum aggregation: 96036 ARIN Deaggregation factor: 2.10 Prefixes being announced from the ARIN address blocks: 203033 Unique aggregates announced from the ARIN address blocks: 93861 ARIN Region origin ASes present in the Internet Routing Table: 17982 ARIN Prefixes per ASN: 11.29 ARIN Region origin ASes announcing only one prefix: 6632 ARIN Region transit ASes present in the Internet Routing Table: 1765 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: 2189 Number of ARIN addresses announced to Internet: 1110326048 Equivalent to 66 /8s, 46 /16s and 59 /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: 177405 Total RIPE prefixes after maximum aggregation: 86787 RIPE Deaggregation factor: 2.04 Prefixes being announced from the RIPE address blocks: 173276 Unique aggregates announced from the RIPE address blocks: 104518 RIPE Region origin ASes present in the Internet Routing Table: 24384 RIPE Prefixes per ASN: 7.11 RIPE Region origin ASes announcing only one prefix: 11191 RIPE Region transit ASes present in the Internet Routing Table: 3453 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 32 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6180 Number of RIPE addresses announced to Internet: 713021312 Equivalent to 42 /8s, 127 /16s and 215 /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: 85235 Total LACNIC prefixes after maximum aggregation: 19020 LACNIC Deaggregation factor: 4.48 Prefixes being announced from the LACNIC address blocks: 86510 Unique aggregates announced from the LACNIC address blocks: 39729 LACNIC Region origin ASes present in the Internet Routing Table: 6377 LACNIC Prefixes per ASN: 13.57 LACNIC Region origin ASes announcing only one prefix: 1767 LACNIC Region transit ASes present in the Internet Routing Table: 1178 Average LACNIC Region AS path length visible: 5.3 Max LACNIC Region AS path length visible: 31 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 3891 Number of LACNIC addresses announced to Internet: 171192544 Equivalent to 10 /8s, 52 /16s and 48 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + 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: 17414 Total AfriNIC prefixes after maximum aggregation: 3848 AfriNIC Deaggregation factor: 4.53 Prefixes being announced from the AfriNIC address blocks: 19307 Unique aggregates announced from the AfriNIC address blocks: 7067 AfriNIC Region origin ASes present in the Internet Routing Table: 1071 AfriNIC Prefixes per ASN: 18.03 AfriNIC Region origin ASes announcing only one prefix: 345 AfriNIC Region transit ASes present in the Internet Routing Table: 212 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 344 Number of AfriNIC addresses announced to Internet: 93524480 Equivalent to 5 /8s, 147 /16s and 18 /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 5404 4192 76 ERX-CERNET-BKB China Education and Rese 7545 3835 406 384 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2968 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4766 2828 11126 752 KIXS-AS-KR Korea Telecom, KR 9829 2758 1499 541 BSNL-NIB National Internet Backbone, IN 9808 2359 8699 32 CMNET-GD Guangdong Mobile Communication 45899 2193 1472 114 VNPT-AS-VN VNPT Corp, VN 9394 2174 4931 27 CTTNET China TieTong Telecommunications 4755 2102 422 221 TATACOMM-AS TATA Communications formerl 7552 1653 1105 70 VIETEL-AS-AP Viettel Corporation, VN 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 3644 2952 158 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 6327 3430 1341 88 SHAW - Shaw Communications Inc., CA 18566 2204 405 109 MEGAPATH5-US - MegaPath Corporation, US 6389 2044 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 20115 2036 2247 430 CHARTER-NET-HKY-NC - Charter Communicat 209 1908 5066 644 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 16509 1842 3963 545 AMAZON-02 - Amazon.com, Inc., US 30036 1835 330 274 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 6983 1686 854 229 ITCDELTA - Earthlink, Inc., US 701 1679 10589 626 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 3387 186 23 ALJAWWALSTC-AS, SA 20940 2964 939 2122 AKAMAI-ASN1, US 8551 2466 377 41 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 34984 2057 332 427 TELLCOM-AS, TR 9121 1882 1691 17 TTNET, TR 12389 1712 1631 664 ROSTELECOM-AS, RU 12479 1701 1051 64 UNI2-AS, ES 13188 1604 100 52 TRIOLAN, UA 6849 1225 355 21 UKRTELNET, UA 8402 1199 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 3564 541 233 Telmex Colombia S.A., CO 8151 3144 3458 584 Uninet S.A. de C.V., MX 11830 2099 370 65 Instituto Costarricense de Electricidad 6503 1565 437 53 Axtel, S.A.B. de C.V., MX 7303 1558 1023 242 Telecom Argentina S.A., AR 6147 1281 377 27 Telefonica del Peru S.A.A., PE 3816 1027 506 95 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 28573 963 2283 184 CLARO S.A., BR 11172 913 126 85 Alestra, S. de R.L. de C.V., MX 18881 898 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 1194 398 48 LINKdotNET-AS, EG 37611 766 91 8 Afrihost, ZA 36903 709 356 136 MT-MPLS, MA 36992 660 1383 31 ETISALAT-MISR, EG 24835 515 850 15 RAYA-AS, EG 29571 421 36 10 CITelecom-AS, CI 37492 410 354 77 ORANGE-, TN 15399 357 35 7 WANANCHI-, KE 8452 318 1730 17 TE-AS TE-AS, EG 23889 311 103 14 MauritiusTelecom, MU 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 5404 4192 76 ERX-CERNET-BKB China Education and Rese 7545 3835 406 384 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3644 2952 158 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3564 541 233 Telmex Colombia S.A., CO 6327 3430 1341 88 SHAW - Shaw Communications Inc., CA 39891 3387 186 23 ALJAWWALSTC-AS, SA 8151 3144 3458 584 Uninet S.A. de C.V., MX 17974 2968 902 73 TELKOMNET-AS2-AP PT Telekomunikasi Indo 20940 2964 939 2122 AKAMAI-ASN1, US 4766 2828 11126 752 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 3644 3486 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7545 3835 3451 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3387 3364 ALJAWWALSTC-AS, SA 6327 3430 3342 SHAW - Shaw Communications Inc., CA 10620 3564 3331 Telmex Colombia S.A., CO 17974 2968 2895 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 8151 3144 2560 Uninet S.A. de C.V., MX 8551 2466 2425 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 9808 2359 2327 CMNET-GD Guangdong Mobile Communication Co.Ltd. 9829 2758 2217 BSNL-NIB National Internet Backbone, IN 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 64525 PRIVATE 45.119.143.0/24 133275 GIGANTIC-AS Gigantic Infotel P 64525 PRIVATE 45.125.62.0/24 133275 GIGANTIC-AS Gigantic Infotel P 65530 PRIVATE 45.249.40.0/24 133720 SOFTCALLCOC-AS SOFT CALL CUST- 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 65534 PRIVATE 58.68.109.0/24 10201 DWL-AS-IN Dishnet Wireless Lim 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW 290012147 UNALLOCATED 63.65.43.0/24 7046 RFC2270-UUNET-CUSTOMER - MCI C 65538 DOCUMENT 64.27.253.0/24 1273 CW Vodafone Group PLC, GB 65099 PRIVATE 95.173.150.0/24 43797 RSNET2-AS RSNET2, RU 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 23.128.126.0/23 62878 XLITT - Xlitt, US 27.100.7.0/24 56096 UNKNOWN 41.78.12.0/23 62878 XLITT - Xlitt, US 41.78.180.0/23 37265 -Reserved AS-, ZZ 41.242.132.0/23 62878 XLITT - Xlitt, US 43.228.144.0/22 9829 BSNL-NIB National Internet Backbone, IN 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:106 /12:283 /13:551 /14:1048 /15:1871 /16:13440 /17:7746 /18:13662 /19:25198 /20:39200 /21:42516 /22:79908 /23:65175 /24:370247 /25:891 /26:662 /27:693 /28:37 /29:38 /30:216 /31:2 /32:27 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3226 3430 SHAW - Shaw Communications Inc., CA 39891 2946 3387 ALJAWWALSTC-AS, SA 22773 2842 3644 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2088 2204 MEGAPATH5-US - MegaPath Corporation, US 8551 1931 2466 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 1613 1835 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1518 3564 Telmex Colombia S.A., CO 11830 1489 2099 Instituto Costarricense de Electricidad y Telec 11492 1418 1596 CABLEONE - CABLE ONE, INC., US 6389 1355 2044 BELLSOUTH-NET-BLK - BellSouth.net Inc., US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1529 2:834 4:18 5:2457 6:31 7:1 8:1069 12:1860 13:154 14:1675 15:28 16:2 17:170 18:90 20:60 23:2438 24:1928 25:2 27:2367 29:1 31:1922 32:90 33:20 35:21 36:396 37:2355 38:1385 39:69 40:98 41:3047 42:404 43:1960 44:81 45:3081 46:2784 47:171 49:1244 50:1008 51:19 52:821 54:364 55:2 56:4 57:43 58:1556 59:982 60:323 61:2002 62:1710 63:1905 64:4686 65:2210 66:4549 67:2276 68:1225 69:3372 70:1167 71:603 72:2147 74:2707 75:400 76:422 77:1487 78:1532 79:1897 80:1399 81:1404 82:1015 83:723 84:965 85:1869 86:468 87:1197 88:794 89:2191 90:170 91:6240 92:1009 93:2386 94:2364 95:2689 96:640 97:350 98:994 99:98 100:153 101:1440 102:1 103:15840 104:3059 105:189 106:560 107:1753 108:826 109:2917 110:1473 111:1752 112:1254 113:1324 114:1072 115:1590 116:1646 117:1769 118:1982 119:1637 120:734 121:1071 122:2431 123:1871 124:1481 125:1799 128:909 129:673 130:434 131:1473 132:593 133:194 134:699 135:225 136:451 137:469 138:1954 139:515 140:380 141:653 142:745 143:910 144:791 145:184 146:1112 147:698 148:1492 149:586 150:700 151:990 152:736 153:300 154:890 155:758 156:679 157:684 158:484 159:1561 160:763 161:748 162:2515 163:507 164:975 165:1430 166:382 167:1296 168:3030 169:835 170:3549 171:368 172:1017 173:1997 174:784 175:778 176:1890 177:3946 178:2578 179:1149 180:2215 181:2046 182:2439 183:758 184:872 185:10751 186:3292 187:2146 188:2578 189:1832 190:8366 191:1361 192:9647 193:5806 194:4732 195:3933 196:2129 197:1321 198:5521 199:5889 200:7577 201:4381 202:10355 203:9920 204:4508 205:2836 206:3074 207:3169 208:3964 209:4027 210:3949 211:2138 212:2876 213:2557 214:845 215:66 216:5856 217:2129 218:915 219:605 220:1676 221:929 222:741 223:1211 End of report

1 0

Can you help on a survey on network testing?
by Yifei Yuan 15 Sep '17

15 Sep '17

Dear Folks, My name is Yifei Yuan, and I am a researcher at Carnegie Mellon University. I am working on a research project related to testing network configurations, where I want to survey the problems that are encountered when conducting testing on networks. I would very much appreciate it, if you could participate this survey, which can be found in the following link: http://cmu.ca1.qualtrics.com/jfe/form/SV_bvE1oBeO9NI5r5X The survey is anonymous, and it would take no more than 5 mins to finish up all questions. Your participation is voluntary with no compensation, and you must be at least 18 years of age to complete the survey. Thanks, Yifei Yuan Postdoctoral researcher ECE, CMU

1 0

Operational message: DNS root zone KSK rollover to occur on October 11, 2017 at 1600 UTC
by Matt Larson 15 Sep '17

15 Sep '17

The root zone management partners, ICANN and Verisign, are working together to change the DNS root zone's key-signing key (KSK). This process is referred to as "rolling" the root zone KSK. The root zone's apex DNSKEY RRset has been signed with the same KSK, known as KSK-2010, since the root zone was first signed in July, 2010. On October 11, 2017, at approximately 1600 UTC, the root zone will be published with the apex DNSKEY RRset signed for the first time with a new KSK, known as KSK-2017. The root zone apex DNSKEY RRset will be signed with only KSK-2017 going forward. While the specific date of the KSK rollover, October 11, 2017, had been announced previously, the time of 1600 UTC on that day has not been announced until now, which is the primary purpose of this message. The public portion of the root zone KSK is configured as a trust anchor in software performing DNSSEC validation. The configuration of any software performing DNSSEC validation will need to be updated to reference KSK-2017 on or before October 11, 2017, or all DNS responses received by that software will fail DNSSEC validation, resulting ultimately in error messages to end users. In many cases, software performing DNSSEC validation supports "Automated Updates of DNS Security", the protocol defined in RFC 5011 that can automatically update a DNSSEC validator's trust anchor configuration. If the software does not support this protocol, or it is incorrectly implemented or not configured correctly, the trust anchor will need to be updated manually. Anyone operating software performing DNSSEC validation with the root zone KSK configured as a trust anchor must take action on or before October 11, 2017, to confirm that their software is configured with KSK-2017 as a trust anchor and, if not, take the necessary steps to update the configuration. Further information about the root KSK rollover, including information about how to check and update the trust anchor configuration of popular recursive resolver implementations that support DNSSEC validation, is available at https://icann.org/kskroll. For the root zone management partners, Matt Larson VP of Research, ICANN Duane Wessels Distinguished Engineer, Verisign

1 0